sensors Mode-S transponder
ADF128
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N998JE · AIRBUS A-321 · operated by JETBLUE AIRWAYS CORP
- Hex
- ADF128
- Octal
- 53370450
- Decimal
- 11,399,464
- Country
- US
- Tail
- N998JE
- Type
- A321
- Flights observed
- 240
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address ADF128 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 |
|---|---|---|---|
| JBU454 | - | 6 | 2026-06-20 |
| JBU922 | - | 5 | 2026-07-13 |
| JBU9 | - | 5 | 2026-07-12 |
| JBU574 | - | 5 | 2026-07-07 |
| JBU151 | - | 5 | 2026-07-11 |
| JBU774 | JetBlue Airways | 4 | 2026-04-17 |
| JBU651 | JetBlue Airways | 4 | 2026-05-13 |
| JBU474 | JetBlue Airways | 4 | 2026-05-16 |
| JBU373 | JetBlue Airways | 4 | 2026-07-01 |
| JBU1347 | JetBlue Airways | 4 | 2026-05-04 |
| JBU803 | - | 3 | 2026-06-25 |
| JBU771 | JetBlue Airways | 3 | 2026-05-07 |
| JBU73 | JetBlue Airways | 3 | 2026-04-17 |
| JBU355 | - | 3 | 2026-06-20 |
| JBU322 | JetBlue Airways | 3 | 2026-05-13 |
| JBU2829 | - | 3 | 2026-07-08 |
| JBU2709 | - | 3 | 2026-06-18 |
| JBU2173 | - | 3 | 2026-07-07 |
| JBU2023 | - | 3 | 2026-07-08 |
| JBU1829 | - | 3 | 2026-07-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU859 | - | Jul 14, 20:15 UTC | Jul 14, 22:00 UTC | 1h 45m |
| 2026-07-14 | JBU1436 | JFK → JFK | Jul 14, 09:15 UTC | Jul 14, 17:45 UTC | 8h 30m |
| 2026-07-13 | JBU922 | - | Jul 13, 21:50 UTC | Jul 13, 23:45 UTC | 1h 55m |
| 2026-07-13 | JBU922 | NAS → JFK | Jul 13, 21:23 UTC | Jul 14, 20:00 UTC | 22h 38m |
| 2026-07-13 | JBU921 | - | Jul 13, 17:15 UTC | Jul 13, 19:20 UTC | 2h 5m |
| 2026-07-12 | JBU9 | JFK → JFK | Jul 12, 22:05 UTC | Jul 13, 14:55 UTC | 16h 50m |
| 2026-07-12 | JBU407 | - | Jul 12, 18:35 UTC | Jul 12, 19:20 UTC | 45m |
| 2026-07-12 | JBU508 | - | Jul 12, 15:50 UTC | Jul 12, 16:40 UTC | 50m |
| 2026-07-11 | JBU151 | JFK → CUN | Jul 11, 13:25 UTC | Jul 12, 02:25 UTC | 13h 1m |
| 2026-07-11 | JBU151 | JFK → CUN | Jul 11, 13:25 UTC | Jul 11, 16:50 UTC | 3h 25m |
| 2026-07-09 | JBU9 | JFK → SDQ | Jul 9, 22:31 UTC | Jul 10, 14:50 UTC | 16h 20m |
| 2026-07-09 | JBU602 | FLL → JFK | Jul 9, 17:43 UTC | Jul 10, 14:50 UTC | 21h 8m |
| 2026-07-09 | JBU1601 | JFK → FLL | Jul 9, 11:20 UTC | Jul 9, 13:50 UTC | 2h 30m |
| 2026-07-09 | JBU1601 | JFK → FLL | Jul 9, 11:18 UTC | Jul 9, 23:10 UTC | 11h 52m |
| 2026-07-08 | JBU2023 | - | Jul 8, 17:45 UTC | Jul 9, 02:35 UTC | 8h 50m |
| 2026-07-08 | JBU2829 | BOS → SDQ | Jul 8, 03:31 UTC | Jul 9, 02:00 UTC | 22h 30m |
| 2026-07-08 | JBU2829 | - | Jul 8, 03:35 UTC | Jul 8, 04:05 UTC | 30m |
| 2026-07-07 | JBU574 | - | Jul 7, 21:45 UTC | Jul 7, 22:40 UTC | 55m |
| 2026-07-07 | JBU574 | - | Jul 7, 18:30 UTC | Jul 7, 18:45 UTC | 15m |
| 2026-07-07 | JBU2173 | BOS → AUA | Jul 7, 12:20 UTC | Jul 7, 16:55 UTC | 4h 35m |
| 2026-07-05 | JBU397 | - | Jul 5, 11:25 UTC | Jul 5, 14:55 UTC | 3h 30m |
| 2026-07-04 | JBU1829 | BOS → SDQ | Jul 4, 16:30 UTC | Jul 5, 15:40 UTC | 23h 11m |
| 2026-07-04 | JBU1323 | BOS → STI | Jul 4, 03:33 UTC | Jul 5, 02:00 UTC | 22h 28m |
| 2026-07-03 | JBU2173 | BOS → AUA | Jul 3, 12:22 UTC | Jul 4, 12:00 UTC | 23h 38m |
| 2026-07-03 | JBU2173 | - | Jul 3, 12:25 UTC | Jul 3, 16:40 UTC | 4h 15m |
| 2026-07-02 | JBU396 | PDX → BOS | Jul 2, 21:45 UTC | Jul 3, 02:30 UTC | 4h 45m |
| 2026-07-02 | JBU395 | BOS → PDX | Jul 2, 14:30 UTC | Jul 2, 19:50 UTC | 5h 20m |
| 2026-07-01 | JBU373 | BOS → AUA | Jul 1, 15:17 UTC | Jul 2, 09:35 UTC | 18h 18m |
| 2026-06-30 | JBU9 | JFK → SDQ | Jun 30, 20:36 UTC | Jul 1, 19:20 UTC | 22h 44m |
| 2026-06-30 | JBU209 | JFK → SDQ | Jun 30, 09:16 UTC | Jun 30, 21:05 UTC | 11h 50m |
| 2026-06-29 | JBU922 | - | Jun 29, 22:05 UTC | Jun 30, 00:00 UTC | 1h 55m |
| 2026-06-29 | JBU922 | NAS → JFK | Jun 29, 21:34 UTC | Jun 30, 17:50 UTC | 20h 17m |
| 2026-06-29 | JBU921 | - | Jun 29, 17:05 UTC | Jun 29, 19:09 UTC | 2h 5m |
| 2026-06-28 | JBU2110 | - | Jun 28, 20:50 UTC | Jun 29, 15:00 UTC | 18h 10m |
| 2026-06-28 | JBU2137 | - | Jun 28, 09:30 UTC | Jun 28, 10:44 UTC | 1h 15m |
| 2026-06-28 | JBU2137 | JFK → STI | Jun 28, 09:25 UTC | Jun 28, 21:24 UTC | 12h 0m |
| 2026-06-27 | JBU58 | MCO → JFK | Jun 27, 20:14 UTC | Jun 27, 23:45 UTC | 3h 30m |
| 2026-06-27 | JBU58 | MCO → JFK | Jun 27, 19:24 UTC | Jun 27, 19:34 UTC | 10m |
| 2026-06-27 | JBU57 | JFK → AUA | Jun 27, 16:39 UTC | Jun 27, 17:25 UTC | 45m |
| 2026-06-27 | JBU57 | JFK → AUA | Jun 27, 13:24 UTC | Jun 27, 14:00 UTC | 35m |
| 2026-06-26 | JBU710 | SDQ → JFK | Jun 26, 16:29 UTC | Jun 27, 14:00 UTC | 21h 31m |
| 2026-06-25 | JBU803 | JFK → SJU | Jun 25, 20:11 UTC | Jun 26, 20:00 UTC | 23h 49m |
| 2026-06-25 | JBU1436 | STI → JFK | Jun 25, 14:11 UTC | Jun 26, 11:40 UTC | 21h 29m |
| 2026-06-25 | JBU636 | - | Jun 25, 03:50 UTC | Jun 25, 04:29 UTC | 40m |
| 2026-06-25 | JBU636 | STI → JFK | Jun 25, 01:16 UTC | Jun 25, 23:30 UTC | 22h 14m |
| 2026-06-24 | JBU2023 | - | Jun 24, 20:40 UTC | Jun 24, 21:24 UTC | 45m |
| 2026-06-24 | JBU2023 | BOS → BOS | Jun 24, 18:50 UTC | Jun 24, 18:55 UTC | 5m |
| 2026-06-23 | JBU330 | - | Jun 23, 22:05 UTC | Jun 24, 16:54 UTC | 18h 50m |
| 2026-06-23 | JBU330 | JFK → BOS | Jun 23, 21:29 UTC | Jun 24, 16:54 UTC | 19h 25m |
| 2026-06-23 | JBU1436 | JFK → JFK | Jun 23, 09:14 UTC | Jun 23, 17:50 UTC | 8h 35m |
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 N998JE page for operator, model, and routing details .