sensors Mode-S transponder
AD6F93
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N965JT · AIRBUS A-321 · operated by JETBLUE AIRWAYS CORP
- Hex
- AD6F93
- Octal
- 53267623
- Decimal
- 11,366,291
- Country
- US
- Tail
- N965JT
- Type
- A321
- Flights observed
- 259
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address AD6F93 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 |
|---|---|---|---|
| JBU503 | - | 6 | 2026-07-09 |
| JBU1004 | - | 6 | 2026-07-09 |
| JBU209 | JetBlue Airways | 5 | 2026-06-03 |
| JBU1858 | - | 5 | 2026-07-10 |
| JBU1161 | JetBlue Airways | 5 | 2026-05-06 |
| JBU91 | JetBlue Airways | 4 | 2026-04-21 |
| JBU662 | - | 4 | 2026-07-05 |
| JBU2052 | JetBlue Airways | 4 | 2026-04-30 |
| JBU1827 | JetBlue Airways | 4 | 2026-05-11 |
| JBU1604 | - | 4 | 2026-06-18 |
| JBU921 | - | 3 | 2026-06-24 |
| JBU904 | - | 3 | 2026-07-01 |
| JBU769 | - | 3 | 2026-04-17 |
| JBU757 | - | 3 | 2026-07-10 |
| JBU721 | JetBlue Airways | 3 | 2026-04-18 |
| JBU592 | JetBlue Airways | 3 | 2026-04-21 |
| JBU361 | - | 3 | 2026-07-05 |
| JBU2904 | - | 3 | 2026-07-09 |
| JBU2903 | - | 3 | 2026-06-30 |
| JBU255 | - | 3 | 2026-07-11 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU869 | - | Jul 13, 10:20 UTC | Jul 13, 10:45 UTC | 25m |
| 2026-07-13 | JBU869 | JFK → PUJ | Jul 13, 10:20 UTC | Jul 14, 02:45 UTC | 16h 26m |
| 2026-07-12 | JBU1852 | - | Jul 12, 21:40 UTC | Jul 13, 01:10 UTC | 3h 30m |
| 2026-07-12 | JBU1851 | - | Jul 12, 15:30 UTC | Jul 12, 18:55 UTC | 3h 25m |
| 2026-07-12 | JBU2637 | JFK → JFK | Jul 12, 01:05 UTC | Jul 12, 13:20 UTC | 12h 15m |
| 2026-07-11 | JBU255 | JFK → PLS | Jul 11, 14:05 UTC | Jul 12, 12:45 UTC | 22h 41m |
| 2026-07-11 | JBU1059 | - | Jul 11, 01:05 UTC | Jul 11, 03:20 UTC | 2h 15m |
| 2026-07-11 | JBU1059 | JFK → KIN | Jul 11, 01:02 UTC | Jul 12, 00:45 UTC | 23h 44m |
| 2026-07-10 | JBU1858 | - | Jul 10, 20:35 UTC | Jul 10, 21:25 UTC | 50m |
| 2026-07-10 | JBU1858 | - | Jul 10, 17:25 UTC | Jul 10, 17:40 UTC | 15m |
| 2026-07-10 | JBU757 | - | Jul 10, 15:30 UTC | Jul 10, 15:50 UTC | 20m |
| 2026-07-10 | JBU757 | - | Jul 10, 12:30 UTC | Jul 10, 15:00 UTC | 2h 30m |
| 2026-07-09 | JBU1004 | - | Jul 9, 22:55 UTC | Jul 10, 00:20 UTC | 1h 25m |
| 2026-07-09 | JBU1004 | - | Jul 9, 20:35 UTC | Jul 9, 20:45 UTC | 10m |
| 2026-07-09 | JBU1004 | SJU → JFK | Jul 9, 20:32 UTC | Jul 10, 17:40 UTC | 21h 8m |
| 2026-07-09 | JBU503 | - | Jul 9, 18:05 UTC | Jul 9, 18:25 UTC | 20m |
| 2026-07-09 | JBU503 | - | Jul 9, 15:00 UTC | Jul 9, 15:45 UTC | 45m |
| 2026-07-09 | JBU2904 | - | Jul 9, 12:15 UTC | Jul 9, 13:00 UTC | 45m |
| 2026-07-08 | JBU8396 | ATL → BOS | Jul 8, 18:50 UTC | Jul 8, 20:20 UTC | 1h 30m |
| 2026-07-08 | JBU8396 | ATL → BOS | Jul 8, 16:32 UTC | Jul 9, 14:45 UTC | 22h 13m |
| 2026-07-05 | JBU662 | - | Jul 5, 19:20 UTC | Jul 5, 19:50 UTC | 30m |
| 2026-07-05 | JBU662 | - | Jul 5, 18:30 UTC | Jul 5, 18:45 UTC | 15m |
| 2026-07-05 | JBU662 | BGI → JFK | Jul 5, 18:24 UTC | Jul 6, 11:25 UTC | 17h 2m |
| 2026-07-05 | JBU361 | - | Jul 5, 16:25 UTC | Jul 5, 16:45 UTC | 20m |
| 2026-07-05 | JBU361 | - | Jul 5, 12:30 UTC | Jul 5, 15:50 UTC | 3h 20m |
| 2026-07-04 | JBU1869 | JFK → PUJ | Jul 4, 17:19 UTC | Jul 5, 16:45 UTC | 23h 27m |
| 2026-07-04 | JBU2904 | SJU → JFK | Jul 4, 09:01 UTC | Jul 5, 02:20 UTC | 17h 19m |
| 2026-07-04 | JBU303 | JFK → SJU | Jul 4, 01:10 UTC | Jul 5, 00:45 UTC | 23h 35m |
| 2026-07-03 | JBU779 | - | Jul 3, 12:40 UTC | Jul 3, 12:45 UTC | 5m |
| 2026-07-03 | JBU264 | SEA → JFK | Jul 3, 06:15 UTC | Jul 3, 10:55 UTC | 4h 40m |
| 2026-07-03 | JBU264 | SEA → JFK | Jul 3, 06:13 UTC | Jul 4, 04:30 UTC | 22h 17m |
| 2026-07-02 | JBU263 | JFK → SEA | Jul 2, 22:10 UTC | Jul 3, 03:40 UTC | 5h 30m |
| 2026-07-01 | JBU904 | - | Jul 1, 11:35 UTC | Jul 1, 15:00 UTC | 3h 25m |
| 2026-06-30 | JBU2903 | - | Jun 30, 03:15 UTC | Jun 30, 03:40 UTC | 25m |
| 2026-06-30 | JBU2903 | JFK → SJU | Jun 30, 00:24 UTC | Jun 30, 03:40 UTC | 3h 17m |
| 2026-06-30 | JBU2903 | - | Jun 30, 00:25 UTC | Jun 30, 01:04 UTC | 40m |
| 2026-06-29 | JBU156 | - | Jun 29, 19:49 UTC | Jun 29, 21:34 UTC | 1h 45m |
| 2026-06-28 | JBU158 | AUA → JFK | Jun 28, 22:09 UTC | Jun 29, 18:30 UTC | 20h 21m |
| 2026-06-28 | JBU1457 | JFK → AUA | Jun 28, 16:25 UTC | Jun 29, 14:44 UTC | 22h 20m |
| 2026-06-28 | JBU1323 | BOS → STI | Jun 28, 02:17 UTC | Jun 28, 22:24 UTC | 20h 8m |
| 2026-06-28 | JBU1323 | - | Jun 28, 02:20 UTC | Jun 28, 02:54 UTC | 35m |
| 2026-06-27 | JBU25 | BOS → BGI | Jun 27, 11:14 UTC | Jun 27, 22:35 UTC | 11h 20m |
| 2026-06-27 | JBU2924 | STI → BOS | Jun 27, 01:10 UTC | Jun 27, 23:04 UTC | 21h 55m |
| 2026-06-26 | JBU2924 | JFK → BOS | Jun 26, 20:24 UTC | Jun 27, 04:29 UTC | 8h 5m |
| 2026-06-26 | JBU602 | - | Jun 26, 15:10 UTC | Jun 26, 17:40 UTC | 2h 30m |
| 2026-06-26 | JBU1601 | JFK → FLL | Jun 26, 10:55 UTC | Jun 26, 13:19 UTC | 2h 25m |
| 2026-06-25 | JBU1532 | JFK → JFK | Jun 25, 13:35 UTC | Jun 26, 00:24 UTC | 10h 50m |
| 2026-06-24 | JBU921 | JFK → NAS | Jun 24, 17:25 UTC | Jun 25, 16:05 UTC | 22h 40m |
| 2026-06-24 | JBU2110 | SDQ → JFK | Jun 24, 11:36 UTC | Jun 25, 00:09 UTC | 12h 34m |
| 2026-06-23 | JBU1829 | - | Jun 23, 20:29 UTC | Jun 24, 14:45 UTC | 18h 15m |
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 N965JT page for operator, model, and routing details .