sensors Mode-S transponder
A1A0A1
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N2038J · AIRBUS A-321neo · operated by JETBLUE AIRWAYS CORP
- Hex
- A1A0A1
- Octal
- 50320241
- Decimal
- 10,592,417
- Country
- US
- Tail
- N2038J
- Type
- A21N
- Flights observed
- 121
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 10h ago
Current position
Country allocation
The ICAO 24-bit address A1A0A1 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 |
|---|---|---|---|
| JBU1328 | JetBlue Airways | 7 | 2026-04-24 |
| JBU596 | JetBlue Airways | 6 | 2026-04-25 |
| JBU528 | - | 5 | 2026-07-12 |
| JBU1188 | - | 5 | 2026-06-29 |
| JBU505 | - | 4 | 2026-07-11 |
| JBU380 | - | 3 | 2026-07-06 |
| JBU309 | - | 3 | 2026-07-08 |
| JBU1965 | - | 3 | 2026-06-22 |
| JBU1817 | JetBlue Airways | 3 | 2026-04-23 |
| JBU1383 | JetBlue Airways | 3 | 2026-04-24 |
| JBU1329 | JetBlue Airways | 3 | 2026-04-25 |
| JBU1256 | - | 3 | 2026-07-11 |
| JBU965 | JetBlue Airways | 2 | 2026-04-19 |
| JBU939 | JetBlue Airways | 2 | 2026-04-20 |
| JBU8642 | - | 2 | 2026-06-19 |
| JBU8529 | JetBlue Airways | 2 | 2026-04-27 |
| JBU8521 | JetBlue Airways | 2 | 2026-04-28 |
| JBU788 | - | 2 | 2026-07-04 |
| JBU610 | - | 2 | 2026-07-07 |
| JBU597 | JetBlue Airways | 2 | 2026-04-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU58 | - | Jul 13, 21:20 UTC | Jul 14, 00:35 UTC | 3h 15m |
| 2026-07-13 | JBU58 | - | Jul 13, 20:20 UTC | Jul 13, 20:35 UTC | 15m |
| 2026-07-13 | JBU57 | - | Jul 13, 18:10 UTC | Jul 13, 18:25 UTC | 15m |
| 2026-07-13 | JBU57 | - | Jul 13, 14:15 UTC | Jul 13, 17:30 UTC | 3h 15m |
| 2026-07-13 | JBU604 | - | Jul 13, 06:45 UTC | Jul 13, 11:35 UTC | 4h 50m |
| 2026-07-12 | JBU528 | GYE → JFK | Jul 12, 14:40 UTC | Jul 13, 14:15 UTC | 23h 36m |
| 2026-07-11 | JBU1256 | GYE → FLL | Jul 11, 18:35 UTC | Jul 12, 17:05 UTC | 22h 31m |
| 2026-07-11 | JBU505 | - | Jul 11, 11:00 UTC | Jul 11, 14:35 UTC | 3h 35m |
| 2026-07-11 | JBU505 | JFK → GYE | Jul 11, 10:59 UTC | Jul 12, 03:30 UTC | 16h 32m |
| 2026-07-10 | JBU168 | - | Jul 10, 19:20 UTC | Jul 10, 20:15 UTC | 55m |
| 2026-07-10 | JBU169 | - | Jul 10, 12:05 UTC | Jul 10, 12:45 UTC | 40m |
| 2026-07-09 | JBU2662 | - | Jul 9, 22:15 UTC | Jul 10, 02:40 UTC | 4h 25m |
| 2026-07-09 | JBU2661 | - | Jul 9, 16:10 UTC | Jul 9, 20:30 UTC | 4h 20m |
| 2026-07-08 | JBU309 | JFK → SDQ | Jul 8, 23:23 UTC | Jul 9, 22:15 UTC | 22h 53m |
| 2026-07-08 | JBU309 | - | Jul 8, 23:25 UTC | Jul 9, 00:00 UTC | 35m |
| 2026-07-08 | JBU780 | JFK → JFK | Jul 8, 12:15 UTC | Jul 8, 20:35 UTC | 8h 20m |
| 2026-07-07 | JBU465 | JFK → GEO | Jul 7, 16:05 UTC | Jul 8, 14:15 UTC | 22h 11m |
| 2026-07-07 | JBU610 | SDQ → JFK | Jul 7, 10:30 UTC | Jul 8, 03:55 UTC | 17h 26m |
| 2026-07-06 | JBU309 | JFK → SDQ | Jul 6, 22:56 UTC | Jul 7, 20:45 UTC | 21h 50m |
| 2026-07-06 | JBU380 | MBJ → JFK | Jul 6, 15:56 UTC | Jul 7, 14:05 UTC | 22h 10m |
| 2026-07-06 | JBU380 | JFK → JFK | Jul 6, 10:45 UTC | Jul 6, 19:15 UTC | 8h 30m |
| 2026-07-05 | JBU1936 | STI → JFK | Jul 5, 05:44 UTC | Jul 5, 23:30 UTC | 17h 46m |
| 2026-07-04 | JBU788 | - | Jul 4, 16:00 UTC | Jul 4, 19:25 UTC | 3h 25m |
| 2026-07-04 | JBU788 | SXM → JFK | Jul 4, 15:39 UTC | Jul 5, 13:15 UTC | 21h 36m |
| 2026-07-03 | JBU2018 | POS → JFK | Jul 3, 19:06 UTC | Jul 4, 16:15 UTC | 21h 10m |
| 2026-07-03 | JBU117 | JFK → POS | Jul 3, 12:54 UTC | Jul 4, 11:30 UTC | 22h 36m |
| 2026-07-03 | JBU117 | - | Jul 3, 12:55 UTC | Jul 3, 17:05 UTC | 4h 10m |
| 2026-07-02 | JBU1966 | JFK → JFK | Jul 2, 21:25 UTC | Jul 3, 09:20 UTC | 11h 55m |
| 2026-07-02 | JBU1770 | GYE → JFK | Jul 2, 12:09 UTC | Jul 3, 09:25 UTC | 21h 16m |
| 2026-07-02 | JBU1769 | JFK → GYE | Jul 2, 03:38 UTC | Jul 3, 02:10 UTC | 22h 32m |
| 2026-07-01 | JBU1533 | JFK → CTG | Jul 1, 13:45 UTC | Jul 1, 16:15 UTC | 2h 30m |
| 2026-07-01 | JBU1533 | JFK → CTG | Jul 1, 13:43 UTC | Jul 2, 07:30 UTC | 17h 47m |
| 2026-06-30 | JBU2661 | JFK → JFK | Jun 30, 15:40 UTC | Jul 1, 01:40 UTC | 10h 0m |
| 2026-06-29 | JBU1188 | - | Jun 29, 19:54 UTC | Jun 29, 23:39 UTC | 3h 45m |
| 2026-06-29 | JBU1188 | SXM → JFK | Jun 29, 19:36 UTC | Jun 30, 16:10 UTC | 20h 35m |
| 2026-06-29 | JBU887 | - | Jun 29, 13:59 UTC | Jun 29, 17:05 UTC | 3h 5m |
| 2026-06-28 | JBU637 | - | Jun 28, 23:14 UTC | Jun 29, 10:24 UTC | 11h 10m |
| 2026-06-28 | JBU1179 | - | Jun 28, 11:09 UTC | Jun 28, 19:40 UTC | 8h 30m |
| 2026-06-27 | JBU1088 | - | Jun 27, 23:34 UTC | Jun 28, 03:05 UTC | 3h 30m |
| 2026-06-27 | JBU1087 | - | Jun 27, 18:20 UTC | Jun 27, 21:40 UTC | 3h 20m |
| 2026-06-27 | JBU384 | MCO → JFK | Jun 27, 14:09 UTC | Jun 27, 16:14 UTC | 2h 5m |
| 2026-06-27 | JBU883 | JFK → MCO | Jun 27, 09:29 UTC | Jun 27, 11:35 UTC | 2h 5m |
| 2026-06-26 | JBU130 | RSW → JFK | Jun 26, 10:15 UTC | Jun 26, 12:34 UTC | 2h 20m |
| 2026-06-26 | JBU130 | RSW → JFK | Jun 26, 10:11 UTC | Jun 27, 04:19 UTC | 18h 9m |
| 2026-06-26 | JBU2129 | - | Jun 26, 02:00 UTC | Jun 26, 04:24 UTC | 2h 25m |
| 2026-06-25 | JBU1681 | JFK → JFK | Jun 25, 12:19 UTC | Jun 25, 22:10 UTC | 9h 50m |
| 2026-06-24 | JBU18 | JFK → JFK | Jun 24, 18:05 UTC | Jun 25, 04:35 UTC | 10h 30m |
| 2026-06-23 | JBU1188 | JFK → JFK | Jun 23, 14:04 UTC | Jun 23, 23:00 UTC | 8h 55m |
| 2026-06-22 | JBU1965 | - | Jun 22, 22:10 UTC | Jun 23, 01:25 UTC | 3h 15m |
| 2026-06-22 | JBU1965 | JFK → GEO | Jun 22, 22:09 UTC | Jun 23, 19:44 UTC | 21h 36m |
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 N2038J page for operator, model, and routing details .