sensors Mode-S transponder
A64D4D
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N505JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORP
- Hex
- A64D4D
- Octal
- 51446515
- Decimal
- 10,898,765
- Country
- US
- Tail
- N505JB
- Type
- A320
- Flights observed
- 262
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address A64D4D 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 |
|---|---|---|---|
| JBU169 | JetBlue Airways | 11 | 2026-05-20 |
| JBU598 | JetBlue Airways | 10 | 2026-05-12 |
| JBU570 | JetBlue Airways | 9 | 2026-05-20 |
| JBU252 | - | 9 | 2026-07-13 |
| JBU240 | JetBlue Airways | 9 | 2026-05-15 |
| JBU1761 | JetBlue Airways | 9 | 2026-05-13 |
| JBU451 | - | 8 | 2026-07-11 |
| JBU299 | JetBlue Airways | 7 | 2026-05-14 |
| JBU969 | - | 6 | 2026-06-27 |
| JBU547 | - | 6 | 2026-07-10 |
| JBU546 | - | 6 | 2026-07-10 |
| JBU2424 | - | 6 | 2026-07-06 |
| JBU2423 | JetBlue Airways | 6 | 2026-07-07 |
| JBU241 | - | 6 | 2026-07-09 |
| JBU1962 | JetBlue Airways | 6 | 2026-05-12 |
| JBU1923 | JetBlue Airways | 6 | 2026-06-02 |
| JBU670 | - | 5 | 2026-06-27 |
| JBU606 | - | 5 | 2026-07-01 |
| JBU251 | - | 5 | 2026-07-11 |
| JBU987 | JetBlue Airways | 4 | 2026-06-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU252 | MCO → BOS | Jul 13, 17:57 UTC | Jul 14, 02:50 UTC | 8h 54m |
| 2026-07-13 | JBU252 | MCO → BOS | Jul 13, 18:00 UTC | Jul 13, 20:35 UTC | 2h 35m |
| 2026-07-13 | JBU729 | MCO → MCO | Jul 13, 09:15 UTC | Jul 13, 15:15 UTC | 6h 0m |
| 2026-07-11 | JBU451 | BOS → MCO | Jul 11, 22:55 UTC | Jul 12, 19:30 UTC | 20h 36m |
| 2026-07-11 | JBU52 | - | Jul 11, 18:55 UTC | Jul 11, 21:15 UTC | 2h 20m |
| 2026-07-11 | JBU52 | MCO → BOS | Jul 11, 18:50 UTC | Jul 12, 15:10 UTC | 20h 21m |
| 2026-07-11 | JBU768 | - | Jul 11, 15:15 UTC | Jul 11, 16:15 UTC | 1h 0m |
| 2026-07-11 | JBU768 | - | Jul 11, 13:35 UTC | Jul 11, 13:45 UTC | 10m |
| 2026-07-11 | JBU767 | - | Jul 11, 09:55 UTC | Jul 11, 10:35 UTC | 40m |
| 2026-07-11 | JBU251 | - | Jul 11, 02:05 UTC | Jul 11, 04:40 UTC | 2h 35m |
| 2026-07-10 | JBU1152 | MCO → BOS | Jul 10, 21:15 UTC | Jul 10, 23:40 UTC | 2h 25m |
| 2026-07-10 | JBU547 | - | Jul 10, 15:40 UTC | Jul 10, 17:55 UTC | 2h 15m |
| 2026-07-10 | JBU546 | MCO → ISP | Jul 10, 12:10 UTC | Jul 10, 14:25 UTC | 2h 15m |
| 2026-07-09 | JBU241 | MCO → NAS | Jul 9, 16:27 UTC | Jul 10, 14:25 UTC | 21h 58m |
| 2026-07-09 | JBU430 | MCO → BQN | Jul 9, 09:10 UTC | Jul 10, 05:15 UTC | 20h 5m |
| 2026-07-08 | JBU2324 | MCO → DCA | Jul 8, 17:52 UTC | Jul 9, 17:05 UTC | 23h 13m |
| 2026-07-08 | JBU699 | LGA → MCO | Jul 8, 03:55 UTC | Jul 9, 03:05 UTC | 23h 10m |
| 2026-07-07 | JBU2423 | DCA → MCO | Jul 7, 10:21 UTC | Jul 8, 06:05 UTC | 19h 44m |
| 2026-07-06 | JBU2424 | MCO → DCA | Jul 6, 23:53 UTC | Jul 7, 23:15 UTC | 23h 23m |
| 2026-07-06 | JBU251 | BOS → MCO | Jul 6, 03:35 UTC | Jul 6, 06:00 UTC | 2h 25m |
| 2026-07-06 | JBU251 | BOS → MCO | Jul 6, 03:30 UTC | Jul 7, 02:05 UTC | 22h 35m |
| 2026-07-05 | JBU1152 | - | Jul 5, 19:50 UTC | Jul 5, 22:20 UTC | 2h 30m |
| 2026-07-05 | JBU547 | - | Jul 5, 16:00 UTC | Jul 5, 18:10 UTC | 2h 10m |
| 2026-07-05 | JBU546 | - | Jul 5, 12:15 UTC | Jul 5, 14:25 UTC | 2h 10m |
| 2026-07-04 | JBU767 | MCO → PSE | Jul 4, 18:22 UTC | Jul 5, 17:15 UTC | 22h 53m |
| 2026-07-04 | JBU847 | - | Jul 4, 14:40 UTC | Jul 4, 15:15 UTC | 35m |
| 2026-07-04 | JBU847 | ISP → MCO | Jul 4, 14:35 UTC | Jul 5, 13:15 UTC | 22h 40m |
| 2026-07-04 | JBU546 | MCO → ISP | Jul 4, 10:38 UTC | Jul 5, 00:30 UTC | 13h 52m |
| 2026-07-04 | JBU546 | - | Jul 4, 10:40 UTC | Jul 4, 13:30 UTC | 2h 50m |
| 2026-07-03 | JBU451 | BOS → MCO | Jul 3, 22:40 UTC | Jul 4, 01:05 UTC | 2h 25m |
| 2026-07-03 | JBU252 | MCO → BOS | Jul 3, 17:50 UTC | Jul 3, 20:15 UTC | 2h 25m |
| 2026-07-03 | JBU655 | - | Jul 3, 13:45 UTC | Jul 3, 16:10 UTC | 2h 25m |
| 2026-07-03 | JBU656 | - | Jul 3, 10:05 UTC | Jul 3, 12:15 UTC | 2h 10m |
| 2026-07-02 | JBU451 | - | Jul 2, 21:45 UTC | Jul 3, 00:15 UTC | 2h 30m |
| 2026-07-02 | JBU451 | BOS → BOS | Jul 2, 21:20 UTC | Jul 2, 21:25 UTC | 5m |
| 2026-07-02 | JBU252 | MCO → BOS | Jul 2, 17:40 UTC | Jul 2, 20:05 UTC | 2h 25m |
| 2026-07-01 | JBU1294 | MCO → HPN | Jul 1, 21:57 UTC | Jul 2, 21:15 UTC | 23h 18m |
| 2026-07-01 | JBU606 | SDQ → MCO | Jul 1, 17:55 UTC | Jul 2, 16:05 UTC | 22h 10m |
| 2026-07-01 | JBU1205 | MCO → SDQ | Jul 1, 14:24 UTC | Jul 2, 12:30 UTC | 22h 6m |
| 2026-07-01 | JBU1205 | - | Jul 1, 14:25 UTC | Jul 1, 15:10 UTC | 45m |
| 2026-07-01 | JBU769 | - | Jul 1, 10:05 UTC | Jul 1, 11:45 UTC | 1h 40m |
| 2026-07-01 | JBU770 | MCO → RIC | Jul 1, 02:50 UTC | Jul 1, 04:20 UTC | 1h 30m |
| 2026-06-30 | JBU137 | BDL → MCO | Jun 30, 22:10 UTC | Jul 1, 00:35 UTC | 2h 25m |
| 2026-06-30 | JBU2938 | - | Jun 30, 16:50 UTC | Jun 30, 19:10 UTC | 2h 20m |
| 2026-06-30 | JBU768 | - | Jun 30, 12:50 UTC | Jun 30, 15:25 UTC | 2h 35m |
| 2026-06-29 | JBU495 | HPN → MCO | Jun 29, 17:09 UTC | Jun 30, 15:15 UTC | 22h 7m |
| 2026-06-29 | JBU94 | - | Jun 29, 13:14 UTC | Jun 29, 15:34 UTC | 2h 20m |
| 2026-06-29 | JBU94 | MCO → HPN | Jun 29, 13:13 UTC | Jun 30, 09:55 UTC | 20h 43m |
| 2026-06-29 | JBU2423 | DCA → MCO | Jun 29, 10:10 UTC | Jun 29, 11:50 UTC | 1h 40m |
| 2026-06-28 | JBU2423 | DCA → MCO | Jun 28, 10:24 UTC | Jun 29, 00:29 UTC | 14h 6m |
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 N505JB page for operator, model, and routing details .