sensors Mode-S transponder
A6B4F7
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N531JL · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORP
- Hex
- A6B4F7
- Octal
- 51532367
- Decimal
- 10,925,303
- Country
- US
- Tail
- N531JL
- Type
- A320
- Flights observed
- 248
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 11d ago
Last known position
Country allocation
The ICAO 24-bit address A6B4F7 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 |
|---|---|---|---|
| JBU1903 | JetBlue Airways | 4 | 2026-05-22 |
| JBU1241 | - | 4 | 2026-06-29 |
| JBU773 | JetBlue Airways | 3 | 2026-05-23 |
| JBU462 | - | 3 | 2026-06-24 |
| JBU2795 | JetBlue Airways | 3 | 2026-06-04 |
| JBU2153 | JetBlue Airways | 3 | 2026-06-20 |
| JBU2028 | JetBlue Airways | 3 | 2026-06-13 |
| JBU1811 | JetBlue Airways | 3 | 2026-04-14 |
| JBU1754 | JetBlue Airways | 3 | 2026-06-18 |
| JBU1447 | - | 3 | 2026-07-01 |
| JBU1112 | JetBlue Airways | 3 | 2026-06-11 |
| JBU969 | - | 2 | 2026-06-25 |
| JBU929 | JetBlue Airways | 2 | 2026-04-27 |
| JBU88 | JetBlue Airways | 2 | 2026-05-28 |
| JBU8358 | JetBlue Airways | 2 | 2026-05-01 |
| JBU795 | JetBlue Airways | 2 | 2026-04-18 |
| JBU737 | - | 2 | 2026-04-14 |
| JBU675 | - | 2 | 2026-06-29 |
| JBU606 | - | 2 | 2026-07-02 |
| JBU575 | JetBlue Airways | 2 | 2026-06-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-02 | JBU606 | SDQ → MCO | Jul 2, 17:49 UTC | Jul 3, 08:55 UTC | 15h 7m |
| 2026-07-02 | JBU606 | - | Jul 2, 14:05 UTC | Jul 2, 20:10 UTC | 6h 5m |
| 2026-07-01 | JBU404 | SJU → RDU | Jul 1, 19:17 UTC | Jul 2, 14:45 UTC | 19h 28m |
| 2026-07-01 | JBU1751 | TPA → SJU | Jul 1, 15:15 UTC | Jul 2, 13:45 UTC | 22h 31m |
| 2026-07-01 | JBU1447 | HPN → TPA | Jul 1, 11:40 UTC | Jul 2, 09:45 UTC | 22h 5m |
| 2026-06-30 | JBU545 | - | Jun 30, 18:35 UTC | Jun 30, 21:00 UTC | 2h 25m |
| 2026-06-30 | JBU545 | ISP → PBI | Jun 30, 18:34 UTC | Jul 1, 17:45 UTC | 23h 12m |
| 2026-06-30 | JBU444 | - | Jun 30, 14:35 UTC | Jun 30, 17:05 UTC | 2h 30m |
| 2026-06-29 | JBU847 | ISP → MCO | Jun 29, 20:44 UTC | Jun 30, 19:45 UTC | 23h 2m |
| 2026-06-29 | JBU1241 | - | Jun 29, 13:09 UTC | Jun 29, 15:39 UTC | 2h 30m |
| 2026-06-29 | JBU1241 | BDL → PBI | Jun 29, 13:08 UTC | Jun 30, 11:45 UTC | 22h 38m |
| 2026-06-29 | JBU675 | - | Jun 29, 04:20 UTC | Jun 29, 04:50 UTC | 30m |
| 2026-06-29 | JBU1117 | - | Jun 29, 01:39 UTC | Jun 29, 02:25 UTC | 45m |
| 2026-06-28 | JBU1433 | MCO → SJU | Jun 28, 04:09 UTC | Jun 29, 02:25 UTC | 22h 16m |
| 2026-06-27 | JBU768 | PSE → MCO | Jun 27, 21:51 UTC | Jun 28, 20:04 UTC | 22h 14m |
| 2026-06-27 | JBU767 | MCO → PSE | Jun 27, 18:09 UTC | Jun 28, 17:34 UTC | 23h 26m |
| 2026-06-27 | JBU546 | MCO → ISP | Jun 27, 10:39 UTC | Jun 28, 06:40 UTC | 20h 1m |
| 2026-06-27 | JBU283 | JFK → MCO | Jun 27, 01:15 UTC | Jun 27, 03:49 UTC | 2h 35m |
| 2026-06-26 | JBU1084 | MCO → JFK | Jun 26, 20:55 UTC | Jun 26, 23:09 UTC | 2h 15m |
| 2026-06-26 | JBU547 | - | Jun 26, 15:49 UTC | Jun 26, 18:04 UTC | 2h 15m |
| 2026-06-26 | JBU546 | MCO → ISP | Jun 26, 12:24 UTC | Jun 26, 14:39 UTC | 2h 15m |
| 2026-06-25 | JBU969 | - | Jun 25, 18:24 UTC | Jun 25, 20:05 UTC | 1h 40m |
| 2026-06-25 | JBU969 | RIC → MCO | Jun 25, 18:21 UTC | Jun 26, 17:44 UTC | 23h 24m |
| 2026-06-25 | JBU670 | - | Jun 25, 15:20 UTC | Jun 25, 16:55 UTC | 1h 35m |
| 2026-06-25 | JBU1076 | MCO → PVD | Jun 25, 11:19 UTC | Jun 25, 13:45 UTC | 2h 25m |
| 2026-06-24 | JBU526 | SJU → PVD | Jun 24, 22:49 UTC | Jun 25, 02:19 UTC | 3h 30m |
| 2026-06-24 | JBU1453 | - | Jun 24, 21:19 UTC | Jun 24, 21:29 UTC | 10m |
| 2026-06-24 | JBU1453 | - | Jun 24, 19:20 UTC | Jun 24, 19:49 UTC | 30m |
| 2026-06-24 | JBU462 | - | Jun 24, 03:55 UTC | Jun 24, 04:34 UTC | 40m |
| 2026-06-24 | JBU462 | - | Jun 24, 01:04 UTC | Jun 24, 01:19 UTC | 15m |
| 2026-06-24 | JBU462 | SJU → BOS | Jun 24, 01:01 UTC | Jun 24, 23:14 UTC | 22h 14m |
| 2026-06-23 | JBU153 | - | Jun 23, 22:29 UTC | Jun 23, 22:40 UTC | 10m |
| 2026-06-23 | JBU153 | - | Jun 23, 20:24 UTC | Jun 23, 20:54 UTC | 30m |
| 2026-06-23 | JBU105 | JFK → ORD | Jun 23, 16:20 UTC | Jun 23, 18:45 UTC | 2h 25m |
| 2026-06-23 | JBU2144 | - | Jun 23, 11:54 UTC | Jun 23, 14:10 UTC | 2h 15m |
| 2026-06-22 | JBU1567 | - | Jun 22, 23:50 UTC | Jun 23, 02:09 UTC | 2h 20m |
| 2026-06-22 | JBU1552 | RSW → HPN | Jun 22, 14:45 UTC | Jun 22, 17:15 UTC | 2h 30m |
| 2026-06-22 | JBU1551 | - | Jun 22, 10:49 UTC | Jun 22, 13:19 UTC | 2h 30m |
| 2026-06-21 | JBU548 | TPA → HPN | Jun 21, 23:50 UTC | Jun 22, 02:10 UTC | 2h 20m |
| 2026-06-21 | JBU873 | BOS → AUA | Jun 21, 19:20 UTC | Jun 21, 21:39 UTC | 2h 20m |
| 2026-06-21 | JBU2274 | TPA → EWR | Jun 21, 14:30 UTC | Jun 21, 16:39 UTC | 2h 10m |
| 2026-06-20 | JBU551 | BOS → MCO | Jun 20, 19:34 UTC | Jun 21, 15:44 UTC | 20h 11m |
| 2026-06-20 | JBU2153 | BOS → GND | Jun 20, 04:34 UTC | Jun 20, 04:49 UTC | 15m |
| 2026-06-20 | JBU2153 | BOS → GND | Jun 20, 02:40 UTC | Jun 20, 03:09 UTC | 30m |
| 2026-06-20 | JBU2153 | BOS → GND | Jun 20, 02:36 UTC | Jun 21, 01:45 UTC | 23h 9m |
| 2026-06-19 | JBU482 | DFW → FLL | Jun 19, 21:49 UTC | Jun 20, 00:29 UTC | 2h 40m |
| 2026-06-19 | JBU2269 | BOS → FLL | Jun 19, 00:40 UTC | Jun 19, 23:44 UTC | 23h 5m |
| 2026-06-18 | JBU1754 | SJU → FLL | Jun 18, 15:40 UTC | Jun 18, 15:45 UTC | 5m |
| 2026-06-18 | JBU525 | - | Jun 18, 11:05 UTC | Jun 18, 14:30 UTC | 3h 25m |
| 2026-06-18 | JBU525 | PVD → SJU | Jun 18, 11:04 UTC | Jun 19, 03:29 UTC | 16h 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 N531JL page for operator, model, and routing details .