sensors Mode-S transponder
A6AB27
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N529JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORPORATION
- Hex
- A6AB27
- Octal
- 51525447
- Decimal
- 10,922,791
- Country
- US
- Tail
- N529JB
- Type
- A320
- Flights observed
- 311
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address A6AB27 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 |
|---|---|---|---|
| JBU808 | JetBlue Airways | 6 | 2026-04-26 |
| JBU929 | JetBlue Airways | 4 | 2026-06-01 |
| JBU928 | JetBlue Airways | 4 | 2026-06-01 |
| JBU88 | - | 4 | 2026-06-29 |
| JBU351 | - | 4 | 2026-07-12 |
| JBU1751 | JetBlue Airways | 4 | 2026-05-02 |
| JBU1476 | JetBlue Airways | 4 | 2026-06-08 |
| JBU1462 | - | 4 | 2026-04-13 |
| JBU87 | - | 3 | 2026-06-17 |
| JBU754 | JetBlue Airways | 3 | 2026-05-02 |
| JBU613 | JetBlue Airways | 3 | 2026-06-09 |
| JBU563 | JetBlue Airways | 3 | 2026-05-31 |
| JBU525 | JetBlue Airways | 3 | 2026-05-09 |
| JBU403 | JetBlue Airways | 3 | 2026-05-22 |
| JBU376 | - | 3 | 2026-07-09 |
| JBU350 | JetBlue Airways | 3 | 2026-04-30 |
| JBU334 | JetBlue Airways | 3 | 2026-06-11 |
| JBU2825 | JetBlue Airways | 3 | 2026-05-01 |
| JBU2404 | JetBlue Airways | 3 | 2026-05-04 |
| JBU1868 | JetBlue Airways | 3 | 2026-05-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU1365 | TPA → CUN | Jul 13, 15:10 UTC | Jul 14, 01:00 UTC | 9h 51m |
| 2026-07-13 | JBU891 | BOS → TPA | Jul 13, 10:37 UTC | Jul 14, 01:00 UTC | 14h 24m |
| 2026-07-13 | JBU1952 | MCO → BOS | Jul 13, 01:54 UTC | Jul 14, 01:00 UTC | 23h 7m |
| 2026-07-12 | JBU1537 | BDL → MCO | Jul 12, 21:41 UTC | Jul 13, 19:45 UTC | 22h 5m |
| 2026-07-12 | JBU1578 | MCO → BDL | Jul 12, 17:53 UTC | Jul 13, 16:40 UTC | 22h 48m |
| 2026-07-12 | JBU351 | BOS → MCO | Jul 12, 13:03 UTC | Jul 13, 11:45 UTC | 22h 43m |
| 2026-07-12 | JBU351 | BOS → MCO | Jul 12, 13:05 UTC | Jul 12, 15:40 UTC | 2h 35m |
| 2026-07-12 | JBU470 | - | Jul 12, 02:55 UTC | Jul 12, 05:30 UTC | 2h 35m |
| 2026-07-11 | JBU2269 | BOS → FLL | Jul 11, 22:35 UTC | Jul 12, 01:20 UTC | 2h 45m |
| 2026-07-11 | JBU782 | - | Jul 11, 19:50 UTC | Jul 11, 20:55 UTC | 1h 5m |
| 2026-07-11 | JBU781 | - | Jul 11, 16:30 UTC | Jul 11, 17:50 UTC | 1h 20m |
| 2026-07-10 | JBU1454 | SJU → FLL | Jul 10, 20:54 UTC | Jul 11, 17:50 UTC | 20h 57m |
| 2026-07-10 | JBU1089 | - | Jul 10, 13:15 UTC | Jul 10, 13:35 UTC | 20m |
| 2026-07-10 | JBU1089 | EWR → SJU | Jul 10, 10:13 UTC | Jul 11, 09:45 UTC | 23h 33m |
| 2026-07-10 | JBU1089 | - | Jul 10, 10:15 UTC | Jul 10, 11:00 UTC | 45m |
| 2026-07-10 | JBU706 | - | Jul 10, 04:05 UTC | Jul 10, 06:20 UTC | 2h 15m |
| 2026-07-09 | JBU590 | - | Jul 9, 17:20 UTC | Jul 9, 22:45 UTC | 5h 25m |
| 2026-07-09 | JBU376 | - | Jul 9, 01:45 UTC | Jul 9, 04:00 UTC | 2h 15m |
| 2026-07-09 | JBU376 | FLL → PHL | Jul 9, 01:42 UTC | Jul 9, 22:45 UTC | 21h 3m |
| 2026-07-08 | JBU469 | - | Jul 8, 21:35 UTC | Jul 9, 00:25 UTC | 2h 50m |
| 2026-07-08 | JBU2896 | - | Jul 8, 11:25 UTC | Jul 8, 18:40 UTC | 7h 15m |
| 2026-07-07 | JBU1694 | MCO → HPN | Jul 7, 20:58 UTC | Jul 8, 19:45 UTC | 22h 48m |
| 2026-07-07 | JBU1694 | MCO → HPN | Jul 7, 21:00 UTC | Jul 7, 23:15 UTC | 2h 15m |
| 2026-07-07 | JBU547 | - | Jul 7, 16:30 UTC | Jul 7, 18:40 UTC | 2h 10m |
| 2026-07-07 | JBU546 | - | Jul 7, 14:35 UTC | Jul 7, 14:45 UTC | 10m |
| 2026-07-07 | JBU546 | - | Jul 7, 12:35 UTC | Jul 7, 14:30 UTC | 1h 55m |
| 2026-07-06 | JBU1043 | ROC → MCO | Jul 6, 19:11 UTC | Jul 7, 17:45 UTC | 22h 35m |
| 2026-07-06 | JBU1042 | SAV → JFK | Jul 6, 15:47 UTC | Jul 7, 13:45 UTC | 21h 59m |
| 2026-07-06 | JBU1076 | PVD → MCO | Jul 6, 11:55 UTC | Jul 7, 11:45 UTC | 23h 51m |
| 2026-07-05 | JBU435 | STT → SJU | Jul 5, 19:59 UTC | Jul 6, 19:45 UTC | 23h 46m |
| 2026-07-05 | JBU936 | SJU → STT | Jul 5, 18:42 UTC | Jul 6, 17:45 UTC | 23h 4m |
| 2026-07-05 | JBU861 | - | Jul 5, 13:55 UTC | Jul 5, 14:55 UTC | 1h 0m |
| 2026-07-05 | JBU861 | BOS → SJU | Jul 5, 13:54 UTC | Jul 6, 13:45 UTC | 23h 52m |
| 2026-07-05 | JBU198 | SEA → BOS | Jul 5, 06:55 UTC | Jul 5, 11:40 UTC | 4h 45m |
| 2026-07-04 | JBU785 | BOS → POP | Jul 4, 11:32 UTC | Jul 5, 09:45 UTC | 22h 14m |
| 2026-07-03 | JBU240 | NAS → MCO | Jul 3, 19:25 UTC | Jul 4, 12:05 UTC | 16h 41m |
| 2026-07-03 | JBU351 | BOS → MCO | Jul 3, 13:04 UTC | Jul 4, 11:45 UTC | 22h 41m |
| 2026-07-03 | JBU351 | BOS → MCO | Jul 3, 13:05 UTC | Jul 3, 15:40 UTC | 2h 35m |
| 2026-07-02 | JBU2052 | - | Jul 2, 22:15 UTC | Jul 3, 00:45 UTC | 2h 30m |
| 2026-07-02 | JBU1827 | EWR → MCO | Jul 2, 17:55 UTC | Jul 2, 20:10 UTC | 2h 15m |
| 2026-07-02 | JBU2028 | - | Jul 2, 14:15 UTC | Jul 2, 16:20 UTC | 2h 5m |
| 2026-07-02 | JBU927 | - | Jul 2, 10:20 UTC | Jul 2, 12:25 UTC | 2h 5m |
| 2026-07-01 | JBU1450 | STI → FLL | Jul 1, 13:21 UTC | Jul 2, 11:45 UTC | 22h 24m |
| 2026-07-01 | JBU1449 | - | Jul 1, 10:20 UTC | Jul 1, 10:50 UTC | 30m |
| 2026-07-01 | JBU1449 | FLL → STI | Jul 1, 10:19 UTC | Jul 2, 09:40 UTC | 23h 21m |
| 2026-06-29 | JBU2076 | TPA → FLL | Jun 29, 20:10 UTC | Jun 29, 20:54 UTC | 45m |
| 2026-06-29 | JBU1005 | FLL → TPA | Jun 29, 17:54 UTC | Jun 29, 20:54 UTC | 3h 1m |
| 2026-06-29 | JBU1126 | MBJ → FLL | Jun 29, 15:06 UTC | Jun 29, 20:54 UTC | 5h 49m |
| 2026-06-29 | JBU88 | ALB → FLL | Jun 29, 00:26 UTC | Jun 29, 20:54 UTC | 20h 29m |
| 2026-06-28 | JBU1062 | PBI → LGA | Jun 28, 11:54 UTC | Jun 29, 03:20 UTC | 15h 26m |
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 N529JB page for operator, model, and routing details .