sensors Mode-S transponder
A65C29
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N509JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORPORATION
- Hex
- A65C29
- Octal
- 51456051
- Decimal
- 10,902,569
- Country
- US
- Tail
- N509JB
- Type
- A320
- Flights observed
- 318
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address A65C29 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 |
|---|---|---|---|
| JBU2476 | JetBlue Airways | 5 | 2026-05-06 |
| JBU613 | - | 4 | 2026-07-11 |
| JBU548 | - | 4 | 2026-07-10 |
| JBU460 | - | 4 | 2026-06-17 |
| JBU371 | JetBlue Airways | 4 | 2026-04-15 |
| JBU2929 | JetBlue Airways | 4 | 2026-05-07 |
| JBU2330 | JetBlue Airways | 4 | 2026-05-17 |
| JBU2028 | JetBlue Airways | 4 | 2026-05-05 |
| JBU1475 | JetBlue Airways | 4 | 2026-05-30 |
| JBU1172 | - | 4 | 2026-06-29 |
| JBU959 | - | 3 | 2026-06-17 |
| JBU754 | - | 3 | 2026-07-13 |
| JBU753 | JetBlue Airways | 3 | 2026-06-11 |
| JBU737 | JetBlue Airways | 3 | 2026-05-05 |
| JBU703 | JetBlue Airways | 3 | 2026-04-24 |
| JBU563 | JetBlue Airways | 3 | 2026-05-15 |
| JBU406 | JetBlue Airways | 3 | 2026-06-05 |
| JBU305 | - | 3 | 2026-07-03 |
| JBU2930 | JetBlue Airways | 3 | 2026-05-07 |
| JBU2406 | - | 3 | 2026-04-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-15 | JBU368 | - | Jul 15, 01:05 UTC | Jul 15, 03:35 UTC | 2h 30m |
| 2026-07-14 | JBU2087 | - | Jul 14, 21:20 UTC | Jul 14, 23:50 UTC | 2h 29m |
| 2026-07-14 | JBU388 | - | Jul 14, 17:40 UTC | Jul 14, 20:10 UTC | 2h 30m |
| 2026-07-14 | JBU1241 | - | Jul 14, 14:00 UTC | Jul 14, 16:35 UTC | 2h 35m |
| 2026-07-13 | JBU754 | SJU → FLL | Jul 13, 09:40 UTC | Jul 14, 03:30 UTC | 17h 51m |
| 2026-07-13 | JBU275 | BDL → SJU | Jul 13, 01:02 UTC | Jul 14, 00:15 UTC | 23h 14m |
| 2026-07-12 | JBU438 | MCO → BDL | Jul 12, 21:25 UTC | Jul 13, 20:15 UTC | 22h 51m |
| 2026-07-12 | JBU83 | JFK → MCO | Jul 12, 17:20 UTC | Jul 13, 16:10 UTC | 22h 51m |
| 2026-07-12 | JBU1901 | BUF → JFK | Jul 12, 15:00 UTC | Jul 13, 14:15 UTC | 23h 16m |
| 2026-07-12 | JBU491 | BUF → LAX | Jul 12, 02:20 UTC | Jul 13, 01:50 UTC | 23h 31m |
| 2026-07-11 | JBU311 | BOS → ORD | Jul 11, 14:51 UTC | Jul 12, 12:55 UTC | 22h 5m |
| 2026-07-11 | JBU613 | - | Jul 11, 05:25 UTC | Jul 11, 06:10 UTC | 45m |
| 2026-07-11 | JBU613 | - | Jul 11, 01:10 UTC | Jul 11, 03:50 UTC | 2h 40m |
| 2026-07-11 | JBU613 | HPN → FLL | Jul 11, 01:10 UTC | Jul 12, 00:15 UTC | 23h 6m |
| 2026-07-10 | JBU548 | TPA → HPN | Jul 10, 21:30 UTC | Jul 10, 23:55 UTC | 2h 25m |
| 2026-07-10 | JBU2459 | BOS → PHL | Jul 10, 00:24 UTC | Jul 10, 23:55 UTC | 23h 32m |
| 2026-07-09 | JBU1807 | BOS → BNA | Jul 9, 15:17 UTC | Jul 10, 14:15 UTC | 22h 59m |
| 2026-07-08 | JBU1014 | CUN → MCO | Jul 8, 21:21 UTC | Jul 9, 20:15 UTC | 22h 54m |
| 2026-07-08 | JBU1014 | - | Jul 8, 21:25 UTC | Jul 8, 22:55 UTC | 1h 30m |
| 2026-07-08 | JBU1013 | MCO → CUN | Jul 8, 17:25 UTC | Jul 8, 18:55 UTC | 1h 30m |
| 2026-07-08 | JBU1076 | - | Jul 8, 10:55 UTC | Jul 8, 13:20 UTC | 2h 25m |
| 2026-07-08 | JBU1196 | - | Jul 8, 01:00 UTC | Jul 8, 03:35 UTC | 2h 35m |
| 2026-07-07 | JBU1383 | - | Jul 7, 20:20 UTC | Jul 7, 23:00 UTC | 2h 40m |
| 2026-07-07 | JBU1383 | - | Jul 7, 15:30 UTC | Jul 7, 17:45 UTC | 2h 15m |
| 2026-07-06 | JBU2119 | - | Jul 6, 22:20 UTC | Jul 7, 01:00 UTC | 2h 40m |
| 2026-07-06 | JBU2119 | ORH → FLL | Jul 6, 22:16 UTC | Jul 7, 20:15 UTC | 22h 0m |
| 2026-07-06 | JBU2020 | - | Jul 6, 18:15 UTC | Jul 6, 20:50 UTC | 2h 35m |
| 2026-07-06 | JBU2154 | - | Jul 6, 15:55 UTC | Jul 6, 16:25 UTC | 30m |
| 2026-07-06 | JBU2154 | - | Jul 6, 14:10 UTC | Jul 6, 14:25 UTC | 15m |
| 2026-07-05 | JBU41 | - | Jul 5, 16:10 UTC | Jul 5, 16:35 UTC | 25m |
| 2026-07-05 | JBU41 | FLL → MDE | Jul 5, 16:08 UTC | Jul 6, 14:15 UTC | 22h 8m |
| 2026-07-05 | JBU1471 | LGA → FLL | Jul 5, 11:50 UTC | Jul 5, 14:15 UTC | 2h 25m |
| 2026-07-04 | JBU1380 | FLL → GUA | Jul 4, 15:29 UTC | Jul 5, 14:15 UTC | 22h 47m |
| 2026-07-04 | JBU2282 | DFW → FLL | Jul 4, 11:09 UTC | Jul 5, 07:35 UTC | 20h 26m |
| 2026-07-04 | JBU2279 | FLL → DFW | Jul 4, 03:30 UTC | Jul 4, 21:55 UTC | 18h 25m |
| 2026-07-04 | JBU2279 | FLL → DFW | Jul 4, 03:35 UTC | Jul 4, 06:10 UTC | 2h 35m |
| 2026-07-03 | JBU305 | - | Jul 3, 23:40 UTC | Jul 4, 02:00 UTC | 2h 20m |
| 2026-07-03 | JBU2420 | - | Jul 3, 19:55 UTC | Jul 3, 21:05 UTC | 1h 10m |
| 2026-07-03 | JBU2420 | - | Jul 3, 16:45 UTC | Jul 3, 17:00 UTC | 15m |
| 2026-07-03 | JBU2219 | EWR → AUA | Jul 3, 11:05 UTC | Jul 3, 15:15 UTC | 4h 10m |
| 2026-07-02 | JBU525 | - | Jul 2, 12:05 UTC | Jul 2, 15:25 UTC | 3h 20m |
| 2026-07-02 | JBU525 | PVD → SJU | Jul 2, 12:03 UTC | Jul 3, 03:35 UTC | 15h 33m |
| 2026-07-01 | JBU1473 | - | Jul 1, 11:10 UTC | Jul 1, 12:35 UTC | 1h 25m |
| 2026-07-01 | JBU1473 | FLL → PUJ | Jul 1, 11:09 UTC | Jul 2, 03:30 UTC | 16h 22m |
| 2026-06-30 | JBU1471 | LGA → FLL | Jun 30, 11:39 UTC | Jul 1, 02:50 UTC | 15h 12m |
| 2026-06-29 | JBU1172 | - | Jun 29, 22:49 UTC | Jun 30, 01:09 UTC | 2h 20m |
| 2026-06-29 | JBU1172 | FLL → LGA | Jun 29, 22:45 UTC | Jun 30, 16:30 UTC | 17h 45m |
| 2026-06-29 | JBU40 | - | Jun 29, 19:54 UTC | Jun 29, 20:35 UTC | 40m |
| 2026-06-29 | JBU613 | HPN → FLL | Jun 29, 00:34 UTC | Jun 30, 00:14 UTC | 23h 41m |
| 2026-06-28 | JBU1694 | MCO → HPN | Jun 28, 20:55 UTC | Jun 29, 13:54 UTC | 17h 0m |
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 N509JB page for operator, model, and routing details .