sensors Mode-S transponder
AAB2BF
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N789JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORP
- Hex
- AAB2BF
- Octal
- 52531277
- Decimal
- 11,186,879
- Country
- US
- Tail
- N789JB
- Type
- A320
- Flights observed
- 292
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 2h ago
Current position
Country allocation
The ICAO 24-bit address AAB2BF 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 |
|---|---|---|---|
| JBU2001 | JetBlue Airways | 6 | 2026-06-15 |
| JBU2840 | - | 5 | 2026-07-09 |
| JBU703 | JetBlue Airways | 4 | 2026-05-21 |
| JBU634 | JetBlue Airways | 4 | 2026-06-05 |
| JBU1809 | JetBlue Airways | 4 | 2026-05-04 |
| JBU1142 | - | 4 | 2026-07-04 |
| JBU861 | - | 3 | 2026-07-12 |
| JBU8586 | - | 3 | 2026-04-13 |
| JBU548 | JetBlue Airways | 3 | 2026-05-10 |
| JBU2937 | JetBlue Airways | 3 | 2026-06-24 |
| JBU2476 | JetBlue Airways | 3 | 2026-04-17 |
| JBU2133 | JetBlue Airways | 3 | 2026-06-13 |
| JBU2041 | JetBlue Airways | 3 | 2026-05-16 |
| JBU1807 | - | 3 | 2026-06-30 |
| JBU1794 | JetBlue Airways | 3 | 2026-04-15 |
| JBU1793 | JetBlue Airways | 3 | 2026-04-15 |
| JBU1719 | JetBlue Airways | 3 | 2026-06-11 |
| JBU1677 | - | 3 | 2026-06-26 |
| JBU153 | - | 3 | 2026-06-20 |
| JBU1475 | JetBlue Airways | 3 | 2026-04-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU2896 | PUJ → BOS | Jul 13, 15:12 UTC | Jul 14, 03:45 UTC | 12h 34m |
| 2026-07-13 | JBU2895 | BOS → PUJ | Jul 13, 10:20 UTC | Jul 14, 03:45 UTC | 17h 26m |
| 2026-07-12 | JBU2941 | PUJ → SJU | Jul 12, 22:34 UTC | Jul 13, 21:45 UTC | 23h 12m |
| 2026-07-12 | JBU2031 | SJU → PUJ | Jul 12, 20:46 UTC | Jul 13, 19:45 UTC | 23h 0m |
| 2026-07-12 | JBU861 | - | Jul 12, 18:45 UTC | Jul 12, 19:10 UTC | 25m |
| 2026-07-11 | JBU1728 | MCO → EWR | Jul 11, 23:38 UTC | Jul 12, 21:00 UTC | 21h 23m |
| 2026-07-11 | JBU1728 | MCO → EWR | Jul 11, 23:40 UTC | Jul 12, 02:01 UTC | 2h 20m |
| 2026-07-11 | JBU495 | - | Jul 11, 17:05 UTC | Jul 11, 19:30 UTC | 2h 25m |
| 2026-07-11 | JBU8394 | - | Jul 11, 13:20 UTC | Jul 11, 15:45 UTC | 2h 25m |
| 2026-07-11 | JBU1434 | - | Jul 11, 11:05 UTC | Jul 11, 12:05 UTC | 1h 0m |
| 2026-07-11 | JBU275 | BDL → SJU | Jul 11, 00:17 UTC | Jul 11, 03:45 UTC | 3h 29m |
| 2026-07-10 | JBU1777 | MCO → PUJ | Jul 10, 12:24 UTC | Jul 11, 11:45 UTC | 23h 22m |
| 2026-07-10 | JBU699 | LGA → MCO | Jul 10, 05:34 UTC | Jul 11, 03:45 UTC | 22h 12m |
| 2026-07-10 | JBU1098 | MCO → LGA | Jul 10, 02:19 UTC | Jul 11, 01:05 UTC | 22h 47m |
| 2026-07-09 | JBU969 | RIC → MCO | Jul 9, 19:43 UTC | Jul 10, 17:00 UTC | 21h 18m |
| 2026-07-09 | JBU2840 | - | Jul 9, 14:35 UTC | Jul 9, 15:30 UTC | 55m |
| 2026-07-09 | JBU2840 | NAS → MCO | Jul 9, 14:26 UTC | Jul 10, 13:10 UTC | 22h 45m |
| 2026-07-09 | JBU2841 | - | Jul 9, 12:15 UTC | Jul 9, 13:10 UTC | 55m |
| 2026-07-08 | JBU283 | - | Jul 8, 23:30 UTC | Jul 9, 01:45 UTC | 2h 15m |
| 2026-07-08 | JBU1084 | MCO → JFK | Jul 8, 19:35 UTC | Jul 8, 21:40 UTC | 2h 5m |
| 2026-07-08 | JBU383 | JFK → MCO | Jul 8, 15:50 UTC | Jul 8, 17:55 UTC | 2h 5m |
| 2026-07-08 | JBU1184 | MCO → JFK | Jul 8, 11:55 UTC | Jul 8, 14:00 UTC | 2h 5m |
| 2026-07-07 | JBU561 | BOS → BOS | Jul 7, 21:20 UTC | Jul 7, 21:30 UTC | 10m |
| 2026-07-07 | JBU1354 | DCA → BOS | Jul 7, 19:05 UTC | Jul 7, 20:35 UTC | 1h 30m |
| 2026-07-07 | JBU1354 | DCA → BOS | Jul 7, 19:01 UTC | Jul 8, 17:45 UTC | 22h 45m |
| 2026-07-06 | JBU2896 | PUJ → BOS | Jul 6, 14:36 UTC | Jul 7, 05:05 UTC | 14h 29m |
| 2026-07-06 | JBU1473 | FLL → PUJ | Jul 6, 11:14 UTC | Jul 7, 05:05 UTC | 17h 51m |
| 2026-07-05 | JBU1880 | - | Jul 5, 22:40 UTC | Jul 5, 23:45 UTC | 1h 5m |
| 2026-07-05 | JBU326 | - | Jul 5, 19:55 UTC | Jul 5, 20:25 UTC | 30m |
| 2026-07-05 | JBU326 | MBJ → FLL | Jul 5, 18:55 UTC | Jul 6, 17:45 UTC | 22h 51m |
| 2026-07-05 | JBU2427 | - | Jul 5, 16:00 UTC | Jul 5, 16:30 UTC | 30m |
| 2026-07-05 | JBU1594 | - | Jul 5, 13:35 UTC | Jul 5, 14:05 UTC | 30m |
| 2026-07-05 | JBU1593 | - | Jul 5, 11:30 UTC | Jul 5, 11:50 UTC | 20m |
| 2026-07-04 | JBU759 | BDL → FLL | Jul 4, 20:35 UTC | Jul 4, 23:10 UTC | 2h 35m |
| 2026-07-04 | JBU1142 | - | Jul 4, 15:10 UTC | Jul 4, 17:30 UTC | 2h 20m |
| 2026-07-04 | JBU1461 | LGA → PBI | Jul 4, 11:10 UTC | Jul 4, 13:25 UTC | 2h 15m |
| 2026-07-04 | JBU572 | - | Jul 4, 00:35 UTC | Jul 4, 03:20 UTC | 2h 45m |
| 2026-07-03 | JBU471 | LGA → FLL | Jul 3, 20:40 UTC | Jul 3, 23:00 UTC | 2h 20m |
| 2026-07-03 | JBU698 | MCO → LGA | Jul 3, 17:10 UTC | Jul 3, 19:15 UTC | 2h 5m |
| 2026-07-03 | JBU2548 | - | Jul 3, 15:05 UTC | Jul 3, 15:40 UTC | 35m |
| 2026-07-03 | JBU2005 | - | Jul 3, 11:45 UTC | Jul 3, 13:55 UTC | 2h 10m |
| 2026-07-03 | JBU2008 | - | Jul 3, 04:05 UTC | Jul 3, 06:05 UTC | 2h 0m |
| 2026-07-02 | JBU305 | - | Jul 2, 23:50 UTC | Jul 3, 02:10 UTC | 2h 20m |
| 2026-07-02 | JBU2420 | - | Jul 2, 17:00 UTC | Jul 2, 21:30 UTC | 4h 30m |
| 2026-07-02 | JBU2219 | - | Jul 2, 13:55 UTC | Jul 2, 14:50 UTC | 55m |
| 2026-07-02 | JBU2219 | - | Jul 2, 10:55 UTC | Jul 2, 11:45 UTC | 50m |
| 2026-07-01 | JBU2031 | - | Jul 1, 19:25 UTC | Jul 1, 19:40 UTC | 15m |
| 2026-07-01 | JBU861 | BOS → SJU | Jul 1, 14:29 UTC | Jul 2, 11:45 UTC | 21h 16m |
| 2026-07-01 | JBU861 | BOS → SJU | Jul 1, 14:30 UTC | Jul 1, 17:55 UTC | 3h 25m |
| 2026-06-30 | JBU1806 | - | Jun 30, 19:20 UTC | Jun 30, 19:45 UTC | 25m |
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 N789JB page for operator, model, and routing details .