sensors Mode-S transponder
A81ABE
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N621JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS
- Hex
- A81ABE
- Octal
- 52015276
- Decimal
- 11,016,894
- Country
- US
- Tail
- N621JB
- Type
- A320
- Flights observed
- 323
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address A81ABE 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 |
|---|---|---|---|
| JBU754 | - | 6 | 2026-07-12 |
| JBU1751 | - | 6 | 2026-07-13 |
| JBU163 | - | 5 | 2026-06-30 |
| JBU85 | - | 4 | 2026-06-21 |
| JBU553 | - | 4 | 2026-06-29 |
| JBU503 | JetBlue Airways | 4 | 2026-05-03 |
| JBU1553 | - | 4 | 2026-06-24 |
| JBU1453 | JetBlue Airways | 4 | 2026-06-04 |
| JBU861 | - | 3 | 2026-07-11 |
| JBU719 | - | 3 | 2026-07-04 |
| JBU697 | JetBlue Airways | 3 | 2026-05-17 |
| JBU696 | JetBlue Airways | 3 | 2026-05-17 |
| JBU504 | JetBlue Airways | 3 | 2026-06-16 |
| JBU499 | JetBlue Airways | 3 | 2026-05-01 |
| JBU461 | JetBlue Airways | 3 | 2026-05-05 |
| JBU2097 | - | 3 | 2026-07-09 |
| JBU2054 | JetBlue Airways | 3 | 2026-05-22 |
| JBU2020 | - | 3 | 2026-07-08 |
| JBU1852 | JetBlue Airways | 3 | 2026-07-03 |
| JBU1476 | - | 3 | 2026-07-06 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU238 | SDQ → SJU | Jul 13, 21:42 UTC | Jul 14, 03:30 UTC | 5h 49m |
| 2026-07-13 | JBU1751 | - | Jul 13, 16:45 UTC | Jul 13, 17:00 UTC | 15m |
| 2026-07-13 | JBU1751 | - | Jul 13, 14:20 UTC | Jul 13, 15:10 UTC | 50m |
| 2026-07-13 | JBU1751 | TPA → SJU | Jul 13, 14:18 UTC | Jul 14, 03:30 UTC | 13h 13m |
| 2026-07-13 | JBU225 | - | Jul 13, 10:35 UTC | Jul 13, 12:50 UTC | 2h 15m |
| 2026-07-13 | JBU18 | - | Jul 13, 00:30 UTC | Jul 13, 05:01 UTC | 4h 30m |
| 2026-07-12 | JBU17 | - | Jul 12, 18:25 UTC | Jul 12, 22:35 UTC | 4h 10m |
| 2026-07-12 | JBU2102 | - | Jul 12, 14:15 UTC | Jul 12, 16:25 UTC | 2h 10m |
| 2026-07-12 | JBU754 | - | Jul 12, 11:15 UTC | Jul 12, 11:50 UTC | 35m |
| 2026-07-12 | JBU754 | - | Jul 12, 09:40 UTC | Jul 12, 09:55 UTC | 15m |
| 2026-07-11 | JBU861 | - | Jul 11, 17:40 UTC | Jul 11, 18:05 UTC | 25m |
| 2026-07-11 | JBU861 | BOS → SJU | Jul 11, 14:21 UTC | Jul 12, 11:50 UTC | 21h 30m |
| 2026-07-11 | JBU861 | - | Jul 11, 14:25 UTC | Jul 11, 15:30 UTC | 1h 5m |
| 2026-07-10 | JBU1136 | - | Jul 10, 23:00 UTC | Jul 11, 00:25 UTC | 1h 25m |
| 2026-07-10 | JBU1237 | BOS → DTW | Jul 10, 20:25 UTC | Jul 10, 22:00 UTC | 1h 35m |
| 2026-07-10 | JBU2471 | FLL → BQN | Jul 10, 03:00 UTC | Jul 11, 00:35 UTC | 21h 36m |
| 2026-07-09 | JBU326 | MBJ → FLL | Jul 9, 22:55 UTC | Jul 10, 21:30 UTC | 22h 36m |
| 2026-07-09 | JBU2427 | FLL → MBJ | Jul 9, 20:17 UTC | Jul 10, 19:15 UTC | 22h 58m |
| 2026-07-09 | JBU2097 | ATL → FLL | Jul 9, 17:05 UTC | Jul 9, 18:30 UTC | 1h 25m |
| 2026-07-09 | JBU2097 | ATL → FLL | Jul 9, 17:04 UTC | Jul 10, 15:30 UTC | 22h 26m |
| 2026-07-09 | JBU1698 | PPM → ATL | Jul 9, 14:20 UTC | Jul 9, 15:40 UTC | 1h 20m |
| 2026-07-09 | JBU2005 | - | Jul 9, 10:15 UTC | Jul 9, 12:40 UTC | 2h 25m |
| 2026-07-08 | JBU2020 | - | Jul 8, 17:10 UTC | Jul 8, 17:30 UTC | 20m |
| 2026-07-08 | JBU669 | BOS → FLL | Jul 8, 13:09 UTC | Jul 9, 11:30 UTC | 22h 21m |
| 2026-07-08 | JBU669 | BOS → FLL | Jul 8, 13:10 UTC | Jul 8, 15:50 UTC | 2h 40m |
| 2026-07-08 | JBU2052 | MCO → BOS | Jul 8, 00:00 UTC | Jul 8, 03:20 UTC | 3h 20m |
| 2026-07-07 | JBU2932 | PUJ → SJU | Jul 7, 00:34 UTC | Jul 7, 23:15 UTC | 22h 42m |
| 2026-07-06 | JBU1476 | - | Jul 6, 13:45 UTC | Jul 6, 14:40 UTC | 55m |
| 2026-07-06 | JBU1476 | - | Jul 6, 11:10 UTC | Jul 6, 11:20 UTC | 10m |
| 2026-07-06 | JBU1476 | SJU → BDL | Jul 6, 11:09 UTC | Jul 7, 01:05 UTC | 13h 57m |
| 2026-07-06 | JBU433 | BTV → JFK | Jul 6, 01:45 UTC | Jul 6, 02:10 UTC | 25m |
| 2026-07-05 | JBU433 | BTV → JFK | Jul 5, 23:35 UTC | Jul 6, 00:15 UTC | 40m |
| 2026-07-05 | JBU102 | JFK → BUF | Jul 5, 04:22 UTC | Jul 6, 02:10 UTC | 21h 48m |
| 2026-07-04 | JBU765 | JFK → GCM | Jul 4, 15:54 UTC | Jul 5, 15:30 UTC | 23h 37m |
| 2026-07-04 | JBU320 | ATL → JFK | Jul 4, 10:12 UTC | Jul 5, 05:20 UTC | 19h 8m |
| 2026-07-04 | JBU719 | JFK → ATL | Jul 4, 02:18 UTC | Jul 5, 00:25 UTC | 22h 7m |
| 2026-07-04 | JBU719 | JFK → ATL | Jul 4, 02:20 UTC | Jul 4, 04:05 UTC | 1h 45m |
| 2026-07-03 | JBU1852 | CUN → JFK | Jul 3, 19:20 UTC | Jul 3, 22:40 UTC | 3h 20m |
| 2026-07-03 | JBU1851 | JFK → CUN | Jul 3, 14:10 UTC | Jul 3, 17:35 UTC | 3h 25m |
| 2026-07-03 | JBU320 | ATL → JFK | Jul 3, 10:10 UTC | Jul 3, 12:00 UTC | 1h 50m |
| 2026-07-03 | JBU719 | JFK → ATL | Jul 3, 02:05 UTC | Jul 3, 03:50 UTC | 1h 45m |
| 2026-07-02 | JBU1852 | CUN → JFK | Jul 2, 19:30 UTC | Jul 2, 22:50 UTC | 3h 20m |
| 2026-07-02 | JBU1851 | JFK → CUN | Jul 2, 14:30 UTC | Jul 2, 18:00 UTC | 3h 30m |
| 2026-07-01 | JBU1640 | SVD → JFK | Jul 1, 21:05 UTC | Jul 2, 19:30 UTC | 22h 25m |
| 2026-07-01 | JBU1639 | - | Jul 1, 17:25 UTC | Jul 1, 22:20 UTC | 4h 55m |
| 2026-07-01 | JBU1639 | - | Jul 1, 14:40 UTC | Jul 1, 15:05 UTC | 25m |
| 2026-07-01 | JBU1038 | - | Jul 1, 09:15 UTC | Jul 1, 12:30 UTC | 3h 15m |
| 2026-06-30 | JBU1039 | - | Jun 30, 20:50 UTC | Jun 30, 23:40 UTC | 2h 50m |
| 2026-06-30 | JBU164 | - | Jun 30, 15:20 UTC | Jun 30, 17:40 UTC | 2h 20m |
| 2026-06-30 | JBU163 | JFK → SRQ | Jun 30, 11:25 UTC | Jun 30, 13:35 UTC | 2h 10m |
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 N621JB page for operator, model, and routing details .