sensors Mode-S transponder
AD8836
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N971JT · AIRBUS A-321 · operated by JETBLUE AIRWAYS CORP
- Hex
- AD8836
- Octal
- 53304066
- Decimal
- 11,372,598
- Country
- US
- Tail
- N971JT
- Type
- A321
- Flights observed
- 237
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 3h ago
Current position
Country allocation
The ICAO 24-bit address AD8836 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 |
|---|---|---|---|
| JBU264 | - | 8 | 2026-07-11 |
| JBU904 | - | 7 | 2026-07-14 |
| JBU1002 | JetBlue Airways | 7 | 2026-05-19 |
| JBU2507 | JetBlue Airways | 6 | 2026-04-28 |
| JBU652 | JetBlue Airways | 5 | 2026-04-27 |
| JBU776 | JetBlue Airways | 4 | 2026-05-16 |
| JBU2924 | - | 4 | 2026-06-28 |
| JBU263 | - | 4 | 2026-07-03 |
| JBU255 | - | 4 | 2026-07-08 |
| JBU1924 | JetBlue Airways | 4 | 2026-05-12 |
| JBU1194 | JetBlue Airways | 4 | 2026-04-26 |
| JBU898 | JetBlue Airways | 3 | 2026-04-16 |
| JBU881 | JetBlue Airways | 3 | 2026-06-01 |
| JBU68 | JetBlue Airways | 3 | 2026-05-06 |
| JBU552 | JetBlue Airways | 3 | 2026-05-13 |
| JBU551 | JetBlue Airways | 3 | 2026-04-27 |
| JBU397 | - | 3 | 2026-07-01 |
| JBU321 | JetBlue Airways | 3 | 2026-04-18 |
| JBU2903 | - | 3 | 2026-07-13 |
| JBU2829 | JetBlue Airways | 3 | 2026-05-11 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU904 | - | Jul 14, 14:10 UTC | Jul 14, 15:00 UTC | 50m |
| 2026-07-13 | JBU2903 | - | Jul 13, 23:30 UTC | Jul 14, 02:45 UTC | 3h 15m |
| 2026-07-13 | JBU1059 | JFK → KIN | Jul 13, 01:36 UTC | Jul 14, 00:10 UTC | 22h 35m |
| 2026-07-12 | JBU152 | CUN → JFK | Jul 12, 18:54 UTC | Jul 13, 16:55 UTC | 22h 2m |
| 2026-07-12 | JBU151 | JFK → CUN | Jul 12, 14:02 UTC | Jul 13, 11:00 UTC | 20h 59m |
| 2026-07-12 | JBU151 | JFK → CUN | Jul 12, 14:05 UTC | Jul 12, 17:25 UTC | 3h 20m |
| 2026-07-12 | JBU1059 | JFK → JFK | Jul 12, 03:05 UTC | Jul 12, 11:30 UTC | 8h 25m |
| 2026-07-11 | JBU264 | SEA → JFK | Jul 11, 06:55 UTC | Jul 11, 11:30 UTC | 4h 35m |
| 2026-07-11 | JBU264 | SEA → JFK | Jul 11, 06:52 UTC | Jul 12, 05:30 UTC | 22h 39m |
| 2026-07-10 | JBU268 | PUJ → JFK | Jul 10, 17:01 UTC | Jul 10, 20:25 UTC | 3h 25m |
| 2026-07-10 | JBU869 | JFK → PUJ | Jul 10, 11:49 UTC | Jul 11, 11:30 UTC | 23h 42m |
| 2026-07-10 | JBU860 | KIN → JFK | Jul 10, 02:17 UTC | Jul 11, 01:30 UTC | 23h 14m |
| 2026-07-09 | JBU1436 | STI → JFK | Jul 9, 14:06 UTC | Jul 10, 12:30 UTC | 22h 24m |
| 2026-07-09 | JBU1436 | - | Jul 9, 09:20 UTC | Jul 9, 17:20 UTC | 8h 0m |
| 2026-07-08 | JBU255 | JFK → JFK | Jul 8, 14:35 UTC | Jul 8, 22:20 UTC | 7h 45m |
| 2026-07-07 | JBU280 | MBJ → JFK | Jul 7, 19:02 UTC | Jul 8, 15:50 UTC | 20h 49m |
| 2026-07-07 | JBU280 | MBJ → JFK | Jul 7, 14:52 UTC | Jul 8, 12:50 UTC | 21h 59m |
| 2026-07-07 | JBU161 | JFK → SMF | Jul 7, 00:11 UTC | Jul 7, 22:45 UTC | 22h 35m |
| 2026-07-06 | JBU255 | JFK → PLS | Jul 6, 14:02 UTC | Jul 7, 12:10 UTC | 22h 9m |
| 2026-07-05 | JBU156 | PLS → JFK | Jul 5, 19:32 UTC | Jul 6, 15:30 UTC | 19h 58m |
| 2026-07-05 | JBU255 | - | Jul 5, 15:15 UTC | Jul 5, 15:30 UTC | 15m |
| 2026-07-05 | JBU8447 | BOS → JFK | Jul 5, 12:57 UTC | Jul 5, 22:50 UTC | 9h 54m |
| 2026-07-05 | JBU8447 | BOS → JFK | Jul 5, 13:00 UTC | Jul 5, 13:45 UTC | 45m |
| 2026-07-04 | JBU58 | - | Jul 4, 22:05 UTC | Jul 5, 02:55 UTC | 4h 50m |
| 2026-07-04 | JBU57 | JFK → AUA | Jul 4, 16:55 UTC | Jul 4, 20:50 UTC | 3h 55m |
| 2026-07-04 | JBU264 | SEA → JFK | Jul 4, 06:10 UTC | Jul 4, 10:45 UTC | 4h 35m |
| 2026-07-03 | JBU263 | JFK → SEA | Jul 3, 22:35 UTC | Jul 4, 04:25 UTC | 5h 50m |
| 2026-07-03 | JBU710 | - | Jul 3, 10:55 UTC | Jul 3, 19:50 UTC | 8h 55m |
| 2026-07-02 | JBU1457 | - | Jul 2, 16:30 UTC | Jul 2, 19:30 UTC | 3h 0m |
| 2026-07-02 | JBU1457 | JFK → AUA | Jul 2, 16:25 UTC | Jul 3, 11:50 UTC | 19h 25m |
| 2026-07-02 | JBU1323 | - | Jul 2, 03:35 UTC | Jul 2, 13:25 UTC | 9h 50m |
| 2026-07-01 | JBU397 | BOS → SEA | Jul 1, 11:30 UTC | Jul 2, 05:10 UTC | 17h 41m |
| 2026-07-01 | JBU397 | - | Jul 1, 11:30 UTC | Jul 1, 13:30 UTC | 2h 0m |
| 2026-06-30 | JBU1830 | SDQ → BOS | Jun 30, 09:19 UTC | Jul 1, 03:25 UTC | 18h 7m |
| 2026-06-29 | JBU574 | AUA → BOS | Jun 29, 18:37 UTC | Jun 30, 17:30 UTC | 22h 54m |
| 2026-06-28 | JBU2924 | STI → BOS | Jun 28, 23:34 UTC | Jun 29, 23:29 UTC | 23h 56m |
| 2026-06-28 | JBU337 | - | Jun 28, 18:14 UTC | Jun 28, 20:04 UTC | 1h 50m |
| 2026-06-28 | JBU337 | JFK → STI | Jun 28, 18:12 UTC | Jun 29, 16:39 UTC | 22h 28m |
| 2026-06-27 | JBU2110 | JFK → JFK | Jun 27, 21:10 UTC | Jun 28, 15:24 UTC | 18h 15m |
| 2026-06-27 | JBU209 | JFK → SDQ | Jun 27, 09:24 UTC | Jun 27, 21:50 UTC | 12h 26m |
| 2026-06-26 | JBU1457 | JFK → AUA | Jun 26, 17:26 UTC | Jun 27, 09:55 UTC | 16h 29m |
| 2026-06-26 | JBU904 | - | Jun 26, 14:29 UTC | Jun 26, 15:34 UTC | 1h 5m |
| 2026-06-26 | JBU904 | - | Jun 26, 12:00 UTC | Jun 26, 12:14 UTC | 15m |
| 2026-06-26 | JBU904 | SJU → JFK | Jun 26, 11:57 UTC | Jun 27, 09:55 UTC | 21h 58m |
| 2026-06-25 | JBU2903 | - | Jun 25, 22:54 UTC | Jun 26, 02:20 UTC | 3h 25m |
| 2026-06-25 | JBU168 | JFK → JFK | Jun 25, 11:50 UTC | Jun 25, 20:09 UTC | 8h 20m |
| 2026-06-24 | JBU1528 | JFK → JFK | Jun 24, 14:45 UTC | Jun 24, 23:04 UTC | 8h 20m |
| 2026-06-24 | JBU454 | - | Jun 24, 08:20 UTC | Jun 24, 13:00 UTC | 4h 40m |
| 2026-06-24 | JBU355 | JFK → ONT | Jun 24, 00:40 UTC | Jun 24, 05:54 UTC | 5h 15m |
| 2026-06-23 | JBU156 | PLS → JFK | Jun 23, 20:10 UTC | Jun 23, 21:20 UTC | 1h 10m |
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 N971JT page for operator, model, and routing details .