sensors Mode-S transponder
AD6BDC
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N964JT · AIRBUS A-321 · operated by JETBLUE AIRWAYS CORP
- Hex
- AD6BDC
- Octal
- 53265734
- Decimal
- 11,365,340
- Country
- US
- Tail
- N964JT
- Type
- A321
- Flights observed
- 269
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 48m ago
Current position
Country allocation
The ICAO 24-bit address AD6BDC 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 |
|---|---|---|---|
| JBU948 | - | 7 | 2026-06-19 |
| JBU411 | JetBlue Airways | 7 | 2026-05-10 |
| JBU177 | JetBlue Airways | 6 | 2026-05-10 |
| JBU1633 | - | 6 | 2026-07-03 |
| JBU900 | JetBlue Airways | 5 | 2026-05-11 |
| JBU289 | JetBlue Airways | 5 | 2026-04-30 |
| JBU1757 | JetBlue Airways | 5 | 2026-06-01 |
| JBU1707 | - | 5 | 2026-06-18 |
| JBU1700 | - | 5 | 2026-07-11 |
| JBU1177 | - | 5 | 2026-06-24 |
| JBU988 | - | 4 | 2026-07-06 |
| JBU956 | JetBlue Airways | 4 | 2026-05-31 |
| JBU920 | JetBlue Airways | 4 | 2026-04-17 |
| JBU620 | JetBlue Airways | 4 | 2026-05-26 |
| JBU619 | JetBlue Airways | 4 | 2026-05-29 |
| JBU608 | JetBlue Airways | 4 | 2026-06-12 |
| JBU423 | JetBlue Airways | 4 | 2026-06-05 |
| JBU2648 | JetBlue Airways | 4 | 2026-04-15 |
| JBU188 | - | 4 | 2026-07-02 |
| JBU1524 | JetBlue Airways | 4 | 2026-05-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU387 | BOS → LAX | Jul 14, 03:04 UTC | Jul 14, 17:00 UTC | 13h 57m |
| 2026-07-13 | JBU1734 | - | Jul 13, 20:15 UTC | Jul 13, 20:45 UTC | 30m |
| 2026-07-13 | JBU115 | JFK → SFO | Jul 13, 13:30 UTC | Jul 14, 08:05 UTC | 18h 36m |
| 2026-07-13 | JBU115 | JFK → SFO | Jul 13, 13:30 UTC | Jul 13, 18:55 UTC | 5h 25m |
| 2026-07-12 | JBU624 | - | Jul 12, 21:55 UTC | Jul 13, 03:01 UTC | 5h 5m |
| 2026-07-12 | JBU700 | LAX → FLL | Jul 12, 06:38 UTC | Jul 13, 03:10 UTC | 20h 33m |
| 2026-07-11 | JBU101 | - | Jul 11, 22:55 UTC | Jul 12, 03:30 UTC | 4h 35m |
| 2026-07-11 | JBU101 | FLL → LAX | Jul 11, 22:53 UTC | Jul 12, 20:20 UTC | 21h 28m |
| 2026-07-11 | JBU1700 | LAX → FLL | Jul 11, 16:15 UTC | Jul 11, 21:15 UTC | 5h 0m |
| 2026-07-10 | JBU223 | JFK → LAX | Jul 10, 11:50 UTC | Jul 10, 17:20 UTC | 5h 30m |
| 2026-07-10 | JBU16 | - | Jul 10, 03:45 UTC | Jul 10, 08:35 UTC | 4h 50m |
| 2026-07-09 | JBU415 | JFK → SFO | Jul 9, 20:15 UTC | Jul 10, 02:05 UTC | 5h 50m |
| 2026-07-09 | JBU2501 | FLL → LAX | Jul 9, 01:53 UTC | Jul 10, 00:55 UTC | 23h 3m |
| 2026-07-08 | JBU1573 | EWR → LAX | Jul 8, 11:40 UTC | Jul 8, 16:40 UTC | 5h 0m |
| 2026-07-08 | JBU1573 | EWR → LAX | Jul 8, 11:39 UTC | Jul 9, 06:45 UTC | 19h 7m |
| 2026-07-08 | JBU1574 | - | Jul 8, 04:05 UTC | Jul 8, 08:55 UTC | 4h 50m |
| 2026-07-07 | JBU1401 | - | Jul 7, 21:10 UTC | Jul 8, 01:55 UTC | 4h 45m |
| 2026-07-07 | JBU8371 | - | Jul 7, 16:25 UTC | Jul 7, 19:10 UTC | 2h 45m |
| 2026-07-07 | JBU8371 | BOS → BOS | Jul 7, 14:00 UTC | Jul 7, 14:05 UTC | 5m |
| 2026-07-07 | JBU777 | BOS → BOS | Jul 7, 02:30 UTC | Jul 7, 02:35 UTC | 5m |
| 2026-07-06 | JBU988 | - | Jul 6, 18:50 UTC | Jul 7, 00:00 UTC | 5h 10m |
| 2026-07-06 | JBU123 | JFK → LAX | Jul 6, 10:15 UTC | Jul 6, 15:35 UTC | 5h 20m |
| 2026-07-06 | JBU924 | - | Jul 6, 06:00 UTC | Jul 6, 06:55 UTC | 55m |
| 2026-07-05 | JBU924 | - | Jul 5, 22:25 UTC | Jul 6, 04:45 UTC | 6h 20m |
| 2026-07-05 | JBU1487 | - | Jul 5, 15:20 UTC | Jul 5, 20:50 UTC | 5h 30m |
| 2026-07-04 | JBU220 | SAN → BOS | Jul 4, 20:54 UTC | Jul 5, 19:00 UTC | 22h 7m |
| 2026-07-04 | JBU134 | SFO → BOS | Jul 4, 05:55 UTC | Jul 5, 02:35 UTC | 20h 40m |
| 2026-07-03 | JBU733 | BOS → SFO | Jul 3, 22:02 UTC | Jul 4, 19:00 UTC | 20h 58m |
| 2026-07-03 | JBU1216 | BUF → BOS | Jul 3, 17:40 UTC | Jul 4, 17:00 UTC | 23h 21m |
| 2026-07-03 | JBU1633 | BOS → SFO | Jul 3, 01:35 UTC | Jul 3, 07:40 UTC | 6h 5m |
| 2026-07-03 | JBU1633 | BOS → SFO | Jul 3, 01:35 UTC | Jul 4, 01:00 UTC | 23h 26m |
| 2026-07-03 | JBU1633 | BOS → BOS | Jul 3, 00:55 UTC | Jul 3, 01:00 UTC | 5m |
| 2026-07-02 | JBU1633 | BOS → BOS | Jul 2, 23:35 UTC | Jul 2, 23:40 UTC | 5m |
| 2026-07-02 | JBU1633 | BOS → BOS | Jul 2, 21:30 UTC | Jul 2, 21:40 UTC | 10m |
| 2026-07-02 | JBU1216 | - | Jul 2, 18:30 UTC | Jul 2, 19:30 UTC | 1h 0m |
| 2026-07-02 | JBU1215 | BOS → BUF | Jul 2, 16:25 UTC | Jul 2, 17:25 UTC | 1h 0m |
| 2026-07-02 | JBU188 | BOS → BOS | Jul 2, 06:30 UTC | Jul 2, 06:35 UTC | 5m |
| 2026-07-01 | JBU188 | LAX → BOS | Jul 1, 22:45 UTC | Jul 2, 04:05 UTC | 5h 20m |
| 2026-07-01 | JBU1123 | JFK → LAX | Jul 1, 15:05 UTC | Jul 1, 20:25 UTC | 5h 20m |
| 2026-07-01 | JBU607 | - | Jul 1, 01:00 UTC | Jul 1, 05:30 UTC | 4h 30m |
| 2026-07-01 | JBU607 | FLL → LAS | Jul 1, 00:59 UTC | Jul 1, 23:00 UTC | 22h 2m |
| 2026-06-30 | JBU1708 | LAS → FLL | Jun 30, 18:45 UTC | Jun 30, 23:15 UTC | 4h 30m |
| 2026-06-30 | JBU278 | - | Jun 30, 04:00 UTC | Jun 30, 09:15 UTC | 5h 15m |
| 2026-06-30 | JBU278 | SFO → FLL | Jun 30, 03:59 UTC | Jul 1, 03:00 UTC | 23h 2m |
| 2026-06-29 | JBU233 | BOS → SFO | Jun 29, 20:35 UTC | Jun 30, 02:30 UTC | 5h 56m |
| 2026-06-28 | JBU1633 | BOS → SFO | Jun 28, 23:20 UTC | Jun 29, 22:59 UTC | 23h 40m |
| 2026-06-28 | JBU8178 | - | Jun 28, 15:49 UTC | Jun 28, 19:29 UTC | 3h 40m |
| 2026-06-28 | JBU8178 | SXM → BOS | Jun 28, 15:25 UTC | Jun 29, 12:55 UTC | 21h 30m |
| 2026-06-27 | JBU8178 | - | Jun 27, 17:04 UTC | Jun 28, 16:05 UTC | 23h 0m |
| 2026-06-27 | JBU1877 | BOS → SXM | Jun 27, 13:09 UTC | Jun 27, 17:14 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 N964JT page for operator, model, and routing details .