sensors Mode-S transponder
A7DE53
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N606JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORP
- Hex
- A7DE53
- Octal
- 51757123
- Decimal
- 11,001,427
- Country
- US
- Tail
- N606JB
- Type
- A320
- Flights observed
- 294
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address A7DE53 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 |
|---|---|---|---|
| JBU2251 | JetBlue Airways | 5 | 2026-06-28 |
| JBU862 | - | 4 | 2026-06-28 |
| JBU2662 | - | 4 | 2026-07-07 |
| JBU768 | - | 3 | 2026-06-17 |
| JBU65 | - | 3 | 2026-04-17 |
| JBU635 | JetBlue Airways | 3 | 2026-06-08 |
| JBU54 | - | 3 | 2026-07-01 |
| JBU2840 | JetBlue Airways | 3 | 2026-05-14 |
| JBU269 | - | 3 | 2026-07-03 |
| JBU2080 | - | 3 | 2026-06-25 |
| JBU1924 | - | 3 | 2026-04-13 |
| JBU1903 | JetBlue Airways | 3 | 2026-05-11 |
| JBU154 | JetBlue Airways | 3 | 2026-04-23 |
| JBU1144 | JetBlue Airways | 3 | 2026-06-17 |
| JBU1047 | JetBlue Airways | 3 | 2026-06-04 |
| JBU98 | JetBlue Airways | 2 | 2026-05-02 |
| JBU972 | JetBlue Airways | 2 | 2026-04-26 |
| JBU97 | JetBlue Airways | 2 | 2026-05-02 |
| JBU934 | - | 2 | 2026-06-16 |
| JBU861 | JetBlue Airways | 2 | 2026-04-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-15 | JBU572 | - | Jul 15, 00:30 UTC | Jul 15, 03:00 UTC | 2h 30m |
| 2026-07-14 | JBU864 | ORD → FLL | Jul 14, 19:50 UTC | Jul 14, 22:25 UTC | 2h 35m |
| 2026-07-14 | JBU663 | - | Jul 14, 15:15 UTC | Jul 14, 18:20 UTC | 3h 5m |
| 2026-07-14 | JBU2005 | - | Jul 14, 10:10 UTC | Jul 14, 12:20 UTC | 2h 10m |
| 2026-07-13 | JBU2008 | PPM → PIT | Jul 13, 23:05 UTC | Jul 14, 01:20 UTC | 2h 15m |
| 2026-07-13 | JBU1474 | - | Jul 13, 14:40 UTC | Jul 13, 20:10 UTC | 5h 30m |
| 2026-07-13 | JBU2005 | - | Jul 13, 10:10 UTC | Jul 13, 12:20 UTC | 2h 10m |
| 2026-07-12 | JBU2008 | - | Jul 12, 23:05 UTC | Jul 13, 01:15 UTC | 2h 10m |
| 2026-07-12 | JBU2076 | TPA → FLL | Jul 12, 19:30 UTC | Jul 12, 20:10 UTC | 40m |
| 2026-07-12 | JBU1005 | - | Jul 12, 17:40 UTC | Jul 12, 18:20 UTC | 40m |
| 2026-07-11 | JBU1130 | FLL → CHS | Jul 11, 21:26 UTC | Jul 12, 18:25 UTC | 21h 0m |
| 2026-07-11 | JBU2097 | ATL → FLL | Jul 11, 18:29 UTC | Jul 12, 15:30 UTC | 21h 2m |
| 2026-07-10 | JBU2780 | IAH → FLL | Jul 10, 18:53 UTC | Jul 11, 18:45 UTC | 23h 53m |
| 2026-07-10 | JBU2179 | FLL → IAH | Jul 10, 14:06 UTC | Jul 11, 12:35 UTC | 22h 30m |
| 2026-07-10 | JBU1505 | EWR → FLL | Jul 10, 10:10 UTC | Jul 11, 02:00 UTC | 15h 51m |
| 2026-07-10 | JBU8406 | FLL → EWR | Jul 10, 01:40 UTC | Jul 10, 04:10 UTC | 2h 30m |
| 2026-07-10 | JBU8406 | FLL → EWR | Jul 10, 01:40 UTC | Jul 11, 00:45 UTC | 23h 6m |
| 2026-07-09 | JBU1579 | DCA → FLL | Jul 9, 19:35 UTC | Jul 9, 21:35 UTC | 2h 0m |
| 2026-07-09 | JBU1680 | JPN → DCA | Jul 9, 17:55 UTC | Jul 9, 18:00 UTC | 5m |
| 2026-07-09 | JBU1680 | - | Jul 9, 16:00 UTC | Jul 9, 17:50 UTC | 1h 50m |
| 2026-07-09 | JBU579 | DCA → FLL | Jul 9, 12:15 UTC | Jul 9, 14:25 UTC | 2h 10m |
| 2026-07-08 | JBU1869 | JFK → PUJ | Jul 8, 13:34 UTC | Jul 9, 12:45 UTC | 23h 12m |
| 2026-07-07 | JBU2662 | - | Jul 7, 22:55 UTC | Jul 8, 02:20 UTC | 3h 25m |
| 2026-07-07 | JBU2662 | - | Jul 7, 22:05 UTC | Jul 7, 22:15 UTC | 10m |
| 2026-07-07 | JBU2662 | BGI → JFK | Jul 7, 21:57 UTC | Jul 8, 20:45 UTC | 22h 49m |
| 2026-07-07 | JBU2661 | - | Jul 7, 20:00 UTC | Jul 7, 20:15 UTC | 15m |
| 2026-07-07 | JBU2661 | - | Jul 7, 16:05 UTC | Jul 7, 19:25 UTC | 3h 20m |
| 2026-07-06 | JBU1736 | STI → JFK | Jul 6, 16:59 UTC | Jul 7, 12:40 UTC | 19h 42m |
| 2026-07-06 | JBU1736 | JFK → JFK | Jul 6, 12:00 UTC | Jul 6, 20:20 UTC | 8h 20m |
| 2026-07-05 | JBU297 | - | Jul 5, 20:50 UTC | Jul 6, 00:20 UTC | 3h 30m |
| 2026-07-05 | JBU2752 | SJU → TPA | Jul 5, 01:46 UTC | Jul 6, 00:20 UTC | 22h 34m |
| 2026-07-04 | JBU2448 | SDQ → FLL | Jul 4, 18:36 UTC | Jul 5, 16:30 UTC | 21h 54m |
| 2026-07-04 | JBU1976 | KIN → FLL | Jul 4, 01:35 UTC | Jul 5, 00:30 UTC | 22h 55m |
| 2026-07-03 | JBU269 | - | Jul 3, 17:20 UTC | Jul 3, 20:00 UTC | 2h 40m |
| 2026-07-03 | JBU269 | BOS → FLL | Jul 3, 17:18 UTC | Jul 4, 16:35 UTC | 23h 17m |
| 2026-07-03 | JBU269 | BOS → BOS | Jul 3, 15:15 UTC | Jul 3, 15:40 UTC | 25m |
| 2026-07-03 | JBU552 | MCO → BOS | Jul 3, 12:20 UTC | Jul 3, 14:40 UTC | 2h 20m |
| 2026-07-03 | JBU234 | - | Jul 3, 08:10 UTC | Jul 3, 08:50 UTC | 40m |
| 2026-07-03 | JBU234 | - | Jul 3, 06:25 UTC | Jul 3, 06:40 UTC | 15m |
| 2026-07-03 | JBU433 | BTV → JFK | Jul 3, 01:25 UTC | Jul 3, 01:50 UTC | 25m |
| 2026-07-02 | JBU433 | BTV → JFK | Jul 2, 23:15 UTC | Jul 2, 23:50 UTC | 35m |
| 2026-07-02 | JBU987 | - | Jul 2, 19:05 UTC | Jul 2, 21:30 UTC | 2h 25m |
| 2026-07-02 | JBU588 | - | Jul 2, 15:40 UTC | Jul 2, 18:00 UTC | 2h 20m |
| 2026-07-01 | JBU1453 | - | Jul 1, 20:35 UTC | Jul 1, 20:45 UTC | 10m |
| 2026-07-01 | JBU1453 | FLL → SJU | Jul 1, 20:30 UTC | Jul 2, 18:45 UTC | 22h 15m |
| 2026-07-01 | JBU54 | - | Jul 1, 18:40 UTC | Jul 1, 19:15 UTC | 35m |
| 2026-07-01 | JBU54 | - | Jul 1, 17:00 UTC | Jul 1, 17:15 UTC | 15m |
| 2026-07-01 | JBU54 | SJU → FLL | Jul 1, 16:58 UTC | Jul 2, 16:45 UTC | 23h 47m |
| 2026-07-01 | JBU761 | - | Jul 1, 10:35 UTC | Jul 1, 14:00 UTC | 3h 25m |
| 2026-06-30 | JBU1205 | MCO → SDQ | Jun 30, 14:05 UTC | Jul 1, 11:10 UTC | 21h 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 N606JB page for operator, model, and routing details .