sensors Mode-S transponder
AAF53A
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N805JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORP
- Hex
- AAF53A
- Octal
- 52572472
- Decimal
- 11,203,898
- Country
- US
- Tail
- N805JB
- Type
- A320
- Flights observed
- 292
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address AAF53A 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 |
|---|---|---|---|
| JBU1450 | - | 8 | 2026-07-06 |
| JBU605 | JetBlue Airways | 4 | 2026-06-06 |
| JBU438 | JetBlue Airways | 4 | 2026-04-29 |
| JBU154 | - | 4 | 2026-07-02 |
| JBU462 | - | 3 | 2026-06-26 |
| JBU390 | JetBlue Airways | 3 | 2026-05-02 |
| JBU320 | - | 3 | 2026-07-13 |
| JBU2201 | - | 3 | 2026-07-08 |
| JBU2028 | JetBlue Airways | 3 | 2026-06-02 |
| JBU133 | JetBlue Airways | 3 | 2026-05-15 |
| JBU1284 | - | 3 | 2026-07-12 |
| JBU1134 | JetBlue Airways | 3 | 2026-04-18 |
| JBU1078 | JetBlue Airways | 3 | 2026-04-14 |
| JBU1048 | JetBlue Airways | 3 | 2026-05-06 |
| JBU998 | JetBlue Airways | 2 | 2026-04-16 |
| JBU974 | - | 2 | 2026-04-13 |
| JBU968 | JetBlue Airways | 2 | 2026-04-16 |
| JBU882 | - | 2 | 2026-07-10 |
| JBU879 | - | 2 | 2026-04-14 |
| JBU808 | - | 2 | 2026-06-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-15 | JBU2752 | SJU → TPA | Jul 15, 01:46 UTC | Jul 15, 04:30 UTC | 2h 44m |
| 2026-07-14 | JBU1454 | SJU → FLL | Jul 14, 18:22 UTC | Jul 15, 04:30 UTC | 10h 8m |
| 2026-07-14 | JBU225 | JFK → TPA | Jul 14, 10:42 UTC | Jul 15, 04:30 UTC | 17h 48m |
| 2026-07-13 | JBU350 | GND → JFK | Jul 13, 19:57 UTC | Jul 14, 15:10 UTC | 19h 14m |
| 2026-07-13 | JBU320 | ATL → JFK | Jul 13, 10:20 UTC | Jul 14, 00:25 UTC | 14h 6m |
| 2026-07-13 | JBU320 | ATL → JFK | Jul 13, 10:20 UTC | Jul 13, 12:25 UTC | 2h 5m |
| 2026-07-13 | JBU719 | JFK → ATL | Jul 13, 02:40 UTC | Jul 13, 04:25 UTC | 1h 45m |
| 2026-07-12 | JBU1112 | JFK → JFK | Jul 12, 14:01 UTC | Jul 12, 23:50 UTC | 9h 50m |
| 2026-07-12 | JBU1284 | MCO → JFK | Jul 12, 01:16 UTC | Jul 13, 00:01 UTC | 22h 45m |
| 2026-07-11 | JBU906 | ORD → JFK | Jul 11, 14:56 UTC | Jul 12, 14:30 UTC | 23h 35m |
| 2026-07-11 | JBU905 | JFK → ORD | Jul 11, 11:10 UTC | Jul 12, 10:30 UTC | 23h 21m |
| 2026-07-10 | JBU882 | - | Jul 10, 21:35 UTC | Jul 10, 22:05 UTC | 30m |
| 2026-07-10 | JBU882 | UVF → JFK | Jul 10, 20:45 UTC | Jul 11, 20:30 UTC | 23h 46m |
| 2026-07-10 | JBU881 | - | Jul 10, 14:30 UTC | Jul 10, 17:50 UTC | 3h 20m |
| 2026-07-09 | JBU508 | JFK → PWM | Jul 9, 16:37 UTC | Jul 10, 15:10 UTC | 22h 33m |
| 2026-07-09 | JBU508 | - | Jul 9, 16:40 UTC | Jul 9, 17:25 UTC | 45m |
| 2026-07-09 | JBU1002 | - | Jul 9, 12:50 UTC | Jul 9, 15:10 UTC | 2h 20m |
| 2026-07-08 | JBU2201 | JFK → FLL | Jul 8, 16:30 UTC | Jul 9, 14:30 UTC | 22h 1m |
| 2026-07-08 | JBU491 | BUF → LAX | Jul 8, 00:38 UTC | Jul 9, 00:25 UTC | 23h 47m |
| 2026-07-07 | JBU1160 | PHL → BOS | Jul 7, 12:50 UTC | Jul 8, 11:30 UTC | 22h 41m |
| 2026-07-07 | JBU1159 | BOS → PHL | Jul 7, 10:21 UTC | Jul 8, 08:30 UTC | 22h 10m |
| 2026-07-06 | JBU1450 | - | Jul 6, 14:45 UTC | Jul 6, 15:15 UTC | 30m |
| 2026-07-06 | JBU1450 | STI → FLL | Jul 6, 13:26 UTC | Jul 7, 12:00 UTC | 22h 35m |
| 2026-07-06 | JBU1449 | - | Jul 6, 10:20 UTC | Jul 6, 10:50 UTC | 30m |
| 2026-07-06 | JBU725 | - | Jul 6, 01:05 UTC | Jul 6, 02:40 UTC | 1h 35m |
| 2026-07-05 | JBU726 | - | Jul 5, 22:00 UTC | Jul 5, 23:35 UTC | 1h 35m |
| 2026-07-05 | JBU1245 | - | Jul 5, 17:10 UTC | Jul 5, 19:05 UTC | 1h 55m |
| 2026-07-05 | JBU1246 | - | Jul 5, 13:55 UTC | Jul 5, 15:45 UTC | 1h 50m |
| 2026-07-04 | JBU754 | SJU → FLL | Jul 4, 09:28 UTC | Jul 4, 22:30 UTC | 13h 2m |
| 2026-07-03 | JBU1501 | JFK → FLL | Jul 3, 22:18 UTC | Jul 4, 20:20 UTC | 22h 3m |
| 2026-07-03 | JBU302 | FLL → JFK | Jul 3, 10:42 UTC | Jul 4, 09:45 UTC | 23h 3m |
| 2026-07-02 | JBU730 | MCO → BQN | Jul 2, 18:35 UTC | Jul 3, 15:45 UTC | 21h 11m |
| 2026-07-02 | JBU499 | LGA → MCO | Jul 2, 14:49 UTC | Jul 3, 13:05 UTC | 22h 17m |
| 2026-07-02 | JBU1072 | - | Jul 2, 10:15 UTC | Jul 2, 12:40 UTC | 2h 25m |
| 2026-07-02 | JBU1072 | FLL → LGA | Jul 2, 10:14 UTC | Jul 3, 08:10 UTC | 21h 56m |
| 2026-07-02 | JBU154 | - | Jul 2, 00:20 UTC | Jul 2, 02:40 UTC | 2h 20m |
| 2026-07-01 | JBU1704 | - | Jul 1, 22:35 UTC | Jul 1, 22:50 UTC | 15m |
| 2026-07-01 | JBU41 | - | Jul 1, 15:55 UTC | Jul 1, 21:45 UTC | 5h 50m |
| 2026-07-01 | JBU1471 | LGA → FLL | Jul 1, 11:50 UTC | Jul 1, 14:15 UTC | 2h 25m |
| 2026-06-30 | JBU598 | MCO → LGA | Jun 30, 20:40 UTC | Jun 30, 22:50 UTC | 2h 10m |
| 2026-06-30 | JBU383 | JFK → MCO | Jun 30, 14:50 UTC | Jun 30, 17:05 UTC | 2h 15m |
| 2026-06-30 | JBU130 | RSW → JFK | Jun 30, 10:10 UTC | Jun 30, 12:35 UTC | 2h 25m |
| 2026-06-30 | JBU2129 | JFK → RSW | Jun 30, 01:35 UTC | Jun 30, 04:00 UTC | 2h 25m |
| 2026-06-29 | JBU1682 | SLU → JFK | Jun 29, 18:10 UTC | Jun 29, 22:30 UTC | 4h 20m |
| 2026-06-28 | JBU1640 | SVD → JFK | Jun 28, 19:53 UTC | Jun 29, 18:19 UTC | 22h 27m |
| 2026-06-28 | JBU320 | ATL → JFK | Jun 28, 10:26 UTC | Jun 29, 00:20 UTC | 13h 54m |
| 2026-06-27 | JBU513 | - | Jun 27, 20:59 UTC | Jun 28, 00:00 UTC | 3h 0m |
| 2026-06-27 | JBU513 | ISP → FLL | Jun 27, 20:54 UTC | Jun 28, 20:09 UTC | 23h 16m |
| 2026-06-27 | JBU514 | - | Jun 27, 16:59 UTC | Jun 27, 19:34 UTC | 2h 35m |
| 2026-06-26 | JBU2632 | STX → SJU | Jun 26, 20:34 UTC | Jun 27, 19:34 UTC | 23h 1m |
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 N805JB page for operator, model, and routing details .