sensors Mode-S transponder
A1A0C4
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N2039J · AIRBUS A-321neo · operated by JETBLUE AIRWAYS CORP
- Hex
- A1A0C4
- Octal
- 50320304
- Decimal
- 10,592,452
- Country
- US
- Tail
- N2039J
- Type
- A21N
- Flights observed
- 221
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address A1A0C4 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 | - | 12 | 2026-07-06 |
| JBU528 | - | 10 | 2026-07-07 |
| JBU939 | JetBlue Airways | 8 | 2026-04-28 |
| JBU1682 | - | 8 | 2026-07-09 |
| JBU610 | - | 7 | 2026-07-04 |
| JBU509 | JetBlue Airways | 7 | 2026-05-15 |
| JBU965 | JetBlue Airways | 6 | 2026-05-08 |
| JBU561 | JetBlue Airways | 6 | 2026-04-20 |
| JBU1329 | JetBlue Airways | 6 | 2026-05-11 |
| JBU1255 | - | 6 | 2026-07-07 |
| JBU938 | JetBlue Airways | 5 | 2026-04-16 |
| JBU1383 | JetBlue Airways | 5 | 2026-05-10 |
| JBU887 | - | 4 | 2026-07-13 |
| JBU466 | - | 4 | 2026-07-11 |
| JBU2709 | JetBlue Airways | 4 | 2026-05-07 |
| JBU1533 | JetBlue Airways | 4 | 2026-06-10 |
| JBU966 | JetBlue Airways | 3 | 2026-05-18 |
| JBU710 | JetBlue Airways | 3 | 2026-05-27 |
| JBU2223 | JetBlue Airways | 3 | 2026-05-14 |
| JBU2210 | JetBlue Airways | 3 | 2026-05-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU1770 | GYE → JFK | Jul 14, 12:12 UTC | Jul 15, 00:05 UTC | 11h 53m |
| 2026-07-14 | JBU1769 | JFK → JFK | Jul 14, 03:25 UTC | Jul 14, 18:20 UTC | 14h 55m |
| 2026-07-13 | JBU887 | JFK → SXM | Jul 13, 14:00 UTC | Jul 14, 07:10 UTC | 17h 11m |
| 2026-07-13 | JBU310 | SDQ → JFK | Jul 13, 08:16 UTC | Jul 14, 07:00 UTC | 22h 45m |
| 2026-07-13 | JBU709 | JFK → SDQ | Jul 13, 01:56 UTC | Jul 13, 22:45 UTC | 20h 50m |
| 2026-07-12 | JBU361 | JFK → BGI | Jul 12, 12:21 UTC | Jul 13, 11:00 UTC | 22h 40m |
| 2026-07-11 | JBU466 | GEO → JFK | Jul 11, 22:07 UTC | Jul 12, 19:40 UTC | 21h 34m |
| 2026-07-11 | JBU466 | JFK → JFK | Jul 11, 15:20 UTC | Jul 12, 03:20 UTC | 12h 0m |
| 2026-07-10 | JBU280 | MBJ → JFK | Jul 10, 19:35 UTC | Jul 11, 18:45 UTC | 23h 11m |
| 2026-07-10 | JBU279 | JFK → JFK | Jul 10, 14:25 UTC | Jul 10, 23:00 UTC | 8h 36m |
| 2026-07-09 | JBU1682 | - | Jul 9, 18:45 UTC | Jul 9, 22:35 UTC | 3h 50m |
| 2026-07-09 | JBU1682 | - | Jul 9, 18:00 UTC | Jul 9, 18:10 UTC | 10m |
| 2026-07-09 | JBU1682 | UVF → JFK | Jul 9, 17:55 UTC | Jul 10, 16:50 UTC | 22h 55m |
| 2026-07-09 | JBU1681 | - | Jul 9, 12:15 UTC | Jul 9, 15:45 UTC | 3h 30m |
| 2026-07-08 | JBU1691 | JFK → LIR | Jul 8, 13:16 UTC | Jul 9, 13:00 UTC | 23h 45m |
| 2026-07-07 | JBU528 | GYE → JFK | Jul 7, 22:40 UTC | Jul 8, 21:00 UTC | 22h 21m |
| 2026-07-07 | JBU528 | GYE → JFK | Jul 7, 22:40 UTC | Jul 8, 21:00 UTC | 22h 21m |
| 2026-07-07 | JBU1255 | - | Jul 7, 15:45 UTC | Jul 7, 17:35 UTC | 1h 50m |
| 2026-07-06 | JBU505 | JFK → FLL | Jul 6, 09:55 UTC | Jul 6, 21:50 UTC | 11h 55m |
| 2026-07-05 | JBU465 | JFK → JFK | Jul 5, 16:45 UTC | Jul 6, 05:00 UTC | 12h 15m |
| 2026-07-04 | JBU1668 | PUJ → JFK | Jul 4, 21:55 UTC | Jul 5, 17:25 UTC | 19h 31m |
| 2026-07-04 | JBU1669 | JFK → PUJ | Jul 4, 16:50 UTC | Jul 5, 13:50 UTC | 21h 1m |
| 2026-07-04 | JBU610 | SDQ → JFK | Jul 4, 09:45 UTC | Jul 5, 05:50 UTC | 20h 5m |
| 2026-07-04 | JBU309 | JFK → SDQ | Jul 4, 01:58 UTC | Jul 5, 01:00 UTC | 23h 2m |
| 2026-07-04 | JBU309 | - | Jul 4, 02:00 UTC | Jul 4, 02:45 UTC | 45m |
| 2026-07-03 | JBU1682 | - | Jul 3, 18:05 UTC | Jul 3, 22:25 UTC | 4h 20m |
| 2026-07-03 | JBU1681 | - | Jul 3, 12:05 UTC | Jul 3, 15:55 UTC | 3h 50m |
| 2026-07-02 | JBU1682 | UVF → JFK | Jul 2, 18:09 UTC | Jul 3, 15:55 UTC | 21h 46m |
| 2026-07-02 | JBU1682 | JFK → JFK | Jul 2, 12:10 UTC | Jul 2, 22:30 UTC | 10h 20m |
| 2026-07-01 | JBU350 | JFK → JFK | Jul 1, 14:00 UTC | Jul 2, 00:35 UTC | 10h 35m |
| 2026-06-30 | JBU1255 | - | Jun 30, 15:25 UTC | Jun 30, 17:15 UTC | 1h 50m |
| 2026-06-30 | JBU1255 | FLL → GYE | Jun 30, 15:21 UTC | Jul 1, 14:30 UTC | 23h 10m |
| 2026-06-30 | JBU2269 | - | Jun 30, 04:50 UTC | Jun 30, 07:35 UTC | 2h 45m |
| 2026-06-30 | JBU2269 | BOS → BOS | Jun 30, 03:55 UTC | Jun 30, 04:00 UTC | 5m |
| 2026-06-29 | JBU70 | - | Jun 29, 23:39 UTC | Jun 30, 02:20 UTC | 2h 41m |
| 2026-06-29 | JBU505 | - | Jun 29, 09:54 UTC | Jun 29, 21:30 UTC | 11h 35m |
| 2026-06-28 | JBU466 | JFK → JFK | Jun 28, 15:34 UTC | Jun 29, 03:20 UTC | 11h 45m |
| 2026-06-27 | JBU2018 | JFK → JFK | Jun 27, 12:50 UTC | Jun 28, 00:25 UTC | 11h 35m |
| 2026-06-26 | JBU1966 | JFK → JFK | Jun 26, 21:15 UTC | Jun 27, 09:19 UTC | 12h 5m |
| 2026-06-26 | JBU1769 | JFK → GYE | Jun 26, 03:42 UTC | Jun 27, 01:49 UTC | 22h 8m |
| 2026-06-25 | JBU1188 | SXM → JFK | Jun 25, 19:31 UTC | Jun 26, 18:29 UTC | 22h 59m |
| 2026-06-25 | JBU887 | - | Jun 25, 13:45 UTC | Jun 25, 17:30 UTC | 3h 45m |
| 2026-06-25 | JBU887 | JFK → SXM | Jun 25, 13:40 UTC | Jun 26, 07:24 UTC | 17h 45m |
| 2026-06-24 | JBU466 | JFK → JFK | Jun 24, 15:14 UTC | Jun 25, 03:15 UTC | 12h 0m |
| 2026-06-23 | JBU1668 | PUJ → JFK | Jun 23, 20:50 UTC | Jun 24, 18:34 UTC | 21h 45m |
| 2026-06-23 | JBU1669 | JFK → JFK | Jun 23, 15:44 UTC | Jun 24, 00:09 UTC | 8h 25m |
| 2026-06-22 | JBU610 | JFK → JFK | Jun 22, 23:24 UTC | Jun 23, 13:19 UTC | 13h 55m |
| 2026-06-22 | JBU787 | JFK → SXM | Jun 22, 10:19 UTC | Jun 23, 00:04 UTC | 13h 46m |
| 2026-06-21 | JBU528 | GYE → JFK | Jun 21, 21:34 UTC | Jun 22, 19:24 UTC | 21h 51m |
| 2026-06-21 | JBU1594 | STI → EWR | Jun 21, 13:29 UTC | Jun 22, 11:00 UTC | 21h 31m |
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 N2039J page for operator, model, and routing details .