sensors Mode-S transponder
AD9AC9
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N976JT · AIRBUS A-321 · operated by JETBLUE AIRWAYS CORP
- Hex
- AD9AC9
- Octal
- 53315311
- Decimal
- 11,377,353
- Country
- US
- Tail
- N976JT
- Type
- A321
- Flights observed
- 284
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 22m ago
Current position
Country allocation
The ICAO 24-bit address AD9AC9 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 |
|---|---|---|---|
| JBU2677 | JetBlue Airways | 9 | 2026-05-20 |
| JBU523 | - | 8 | 2026-07-10 |
| JBU1757 | JetBlue Airways | 8 | 2026-05-04 |
| JBU387 | - | 7 | 2026-07-02 |
| JBU1707 | - | 7 | 2026-07-14 |
| JBU278 | - | 6 | 2026-06-20 |
| JBU277 | - | 6 | 2026-06-21 |
| JBU101 | JetBlue Airways | 6 | 2026-05-31 |
| JBU956 | JetBlue Airways | 5 | 2026-05-03 |
| JBU900 | JetBlue Airways | 5 | 2026-05-09 |
| JBU316 | JetBlue Airways | 5 | 2026-06-21 |
| JBU233 | JetBlue Airways | 5 | 2026-06-19 |
| JBU988 | - | 4 | 2026-07-09 |
| JBU957 | JetBlue Airways | 4 | 2026-06-05 |
| JBU608 | - | 4 | 2026-07-14 |
| JBU301 | JetBlue Airways | 4 | 2026-04-15 |
| JBU300 | JetBlue Airways | 4 | 2026-04-14 |
| JBU2821 | - | 4 | 2026-07-05 |
| JBU2801 | JetBlue Airways | 4 | 2026-06-01 |
| JBU2178 | JetBlue Airways | 4 | 2026-04-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU1707 | - | Jul 14, 13:40 UTC | Jul 14, 14:15 UTC | 35m |
| 2026-07-14 | JBU608 | LAS → FLL | Jul 14, 06:10 UTC | Jul 14, 10:35 UTC | 4h 25m |
| 2026-07-13 | JBU657 | - | Jul 13, 20:15 UTC | Jul 14, 01:00 UTC | 4h 45m |
| 2026-07-13 | JBU658 | LAS → FLL | Jul 13, 14:05 UTC | Jul 13, 18:35 UTC | 4h 30m |
| 2026-07-13 | JBU1511 | - | Jul 13, 04:45 UTC | Jul 13, 09:05 UTC | 4h 20m |
| 2026-07-12 | JBU1833 | - | Jul 12, 14:15 UTC | Jul 12, 19:50 UTC | 5h 35m |
| 2026-07-12 | JBU1833 | BOS → SFO | Jul 12, 14:14 UTC | Jul 13, 09:15 UTC | 19h 2m |
| 2026-07-11 | JBU220 | - | Jul 11, 21:05 UTC | Jul 12, 02:15 UTC | 5h 10m |
| 2026-07-11 | JBU219 | BOS → SAN | Jul 11, 14:10 UTC | Jul 11, 19:40 UTC | 5h 30m |
| 2026-07-10 | JBU523 | JFK → LAX | Jul 10, 14:02 UTC | Jul 11, 02:05 UTC | 12h 4m |
| 2026-07-10 | JBU523 | JFK → LAX | Jul 10, 14:05 UTC | Jul 10, 19:30 UTC | 5h 25m |
| 2026-07-10 | JBU948 | LAS → JFK | Jul 10, 07:05 UTC | Jul 10, 11:30 UTC | 4h 25m |
| 2026-07-10 | JBU777 | - | Jul 10, 00:20 UTC | Jul 10, 05:40 UTC | 5h 20m |
| 2026-07-09 | JBU988 | - | Jul 9, 17:15 UTC | Jul 9, 22:05 UTC | 4h 50m |
| 2026-07-09 | JBU123 | - | Jul 9, 10:05 UTC | Jul 9, 15:35 UTC | 5h 30m |
| 2026-07-08 | JBU216 | SFO → JFK | Jul 8, 20:10 UTC | Jul 9, 01:15 UTC | 5h 5m |
| 2026-07-08 | JBU833 | - | Jul 8, 12:55 UTC | Jul 8, 18:35 UTC | 5h 40m |
| 2026-07-07 | JBU1634 | - | Jul 7, 22:40 UTC | Jul 8, 04:00 UTC | 5h 20m |
| 2026-07-07 | JBU15 | JFK → SFO | Jul 7, 12:25 UTC | Jul 7, 18:00 UTC | 5h 35m |
| 2026-07-06 | JBU324 | - | Jul 6, 21:10 UTC | Jul 7, 02:30 UTC | 5h 20m |
| 2026-07-06 | JBU687 | - | Jul 6, 11:20 UTC | Jul 6, 16:45 UTC | 5h 25m |
| 2026-07-06 | JBU778 | LAS → BOS | Jul 6, 04:10 UTC | Jul 6, 08:50 UTC | 4h 40m |
| 2026-07-05 | JBU2821 | MCO → LAS | Jul 5, 12:30 UTC | Jul 5, 16:45 UTC | 4h 15m |
| 2026-07-04 | JBU2832 | - | Jul 4, 22:00 UTC | Jul 5, 02:05 UTC | 4h 5m |
| 2026-07-04 | JBU2821 | MCO → LAS | Jul 4, 12:15 UTC | Jul 4, 16:35 UTC | 4h 20m |
| 2026-07-03 | JBU511 | JFK → LAS | Jul 3, 15:10 UTC | Jul 3, 20:00 UTC | 4h 50m |
| 2026-07-03 | JBU511 | JFK → LAS | Jul 3, 15:08 UTC | Jul 4, 14:15 UTC | 23h 8m |
| 2026-07-03 | JBU1224 | - | Jul 3, 07:15 UTC | Jul 3, 12:10 UTC | 4h 55m |
| 2026-07-02 | JBU1700 | LAX → FLL | Jul 2, 16:15 UTC | Jul 3, 12:10 UTC | 19h 56m |
| 2026-07-02 | JBU387 | - | Jul 2, 04:35 UTC | Jul 2, 10:15 UTC | 5h 40m |
| 2026-07-02 | JBU387 | BOS → LAX | Jul 2, 04:31 UTC | Jul 3, 03:40 UTC | 23h 9m |
| 2026-07-01 | JBU1734 | - | Jul 1, 21:00 UTC | Jul 2, 02:10 UTC | 5h 10m |
| 2026-06-30 | JBU624 | LAX → JFK | Jun 30, 21:19 UTC | Jul 1, 15:50 UTC | 18h 32m |
| 2026-06-30 | JBU523 | JFK → LAX | Jun 30, 14:00 UTC | Jun 30, 19:15 UTC | 5h 15m |
| 2026-06-30 | JBU523 | JFK → LAX | Jun 30, 13:56 UTC | Jul 1, 10:15 UTC | 20h 20m |
| 2026-06-30 | JBU604 | - | Jun 30, 06:40 UTC | Jun 30, 11:40 UTC | 5h 0m |
| 2026-06-29 | JBU603 | JFK → YVR | Jun 29, 23:25 UTC | Jun 30, 05:00 UTC | 5h 36m |
| 2026-06-29 | JBU524 | - | Jun 29, 14:44 UTC | Jun 29, 19:35 UTC | 4h 50m |
| 2026-06-28 | JBU100 | - | Jun 28, 19:20 UTC | Jun 29, 00:00 UTC | 4h 40m |
| 2026-06-28 | JBU100 | LAX → FLL | Jun 28, 19:16 UTC | Jun 29, 18:14 UTC | 22h 59m |
| 2026-06-28 | JBU1573 | EWR → LAX | Jun 28, 12:25 UTC | Jun 28, 17:39 UTC | 5h 15m |
| 2026-06-28 | JBU1574 | - | Jun 28, 04:05 UTC | Jun 28, 08:50 UTC | 4h 45m |
| 2026-06-27 | JBU487 | - | Jun 27, 20:24 UTC | Jun 28, 02:20 UTC | 5h 55m |
| 2026-06-27 | JBU2501 | FXE → LAX | Jun 27, 03:09 UTC | Jun 27, 07:59 UTC | 4h 50m |
| 2026-06-27 | JBU2501 | FLL → LAX | Jun 27, 03:06 UTC | Jun 28, 02:14 UTC | 23h 9m |
| 2026-06-26 | JBU100 | - | Jun 26, 20:50 UTC | Jun 27, 01:24 UTC | 4h 35m |
| 2026-06-26 | JBU1574 | - | Jun 26, 04:04 UTC | Jun 26, 08:30 UTC | 4h 25m |
| 2026-06-26 | JBU1574 | LAX → EWR | Jun 26, 04:00 UTC | Jun 27, 01:24 UTC | 21h 25m |
| 2026-06-25 | JBU487 | - | Jun 25, 19:59 UTC | Jun 26, 02:05 UTC | 6h 5m |
| 2026-06-25 | JBU888 | - | Jun 25, 13:09 UTC | Jun 25, 18:00 UTC | 4h 50m |
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 N976JT page for operator, model, and routing details .