sensors Mode-S transponder
A6A00B
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N526JL · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORP
- Hex
- A6A00B
- Octal
- 51520013
- Decimal
- 10,919,947
- Country
- US
- Tail
- N526JL
- Type
- A320
- Flights observed
- 315
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 45m ago
Last known position
Country allocation
The ICAO 24-bit address A6A00B 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 |
|---|---|---|---|
| JBU2013 | JetBlue Airways | 5 | 2026-04-30 |
| JBU87 | JetBlue Airways | 4 | 2026-06-06 |
| JBU613 | - | 4 | 2026-07-10 |
| JBU2929 | JetBlue Airways | 4 | 2026-04-27 |
| JBU2722 | - | 4 | 2026-07-06 |
| JBU914 | - | 3 | 2026-07-03 |
| JBU88 | JetBlue Airways | 3 | 2026-06-06 |
| JBU85 | - | 3 | 2026-07-13 |
| JBU766 | JetBlue Airways | 3 | 2026-04-15 |
| JBU753 | JetBlue Airways | 3 | 2026-06-13 |
| JBU726 | - | 3 | 2026-07-04 |
| JBU634 | - | 3 | 2026-07-11 |
| JBU627 | JetBlue Airways | 3 | 2026-05-10 |
| JBU492 | - | 3 | 2026-07-13 |
| JBU2631 | JetBlue Airways | 3 | 2026-05-22 |
| JBU241 | JetBlue Airways | 3 | 2026-06-21 |
| JBU2154 | JetBlue Airways | 3 | 2026-06-12 |
| JBU2090 | JetBlue Airways | 3 | 2026-06-17 |
| JBU1823 | JetBlue Airways | 3 | 2026-07-01 |
| JBU1553 | JetBlue Airways | 3 | 2026-05-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU1126 | MBJ → FLL | Jul 14, 17:13 UTC | Jul 15, 02:25 UTC | 9h 12m |
| 2026-07-14 | JBU1127 | - | Jul 14, 14:35 UTC | Jul 14, 14:45 UTC | 10m |
| 2026-07-14 | JBU1197 | - | Jul 14, 10:05 UTC | Jul 14, 12:50 UTC | 2h 45m |
| 2026-07-14 | JBU1197 | PVD → FLL | Jul 14, 10:02 UTC | Jul 15, 02:25 UTC | 16h 23m |
| 2026-07-14 | JBU1075 | MCO → PVD | Jul 14, 00:30 UTC | Jul 14, 02:50 UTC | 2h 20m |
| 2026-07-13 | JBU85 | - | Jul 13, 20:35 UTC | Jul 13, 22:55 UTC | 2h 20m |
| 2026-07-13 | JBU492 | - | Jul 13, 13:10 UTC | Jul 13, 17:50 UTC | 4h 40m |
| 2026-07-12 | JBU618 | JFK → BOS | Jul 12, 22:04 UTC | Jul 13, 20:45 UTC | 22h 42m |
| 2026-07-12 | JBU852 | - | Jul 12, 16:50 UTC | Jul 12, 18:45 UTC | 1h 55m |
| 2026-07-12 | JBU852 | CUN → JFK | Jul 12, 16:46 UTC | Jul 13, 14:45 UTC | 22h 0m |
| 2026-07-12 | JBU851 | JFK → CUN | Jul 12, 11:40 UTC | Jul 12, 14:55 UTC | 3h 15m |
| 2026-07-11 | JBU634 | - | Jul 11, 01:10 UTC | Jul 11, 02:45 UTC | 1h 35m |
| 2026-07-10 | JBU634 | - | Jul 10, 22:45 UTC | Jul 10, 22:55 UTC | 10m |
| 2026-07-10 | JBU634 | SJU → BUF | Jul 10, 22:41 UTC | Jul 11, 13:30 UTC | 14h 50m |
| 2026-07-10 | JBU613 | - | Jul 10, 03:00 UTC | Jul 10, 05:35 UTC | 2h 35m |
| 2026-07-10 | JBU613 | HPN → FLL | Jul 10, 02:59 UTC | Jul 11, 02:45 UTC | 23h 47m |
| 2026-07-09 | JBU548 | - | Jul 9, 21:30 UTC | Jul 10, 00:10 UTC | 2h 40m |
| 2026-07-09 | JBU1366 | CUN → TPA | Jul 9, 17:55 UTC | Jul 9, 19:20 UTC | 1h 25m |
| 2026-07-09 | JBU1365 | TPA → CUN | Jul 9, 15:00 UTC | Jul 9, 16:30 UTC | 1h 30m |
| 2026-07-09 | JBU891 | BOS → TPA | Jul 9, 10:50 UTC | Jul 9, 13:35 UTC | 2h 45m |
| 2026-07-08 | JBU1450 | STI → FLL | Jul 8, 13:31 UTC | Jul 9, 12:45 UTC | 23h 15m |
| 2026-07-07 | JBU1126 | MBJ → FLL | Jul 7, 16:59 UTC | Jul 8, 15:20 UTC | 22h 22m |
| 2026-07-07 | JBU1127 | FLL → MBJ | Jul 7, 14:15 UTC | Jul 8, 10:55 UTC | 20h 41m |
| 2026-07-07 | JBU1906 | TPA → FLL | Jul 7, 11:37 UTC | Jul 8, 10:45 UTC | 23h 9m |
| 2026-07-06 | JBU2722 | MSY → FLL | Jul 6, 23:42 UTC | Jul 7, 21:25 UTC | 21h 44m |
| 2026-07-06 | JBU1799 | ORF → FLL | Jul 6, 16:50 UTC | Jul 7, 14:45 UTC | 21h 55m |
| 2026-07-06 | JBU1906 | TPA → FLL | Jul 6, 11:30 UTC | Jul 7, 04:15 UTC | 16h 45m |
| 2026-07-05 | JBU579 | DCA → FLL | Jul 5, 15:17 UTC | Jul 6, 14:45 UTC | 23h 28m |
| 2026-07-05 | JBU1480 | FLL → DCA | Jul 5, 11:40 UTC | Jul 6, 04:35 UTC | 16h 56m |
| 2026-07-05 | JBU725 | - | Jul 5, 00:30 UTC | Jul 5, 00:45 UTC | 15m |
| 2026-07-04 | JBU726 | - | Jul 4, 22:00 UTC | Jul 4, 23:35 UTC | 1h 35m |
| 2026-07-04 | JBU726 | FLL → RDU | Jul 4, 21:56 UTC | Jul 5, 20:45 UTC | 22h 49m |
| 2026-07-04 | JBU2427 | - | Jul 4, 16:20 UTC | Jul 4, 20:25 UTC | 4h 5m |
| 2026-07-04 | JBU1471 | - | Jul 4, 12:00 UTC | Jul 4, 14:25 UTC | 2h 25m |
| 2026-07-04 | JBU1962 | BDL → LGA | Jul 4, 03:15 UTC | Jul 4, 03:40 UTC | 25m |
| 2026-07-03 | JBU1962 | - | Jul 3, 22:20 UTC | Jul 4, 01:30 UTC | 3h 10m |
| 2026-07-03 | JBU367 | - | Jul 3, 18:30 UTC | Jul 3, 20:50 UTC | 2h 20m |
| 2026-07-03 | JBU1552 | RSW → HPN | Jul 3, 14:45 UTC | Jul 3, 17:15 UTC | 2h 30m |
| 2026-07-03 | JBU1551 | - | Jul 3, 10:50 UTC | Jul 3, 13:25 UTC | 2h 35m |
| 2026-07-03 | JBU914 | - | Jul 3, 02:05 UTC | Jul 3, 02:15 UTC | 10m |
| 2026-07-02 | JBU914 | - | Jul 2, 23:45 UTC | Jul 3, 02:00 UTC | 2h 15m |
| 2026-07-02 | JBU1972 | - | Jul 2, 19:10 UTC | Jul 2, 21:35 UTC | 2h 25m |
| 2026-07-02 | JBU1971 | - | Jul 2, 15:15 UTC | Jul 2, 17:40 UTC | 2h 25m |
| 2026-07-01 | JBU2722 | MSY → FLL | Jul 1, 21:02 UTC | Jul 2, 20:45 UTC | 23h 43m |
| 2026-07-01 | JBU1823 | JFK → LAX | Jul 1, 17:52 UTC | Jul 2, 16:45 UTC | 22h 53m |
| 2026-07-01 | JBU1801 | JFK → FLL | Jul 1, 14:05 UTC | Jul 2, 12:45 UTC | 22h 40m |
| 2026-07-01 | JBU1678 | JAX → JFK | Jul 1, 10:15 UTC | Jul 2, 02:15 UTC | 16h 1m |
| 2026-07-01 | JBU1677 | JFK → JAX | Jul 1, 02:43 UTC | Jul 2, 00:45 UTC | 22h 3m |
| 2026-06-30 | JBU1568 | PUJ → JFK | Jun 30, 19:31 UTC | Jul 1, 18:45 UTC | 23h 15m |
| 2026-06-30 | JBU1568 | PUJ → JFK | Jun 30, 16:05 UTC | Jun 30, 23:00 UTC | 6h 55m |
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 N526JL page for operator, model, and routing details .