sensors Mode-S transponder
AAF183
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N804JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORP
- Hex
- AAF183
- Octal
- 52570603
- Decimal
- 11,202,947
- Country
- US
- Tail
- N804JB
- Type
- A320
- Flights observed
- 285
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address AAF183 falls within the block assigned to United States (US) by ICAO Annex 10, Volume III. Every aircraft registered in United States receives a permanent address from this block at the time of registration; the address stays with the airframe even if the aircraft is re-registered to a different operator within the country.
Callsign history 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| JBU2041 | JetBlue Airways | 5 | 2026-04-18 |
| JBU814 | - | 4 | 2026-06-26 |
| JBU495 | JetBlue Airways | 4 | 2026-04-19 |
| JBU349 | JetBlue Airways | 4 | 2026-05-07 |
| JBU1453 | JetBlue Airways | 4 | 2026-05-24 |
| JBU808 | JetBlue Airways | 3 | 2026-04-15 |
| JBU767 | - | 3 | 2026-06-25 |
| JBU684 | JetBlue Airways | 3 | 2026-05-21 |
| JBU675 | - | 3 | 2026-07-12 |
| JBU499 | - | 3 | 2026-06-14 |
| JBU2984 | - | 3 | 2026-06-21 |
| JBU294 | - | 3 | 2026-07-08 |
| JBU250 | JetBlue Airways | 3 | 2026-04-20 |
| JBU2420 | JetBlue Airways | 3 | 2026-06-13 |
| JBU2219 | - | 3 | 2026-04-13 |
| JBU1877 | - | 3 | 2026-04-14 |
| JBU183 | JetBlue Airways | 3 | 2026-05-10 |
| JBU1142 | - | 3 | 2026-07-13 |
| JBU1047 | JetBlue Airways | 3 | 2026-05-18 |
| JBU994 | JetBlue Airways | 2 | 2026-04-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU1882 | - | Jul 14, 23:40 UTC | Jul 15, 00:45 UTC | 1h 5m |
| 2026-07-14 | JBU2182 | - | Jul 14, 17:10 UTC | Jul 14, 19:45 UTC | 2h 35m |
| 2026-07-14 | JBU813 | - | Jul 14, 13:00 UTC | Jul 14, 15:30 UTC | 2h 30m |
| 2026-07-14 | JBU8362 | JFK → HPN | Jul 14, 11:35 UTC | Jul 14, 11:50 UTC | 15m |
| 2026-07-13 | JBU1142 | - | Jul 13, 14:40 UTC | Jul 14, 11:50 UTC | 21h 11m |
| 2026-07-13 | JBU368 | - | Jul 13, 00:40 UTC | Jul 13, 03:25 UTC | 2h 45m |
| 2026-07-13 | JBU368 | - | Jul 13, 00:38 UTC | Jul 13, 21:50 UTC | 21h 13m |
| 2026-07-12 | JBU675 | JFK → BDL | Jul 12, 04:03 UTC | Jul 13, 02:45 UTC | 22h 43m |
| 2026-07-11 | JBU1793 | JFK → SJO | Jul 11, 13:45 UTC | Jul 12, 12:45 UTC | 23h 1m |
| 2026-07-10 | JBU1568 | - | Jul 10, 19:45 UTC | Jul 10, 20:35 UTC | 50m |
| 2026-07-10 | JBU1568 | PUJ → JFK | Jul 10, 17:23 UTC | Jul 11, 16:20 UTC | 22h 58m |
| 2026-07-08 | JBU294 | - | Jul 8, 23:35 UTC | Jul 9, 00:05 UTC | 30m |
| 2026-07-08 | JBU294 | NAS → FLL | Jul 8, 23:26 UTC | Jul 9, 16:25 UTC | 16h 59m |
| 2026-07-08 | JBU1693 | - | Jul 8, 21:35 UTC | Jul 8, 21:55 UTC | 20m |
| 2026-07-08 | JBU1494 | - | Jul 8, 17:45 UTC | Jul 8, 18:20 UTC | 35m |
| 2026-07-08 | JBU1393 | - | Jul 8, 15:45 UTC | Jul 8, 16:05 UTC | 20m |
| 2026-07-08 | JBU2282 | - | Jul 8, 11:25 UTC | Jul 8, 13:45 UTC | 2h 20m |
| 2026-07-07 | JBU172 | FLL → LGA | Jul 7, 15:02 UTC | Jul 8, 13:45 UTC | 22h 44m |
| 2026-07-07 | JBU1146 | FLL → RIC | Jul 7, 02:41 UTC | Jul 8, 00:20 UTC | 21h 40m |
| 2026-07-07 | JBU294 | - | Jul 7, 00:50 UTC | Jul 7, 01:10 UTC | 20m |
| 2026-07-06 | JBU1693 | - | Jul 6, 22:20 UTC | Jul 6, 22:45 UTC | 25m |
| 2026-07-06 | JBU770 | MCO → RIC | Jul 6, 01:54 UTC | Jul 6, 22:45 UTC | 20h 51m |
| 2026-07-05 | JBU39 | FLL → SJO | Jul 5, 15:39 UTC | Jul 6, 14:20 UTC | 22h 42m |
| 2026-07-05 | JBU1822 | MSY → FLL | Jul 5, 12:15 UTC | Jul 6, 03:25 UTC | 15h 10m |
| 2026-07-05 | JBU2823 | FLL → MSY | Jul 5, 01:02 UTC | Jul 6, 00:30 UTC | 23h 28m |
| 2026-07-04 | JBU2072 | BQN → FLL | Jul 4, 21:37 UTC | Jul 5, 18:05 UTC | 20h 28m |
| 2026-07-04 | JBU2071 | - | Jul 4, 18:30 UTC | Jul 4, 19:00 UTC | 30m |
| 2026-07-04 | JBU2071 | FLL → BQN | Jul 4, 18:29 UTC | Jul 5, 16:15 UTC | 21h 46m |
| 2026-07-04 | JBU1126 | - | Jul 4, 12:15 UTC | Jul 4, 16:25 UTC | 4h 10m |
| 2026-07-03 | JBU1233 | MCO → SJU | Jul 3, 09:30 UTC | Jul 3, 12:00 UTC | 2h 30m |
| 2026-07-03 | JBU1233 | MCO → SJU | Jul 3, 09:28 UTC | Jul 3, 23:25 UTC | 13h 57m |
| 2026-07-03 | JBU334 | - | Jul 3, 04:35 UTC | Jul 3, 05:15 UTC | 40m |
| 2026-07-03 | JBU334 | - | Jul 3, 02:50 UTC | Jul 3, 03:00 UTC | 10m |
| 2026-07-03 | JBU2932 | - | Jul 3, 00:40 UTC | Jul 3, 00:50 UTC | 10m |
| 2026-07-02 | JBU2931 | - | Jul 2, 22:35 UTC | Jul 2, 22:50 UTC | 15m |
| 2026-07-02 | JBU435 | - | Jul 2, 20:10 UTC | Jul 2, 20:30 UTC | 20m |
| 2026-07-02 | JBU1638 | - | Jul 2, 17:05 UTC | Jul 2, 17:15 UTC | 10m |
| 2026-07-01 | JBU1608 | STI → SJU | Jul 1, 21:04 UTC | Jul 2, 20:30 UTC | 23h 26m |
| 2026-07-01 | JBU193 | EWR → STI | Jul 1, 02:45 UTC | Jul 2, 00:25 UTC | 21h 41m |
| 2026-06-30 | JBU2427 | - | Jun 30, 16:10 UTC | Jun 30, 16:40 UTC | 30m |
| 2026-06-30 | JBU2427 | FLL → MBJ | Jun 30, 16:05 UTC | Jul 1, 14:40 UTC | 22h 36m |
| 2026-06-30 | JBU2005 | - | Jun 30, 11:35 UTC | Jun 30, 13:45 UTC | 2h 10m |
| 2026-06-29 | JBU293 | MCO → SJU | Jun 29, 10:09 UTC | Jun 30, 04:15 UTC | 18h 7m |
| 2026-06-28 | JBU2851 | TPA → SJU | Jun 28, 22:24 UTC | Jun 29, 18:44 UTC | 20h 21m |
| 2026-06-28 | JBU1366 | - | Jun 28, 18:25 UTC | Jun 28, 19:49 UTC | 1h 25m |
| 2026-06-28 | JBU1366 | CUN → TPA | Jun 28, 18:22 UTC | Jun 29, 16:19 UTC | 21h 58m |
| 2026-06-28 | JBU1365 | TPA → CUN | Jun 28, 15:29 UTC | Jun 28, 16:55 UTC | 1h 25m |
| 2026-06-28 | JBU891 | BOS → TPA | Jun 28, 10:39 UTC | Jun 28, 13:19 UTC | 2h 40m |
| 2026-06-27 | JBU322 | - | Jun 27, 11:04 UTC | Jun 27, 13:44 UTC | 2h 40m |
| 2026-06-27 | JBU322 | PBI → BOS | Jun 27, 11:04 UTC | Jun 28, 10:44 UTC | 23h 41m |
About Mode-S
A Mode-S transponder code (also called an "ICAO 24-bit address" or "hex code") is a 6-character hexadecimal identifier permanently assigned to an aircraft when it's first registered. Unlike callsigns (which change with each flight) or registrations (which can change if an aircraft is sold internationally), the Mode-S address stays with the airframe for the life of the aircraft in that country.
Every ADS-B transmission from an aircraft includes its Mode-S address, making it the most reliable way to identify a specific airframe. Flight-tracking services like Apparatus use the Mode-S address as the primary key for tying position broadcasts, callsigns, and ownership records together.
Prefer a tail-number view? See the N804JB page for operator, model, and routing details .