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
- 291
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- Jul 26, 21:15 UTC
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 |
| JBU987 | JetBlue Airways | 10 | 2026-07-26 |
| 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 |
| JBU768 | JetBlue Airways | 7 | 2026-07-20 |
| JBU547 | - | 7 | 2026-07-16 |
| JBU546 | - | 7 | 2026-07-16 |
| JBU299 | JetBlue Airways | 7 | 2026-05-14 |
| JBU969 | - | 6 | 2026-06-27 |
| JBU798 | JetBlue Airways | 6 | 2026-07-25 |
| 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 |
| JBU1152 | - | 6 | 2026-07-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | JBU987 | ORH → MCO | Jul 26, 19:00 UTC | Jul 26, 21:15 UTC | 2h 15m |
| 2026-07-26 | JBU588 | LAX → BOS | Jul 26, 15:30 UTC | Jul 26, 17:50 UTC | 2h 20m |
| 2026-07-26 | JBU599 | LGA → MCO | Jul 26, 11:50 UTC | Jul 26, 14:00 UTC | 2h 10m |
| 2026-07-25 | JBU798 | MCO → LGA | Jul 25, 23:30 UTC | Jul 26, 01:45 UTC | 2h 15m |
| 2026-07-25 | JBU987 | ORH → MCO | Jul 25, 18:45 UTC | Jul 25, 21:10 UTC | 2h 25m |
| 2026-07-25 | JBU588 | LAX → BOS | Jul 25, 15:05 UTC | Jul 25, 17:30 UTC | 2h 25m |
| 2026-07-25 | JBU599 | LGA → MCO | Jul 25, 10:25 UTC | Jul 25, 12:30 UTC | 2h 5m |
| 2026-07-24 | JBU798 | MCO → LGA | Jul 24, 23:45 UTC | Jul 25, 02:00 UTC | 2h 15m |
| 2026-07-24 | JBU987 | ORH → MCO | Jul 24, 18:50 UTC | Jul 24, 21:05 UTC | 2h 15m |
| 2026-07-24 | JBU588 | LAX → BOS | Jul 24, 15:05 UTC | Jul 24, 17:30 UTC | 2h 25m |
| 2026-07-22 | JBU798 | MCO → LGA | Jul 22, 23:35 UTC | Jul 23, 02:00 UTC | 2h 25m |
| 2026-07-22 | JBU798 | MCO → LGA | Jul 22, 23:31 UTC | Jul 23, 15:40 UTC | 16h 9m |
| 2026-07-22 | JBU987 | ORH → MCO | Jul 22, 19:30 UTC | Jul 22, 22:05 UTC | 2h 35m |
| 2026-07-22 | JBU798 | MCO → LGA | Jul 22, 02:43 UTC | Jul 23, 01:15 UTC | 22h 32m |
| 2026-07-21 | JBU987 | ORH → MCO | Jul 21, 20:01 UTC | Jul 22, 19:15 UTC | 23h 14m |
| 2026-07-21 | JBU588 | LAX → BOS | Jul 21, 15:07 UTC | Jul 22, 13:15 UTC | 22h 8m |
| 2026-07-21 | JBU599 | LGA → MCO | Jul 21, 11:33 UTC | Jul 22, 11:15 UTC | 23h 42m |
| 2026-07-21 | JBU798 | MCO → LGA | Jul 21, 01:54 UTC | Jul 21, 23:35 UTC | 21h 41m |
| 2026-07-20 | JBU768 | PSE → MCO | Jul 20, 15:05 UTC | Jul 20, 16:00 UTC | 55m |
| 2026-07-20 | JBU768 | PSE → MCO | Jul 20, 13:22 UTC | Jul 21, 13:15 UTC | 23h 53m |
| 2026-07-20 | JBU767 | - | Jul 20, 09:50 UTC | Jul 20, 10:25 UTC | 35m |
| 2026-07-19 | JBU768 | PSE → MCO | Jul 19, 13:49 UTC | Jul 20, 10:25 UTC | 20h 37m |
| 2026-07-18 | JBU987 | ORH → MCO | Jul 18, 19:09 UTC | Jul 19, 17:15 UTC | 22h 7m |
| 2026-07-18 | JBU2919 | BOS → SAN | Jul 18, 00:59 UTC | Jul 18, 22:55 UTC | 21h 57m |
| 2026-07-17 | JBU770 | MCO → RIC | Jul 17, 10:15 UTC | Jul 18, 03:25 UTC | 17h 11m |
| 2026-07-16 | JBU1152 | MCO → BOS | Jul 16, 20:08 UTC | Jul 17, 19:15 UTC | 23h 7m |
| 2026-07-16 | JBU1152 | MCO → BOS | Jul 16, 20:09 UTC | Jul 16, 23:15 UTC | 3h 5m |
| 2026-07-16 | JBU547 | - | Jul 16, 15:49 UTC | Jul 16, 18:00 UTC | 2h 10m |
| 2026-07-16 | JBU546 | - | Jul 16, 12:30 UTC | Jul 16, 14:45 UTC | 2h 15m |
| 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 |
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 .