sensors Mode-S transponder
A19910
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N2017J · AIRBUS A-321neo · operated by JETBLUE AIRWAYS CORP
- Hex
- A19910
- Octal
- 50314420
- Decimal
- 10,590,480
- Country
- US
- Tail
- N2017J
- Type
- A21N
- Flights observed
- 228
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 9m ago
Current position
Country allocation
The ICAO 24-bit address A19910 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 | JetBlue Airways | 10 | 2026-05-28 |
| JBU505 | JetBlue Airways | 7 | 2026-06-07 |
| JBU1383 | JetBlue Airways | 7 | 2026-05-18 |
| JBU1328 | JetBlue Airways | 7 | 2026-05-18 |
| JBU1255 | JetBlue Airways | 7 | 2026-06-08 |
| JBU887 | - | 6 | 2026-07-12 |
| JBU1966 | - | 6 | 2026-07-07 |
| JBU637 | JetBlue Airways | 5 | 2026-06-18 |
| JBU569 | JetBlue Airways | 5 | 2026-05-19 |
| JBU470 | JetBlue Airways | 5 | 2026-05-19 |
| JBU1188 | - | 5 | 2026-07-12 |
| JBU939 | JetBlue Airways | 4 | 2026-05-22 |
| JBU882 | - | 4 | 2026-06-29 |
| JBU466 | - | 4 | 2026-06-30 |
| JBU2536 | - | 4 | 2026-07-08 |
| JBU1965 | - | 4 | 2026-07-07 |
| JBU836 | - | 3 | 2026-04-13 |
| JBU803 | - | 3 | 2026-07-02 |
| JBU787 | - | 3 | 2026-06-25 |
| JBU662 | JetBlue Airways | 3 | 2026-05-31 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU1759 | JFK → KIN | Jul 13, 21:35 UTC | Jul 14, 04:00 UTC | 6h 26m |
| 2026-07-13 | JBU1769 | JFK → GYE | Jul 13, 03:41 UTC | Jul 13, 23:55 UTC | 20h 15m |
| 2026-07-12 | JBU1188 | - | Jul 12, 20:05 UTC | Jul 12, 23:20 UTC | 3h 15m |
| 2026-07-12 | JBU1188 | SXM → JFK | Jul 12, 19:45 UTC | Jul 13, 18:00 UTC | 22h 16m |
| 2026-07-12 | JBU887 | - | Jul 12, 14:45 UTC | Jul 12, 17:55 UTC | 3h 10m |
| 2026-07-11 | JBU309 | JFK → JFK | Jul 11, 23:10 UTC | Jul 12, 12:10 UTC | 13h 0m |
| 2026-07-11 | JBU268 | - | Jul 11, 18:35 UTC | Jul 11, 19:35 UTC | 1h 0m |
| 2026-07-11 | JBU268 | PUJ → JFK | Jul 11, 16:17 UTC | Jul 12, 15:25 UTC | 23h 9m |
| 2026-07-10 | JBU610 | SDQ → JFK | Jul 10, 09:59 UTC | Jul 10, 16:45 UTC | 6h 46m |
| 2026-07-10 | JBU709 | JFK → JFK | Jul 10, 03:30 UTC | Jul 10, 13:20 UTC | 9h 50m |
| 2026-07-09 | JBU1851 | JFK → CUN | Jul 9, 14:44 UTC | Jul 10, 13:30 UTC | 22h 46m |
| 2026-07-09 | JBU1851 | JFK → CUN | Jul 9, 14:45 UTC | Jul 9, 18:15 UTC | 3h 30m |
| 2026-07-08 | JBU2018 | POS → JFK | Jul 8, 19:49 UTC | Jul 9, 18:00 UTC | 22h 11m |
| 2026-07-08 | JBU117 | - | Jul 8, 12:50 UTC | Jul 8, 17:25 UTC | 4h 35m |
| 2026-07-08 | JBU117 | JFK → POS | Jul 8, 12:46 UTC | Jul 9, 00:20 UTC | 11h 35m |
| 2026-07-08 | JBU2536 | JFK → JFK | Jul 8, 01:55 UTC | Jul 8, 10:25 UTC | 8h 30m |
| 2026-07-07 | JBU887 | JFK → SXM | Jul 7, 14:14 UTC | Jul 8, 14:00 UTC | 23h 47m |
| 2026-07-07 | JBU1966 | GEO → JFK | Jul 7, 06:46 UTC | Jul 8, 02:30 UTC | 19h 45m |
| 2026-07-07 | JBU1965 | JFK → GEO | Jul 7, 00:05 UTC | Jul 7, 23:25 UTC | 23h 20m |
| 2026-07-06 | JBU780 | JFK → JFK | Jul 6, 12:25 UTC | Jul 6, 21:05 UTC | 8h 40m |
| 2026-07-05 | JBU905 | JFK → ORD | Jul 5, 11:18 UTC | Jul 6, 04:50 UTC | 17h 32m |
| 2026-07-04 | JBU18 | - | Jul 4, 23:50 UTC | Jul 5, 00:00 UTC | 10m |
| 2026-07-04 | JBU18 | POS → JFK | Jul 4, 23:39 UTC | Jul 5, 22:00 UTC | 22h 22m |
| 2026-07-04 | JBU17 | - | Jul 4, 18:25 UTC | Jul 4, 22:10 UTC | 3h 45m |
| 2026-07-04 | JBU17 | - | Jul 4, 17:50 UTC | Jul 4, 18:20 UTC | 30m |
| 2026-07-04 | JBU17 | JFK → POS | Jul 4, 17:49 UTC | Jul 5, 16:00 UTC | 22h 11m |
| 2026-07-03 | JBU1188 | SXM → JFK | Jul 3, 20:30 UTC | Jul 4, 18:35 UTC | 22h 5m |
| 2026-07-03 | JBU887 | - | Jul 3, 15:20 UTC | Jul 3, 18:40 UTC | 3h 20m |
| 2026-07-03 | JBU887 | JFK → SXM | Jul 3, 15:19 UTC | Jul 4, 14:00 UTC | 22h 42m |
| 2026-07-03 | JBU610 | JFK → JFK | Jul 3, 01:15 UTC | Jul 3, 13:15 UTC | 12h 0m |
| 2026-07-02 | JBU361 | JFK → BGI | Jul 2, 12:20 UTC | Jul 3, 01:55 UTC | 13h 35m |
| 2026-07-02 | JBU803 | - | Jul 2, 00:15 UTC | Jul 2, 00:40 UTC | 25m |
| 2026-07-01 | JBU803 | - | Jul 1, 21:25 UTC | Jul 1, 22:00 UTC | 35m |
| 2026-07-01 | JBU803 | JFK → SJU | Jul 1, 21:22 UTC | Jul 2, 19:45 UTC | 22h 23m |
| 2026-07-01 | JBU1436 | JFK → JFK | Jul 1, 09:10 UTC | Jul 1, 17:50 UTC | 8h 40m |
| 2026-06-30 | JBU466 | JFK → JFK | Jun 30, 15:50 UTC | Jul 1, 03:35 UTC | 11h 45m |
| 2026-06-29 | JBU882 | UVF → JFK | Jun 29, 20:39 UTC | Jun 30, 19:00 UTC | 22h 22m |
| 2026-06-29 | JBU2584 | MCO → JFK | Jun 29, 10:04 UTC | Jun 30, 01:25 UTC | 15h 21m |
| 2026-06-29 | JBU2584 | MCO → JFK | Jun 29, 10:04 UTC | Jun 29, 12:20 UTC | 2h 15m |
| 2026-06-29 | JBU2583 | - | Jun 29, 02:00 UTC | Jun 29, 04:09 UTC | 2h 10m |
| 2026-06-28 | JBU1682 | - | Jun 28, 18:49 UTC | Jun 28, 22:15 UTC | 3h 25m |
| 2026-06-28 | JBU1682 | - | Jun 28, 17:55 UTC | Jun 28, 18:05 UTC | 10m |
| 2026-06-27 | JBU1965 | JFK → GEO | Jun 27, 21:34 UTC | Jun 28, 19:09 UTC | 21h 36m |
| 2026-06-27 | JBU1770 | GYE → JFK | Jun 27, 12:14 UTC | Jun 28, 09:25 UTC | 21h 11m |
| 2026-06-27 | JBU1769 | - | Jun 27, 03:30 UTC | Jun 27, 07:15 UTC | 3h 45m |
| 2026-06-26 | JBU1669 | JFK → JFK | Jun 26, 15:45 UTC | Jun 27, 00:39 UTC | 8h 55m |
| 2026-06-25 | JBU309 | - | Jun 25, 22:45 UTC | Jun 26, 13:24 UTC | 14h 40m |
| 2026-06-25 | JBU787 | JFK → JFK | Jun 25, 10:15 UTC | Jun 25, 18:59 UTC | 8h 45m |
| 2026-06-24 | JBU887 | JFK → JFK | Jun 24, 13:50 UTC | Jun 24, 23:00 UTC | 9h 10m |
| 2026-06-24 | JBU1059 | JFK → KIN | Jun 24, 02:27 UTC | Jun 24, 23:04 UTC | 20h 38m |
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 N2017J page for operator, model, and routing details .