sensors Mode-S transponder
A654CB
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N507JT · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORP
- Hex
- A654CB
- Octal
- 51452313
- Decimal
- 10,900,683
- Country
- US
- Tail
- N507JT
- Type
- A320
- Flights observed
- 260
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 3h ago
Current position
Country allocation
The ICAO 24-bit address A654CB 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 |
|---|---|---|---|
| JBU1696 | - | 6 | 2026-06-29 |
| JBU814 | - | 5 | 2026-07-12 |
| JBU928 | JetBlue Airways | 4 | 2026-05-04 |
| JBU39 | - | 4 | 2026-06-28 |
| JBU914 | JetBlue Airways | 3 | 2026-05-11 |
| JBU613 | JetBlue Airways | 3 | 2026-04-16 |
| JBU503 | JetBlue Airways | 3 | 2026-05-23 |
| JBU2895 | - | 3 | 2026-06-28 |
| JBU2761 | - | 3 | 2026-06-24 |
| JBU2760 | - | 3 | 2026-06-24 |
| JBU2631 | JetBlue Airways | 3 | 2026-05-02 |
| JBU213 | JetBlue Airways | 3 | 2026-05-07 |
| JBU2087 | - | 3 | 2026-07-07 |
| JBU2020 | - | 3 | 2026-07-03 |
| JBU1693 | - | 3 | 2026-07-11 |
| JBU156 | JetBlue Airways | 3 | 2026-06-08 |
| JBU1493 | JetBlue Airways | 3 | 2026-06-20 |
| JBU1390 | - | 3 | 2026-06-14 |
| JBU1288 | JetBlue Airways | 3 | 2026-04-30 |
| JBU974 | JetBlue Airways | 2 | 2026-05-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU959 | BDL → FLL | Jul 13, 12:08 UTC | Jul 14, 00:40 UTC | 12h 33m |
| 2026-07-12 | JBU276 | SJU → BDL | Jul 12, 23:23 UTC | Jul 13, 22:45 UTC | 23h 23m |
| 2026-07-12 | JBU2851 | TPA → SJU | Jul 12, 19:15 UTC | Jul 13, 16:45 UTC | 21h 31m |
| 2026-07-12 | JBU814 | FLL → HPN | Jul 12, 11:04 UTC | Jul 13, 02:55 UTC | 15h 52m |
| 2026-07-11 | JBU1693 | - | Jul 11, 20:45 UTC | Jul 11, 21:05 UTC | 20m |
| 2026-07-11 | JBU1693 | FLL → NAS | Jul 11, 20:44 UTC | Jul 12, 18:45 UTC | 22h 2m |
| 2026-07-11 | JBU1371 | LGA → FLL | Jul 11, 16:30 UTC | Jul 11, 19:05 UTC | 2h 35m |
| 2026-07-11 | JBU1062 | - | Jul 11, 12:05 UTC | Jul 11, 14:25 UTC | 2h 20m |
| 2026-07-10 | JBU1167 | - | Jul 10, 14:30 UTC | Jul 10, 14:45 UTC | 15m |
| 2026-07-10 | JBU1368 | - | Jul 10, 10:40 UTC | Jul 10, 13:00 UTC | 2h 20m |
| 2026-07-10 | JBU1368 | - | Jul 10, 10:37 UTC | Jul 10, 16:50 UTC | 6h 13m |
| 2026-07-10 | JBU2421 | - | Jul 10, 03:35 UTC | Jul 10, 06:20 UTC | 2h 45m |
| 2026-07-09 | JBU1194 | BOS → BOS | Jul 9, 15:40 UTC | Jul 10, 01:40 UTC | 10h 0m |
| 2026-07-09 | JBU322 | - | Jul 9, 10:55 UTC | Jul 9, 13:40 UTC | 2h 45m |
| 2026-07-08 | JBU1229 | EWR → CUN | Jul 8, 12:55 UTC | Jul 9, 12:45 UTC | 23h 51m |
| 2026-07-08 | JBU1229 | EWR → CUN | Jul 8, 12:55 UTC | Jul 8, 16:15 UTC | 3h 20m |
| 2026-07-08 | JBU144 | - | Jul 8, 03:35 UTC | Jul 8, 05:50 UTC | 2h 15m |
| 2026-07-07 | JBU2087 | - | Jul 7, 23:45 UTC | Jul 8, 02:25 UTC | 2h 40m |
| 2026-07-07 | JBU388 | LAX → BOS | Jul 7, 17:35 UTC | Jul 7, 20:15 UTC | 2h 40m |
| 2026-07-07 | JBU1461 | LGA → PBI | Jul 7, 13:55 UTC | Jul 7, 16:10 UTC | 2h 15m |
| 2026-07-06 | JBU579 | DCA → FLL | Jul 6, 17:35 UTC | Jul 7, 14:45 UTC | 21h 10m |
| 2026-07-06 | JBU1480 | - | Jul 6, 12:05 UTC | Jul 6, 14:00 UTC | 1h 55m |
| 2026-07-06 | JBU1480 | FLL → DCA | Jul 6, 12:02 UTC | Jul 7, 10:45 UTC | 22h 44m |
| 2026-07-05 | JBU1784 | - | Jul 5, 21:15 UTC | Jul 5, 21:50 UTC | 35m |
| 2026-07-05 | JBU1783 | - | Jul 5, 15:20 UTC | Jul 5, 15:50 UTC | 30m |
| 2026-07-05 | JBU375 | PVD → MCO | Jul 5, 11:15 UTC | Jul 5, 13:25 UTC | 2h 10m |
| 2026-07-04 | JBU2276 | - | Jul 4, 23:15 UTC | Jul 5, 01:25 UTC | 2h 10m |
| 2026-07-04 | JBU375 | PVD → MCO | Jul 4, 19:30 UTC | Jul 4, 21:45 UTC | 2h 15m |
| 2026-07-03 | JBU2119 | ORH → FLL | Jul 3, 23:30 UTC | Jul 4, 02:10 UTC | 2h 40m |
| 2026-07-03 | JBU2119 | ORH → FLL | Jul 3, 23:30 UTC | Jul 4, 21:45 UTC | 22h 15m |
| 2026-07-03 | JBU2020 | - | Jul 3, 19:45 UTC | Jul 3, 22:30 UTC | 2h 45m |
| 2026-07-03 | JBU669 | MCO → FLL | Jul 3, 17:30 UTC | Jul 3, 18:25 UTC | 55m |
| 2026-07-02 | JBU313 | ISP → FLL | Jul 2, 21:13 UTC | Jul 3, 20:45 UTC | 23h 32m |
| 2026-07-02 | JBU544 | PBI → ISP | Jul 2, 17:03 UTC | Jul 3, 16:05 UTC | 23h 3m |
| 2026-07-01 | JBU276 | SJU → BDL | Jul 1, 22:54 UTC | Jul 2, 22:45 UTC | 23h 52m |
| 2026-07-01 | JBU2632 | STX → SJU | Jul 1, 21:10 UTC | Jul 2, 19:20 UTC | 22h 10m |
| 2026-07-01 | JBU133 | MCO → SJU | Jul 1, 15:55 UTC | Jul 2, 14:45 UTC | 22h 50m |
| 2026-06-30 | JBU987 | ORH → MCO | Jun 30, 21:06 UTC | Jul 1, 19:55 UTC | 22h 50m |
| 2026-06-30 | JBU2920 | ALB → MCO | Jun 30, 10:36 UTC | Jul 1, 03:55 UTC | 17h 19m |
| 2026-06-29 | JBU137 | BDL → MCO | Jun 29, 21:08 UTC | Jun 30, 20:40 UTC | 23h 33m |
| 2026-06-29 | JBU767 | - | Jun 29, 09:20 UTC | Jun 29, 10:04 UTC | 45m |
| 2026-06-29 | JBU767 | MCO → PSE | Jun 29, 09:15 UTC | Jun 30, 03:30 UTC | 18h 16m |
| 2026-06-29 | JBU1696 | - | Jun 29, 00:34 UTC | Jun 29, 02:59 UTC | 2h 25m |
| 2026-06-28 | JBU39 | - | Jun 28, 20:45 UTC | Jun 28, 22:55 UTC | 2h 10m |
| 2026-06-28 | JBU2895 | BOS → FLL | Jun 28, 10:24 UTC | Jun 28, 18:55 UTC | 8h 30m |
| 2026-06-27 | JBU606 | SDQ → MCO | Jun 27, 17:57 UTC | Jun 28, 12:09 UTC | 18h 13m |
| 2026-06-27 | JBU1608 | STI → SJU | Jun 27, 00:50 UTC | Jun 27, 23:50 UTC | 23h 0m |
| 2026-06-26 | JBU593 | EWR → STI | Jun 26, 16:19 UTC | Jun 27, 14:45 UTC | 22h 26m |
| 2026-06-26 | JBU193 | EWR → STI | Jun 26, 03:00 UTC | Jun 27, 01:39 UTC | 22h 40m |
| 2026-06-26 | JBU193 | - | Jun 26, 03:05 UTC | Jun 26, 03:34 UTC | 30m |
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 N507JT page for operator, model, and routing details .