sensors Mode-S transponder
A1A832
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N2059J · AIRBUS A-321neo · operated by JETBLUE AIRWAYS CORP
- Hex
- A1A832
- Octal
- 50324062
- Decimal
- 10,594,354
- Country
- US
- Tail
- N2059J
- Type
- A21N
- Flights observed
- 200
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address A1A832 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 |
|---|---|---|---|
| JBU505 | - | 17 | 2026-06-26 |
| JBU528 | - | 11 | 2026-06-27 |
| JBU1256 | - | 10 | 2026-06-26 |
| JBU1329 | JetBlue Airways | 9 | 2026-05-16 |
| JBU597 | JetBlue Airways | 8 | 2026-05-18 |
| JBU1380 | JetBlue Airways | 7 | 2026-05-18 |
| JBU1255 | JetBlue Airways | 6 | 2026-06-14 |
| JBU966 | JetBlue Airways | 5 | 2026-05-19 |
| JBU361 | JetBlue Airways | 5 | 2026-06-11 |
| JBU117 | - | 5 | 2026-07-05 |
| JBU965 | JetBlue Airways | 4 | 2026-05-19 |
| JBU939 | JetBlue Airways | 4 | 2026-05-06 |
| JBU938 | JetBlue Airways | 4 | 2026-05-06 |
| JBU887 | - | 4 | 2026-07-09 |
| JBU596 | JetBlue Airways | 4 | 2026-05-05 |
| JBU470 | JetBlue Airways | 4 | 2026-05-12 |
| JBU1818 | JetBlue Airways | 4 | 2026-05-03 |
| JBU1383 | JetBlue Airways | 4 | 2026-05-07 |
| JBU1179 | - | 4 | 2026-07-13 |
| JBU788 | - | 3 | 2026-06-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU1179 | JFK → MBJ | Jul 13, 10:44 UTC | Jul 13, 23:15 UTC | 12h 32m |
| 2026-07-13 | JBU1179 | - | Jul 13, 10:45 UTC | Jul 13, 13:25 UTC | 2h 40m |
| 2026-07-12 | JBU1759 | JFK → JFK | Jul 12, 22:50 UTC | Jul 13, 07:10 UTC | 8h 20m |
| 2026-07-12 | JBU1770 | GYE → JFK | Jul 12, 12:13 UTC | Jul 13, 10:30 UTC | 22h 18m |
| 2026-07-12 | JBU1770 | GYE → JFK | Jul 12, 12:13 UTC | Jul 13, 10:30 UTC | 22h 18m |
| 2026-07-11 | JBU1668 | PUJ → JFK | Jul 11, 21:12 UTC | Jul 12, 20:30 UTC | 23h 19m |
| 2026-07-11 | JBU1669 | JFK → JFK | Jul 11, 15:45 UTC | Jul 12, 00:25 UTC | 8h 40m |
| 2026-07-10 | JBU309 | JFK → JFK | Jul 10, 22:35 UTC | Jul 11, 13:20 UTC | 14h 45m |
| 2026-07-10 | JBU1179 | JFK → JFK | Jul 10, 10:45 UTC | Jul 10, 18:50 UTC | 8h 5m |
| 2026-07-09 | JBU1188 | - | Jul 9, 19:55 UTC | Jul 9, 23:35 UTC | 3h 40m |
| 2026-07-09 | JBU887 | - | Jul 9, 14:15 UTC | Jul 9, 17:35 UTC | 3h 20m |
| 2026-07-08 | JBU224 | - | Jul 8, 19:50 UTC | Jul 9, 00:55 UTC | 5h 5m |
| 2026-07-08 | JBU323 | JFK → LAX | Jul 8, 12:45 UTC | Jul 8, 17:55 UTC | 5h 10m |
| 2026-07-07 | JBU883 | JFK → MCO | Jul 7, 10:05 UTC | Jul 8, 03:45 UTC | 17h 40m |
| 2026-07-06 | JBU1692 | LIR → JFK | Jul 6, 20:08 UTC | Jul 7, 18:30 UTC | 22h 23m |
| 2026-07-06 | JBU1691 | JFK → LIR | Jul 6, 13:50 UTC | Jul 7, 00:40 UTC | 10h 50m |
| 2026-07-05 | JBU2018 | - | Jul 5, 19:40 UTC | Jul 6, 00:10 UTC | 4h 30m |
| 2026-07-05 | JBU117 | - | Jul 5, 12:55 UTC | Jul 5, 17:10 UTC | 4h 15m |
| 2026-07-04 | JBU466 | JFK → JFK | Jul 4, 18:30 UTC | Jul 5, 06:15 UTC | 11h 45m |
| 2026-07-04 | JBU2129 | JFK → RSW | Jul 4, 02:21 UTC | Jul 4, 23:05 UTC | 20h 44m |
| 2026-07-04 | JBU2129 | JFK → RSW | Jul 4, 02:25 UTC | Jul 4, 04:55 UTC | 2h 30m |
| 2026-07-03 | JBU36 | JFK → JFK | Jul 3, 14:00 UTC | Jul 3, 22:30 UTC | 8h 30m |
| 2026-07-02 | JBU609 | JFK → JFK | Jul 2, 19:45 UTC | Jul 3, 04:25 UTC | 8h 40m |
| 2026-07-02 | JBU384 | - | Jul 2, 16:00 UTC | Jul 2, 16:05 UTC | 5m |
| 2026-07-02 | JBU384 | - | Jul 2, 14:00 UTC | Jul 2, 15:55 UTC | 1h 55m |
| 2026-07-02 | JBU883 | JFK → MCO | Jul 2, 09:15 UTC | Jul 2, 11:20 UTC | 2h 5m |
| 2026-07-01 | JBU922 | JFK → JFK | Jul 1, 18:50 UTC | Jul 2, 01:05 UTC | 6h 15m |
| 2026-06-30 | JBU2510 | JFK → JFK | Jun 30, 15:05 UTC | Jul 1, 00:35 UTC | 9h 30m |
| 2026-06-29 | JBU466 | GEO → JFK | Jun 29, 22:32 UTC | Jun 30, 15:40 UTC | 17h 9m |
| 2026-06-29 | JBU465 | JFK → JFK | Jun 29, 15:19 UTC | Jun 30, 03:55 UTC | 12h 36m |
| 2026-06-27 | JBU528 | - | Jun 27, 15:49 UTC | Jun 28, 03:14 UTC | 11h 25m |
| 2026-06-26 | JBU1256 | GYE → FLL | Jun 26, 17:32 UTC | Jun 27, 16:14 UTC | 22h 43m |
| 2026-06-26 | JBU505 | - | Jun 26, 09:50 UTC | Jun 26, 21:55 UTC | 12h 5m |
| 2026-06-25 | JBU528 | - | Jun 25, 15:34 UTC | Jun 26, 03:05 UTC | 11h 30m |
| 2026-06-24 | JBU1501 | JFK → FLL | Jun 24, 21:40 UTC | Jun 24, 23:59 UTC | 2h 20m |
| 2026-06-24 | JBU788 | - | Jun 24, 15:29 UTC | Jun 24, 19:00 UTC | 3h 30m |
| 2026-06-24 | JBU787 | - | Jun 24, 10:04 UTC | Jun 24, 13:20 UTC | 3h 15m |
| 2026-06-22 | JBU130 | RSW → JFK | Jun 22, 14:49 UTC | Jun 22, 17:10 UTC | 2h 20m |
| 2026-06-22 | JBU2129 | JFK → RSW | Jun 22, 01:15 UTC | Jun 22, 03:40 UTC | 2h 25m |
| 2026-06-21 | JBU1681 | JFK → JFK | Jun 21, 12:35 UTC | Jun 21, 22:20 UTC | 9h 45m |
| 2026-06-20 | JBU1769 | JFK → GYE | Jun 20, 03:55 UTC | Jun 20, 18:04 UTC | 14h 10m |
| 2026-06-19 | JBU2018 | MIA → BOS | Jun 19, 19:39 UTC | Jun 20, 16:29 UTC | 20h 51m |
| 2026-06-19 | JBU117 | JFK → POS | Jun 19, 13:15 UTC | Jun 20, 07:49 UTC | 18h 35m |
| 2026-06-19 | JBU117 | - | Jun 19, 13:20 UTC | Jun 19, 16:34 UTC | 3h 15m |
| 2026-06-19 | JBU966B | - | Jun 19, 01:10 UTC | Jun 19, 10:50 UTC | 9h 40m |
| 2026-06-18 | JBU1965 | - | Jun 18, 22:25 UTC | Jun 18, 22:50 UTC | 25m |
| 2026-06-18 | JBU1179 | JFK → MBJ | Jun 18, 12:05 UTC | Jun 18, 20:00 UTC | 7h 55m |
| 2026-06-17 | JBU528 | - | Jun 17, 15:35 UTC | Jun 18, 03:35 UTC | 12h 0m |
| 2026-06-16 | JBU1256 | GYE → FLL | Jun 16, 17:44 UTC | Jun 17, 16:05 UTC | 22h 22m |
| 2026-06-16 | JBU1256 | GYE → FLL | Jun 16, 17:44 UTC | Jun 17, 16:05 UTC | 22h 22m |
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 N2059J page for operator, model, and routing details .