sensors Mode-S transponder
AD646E
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N962JT · AIRBUS A-321 · operated by JETBLUE AIRWAYS CORP
- Hex
- AD646E
- Octal
- 53262156
- Decimal
- 11,363,438
- Country
- US
- Tail
- N962JT
- Type
- A321
- Flights observed
- 278
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address AD646E 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 |
|---|---|---|---|
| JBU423 | - | 10 | 2026-07-08 |
| JBU333 | JetBlue Airways | 10 | 2026-06-11 |
| JBU607 | - | 8 | 2026-07-04 |
| JBU578 | JetBlue Airways | 7 | 2026-05-14 |
| JBU115 | JetBlue Airways | 7 | 2026-06-28 |
| JBU487 | JetBlue Airways | 6 | 2026-05-23 |
| JBU387 | - | 6 | 2026-06-29 |
| JBU288 | JetBlue Airways | 6 | 2026-06-18 |
| JBU1708 | - | 6 | 2026-07-03 |
| JBU716 | - | 5 | 2026-04-13 |
| JBU623 | JetBlue Airways | 5 | 2026-05-05 |
| JBU434 | - | 5 | 2026-06-12 |
| JBU424 | JetBlue Airways | 5 | 2026-05-31 |
| JBU300 | JetBlue Airways | 5 | 2026-04-28 |
| JBU2801 | JetBlue Airways | 5 | 2026-05-30 |
| JBU277 | JetBlue Airways | 5 | 2026-05-16 |
| JBU1734 | - | 5 | 2026-06-28 |
| JBU957 | JetBlue Airways | 4 | 2026-05-15 |
| JBU833 | - | 4 | 2026-07-12 |
| JBU733 | JetBlue Airways | 4 | 2026-06-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU2832 | LAS → MCO | Jul 13, 22:15 UTC | Jul 14, 02:30 UTC | 4h 15m |
| 2026-07-13 | JBU511 | JFK → LAS | Jul 13, 15:10 UTC | Jul 13, 19:40 UTC | 4h 30m |
| 2026-07-12 | JBU216 | SFO → JFK | Jul 12, 20:35 UTC | Jul 13, 01:50 UTC | 5h 15m |
| 2026-07-12 | JBU833 | - | Jul 12, 12:45 UTC | Jul 12, 18:25 UTC | 5h 40m |
| 2026-07-11 | JBU1401 | - | Jul 11, 15:15 UTC | Jul 11, 20:05 UTC | 4h 50m |
| 2026-07-11 | JBU1401 | FLL → LAX | Jul 11, 15:14 UTC | Jul 12, 13:30 UTC | 22h 17m |
| 2026-07-10 | JBU1700 | - | Jul 10, 15:55 UTC | Jul 10, 21:00 UTC | 5h 5m |
| 2026-07-10 | JBU1700 | LAX → FLL | Jul 10, 15:52 UTC | Jul 11, 15:30 UTC | 23h 39m |
| 2026-07-10 | JBU2073 | - | Jul 10, 03:10 UTC | Jul 10, 03:30 UTC | 20m |
| 2026-07-09 | JBU1874 | - | Jul 9, 21:00 UTC | Jul 10, 01:45 UTC | 4h 45m |
| 2026-07-09 | JBU1874 | LAX → EWR | Jul 9, 20:59 UTC | Jul 10, 19:30 UTC | 22h 31m |
| 2026-07-09 | JBU1573 | - | Jul 9, 11:25 UTC | Jul 9, 16:35 UTC | 5h 10m |
| 2026-07-09 | JBU1574 | - | Jul 9, 03:40 UTC | Jul 9, 08:35 UTC | 4h 55m |
| 2026-07-08 | JBU423 | - | Jul 8, 20:25 UTC | Jul 9, 01:50 UTC | 5h 25m |
| 2026-07-07 | JBU423 | - | Jul 7, 17:10 UTC | Jul 7, 22:15 UTC | 5h 5m |
| 2026-07-07 | JBU423 | JFK → LAX | Jul 7, 17:09 UTC | Jul 8, 12:40 UTC | 19h 32m |
| 2026-07-06 | JBU216 | OAK → JFK | Jul 6, 21:00 UTC | Jul 7, 01:55 UTC | 4h 55m |
| 2026-07-06 | JBU833 | BOS → SFO | Jul 6, 12:10 UTC | Jul 6, 17:50 UTC | 5h 40m |
| 2026-07-06 | JBU134 | SFO → BOS | Jul 6, 05:25 UTC | Jul 6, 10:25 UTC | 5h 0m |
| 2026-07-05 | JBU833 | BOS → SFO | Jul 5, 12:00 UTC | Jul 5, 17:40 UTC | 5h 40m |
| 2026-07-04 | JBU734 | - | Jul 4, 22:30 UTC | Jul 5, 03:45 UTC | 5h 15m |
| 2026-07-04 | JBU215 | JFK → SFO | Jul 4, 15:55 UTC | Jul 4, 21:20 UTC | 5h 25m |
| 2026-07-04 | JBU607 | - | Jul 4, 00:50 UTC | Jul 4, 05:20 UTC | 4h 30m |
| 2026-07-04 | JBU607 | FLL → LAS | Jul 4, 00:47 UTC | Jul 4, 23:30 UTC | 22h 44m |
| 2026-07-03 | JBU1708 | - | Jul 3, 18:55 UTC | Jul 3, 23:20 UTC | 4h 25m |
| 2026-07-03 | JBU2821 | MCO → LAS | Jul 3, 12:15 UTC | Jul 3, 16:35 UTC | 4h 20m |
| 2026-07-02 | JBU511 | JFK → LAS | Jul 2, 15:16 UTC | Jul 3, 13:30 UTC | 22h 15m |
| 2026-07-02 | JBU607 | - | Jul 2, 00:55 UTC | Jul 2, 05:25 UTC | 4h 30m |
| 2026-07-02 | JBU607 | FLL → LAS | Jul 2, 00:52 UTC | Jul 2, 23:30 UTC | 22h 39m |
| 2026-07-01 | JBU1708 | LAS → FLL | Jul 1, 18:45 UTC | Jul 1, 23:10 UTC | 4h 25m |
| 2026-07-01 | JBU1707 | - | Jul 1, 11:25 UTC | Jul 1, 15:55 UTC | 4h 30m |
| 2026-06-30 | JBU100 | - | Jun 30, 19:20 UTC | Jul 1, 00:00 UTC | 4h 40m |
| 2026-06-30 | JBU1574 | LAX → EWR | Jun 30, 03:59 UTC | Jul 1, 00:00 UTC | 20h 2m |
| 2026-06-29 | JBU2074 | - | Jun 29, 13:14 UTC | Jun 29, 17:55 UTC | 4h 40m |
| 2026-06-29 | JBU2074 | LAX → EWR | Jun 29, 13:11 UTC | Jun 30, 11:30 UTC | 22h 19m |
| 2026-06-29 | JBU387 | BOS → LAX | Jun 29, 01:00 UTC | Jun 29, 06:44 UTC | 5h 45m |
| 2026-06-28 | JBU1734 | - | Jun 28, 18:14 UTC | Jun 28, 23:25 UTC | 5h 10m |
| 2026-06-28 | JBU115 | JFK → MSY | Jun 28, 10:24 UTC | Jun 28, 16:35 UTC | 6h 10m |
| 2026-06-28 | JBU158 | - | Jun 28, 00:59 UTC | Jun 28, 01:50 UTC | 50m |
| 2026-06-27 | JBU158 | - | Jun 27, 21:25 UTC | Jun 27, 21:34 UTC | 10m |
| 2026-06-27 | JBU1457 | - | Jun 27, 19:09 UTC | Jun 27, 19:24 UTC | 15m |
| 2026-06-27 | JBU1457 | - | Jun 27, 15:24 UTC | Jun 27, 18:39 UTC | 3h 15m |
| 2026-06-26 | JBU224 | - | Jun 26, 20:20 UTC | Jun 27, 01:04 UTC | 4h 45m |
| 2026-06-26 | JBU323 | - | Jun 26, 12:50 UTC | Jun 26, 18:29 UTC | 5h 40m |
| 2026-06-25 | JBU1189 | JFK → JFK | Jun 25, 20:14 UTC | Jun 26, 08:50 UTC | 12h 35m |
| 2026-06-25 | JBU116 | JFK → SYR | Jun 25, 13:09 UTC | Jun 25, 17:49 UTC | 4h 40m |
| 2026-06-25 | JBU515 | JFK → SFO | Jun 25, 01:35 UTC | Jun 25, 07:39 UTC | 6h 5m |
| 2026-06-24 | JBU348 | - | Jun 24, 18:29 UTC | Jun 24, 22:55 UTC | 4h 25m |
| 2026-06-24 | JBU2821 | MCO → LAS | Jun 24, 12:25 UTC | Jun 24, 16:40 UTC | 4h 15m |
| 2026-06-23 | JBU2832 | LAS → MCO | Jun 23, 21:54 UTC | Jun 24, 02:00 UTC | 4h 5m |
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 N962JT page for operator, model, and routing details .