sensors Mode-S transponder
A1CF48
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N2156J · AIRBUS A-321neo · operated by JETBLUE AIRWAYS CORP
- Hex
- A1CF48
- Octal
- 50347510
- Decimal
- 10,604,360
- Country
- US
- Tail
- N2156J
- Type
- A21N
- Flights observed
- 255
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address A1CF48 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 |
|---|---|---|---|
| JBU842 | - | 16 | 2026-07-11 |
| JBU133 | JetBlue Airways | 16 | 2026-04-16 |
| JBU353 | - | 15 | 2026-07-08 |
| JBU1080 | - | 12 | 2026-07-13 |
| JBU1079 | - | 12 | 2026-06-24 |
| JBU1734 | JetBlue Airways | 11 | 2026-04-16 |
| JBU354 | - | 10 | 2026-07-04 |
| JBU841 | - | 9 | 2026-07-09 |
| JBU123 | JetBlue Airways | 9 | 2026-05-20 |
| JBU224 | JetBlue Airways | 8 | 2026-05-17 |
| JBU73 | - | 7 | 2026-07-13 |
| JBU72 | - | 7 | 2026-06-24 |
| JBU1926 | - | 6 | 2026-06-23 |
| JBU724 | JetBlue Airways | 5 | 2026-05-10 |
| JBU411 | - | 5 | 2026-07-10 |
| JBU323 | - | 5 | 2026-06-12 |
| JBU223 | JetBlue Airways | 5 | 2026-06-13 |
| JBU2124 | JetBlue Airways | 5 | 2026-05-19 |
| JBU1190 | JetBlue Airways | 5 | 2026-05-13 |
| JBU834 | JetBlue Airways | 4 | 2026-06-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU31 | BOS → AMS | Jul 14, 00:31 UTC | Jul 14, 01:50 UTC | 1h 20m |
| 2026-07-13 | JBU1080 | - | Jul 13, 10:45 UTC | Jul 13, 11:50 UTC | 1h 5m |
| 2026-07-13 | JBU1080 | EDI → BOS | Jul 13, 10:41 UTC | Jul 14, 01:50 UTC | 15h 10m |
| 2026-07-13 | JBU73 | JFK → EDI | Jul 13, 01:30 UTC | Jul 13, 07:55 UTC | 6h 25m |
| 2026-07-11 | JBU842 | DUB → JFK | Jul 11, 11:05 UTC | Jul 11, 18:10 UTC | 7h 5m |
| 2026-07-10 | JBU1548 | LAS → JFK | Jul 10, 18:59 UTC | Jul 11, 18:00 UTC | 23h 2m |
| 2026-07-10 | JBU1548 | LAS → JFK | Jul 10, 19:00 UTC | Jul 10, 23:20 UTC | 4h 21m |
| 2026-07-10 | JBU411 | JFK → LAS | Jul 10, 12:35 UTC | Jul 10, 17:15 UTC | 4h 40m |
| 2026-07-09 | JBU842 | DUB → JFK | Jul 9, 12:13 UTC | Jul 9, 19:05 UTC | 6h 52m |
| 2026-07-09 | JBU841 | JFK → DUB | Jul 9, 01:35 UTC | Jul 9, 19:05 UTC | 17h 30m |
| 2026-07-09 | JBU841 | - | Jul 9, 01:35 UTC | Jul 9, 03:10 UTC | 1h 35m |
| 2026-07-08 | JBU842 | DUB → JFK | Jul 8, 11:00 UTC | Jul 8, 17:50 UTC | 6h 50m |
| 2026-07-08 | JBU353 | - | Jul 8, 01:25 UTC | Jul 8, 07:20 UTC | 5h 55m |
| 2026-07-07 | JBU73 | JFK → EDI | Jul 7, 01:57 UTC | Jul 7, 18:00 UTC | 16h 4m |
| 2026-07-06 | JBU842 | DUB → JFK | Jul 6, 11:45 UTC | Jul 7, 08:15 UTC | 20h 31m |
| 2026-07-06 | JBU353 | BOS → DUB | Jul 6, 04:15 UTC | Jul 7, 03:40 UTC | 23h 25m |
| 2026-07-05 | JBU1034 | SFO → BOS | Jul 5, 04:09 UTC | Jul 6, 04:00 UTC | 23h 52m |
| 2026-07-04 | JBU833 | - | Jul 4, 20:00 UTC | Jul 5, 01:45 UTC | 5h 45m |
| 2026-07-04 | JBU833 | BOS → SFO | Jul 4, 19:56 UTC | Jul 5, 18:00 UTC | 22h 5m |
| 2026-07-04 | JBU833 | BOS → BOS | Jul 4, 19:25 UTC | Jul 4, 19:35 UTC | 10m |
| 2026-07-04 | JBU354 | DUB → BOS | Jul 4, 10:00 UTC | Jul 4, 16:35 UTC | 6h 35m |
| 2026-07-03 | JBU1177 | BOS → LAS | Jul 3, 12:40 UTC | Jul 3, 17:45 UTC | 5h 5m |
| 2026-07-03 | JBU1177 | BOS → LAS | Jul 3, 12:40 UTC | Jul 4, 10:50 UTC | 22h 10m |
| 2026-07-03 | JBU488 | - | Jul 3, 06:10 UTC | Jul 3, 11:10 UTC | 5h 0m |
| 2026-07-02 | JBU1387 | - | Jul 2, 22:45 UTC | Jul 3, 04:20 UTC | 5h 35m |
| 2026-07-02 | JBU354 | DUB → BOS | Jul 2, 09:55 UTC | Jul 2, 16:40 UTC | 6h 45m |
| 2026-07-02 | JBU353 | BOS → DUB | Jul 2, 01:15 UTC | Jul 2, 06:45 UTC | 5h 30m |
| 2026-07-01 | JBU2120 | - | Jul 1, 04:15 UTC | Jul 1, 09:05 UTC | 4h 50m |
| 2026-06-30 | JBU354 | DUB → BOS | Jun 30, 10:00 UTC | Jun 30, 16:25 UTC | 6h 25m |
| 2026-06-30 | JBU354 | DUB → BOS | Jun 30, 09:58 UTC | Jul 1, 08:00 UTC | 22h 3m |
| 2026-06-30 | JBU353 | BOS → DUB | Jun 30, 01:19 UTC | Jun 30, 06:45 UTC | 5h 26m |
| 2026-06-29 | JBU620 | - | Jun 29, 17:40 UTC | Jun 29, 22:35 UTC | 4h 55m |
| 2026-06-29 | JBU619 | - | Jun 29, 10:24 UTC | Jun 29, 16:10 UTC | 5h 45m |
| 2026-06-28 | JBU219 | - | Jun 28, 13:00 UTC | Jun 28, 18:40 UTC | 5h 40m |
| 2026-06-28 | JBU219 | BOS → SAN | Jun 28, 12:57 UTC | Jun 29, 12:00 UTC | 23h 3m |
| 2026-06-27 | JBU833 | BOS → SFO | Jun 27, 19:15 UTC | Jun 28, 18:00 UTC | 22h 45m |
| 2026-06-27 | JBU354 | - | Jun 27, 09:55 UTC | Jun 27, 10:45 UTC | 50m |
| 2026-06-27 | JBU354 | DUB → BOS | Jun 27, 09:53 UTC | Jun 28, 08:00 UTC | 22h 7m |
| 2026-06-27 | JBU353 | BOS → DUB | Jun 27, 01:35 UTC | Jun 27, 06:59 UTC | 5h 25m |
| 2026-06-26 | 123456 | BOS → BOS | Jun 26, 21:35 UTC | Jun 26, 21:39 UTC | 5m |
| 2026-06-26 | JBU354 | DUB → BOS | Jun 26, 09:59 UTC | Jun 26, 16:39 UTC | 6h 40m |
| 2026-06-26 | JBU353 | - | Jun 26, 01:15 UTC | Jun 26, 06:29 UTC | 5h 15m |
| 2026-06-26 | JBU353 | BOS → BOS | Jun 26, 01:05 UTC | Jun 26, 01:10 UTC | 5m |
| 2026-06-25 | JBU488 | - | Jun 25, 05:35 UTC | Jun 25, 10:30 UTC | 4h 55m |
| 2026-06-24 | JBU72 | EDI → JFK | Jun 24, 11:11 UTC | Jun 25, 09:59 UTC | 22h 49m |
| 2026-06-24 | JBU72 | - | Jun 24, 11:14 UTC | Jun 24, 12:04 UTC | 50m |
| 2026-06-24 | JBU1079 | BOS → EDI | Jun 24, 02:49 UTC | Jun 24, 08:35 UTC | 5h 45m |
| 2026-06-23 | JBU1926 | LGW → BOS | Jun 23, 11:59 UTC | Jun 24, 09:59 UTC | 22h 1m |
| 2026-06-23 | JBU1926 | LGW → BOS | Jun 23, 11:59 UTC | Jun 24, 09:59 UTC | 22h 1m |
| 2026-06-23 | JBU2104 | BOS → LGW | Jun 23, 02:07 UTC | Jun 24, 01:55 UTC | 23h 48m |
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 N2156J page for operator, model, and routing details .