sensors Mode-S transponder
A7DA9C
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N605JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORP
- Hex
- A7DA9C
- Octal
- 51755234
- Decimal
- 11,000,476
- Country
- US
- Tail
- N605JB
- Type
- A320
- Flights observed
- 278
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address A7DA9C 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 |
|---|---|---|---|
| JBU1718 | - | 6 | 2026-06-27 |
| JBU1553 | - | 6 | 2026-07-08 |
| JBU773 | JetBlue Airways | 5 | 2026-06-20 |
| JBU1475 | - | 5 | 2026-07-10 |
| JBU754 | JetBlue Airways | 4 | 2026-06-03 |
| JBU594 | - | 4 | 2026-06-25 |
| JBU149 | JetBlue Airways | 4 | 2026-05-26 |
| JBU968 | - | 3 | 2026-04-13 |
| JBU959 | - | 3 | 2026-06-26 |
| JBU66 | - | 3 | 2026-06-24 |
| JBU465 | JetBlue Airways | 3 | 2026-05-17 |
| JBU304 | JetBlue Airways | 3 | 2026-06-16 |
| JBU241 | JetBlue Airways | 3 | 2026-06-18 |
| JBU1267 | - | 3 | 2026-04-13 |
| JBU1233 | JetBlue Airways | 3 | 2026-04-29 |
| JBU1174 | JetBlue Airways | 3 | 2026-06-05 |
| JBU1158 | JetBlue Airways | 3 | 2026-05-30 |
| JBU1061 | JetBlue Airways | 3 | 2026-04-15 |
| JBU974 | JetBlue Airways | 2 | 2026-06-20 |
| JBU892 | - | 2 | 2026-07-02 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU655 | SYR → MCO | Jul 13, 17:32 UTC | Jul 14, 02:20 UTC | 8h 49m |
| 2026-07-13 | JBU87 | FLL → ALB | Jul 13, 02:10 UTC | Jul 14, 01:00 UTC | 22h 51m |
| 2026-07-12 | JBU1245 | - | Jul 12, 17:01 UTC | Jul 12, 18:50 UTC | 1h 50m |
| 2026-07-12 | JBU1245 | RIC → FLL | Jul 12, 16:56 UTC | Jul 13, 15:00 UTC | 22h 5m |
| 2026-07-12 | JBU1246 | - | Jul 12, 13:55 UTC | Jul 12, 15:40 UTC | 1h 45m |
| 2026-07-12 | JBU193 | EWR → FLL | Jul 12, 03:50 UTC | Jul 12, 10:40 UTC | 6h 50m |
| 2026-07-11 | JBU106 | - | Jul 11, 22:55 UTC | Jul 12, 01:20 UTC | 2h 25m |
| 2026-07-11 | JBU2760 | - | Jul 11, 18:45 UTC | Jul 11, 21:05 UTC | 2h 20m |
| 2026-07-11 | JBU2153 | FLL → SJU | Jul 11, 01:14 UTC | Jul 12, 01:00 UTC | 23h 47m |
| 2026-07-10 | JBU1475 | - | Jul 10, 20:10 UTC | Jul 10, 20:25 UTC | 15m |
| 2026-07-10 | JBU1475 | - | Jul 10, 17:10 UTC | Jul 10, 17:55 UTC | 45m |
| 2026-07-10 | JBU1475 | BDL → SJU | Jul 10, 17:06 UTC | Jul 11, 16:55 UTC | 23h 50m |
| 2026-07-10 | JBU1476 | - | Jul 10, 14:45 UTC | Jul 10, 15:35 UTC | 50m |
| 2026-07-10 | JBU1476 | - | Jul 10, 12:15 UTC | Jul 10, 12:25 UTC | 10m |
| 2026-07-10 | JBU2932 | - | Jul 10, 02:00 UTC | Jul 10, 02:15 UTC | 15m |
| 2026-07-10 | JBU2931 | - | Jul 10, 00:05 UTC | Jul 10, 00:20 UTC | 15m |
| 2026-07-09 | JBU1608 | - | Jul 9, 21:50 UTC | Jul 9, 22:00 UTC | 10m |
| 2026-07-09 | JBU1138 | SDQ → SJU | Jul 9, 01:00 UTC | Jul 9, 22:00 UTC | 21h 0m |
| 2026-07-08 | JBU1137 | BOS → DTW | Jul 8, 23:14 UTC | Jul 9, 22:00 UTC | 22h 46m |
| 2026-07-08 | JBU1553 | - | Jul 8, 15:35 UTC | Jul 8, 17:50 UTC | 2h 15m |
| 2026-07-08 | JBU1553 | FLL → SJU | Jul 8, 15:32 UTC | Jul 9, 15:00 UTC | 23h 28m |
| 2026-07-07 | JBU1880 | - | Jul 7, 00:30 UTC | Jul 7, 02:35 UTC | 2h 5m |
| 2026-07-07 | JBU1880 | FLL → DCA | Jul 7, 00:29 UTC | Jul 7, 15:40 UTC | 15h 12m |
| 2026-07-06 | JBU1869 | JFK → FLL | Jul 6, 14:25 UTC | Jul 6, 22:25 UTC | 8h 0m |
| 2026-07-05 | JBU8023 | BOS → STI | Jul 5, 22:14 UTC | Jul 6, 21:00 UTC | 22h 47m |
| 2026-07-05 | JBU862 | SJU → BOS | Jul 5, 13:47 UTC | Jul 6, 06:55 UTC | 17h 9m |
| 2026-07-05 | JBU403 | JFK → SJU | Jul 5, 09:20 UTC | Jul 5, 12:40 UTC | 3h 20m |
| 2026-07-05 | JBU403 | JFK → SJU | Jul 5, 09:17 UTC | Jul 6, 06:55 UTC | 21h 39m |
| 2026-07-04 | JBU676 | BDL → JFK | Jul 4, 10:48 UTC | Jul 5, 02:20 UTC | 15h 32m |
| 2026-07-04 | JBU485 | - | Jul 4, 01:10 UTC | Jul 4, 02:00 UTC | 50m |
| 2026-07-04 | JBU485 | ROC → JFK | Jul 4, 01:06 UTC | Jul 5, 01:00 UTC | 23h 54m |
| 2026-07-03 | JBU186 | JFK → ROC | Jul 3, 22:20 UTC | Jul 3, 23:20 UTC | 1h 0m |
| 2026-07-03 | JBU852 | CUN → JFK | Jul 3, 16:45 UTC | Jul 3, 20:10 UTC | 3h 25m |
| 2026-07-02 | JBU1290 | OAJ → BOS | Jul 2, 21:35 UTC | Jul 2, 23:10 UTC | 1h 35m |
| 2026-07-02 | JBU1290 | ILM → BOS | Jul 2, 21:27 UTC | Jul 3, 20:10 UTC | 22h 44m |
| 2026-07-02 | JBU1293 | - | Jul 2, 18:10 UTC | Jul 2, 19:35 UTC | 1h 25m |
| 2026-07-02 | JBU892 | TPA → BOS | Jul 2, 14:05 UTC | Jul 2, 16:35 UTC | 2h 30m |
| 2026-07-02 | JBU452 | - | Jul 2, 10:00 UTC | Jul 2, 12:45 UTC | 2h 45m |
| 2026-07-01 | JBU2089 | FLL → SAP | Jul 1, 15:25 UTC | Jul 2, 15:00 UTC | 23h 35m |
| 2026-07-01 | JBU2547 | MCO → FLL | Jul 1, 13:04 UTC | Jul 2, 12:50 UTC | 23h 46m |
| 2026-06-30 | JBU2722 | - | Jun 30, 20:50 UTC | Jun 30, 22:25 UTC | 1h 35m |
| 2026-06-30 | JBU2722 | MSY → FLL | Jun 30, 20:48 UTC | Jul 1, 17:10 UTC | 20h 23m |
| 2026-06-30 | JBU1823 | JFK → LAX | Jun 30, 17:50 UTC | Jun 30, 19:25 UTC | 1h 35m |
| 2026-06-30 | JBU1801 | JFK → FLL | Jun 30, 13:50 UTC | Jun 30, 16:05 UTC | 2h 15m |
| 2026-06-29 | JBU1568 | PUJ → JFK | Jun 29, 19:58 UTC | Jun 30, 16:05 UTC | 20h 8m |
| 2026-06-29 | JBU1568 | PUJ → JFK | Jun 29, 16:15 UTC | Jun 29, 23:25 UTC | 7h 10m |
| 2026-06-29 | JBU1754 | - | Jun 29, 13:49 UTC | Jun 29, 14:25 UTC | 35m |
| 2026-06-29 | JBU1754 | - | Jun 29, 12:09 UTC | Jun 29, 12:24 UTC | 15m |
| 2026-06-28 | JBU1778 | PUJ → MCO | Jun 28, 16:21 UTC | Jun 29, 14:25 UTC | 22h 4m |
| 2026-06-28 | JBU334 | SJU → MCO | Jun 28, 02:44 UTC | Jun 29, 01:00 UTC | 22h 16m |
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 N605JB page for operator, model, and routing details .