sensors Mode-S transponder
A1CE99
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N2151J · AIRBUS A-321neo · operated by JETBLUE AIRWAYS CORP
- Hex
- A1CE99
- Octal
- 50347231
- Decimal
- 10,604,185
- Country
- US
- Tail
- N2151J
- Type
- A21N
- Flights observed
- 237
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 2h ago
Current position
Country allocation
The ICAO 24-bit address A1CE99 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 |
|---|---|---|---|
| JBU841 | - | 15 | 2026-07-14 |
| JBU842 | - | 14 | 2026-07-13 |
| JBU1079 | - | 14 | 2026-07-01 |
| JBU115 | JetBlue Airways | 10 | 2026-05-05 |
| JBU72 | - | 9 | 2026-06-26 |
| JBU354 | JetBlue Airways | 9 | 2026-04-26 |
| JBU1926 | - | 9 | 2026-07-07 |
| JBU334 | JetBlue Airways | 8 | 2026-04-17 |
| JBU1333 | JetBlue Airways | 8 | 2026-06-25 |
| JBU1080 | JetBlue Airways | 8 | 2026-05-31 |
| JBU1524 | JetBlue Airways | 7 | 2026-06-03 |
| JBU1216 | JetBlue Airways | 7 | 2026-05-19 |
| JBU353 | - | 6 | 2026-07-05 |
| JBU1515 | JetBlue Airways | 6 | 2026-05-19 |
| JBU133 | JetBlue Airways | 6 | 2026-04-24 |
| JBU1734 | JetBlue Airways | 5 | 2026-04-24 |
| JBU2233 | JetBlue Airways | 4 | 2026-04-15 |
| JBU220 | - | 4 | 2026-07-06 |
| JBU2104 | - | 4 | 2026-07-07 |
| JBU834 | JetBlue Airways | 3 | 2026-05-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU841 | JFK → DUB | Jul 14, 01:19 UTC | Jul 14, 17:30 UTC | 16h 12m |
| 2026-07-13 | JBU842 | DUB → JFK | Jul 13, 10:50 UTC | Jul 14, 07:35 UTC | 20h 46m |
| 2026-07-13 | JBU842 | DUB → JFK | Jul 13, 10:50 UTC | Jul 14, 07:35 UTC | 20h 46m |
| 2026-07-13 | JBU841 | JFK → DUB | Jul 13, 02:06 UTC | Jul 13, 17:35 UTC | 15h 30m |
| 2026-07-13 | JBU841 | JFK → DUB | Jul 13, 02:10 UTC | Jul 13, 08:20 UTC | 6h 10m |
| 2026-07-12 | JBU841 | JFK → DUB | Jul 12, 02:23 UTC | Jul 13, 02:15 UTC | 23h 53m |
| 2026-07-11 | JBU887 | - | Jul 11, 13:50 UTC | Jul 11, 17:15 UTC | 3h 25m |
| 2026-07-11 | JBU887 | JFK → SXM | Jul 11, 13:50 UTC | Jul 12, 11:35 UTC | 21h 46m |
| 2026-07-10 | JBU1548 | - | Jul 10, 01:55 UTC | Jul 10, 03:00 UTC | 1h 5m |
| 2026-07-09 | JBU1548 | LAS → BUF | Jul 9, 19:15 UTC | Jul 9, 23:50 UTC | 4h 35m |
| 2026-07-09 | JBU411 | JFK → LAS | Jul 9, 10:55 UTC | Jul 9, 15:50 UTC | 4h 55m |
| 2026-07-09 | JBU416 | - | Jul 9, 02:00 UTC | Jul 9, 07:00 UTC | 5h 0m |
| 2026-07-08 | JBU1833 | - | Jul 8, 14:55 UTC | Jul 8, 20:35 UTC | 5h 40m |
| 2026-07-07 | JBU1926 | LGW → BOS | Jul 7, 13:29 UTC | Jul 7, 20:50 UTC | 7h 22m |
| 2026-07-07 | JBU1926 | LGW → BOS | Jul 7, 13:30 UTC | Jul 7, 20:30 UTC | 7h 0m |
| 2026-07-07 | JBU2104 | BOS → LGW | Jul 7, 04:45 UTC | Jul 7, 11:00 UTC | 6h 15m |
| 2026-07-06 | JBU220 | - | Jul 6, 21:00 UTC | Jul 7, 02:15 UTC | 5h 15m |
| 2026-07-06 | JBU219 | - | Jul 6, 13:15 UTC | Jul 6, 18:30 UTC | 5h 15m |
| 2026-07-06 | JBU2120 | - | Jul 6, 03:55 UTC | Jul 6, 08:55 UTC | 5h 0m |
| 2026-07-05 | JBU319 | - | Jul 5, 20:35 UTC | Jul 6, 02:00 UTC | 5h 25m |
| 2026-07-05 | JBU353 | BOS → DUB | Jul 5, 01:26 UTC | Jul 6, 00:15 UTC | 22h 50m |
| 2026-07-04 | JBU1926 | LGW → BOS | Jul 4, 12:11 UTC | Jul 5, 10:15 UTC | 22h 4m |
| 2026-07-04 | JBU1926 | LGW → BOS | Jul 4, 12:15 UTC | Jul 4, 19:40 UTC | 7h 25m |
| 2026-07-04 | JBU2104 | BOS → LGW | Jul 4, 03:45 UTC | Jul 4, 09:50 UTC | 6h 5m |
| 2026-07-03 | JBU220 | - | Jul 3, 20:30 UTC | Jul 4, 01:35 UTC | 5h 5m |
| 2026-07-03 | JBU2120 | SAN → BOS | Jul 3, 05:15 UTC | Jul 3, 10:20 UTC | 5h 5m |
| 2026-07-03 | JBU2120 | SAN → BOS | Jul 3, 05:15 UTC | Jul 4, 04:15 UTC | 23h 1m |
| 2026-07-02 | JBU319 | - | Jul 2, 22:15 UTC | Jul 3, 03:55 UTC | 5h 40m |
| 2026-07-02 | JBU1926 | LGW → BOS | Jul 2, 11:55 UTC | Jul 2, 19:10 UTC | 7h 15m |
| 2026-07-02 | JBU2104 | BOS → LGW | Jul 2, 02:35 UTC | Jul 2, 08:50 UTC | 6h 15m |
| 2026-07-01 | JBU1079 | BOS → EDI | Jul 1, 02:49 UTC | Jul 1, 18:45 UTC | 15h 57m |
| 2026-06-30 | JBU1177 | BOS → LAS | Jun 30, 12:13 UTC | Jul 1, 08:50 UTC | 20h 38m |
| 2026-06-29 | JBU220 | - | Jun 29, 20:30 UTC | Jun 30, 01:19 UTC | 4h 50m |
| 2026-06-29 | JBU220 | SAN → BOS | Jun 29, 20:25 UTC | Jun 30, 20:15 UTC | 23h 51m |
| 2026-06-29 | JBU219 | - | Jun 29, 13:09 UTC | Jun 29, 18:49 UTC | 5h 40m |
| 2026-06-28 | JBU1387 | BOS → LAX | Jun 28, 22:33 UTC | Jun 29, 22:15 UTC | 23h 42m |
| 2026-06-28 | JBU1926 | - | Jun 28, 11:35 UTC | Jun 28, 13:00 UTC | 1h 25m |
| 2026-06-28 | JBU1926 | LGW → BOS | Jun 28, 11:34 UTC | Jun 29, 10:15 UTC | 22h 41m |
| 2026-06-28 | JBU1926 | LGW → BOS | Jun 28, 11:34 UTC | Jun 29, 10:15 UTC | 22h 41m |
| 2026-06-28 | JBU2104 | - | Jun 28, 02:20 UTC | Jun 28, 08:19 UTC | 6h 0m |
| 2026-06-27 | JBU808 | - | Jun 27, 22:55 UTC | Jun 27, 23:45 UTC | 50m |
| 2026-06-27 | JBU808 | - | Jun 27, 20:19 UTC | Jun 27, 20:29 UTC | 10m |
| 2026-06-27 | JBU808 | - | Jun 27, 18:45 UTC | Jun 27, 19:05 UTC | 20m |
| 2026-06-27 | JBU807 | - | Jun 27, 13:49 UTC | Jun 27, 17:14 UTC | 3h 25m |
| 2026-06-27 | JBU807 | BOS → STT | Jun 27, 13:47 UTC | Jun 27, 17:14 UTC | 3h 28m |
| 2026-06-27 | JBU488 | - | Jun 27, 05:55 UTC | Jun 27, 10:45 UTC | 4h 50m |
| 2026-06-26 | JBU72 | EDI → JFK | Jun 26, 11:34 UTC | Jun 26, 18:54 UTC | 7h 20m |
| 2026-06-26 | JBU72 | EDI → JFK | Jun 26, 11:33 UTC | Jun 27, 10:14 UTC | 22h 42m |
| 2026-06-26 | JBU1079 | BOS → EDI | Jun 26, 02:44 UTC | Jun 26, 08:34 UTC | 5h 50m |
| 2026-06-25 | JBU1333 | BOS → SFO | Jun 25, 10:39 UTC | Jun 25, 17:05 UTC | 6h 25m |
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 N2151J page for operator, model, and routing details .