sensors Mode-S transponder
A19CC7
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N2027J · AIRBUS A-321neo · operated by JETBLUE AIRWAYS CORP
- Hex
- A19CC7
- Octal
- 50316307
- Decimal
- 10,591,431
- Country
- US
- Tail
- N2027J
- Type
- A21N
- Flights observed
- 211
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 52m ago
Last known position
Country allocation
The ICAO 24-bit address A19CC7 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 |
|---|---|---|---|
| JBU528 | - | 12 | 2026-07-13 |
| JBU505 | - | 11 | 2026-07-10 |
| JBU1 | JetBlue Airways | 8 | 2026-07-07 |
| JBU1255 | - | 7 | 2026-07-13 |
| JBU1188 | JetBlue Airways | 7 | 2026-04-16 |
| JBU1587 | JetBlue Airways | 6 | 2026-04-16 |
| JBU1533 | JetBlue Airways | 6 | 2026-07-06 |
| JBU1328 | JetBlue Airways | 6 | 2026-04-29 |
| JBU1256 | - | 6 | 2026-07-10 |
| JBU596 | JetBlue Airways | 5 | 2026-05-09 |
| JBU1669 | - | 5 | 2026-07-09 |
| JBU610 | - | 4 | 2026-07-02 |
| JBU597 | JetBlue Airways | 4 | 2026-05-09 |
| JBU350 | - | 4 | 2026-07-05 |
| JBU2018 | JetBlue Airways | 4 | 2026-06-11 |
| JBU1383 | JetBlue Airways | 4 | 2026-04-27 |
| JBU965 | JetBlue Airways | 3 | 2026-05-03 |
| JBU569 | JetBlue Airways | 3 | 2026-05-11 |
| JBU523 | JetBlue Airways | 3 | 2026-05-22 |
| JBU2661 | JetBlue Airways | 3 | 2026-04-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU169 | JFK → PUJ | Jul 14, 11:51 UTC | Jul 14, 21:25 UTC | 9h 35m |
| 2026-07-13 | JBU528 | GYE → JFK | Jul 13, 21:49 UTC | Jul 14, 21:25 UTC | 23h 37m |
| 2026-07-13 | JBU1255 | - | Jul 13, 16:20 UTC | Jul 13, 16:45 UTC | 25m |
| 2026-07-13 | JBU1255 | FLL → GYE | Jul 13, 16:17 UTC | Jul 14, 12:30 UTC | 20h 14m |
| 2026-07-12 | JBU1611 | FLL → AUA | Jul 12, 17:11 UTC | Jul 13, 00:01 UTC | 6h 50m |
| 2026-07-12 | JBU706 | - | Jul 12, 01:05 UTC | Jul 12, 03:25 UTC | 2h 20m |
| 2026-07-12 | JBU706 | FLL → EWR | Jul 12, 01:03 UTC | Jul 12, 23:45 UTC | 22h 43m |
| 2026-07-11 | JBU517 | BOS → JFK | Jul 11, 14:10 UTC | Jul 11, 15:35 UTC | 1h 25m |
| 2026-07-10 | JBU1256 | GYE → FLL | Jul 10, 19:19 UTC | Jul 11, 15:35 UTC | 20h 17m |
| 2026-07-10 | JBU505 | - | Jul 10, 12:10 UTC | Jul 10, 20:45 UTC | 8h 35m |
| 2026-07-09 | JBU1669 | JFK → JFK | Jul 9, 16:45 UTC | Jul 10, 01:30 UTC | 8h 45m |
| 2026-07-09 | JBU1837 | - | Jul 9, 00:15 UTC | Jul 9, 14:10 UTC | 13h 55m |
| 2026-07-08 | JBU869 | JFK → PUJ | Jul 8, 10:32 UTC | Jul 9, 01:25 UTC | 14h 54m |
| 2026-07-07 | JBU1039 | - | Jul 7, 20:25 UTC | Jul 7, 21:05 UTC | 40m |
| 2026-07-07 | JBU1039 | JFK → BQN | Jul 7, 20:21 UTC | Jul 8, 19:40 UTC | 23h 20m |
| 2026-07-07 | JBU602 | - | Jul 7, 16:25 UTC | Jul 7, 18:40 UTC | 2h 15m |
| 2026-07-07 | JBU1 | JFK → FLL | Jul 7, 11:10 UTC | Jul 7, 13:35 UTC | 2h 25m |
| 2026-07-06 | JBU1533 | JFK → CTG | Jul 6, 14:30 UTC | Jul 7, 00:45 UTC | 10h 15m |
| 2026-07-05 | JBU350 | - | Jul 5, 21:40 UTC | Jul 6, 01:55 UTC | 4h 15m |
| 2026-07-05 | JBU149 | - | Jul 5, 15:50 UTC | Jul 5, 19:15 UTC | 3h 25m |
| 2026-07-05 | JBU8446 | BOS → JFK | Jul 5, 13:20 UTC | Jul 5, 14:00 UTC | 40m |
| 2026-07-04 | JBU528 | - | Jul 4, 15:30 UTC | Jul 5, 04:25 UTC | 12h 55m |
| 2026-07-04 | JBU1 | JFK → FLL | Jul 4, 09:45 UTC | Jul 4, 12:10 UTC | 2h 25m |
| 2026-07-03 | JBU1256 | GYE → FLL | Jul 3, 17:25 UTC | Jul 4, 15:45 UTC | 22h 20m |
| 2026-07-03 | JBU1256 | GYE → FLL | Jul 3, 17:25 UTC | Jul 4, 15:45 UTC | 22h 20m |
| 2026-07-03 | JBU505 | - | Jul 3, 09:55 UTC | Jul 3, 12:20 UTC | 2h 25m |
| 2026-07-02 | JBU1669 | JFK → PUJ | Jul 2, 16:17 UTC | Jul 3, 12:20 UTC | 20h 4m |
| 2026-07-02 | JBU610 | SDQ → JFK | Jul 2, 11:01 UTC | Jul 3, 00:40 UTC | 13h 39m |
| 2026-07-01 | JBU610 | JFK → JFK | Jul 1, 22:00 UTC | Jul 2, 14:25 UTC | 16h 25m |
| 2026-07-01 | JBU787 | JFK → JFK | Jul 1, 10:15 UTC | Jul 1, 18:55 UTC | 8h 40m |
| 2026-06-30 | JBU350 | GND → JFK | Jun 30, 19:58 UTC | Jul 1, 18:55 UTC | 22h 58m |
| 2026-06-30 | JBU350 | JFK → JFK | Jun 30, 13:50 UTC | Jul 1, 00:25 UTC | 10h 35m |
| 2026-06-29 | JBU528 | GYE → JFK | Jun 29, 21:03 UTC | Jun 30, 17:00 UTC | 19h 57m |
| 2026-06-29 | JBU1255 | - | Jun 29, 15:30 UTC | Jun 29, 23:25 UTC | 7h 55m |
| 2026-06-28 | JBU1501 | - | Jun 28, 22:39 UTC | Jun 29, 01:10 UTC | 2h 30m |
| 2026-06-28 | JBU1501 | JFK → FLL | Jun 28, 22:36 UTC | Jun 29, 17:19 UTC | 18h 44m |
| 2026-06-28 | JBU852 | CUN → JFK | Jun 28, 16:39 UTC | Jun 28, 19:55 UTC | 3h 15m |
| 2026-06-28 | JBU851 | JFK → CUN | Jun 28, 11:39 UTC | Jun 28, 15:05 UTC | 3h 25m |
| 2026-06-27 | JBU1794 | - | Jun 27, 20:44 UTC | Jun 28, 01:04 UTC | 4h 20m |
| 2026-06-27 | JBU1793 | - | Jun 27, 13:55 UTC | Jun 27, 18:15 UTC | 4h 20m |
| 2026-06-26 | JBU882 | UVF → JFK | Jun 26, 20:32 UTC | Jun 27, 18:15 UTC | 21h 43m |
| 2026-06-26 | JBU881 | - | Jun 26, 14:35 UTC | Jun 26, 21:50 UTC | 7h 15m |
| 2026-06-25 | JBU350 | JFK → JFK | Jun 25, 14:04 UTC | Jun 26, 00:05 UTC | 10h 0m |
| 2026-06-24 | JBU528 | - | Jun 24, 15:29 UTC | Jun 25, 03:29 UTC | 12h 0m |
| 2026-06-23 | JBU505 | JFK → GYE | Jun 23, 10:17 UTC | Jun 23, 13:59 UTC | 3h 43m |
| 2026-06-23 | JBU505 | JFK → FLL | Jun 23, 10:19 UTC | Jun 23, 21:54 UTC | 11h 35m |
| 2026-06-22 | JBU18 | JFK → JFK | Jun 22, 21:05 UTC | Jun 23, 07:19 UTC | 10h 15m |
| 2026-06-22 | JBU1601 | JFK → FLL | Jun 22, 11:06 UTC | Jun 23, 09:45 UTC | 22h 39m |
| 2026-06-21 | JBU1669 | - | Jun 21, 17:10 UTC | Jun 21, 17:50 UTC | 40m |
| 2026-06-21 | JBU1669 | JFK → PUJ | Jun 21, 17:09 UTC | Jun 22, 13:29 UTC | 20h 21m |
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 N2027J page for operator, model, and routing details .