sensors Mode-S transponder
A6587B
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N508JL · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORP
- Hex
- A6587B
- Octal
- 51454173
- Decimal
- 10,901,627
- Country
- US
- Tail
- N508JL
- Type
- A320
- Flights observed
- 297
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address A6587B 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 |
|---|---|---|---|
| JBU433 | JetBlue Airways | 4 | 2026-05-23 |
| JBU1990 | - | 4 | 2026-07-11 |
| JBU1797 | - | 4 | 2026-07-08 |
| JBU1743 | - | 4 | 2026-07-06 |
| JBU772 | - | 3 | 2026-06-16 |
| JBU669 | - | 3 | 2026-06-23 |
| JBU389 | JetBlue Airways | 3 | 2026-05-07 |
| JBU38 | JetBlue Airways | 3 | 2026-04-27 |
| JBU250 | JetBlue Airways | 3 | 2026-05-04 |
| JBU1903 | JetBlue Airways | 3 | 2026-06-03 |
| JBU1678 | - | 3 | 2026-06-20 |
| JBU1533 | JetBlue Airways | 3 | 2026-04-24 |
| JBU1532 | JetBlue Airways | 3 | 2026-04-17 |
| JBU143 | JetBlue Airways | 3 | 2026-04-30 |
| JBU1047 | JetBlue Airways | 3 | 2026-05-26 |
| JBU987 | JetBlue Airways | 2 | 2026-05-18 |
| JBU94 | JetBlue Airways | 2 | 2026-06-05 |
| JBU929 | JetBlue Airways | 2 | 2026-05-10 |
| JBU846 | - | 2 | 2026-07-04 |
| JBU768 | JetBlue Airways | 2 | 2026-06-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU517 | BOS → JFK | Jul 13, 13:20 UTC | Jul 14, 01:45 UTC | 12h 26m |
| 2026-07-13 | JBU518 | FLL → ATL | Jul 13, 10:25 UTC | Jul 14, 01:45 UTC | 15h 21m |
| 2026-07-12 | JBU70 | FLL → BOS | Jul 12, 18:51 UTC | Jul 13, 17:25 UTC | 22h 35m |
| 2026-07-12 | JBU761 | BOS → SJU | Jul 12, 10:12 UTC | Jul 13, 01:55 UTC | 15h 44m |
| 2026-07-12 | JBU462 | SJU → BOS | Jul 12, 00:17 UTC | Jul 12, 21:40 UTC | 21h 24m |
| 2026-07-11 | JBU2941 | PUJ → SJU | Jul 11, 22:06 UTC | Jul 12, 17:25 UTC | 19h 20m |
| 2026-07-11 | JBU2031 | SJU → PUJ | Jul 11, 20:06 UTC | Jul 12, 17:25 UTC | 21h 20m |
| 2026-07-11 | JBU2831 | SJU → PUJ | Jul 11, 15:23 UTC | Jul 12, 13:40 UTC | 22h 18m |
| 2026-07-11 | JBU1990 | - | Jul 11, 01:20 UTC | Jul 11, 01:30 UTC | 10m |
| 2026-07-11 | JBU1990 | SJU → EWR | Jul 11, 01:17 UTC | Jul 12, 00:35 UTC | 23h 19m |
| 2026-07-11 | JBU1990 | SJU → EWR | Jul 11, 01:17 UTC | Jul 12, 00:35 UTC | 23h 19m |
| 2026-07-10 | JBU153 | - | Jul 10, 23:45 UTC | Jul 10, 23:55 UTC | 10m |
| 2026-07-10 | JBU153 | - | Jul 10, 21:35 UTC | Jul 10, 22:00 UTC | 25m |
| 2026-07-10 | JBU1796 | CUN → FLL | Jul 10, 18:25 UTC | Jul 10, 19:50 UTC | 1h 25m |
| 2026-07-10 | JBU2795 | - | Jul 10, 14:45 UTC | Jul 10, 16:05 UTC | 1h 20m |
| 2026-07-10 | JBU682 | - | Jul 10, 10:50 UTC | Jul 10, 12:40 UTC | 1h 50m |
| 2026-07-09 | JBU1158 | - | Jul 9, 20:20 UTC | Jul 9, 20:45 UTC | 25m |
| 2026-07-09 | JBU1157 | - | Jul 9, 16:25 UTC | Jul 9, 16:55 UTC | 30m |
| 2026-07-09 | JBU1157 | FLL → LIR | Jul 9, 16:21 UTC | Jul 10, 14:45 UTC | 22h 24m |
| 2026-07-09 | JBU1145 | - | Jul 9, 12:15 UTC | Jul 9, 14:15 UTC | 2h 0m |
| 2026-07-08 | JBU698 | - | Jul 8, 16:40 UTC | Jul 8, 16:45 UTC | 5m |
| 2026-07-08 | JBU2548 | - | Jul 8, 15:00 UTC | Jul 8, 15:35 UTC | 35m |
| 2026-07-08 | JBU2548 | FLL → MCO | Jul 8, 14:57 UTC | Jul 9, 14:15 UTC | 23h 18m |
| 2026-07-08 | JBU1797 | ATL → FLL | Jul 8, 12:30 UTC | Jul 8, 13:55 UTC | 1h 25m |
| 2026-07-08 | JBU719 | JFK → ATL | Jul 8, 01:25 UTC | Jul 8, 03:10 UTC | 1h 45m |
| 2026-07-07 | JBU297 | - | Jul 7, 20:00 UTC | Jul 7, 23:25 UTC | 3h 25m |
| 2026-07-06 | JBU1294 | - | Jul 6, 23:35 UTC | Jul 7, 02:10 UTC | 2h 35m |
| 2026-07-06 | JBU1294 | MCO → HPN | Jul 6, 23:33 UTC | Jul 7, 22:45 UTC | 23h 13m |
| 2026-07-06 | JBU2251 | BOS → MCO | Jul 6, 17:45 UTC | Jul 6, 20:25 UTC | 2h 40m |
| 2026-07-06 | JBU862 | - | Jul 6, 12:10 UTC | Jul 6, 15:45 UTC | 3h 35m |
| 2026-07-06 | JBU1743 | - | Jul 6, 02:05 UTC | Jul 6, 02:25 UTC | 20m |
| 2026-07-05 | JBU1743 | - | Jul 5, 23:50 UTC | Jul 6, 00:35 UTC | 45m |
| 2026-07-05 | JBU1742 | - | Jul 5, 20:30 UTC | Jul 5, 21:40 UTC | 1h 10m |
| 2026-07-05 | JBU2008 | FLL → PIT | Jul 5, 01:18 UTC | Jul 6, 00:35 UTC | 23h 17m |
| 2026-07-04 | JBU1947 | - | Jul 4, 23:20 UTC | Jul 5, 00:00 UTC | 40m |
| 2026-07-04 | JBU1947 | MCO → FLL | Jul 4, 23:16 UTC | Jul 5, 21:40 UTC | 22h 25m |
| 2026-07-04 | JBU547 | - | Jul 4, 18:15 UTC | Jul 4, 20:35 UTC | 2h 20m |
| 2026-07-04 | JBU544 | - | Jul 4, 14:35 UTC | Jul 4, 16:50 UTC | 2h 15m |
| 2026-07-04 | JBU445 | - | Jul 4, 10:25 UTC | Jul 4, 12:50 UTC | 2h 25m |
| 2026-07-04 | JBU846 | - | Jul 4, 03:00 UTC | Jul 4, 05:15 UTC | 2h 15m |
| 2026-07-04 | JBU846 | - | Jul 4, 00:35 UTC | Jul 4, 00:55 UTC | 20m |
| 2026-07-03 | JBU847 | - | Jul 3, 20:45 UTC | Jul 3, 23:25 UTC | 2h 40m |
| 2026-07-03 | JBU544 | - | Jul 3, 17:10 UTC | Jul 3, 19:30 UTC | 2h 20m |
| 2026-07-03 | JBU1241 | - | Jul 3, 13:10 UTC | Jul 3, 15:40 UTC | 2h 30m |
| 2026-07-02 | JBU276 | - | Jul 2, 23:05 UTC | Jul 3, 02:30 UTC | 3h 25m |
| 2026-07-02 | JBU1453 | - | Jul 2, 21:30 UTC | Jul 2, 21:40 UTC | 10m |
| 2026-07-02 | JBU1453 | - | Jul 2, 19:30 UTC | Jul 2, 19:55 UTC | 25m |
| 2026-07-02 | JBU2895 | BOS → FLL | Jul 2, 10:40 UTC | Jul 2, 17:40 UTC | 7h 0m |
| 2026-07-01 | JBU1496 | CUN → FLL | Jul 1, 19:31 UTC | Jul 2, 17:40 UTC | 22h 9m |
| 2026-07-01 | JBU2052 | MCO → BOS | Jul 1, 01:01 UTC | Jul 1, 21:05 UTC | 20h 5m |
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 N508JL page for operator, model, and routing details .