sensors Mode-S transponder
A67C3A
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N517JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORP
- Hex
- A67C3A
- Octal
- 51476072
- Decimal
- 10,910,778
- Country
- US
- Tail
- N517JB
- Type
- A320
- Flights observed
- 248
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address A67C3A 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 |
|---|---|---|---|
| JBU37 | JetBlue Airways | 11 | 2026-04-21 |
| JBU1152 | - | 11 | 2026-07-13 |
| JBU1098 | JetBlue Airways | 11 | 2026-05-18 |
| JBU94 | - | 10 | 2026-07-08 |
| JBU547 | - | 10 | 2026-07-13 |
| JBU138 | JetBlue Airways | 10 | 2026-04-21 |
| JBU1199 | JetBlue Airways | 9 | 2026-05-18 |
| JBU1076 | JetBlue Airways | 8 | 2026-05-20 |
| JBU546 | - | 7 | 2026-07-13 |
| JBU2875 | JetBlue Airways | 7 | 2026-05-19 |
| JBU768 | - | 6 | 2026-07-05 |
| JBU595 | JetBlue Airways | 6 | 2026-05-20 |
| JBU570 | JetBlue Airways | 6 | 2026-05-15 |
| JBU251 | - | 6 | 2026-07-13 |
| JBU169 | JetBlue Airways | 6 | 2026-05-15 |
| JBU495 | - | 5 | 2026-07-08 |
| JBU2423 | JetBlue Airways | 5 | 2026-07-03 |
| JBU1338 | JetBlue Airways | 5 | 2026-04-25 |
| JBU770 | - | 4 | 2026-07-10 |
| JBU655 | - | 4 | 2026-07-01 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU1152 | MCO → BOS | Jul 13, 20:10 UTC | Jul 14, 10:05 UTC | 13h 56m |
| 2026-07-13 | JBU1152 | MCO → BOS | Jul 13, 20:10 UTC | Jul 13, 22:50 UTC | 2h 40m |
| 2026-07-13 | JBU547 | - | Jul 13, 15:45 UTC | Jul 13, 18:05 UTC | 2h 20m |
| 2026-07-13 | JBU546 | - | Jul 13, 12:20 UTC | Jul 13, 14:40 UTC | 2h 20m |
| 2026-07-13 | JBU251 | - | Jul 13, 02:15 UTC | Jul 13, 04:50 UTC | 2h 35m |
| 2026-07-12 | JBU251 | BOS → BOS | Jul 12, 23:55 UTC | Jul 13, 00:01 UTC | 5m |
| 2026-07-12 | JBU1152 | - | Jul 12, 20:55 UTC | Jul 12, 23:25 UTC | 2h 30m |
| 2026-07-12 | JBU547 | - | Jul 12, 15:35 UTC | Jul 12, 17:55 UTC | 2h 20m |
| 2026-07-11 | JBU1152 | MCO → BOS | Jul 11, 20:21 UTC | Jul 12, 18:30 UTC | 22h 10m |
| 2026-07-11 | JBU670 | MCO → RIC | Jul 11, 14:10 UTC | Jul 12, 12:30 UTC | 22h 21m |
| 2026-07-11 | JBU2920 | ALB → MCO | Jul 11, 10:08 UTC | Jul 12, 05:30 UTC | 19h 23m |
| 2026-07-11 | JBU2919 | MCO → ALB | Jul 11, 01:39 UTC | Jul 11, 23:05 UTC | 21h 27m |
| 2026-07-10 | JBU1433 | MCO → SJU | Jul 10, 16:11 UTC | Jul 11, 14:30 UTC | 22h 20m |
| 2026-07-10 | JBU770 | MCO → RIC | Jul 10, 10:05 UTC | Jul 11, 04:01 UTC | 17h 56m |
| 2026-07-10 | JBU770 | - | Jul 10, 10:05 UTC | Jul 10, 11:35 UTC | 1h 30m |
| 2026-07-09 | JBU451 | - | Jul 9, 22:35 UTC | Jul 10, 01:35 UTC | 3h 0m |
| 2026-07-09 | JBU334 | - | Jul 9, 02:45 UTC | Jul 9, 05:15 UTC | 2h 30m |
| 2026-07-09 | JBU334 | SJU → MCO | Jul 9, 02:41 UTC | Jul 10, 01:35 UTC | 22h 55m |
| 2026-07-08 | JBU433 | MCO → SJU | Jul 8, 23:00 UTC | Jul 9, 01:30 UTC | 2h 30m |
| 2026-07-08 | JBU495 | - | Jul 8, 17:10 UTC | Jul 8, 19:25 UTC | 2h 15m |
| 2026-07-08 | JBU94 | MCO → HPN | Jul 8, 13:25 UTC | Jul 8, 15:40 UTC | 2h 15m |
| 2026-07-07 | JBU8153 | BOS → MCO | Jul 7, 17:35 UTC | Jul 7, 20:10 UTC | 2h 35m |
| 2026-07-06 | JBU547 | ISP → MCO | Jul 6, 16:06 UTC | Jul 7, 08:45 UTC | 16h 39m |
| 2026-07-05 | JBU451 | BOS → MCO | Jul 5, 21:52 UTC | Jul 6, 18:50 UTC | 20h 58m |
| 2026-07-05 | JBU252 | MCO → BOS | Jul 5, 17:39 UTC | Jul 6, 16:30 UTC | 22h 52m |
| 2026-07-05 | JBU768 | PSE → MCO | Jul 5, 12:47 UTC | Jul 6, 12:30 UTC | 23h 44m |
| 2026-07-04 | JBU521 | MCO → MBJ | Jul 4, 17:21 UTC | Jul 5, 15:30 UTC | 22h 10m |
| 2026-07-04 | JBU2265 | MCO → STI | Jul 4, 09:33 UTC | Jul 5, 08:30 UTC | 22h 57m |
| 2026-07-04 | JBU195 | HPN → MCO | Jul 4, 02:03 UTC | Jul 4, 22:00 UTC | 19h 57m |
| 2026-07-03 | JBU2423 | DCA → MCO | Jul 3, 10:07 UTC | Jul 4, 08:30 UTC | 22h 24m |
| 2026-07-02 | JBU2424 | MCO → DCA | Jul 2, 21:48 UTC | Jul 3, 20:15 UTC | 22h 27m |
| 2026-07-02 | JBU1806 | BNA → BOS | Jul 2, 03:05 UTC | Jul 2, 23:45 UTC | 20h 40m |
| 2026-07-01 | JBU655 | - | Jul 1, 13:35 UTC | Jul 1, 14:30 UTC | 55m |
| 2026-07-01 | JBU656 | - | Jul 1, 10:05 UTC | Jul 1, 12:20 UTC | 2h 15m |
| 2026-07-01 | JBU656 | MCO → SYR | Jul 1, 10:03 UTC | Jul 2, 05:30 UTC | 19h 28m |
| 2026-07-01 | JBU251 | - | Jul 1, 03:20 UTC | Jul 1, 05:50 UTC | 2h 30m |
| 2026-06-30 | JBU1152 | - | Jun 30, 23:20 UTC | Jul 1, 01:55 UTC | 2h 35m |
| 2026-06-30 | JBU547 | - | Jun 30, 21:05 UTC | Jun 30, 21:45 UTC | 40m |
| 2026-06-30 | JBU547 | ISP → JAX | Jun 30, 16:25 UTC | Jun 30, 19:00 UTC | 2h 35m |
| 2026-06-30 | JBU546 | - | Jun 30, 15:00 UTC | Jun 30, 15:20 UTC | 20m |
| 2026-06-30 | JBU546 | - | Jun 30, 13:05 UTC | Jun 30, 14:55 UTC | 1h 50m |
| 2026-06-30 | JBU251 | - | Jun 30, 01:19 UTC | Jun 30, 03:45 UTC | 2h 26m |
| 2026-06-29 | JBU1152 | MCO → BOS | Jun 29, 20:59 UTC | Jun 29, 23:29 UTC | 2h 30m |
| 2026-06-29 | JBU547 | - | Jun 29, 16:59 UTC | Jun 29, 19:15 UTC | 2h 15m |
| 2026-06-29 | JBU546 | - | Jun 29, 12:14 UTC | Jun 29, 14:29 UTC | 2h 15m |
| 2026-06-28 | JBU547 | ISP → MCO | Jun 28, 15:30 UTC | Jun 29, 14:29 UTC | 23h 0m |
| 2026-06-27 | JBU1152 | MCO → JFK | Jun 27, 20:23 UTC | Jun 28, 18:05 UTC | 21h 42m |
| 2026-06-27 | JBU1152 | MCO → JFK | Jun 27, 20:24 UTC | Jun 27, 23:34 UTC | 3h 10m |
| 2026-06-27 | JBU655 | - | Jun 27, 13:40 UTC | Jun 27, 15:55 UTC | 2h 15m |
| 2026-06-26 | JBU1152 | MCO → BOS | Jun 26, 20:24 UTC | Jun 27, 16:00 UTC | 19h 36m |
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 N517JB page for operator, model, and routing details .