sensors Mode-S transponder
A4C9D5
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N4076J · AIRBUS A-321neo · operated by JETBLUE AIRWAYS CORP
- Hex
- A4C9D5
- Octal
- 51144725
- Decimal
- 10,799,573
- Country
- US
- Tail
- N4076J
- Type
- A21N
- Flights observed
- 209
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address A4C9D5 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 |
|---|---|---|---|
| JBU32 | - | 21 | 2026-07-13 |
| JBU31 | - | 20 | 2026-07-13 |
| JBU346 | - | 13 | 2026-07-04 |
| JBU1407 | JetBlue Airways | 13 | 2026-06-26 |
| JBU1107 | JetBlue Airways | 13 | 2026-06-24 |
| JBU345 | - | 12 | 2026-07-04 |
| JBU33 | - | 12 | 2026-06-22 |
| JBU1408 | JetBlue Airways | 12 | 2026-06-22 |
| JBU2261 | - | 11 | 2026-07-09 |
| JBU2220 | JetBlue Airways | 11 | 2026-06-25 |
| JBU34 | JetBlue Airways | 10 | 2026-06-12 |
| JBU1621 | - | 10 | 2026-07-12 |
| JBU7 | - | 8 | 2026-06-23 |
| JBU331 | JetBlue Airways | 8 | 2026-07-06 |
| JBU1620 | - | 8 | 2026-07-11 |
| JBU2260 | - | 7 | 2026-07-02 |
| JBU332 | - | 5 | 2026-07-07 |
| JBU20 | JetBlue Airways | 5 | 2026-06-23 |
| JBU523 | JetBlue Airways | 2 | 2026-05-07 |
| JBU2223 | JetBlue Airways | 2 | 2026-04-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU32 | - | Jul 13, 09:35 UTC | Jul 13, 16:30 UTC | 6h 55m |
| 2026-07-13 | JBU32 | AMS → BOS | Jul 13, 09:32 UTC | Jul 14, 05:15 UTC | 19h 44m |
| 2026-07-13 | JBU31 | BNH → AMS | Jul 13, 00:25 UTC | Jul 13, 07:01 UTC | 6h 35m |
| 2026-07-12 | JBU1621 | LHR → BOS | Jul 12, 07:55 UTC | Jul 12, 14:45 UTC | 6h 50m |
| 2026-07-11 | JBU1620 | - | Jul 11, 23:25 UTC | Jul 12, 05:35 UTC | 6h 10m |
| 2026-07-11 | JBU32 | - | Jul 11, 09:40 UTC | Jul 11, 17:05 UTC | 7h 25m |
| 2026-07-11 | JBU31 | BOS → AMS | Jul 11, 00:35 UTC | Jul 11, 07:05 UTC | 6h 30m |
| 2026-07-09 | JBU1620 | BOS → LHR | Jul 9, 23:09 UTC | Jul 10, 15:30 UTC | 16h 21m |
| 2026-07-09 | JBU2261 | - | Jul 9, 03:00 UTC | Jul 9, 04:25 UTC | 1h 25m |
| 2026-07-09 | JBU2261 | BOS → MAD | Jul 9, 02:57 UTC | Jul 10, 00:25 UTC | 21h 28m |
| 2026-07-08 | JBU32 | - | Jul 8, 10:50 UTC | Jul 8, 18:05 UTC | 7h 15m |
| 2026-07-08 | JBU31 | - | Jul 8, 01:10 UTC | Jul 8, 07:55 UTC | 6h 45m |
| 2026-07-07 | JBU332 | MXP → BOS | Jul 7, 08:57 UTC | Jul 8, 07:15 UTC | 22h 19m |
| 2026-07-06 | JBU331 | BDL → MCO | Jul 6, 22:30 UTC | Jul 7, 17:50 UTC | 19h 21m |
| 2026-07-06 | JBU32 | AMS → BOS | Jul 6, 10:51 UTC | Jul 7, 09:15 UTC | 22h 25m |
| 2026-07-06 | JBU32 | - | Jul 6, 10:55 UTC | Jul 6, 11:15 UTC | 20m |
| 2026-07-06 | JBU31 | - | Jul 6, 02:20 UTC | Jul 6, 08:20 UTC | 6h 0m |
| 2026-07-04 | JBU331 | BDL → MCO | Jul 4, 22:32 UTC | Jul 5, 17:05 UTC | 18h 34m |
| 2026-07-04 | JBU346 | BCN → BOS | Jul 4, 11:16 UTC | Jul 5, 09:15 UTC | 21h 59m |
| 2026-07-04 | JBU346 | - | Jul 4, 11:20 UTC | Jul 4, 13:00 UTC | 1h 40m |
| 2026-07-04 | JBU345 | - | Jul 4, 00:40 UTC | Jul 4, 07:35 UTC | 6h 55m |
| 2026-07-03 | JBU32 | AMS → BOS | Jul 3, 09:44 UTC | Jul 4, 08:15 UTC | 22h 32m |
| 2026-07-03 | JBU32 | - | Jul 3, 09:45 UTC | Jul 3, 17:15 UTC | 7h 30m |
| 2026-07-02 | JBU2260 | MAD → BOS | Jul 2, 12:20 UTC | Jul 3, 11:15 UTC | 22h 55m |
| 2026-07-02 | JBU2261 | BOS → MAD | Jul 2, 03:00 UTC | Jul 3, 01:15 UTC | 22h 15m |
| 2026-07-01 | JBU346 | - | Jul 1, 11:20 UTC | Jul 1, 13:05 UTC | 1h 45m |
| 2026-07-01 | JBU346 | BCN → BOS | Jul 1, 11:17 UTC | Jul 2, 09:15 UTC | 21h 59m |
| 2026-07-01 | JBU345 | BOS → BCN | Jul 1, 01:15 UTC | Jul 1, 08:15 UTC | 7h 0m |
| 2026-06-30 | JBU31 | BOS → AMS | Jun 30, 00:38 UTC | Jun 30, 17:10 UTC | 16h 32m |
| 2026-06-30 | JBU31 | - | Jun 30, 00:39 UTC | Jun 30, 01:14 UTC | 35m |
| 2026-06-29 | JBU2260 | MAD → BOS | Jun 29, 12:34 UTC | Jun 29, 20:09 UTC | 7h 35m |
| 2026-06-29 | JBU2261 | - | Jun 29, 03:20 UTC | Jun 29, 09:29 UTC | 6h 10m |
| 2026-06-28 | JBU353 | BOS → DUB | Jun 28, 01:21 UTC | Jun 28, 21:55 UTC | 20h 34m |
| 2026-06-27 | JBU1034 | TPA → BDL | Jun 27, 07:24 UTC | Jun 27, 12:19 UTC | 4h 55m |
| 2026-06-27 | JBU1034 | TPA → BDL | Jun 27, 07:23 UTC | Jun 28, 06:55 UTC | 23h 32m |
| 2026-06-26 | JBU1633 | BTV → JFK | Jun 26, 23:30 UTC | Jun 27, 05:39 UTC | 6h 10m |
| 2026-06-26 | JBU1407 | JFK → CDG | Jun 26, 00:34 UTC | Jun 26, 23:15 UTC | 22h 41m |
| 2026-06-25 | JBU2220 | LHR → JFK | Jun 25, 07:54 UTC | Jun 25, 15:40 UTC | 7h 45m |
| 2026-06-25 | JBU2220 | LHR → JFK | Jun 25, 07:51 UTC | Jun 26, 07:14 UTC | 23h 24m |
| 2026-06-24 | JBU1107 | JFK → LHR | Jun 24, 13:05 UTC | Jun 24, 19:10 UTC | 6h 5m |
| 2026-06-24 | JBU1107 | JFK → LHR | Jun 24, 13:01 UTC | Jun 25, 09:10 UTC | 20h 9m |
| 2026-06-23 | JBU20 | LHR → JFK | Jun 23, 11:15 UTC | Jun 23, 19:00 UTC | 7h 45m |
| 2026-06-23 | JBU7 | JFK → LHR | Jun 23, 01:33 UTC | Jun 23, 19:00 UTC | 17h 27m |
| 2026-06-23 | JBU7 | JFK → LHR | Jun 23, 01:35 UTC | Jun 23, 08:09 UTC | 6h 35m |
| 2026-06-22 | JBU1408 | MIA → EWR | Jun 22, 11:24 UTC | Jun 22, 19:29 UTC | 8h 5m |
| 2026-06-22 | JBU33 | BOS → CDG | Jun 22, 02:30 UTC | Jun 22, 08:54 UTC | 6h 25m |
| 2026-06-21 | JBU1621 | - | Jun 21, 08:04 UTC | Jun 21, 09:15 UTC | 1h 10m |
| 2026-06-21 | JBU1621 | LHR → BOS | Jun 21, 08:00 UTC | Jun 22, 02:59 UTC | 19h 0m |
| 2026-06-20 | JBU1620 | BOS → LHR | Jun 20, 23:04 UTC | Jun 21, 05:20 UTC | 6h 15m |
| 2026-06-20 | JBU332 | MXP → BOS | Jun 20, 09:13 UTC | Jun 21, 05:20 UTC | 20h 7m |
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 N4076J page for operator, model, and routing details .