sensors Mode-S transponder
A8AEF3
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N659JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORP
- Hex
- A8AEF3
- Octal
- 52127363
- Decimal
- 11,054,835
- Country
- US
- Tail
- N659JB
- Type
- A320
- Flights observed
- 281
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address A8AEF3 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 |
|---|---|---|---|
| JBU304 | - | 5 | 2026-07-08 |
| JBU993 | JetBlue Airways | 4 | 2026-04-18 |
| JBU1584 | JetBlue Airways | 4 | 2026-04-15 |
| JBU1483 | JetBlue Airways | 4 | 2026-04-15 |
| JBU98 | JetBlue Airways | 3 | 2026-04-15 |
| JBU97 | JetBlue Airways | 3 | 2026-04-15 |
| JBU872 | JetBlue Airways | 3 | 2026-04-17 |
| JBU871 | JetBlue Airways | 3 | 2026-04-17 |
| JBU8503 | JetBlue Airways | 3 | 2026-05-14 |
| JBU41 | - | 3 | 2026-06-20 |
| JBU337 | JetBlue Airways | 3 | 2026-05-17 |
| JBU275 | - | 3 | 2026-07-01 |
| JBU2133 | JetBlue Airways | 3 | 2026-04-28 |
| JBU1889 | - | 3 | 2026-07-04 |
| JBU1533 | JetBlue Airways | 3 | 2026-04-13 |
| JBU1461 | JetBlue Airways | 3 | 2026-06-15 |
| JBU1453 | - | 3 | 2026-07-07 |
| JBU1400 | - | 3 | 2026-04-13 |
| JBU1128 | JetBlue Airways | 3 | 2026-05-15 |
| JBU927 | JetBlue Airways | 2 | 2026-05-31 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU1950 | RSW → BUF | Jul 14, 19:05 UTC | Jul 15, 14:35 UTC | 19h 30m |
| 2026-07-14 | JBU2049 | BUF → RSW | Jul 14, 15:15 UTC | Jul 14, 17:40 UTC | 2h 25m |
| 2026-07-14 | JBU2049 | BUF → RSW | Jul 14, 15:15 UTC | Jul 15, 14:35 UTC | 23h 20m |
| 2026-07-13 | JBU861 | BOS → SJU | Jul 13, 14:40 UTC | Jul 14, 02:45 UTC | 12h 6m |
| 2026-07-13 | JBU690 | FLL → BOS | Jul 13, 10:12 UTC | Jul 14, 02:45 UTC | 16h 34m |
| 2026-07-13 | JBU1990 | SJU → EWR | Jul 13, 00:40 UTC | Jul 13, 21:30 UTC | 20h 51m |
| 2026-07-12 | JBU269 | BOS → FLL | Jul 12, 16:56 UTC | Jul 13, 15:15 UTC | 22h 20m |
| 2026-07-11 | JBU2937 | - | Jul 11, 22:01 UTC | Jul 12, 00:20 UTC | 2h 20m |
| 2026-07-11 | JBU2937 | BDL → MCO | Jul 11, 21:55 UTC | Jul 12, 18:45 UTC | 20h 51m |
| 2026-07-11 | JBU760 | - | Jul 11, 20:20 UTC | Jul 11, 20:40 UTC | 20m |
| 2026-07-11 | JBU760 | - | Jul 11, 16:30 UTC | Jul 11, 19:20 UTC | 2h 50m |
| 2026-07-11 | JBU1145 | - | Jul 11, 12:20 UTC | Jul 11, 14:15 UTC | 1h 55m |
| 2026-07-11 | JBU1146 | PPM → RIC | Jul 11, 01:30 UTC | Jul 11, 03:25 UTC | 1h 55m |
| 2026-07-10 | JBU789 | - | Jul 10, 21:40 UTC | Jul 11, 00:15 UTC | 2h 35m |
| 2026-07-10 | JBU790 | - | Jul 10, 18:00 UTC | Jul 10, 20:35 UTC | 2h 35m |
| 2026-07-10 | JBU2995 | - | Jul 10, 12:30 UTC | Jul 10, 14:35 UTC | 2h 5m |
| 2026-07-10 | JBU2594 | - | Jul 10, 01:00 UTC | Jul 10, 03:00 UTC | 2h 0m |
| 2026-07-09 | JBU1417 | - | Jul 9, 19:40 UTC | Jul 9, 20:35 UTC | 55m |
| 2026-07-09 | JBU2118 | - | Jul 9, 17:35 UTC | Jul 9, 18:30 UTC | 55m |
| 2026-07-08 | JBU2510 | SDQ → JFK | Jul 8, 21:05 UTC | Jul 9, 20:35 UTC | 23h 31m |
| 2026-07-08 | JBU1009 | JFK → SDQ | Jul 8, 15:24 UTC | Jul 9, 14:25 UTC | 23h 2m |
| 2026-07-08 | JBU2718 | JFK → BOS | Jul 8, 10:55 UTC | Jul 9, 10:10 UTC | 23h 16m |
| 2026-07-08 | JBU304 | - | Jul 8, 02:10 UTC | Jul 8, 02:55 UTC | 45m |
| 2026-07-07 | JBU304 | - | Jul 7, 23:35 UTC | Jul 7, 23:45 UTC | 10m |
| 2026-07-07 | JBU304 | SJU → JFK | Jul 7, 23:31 UTC | Jul 8, 16:45 UTC | 17h 15m |
| 2026-07-07 | JBU1453 | - | Jul 7, 22:05 UTC | Jul 7, 22:15 UTC | 10m |
| 2026-07-07 | JBU1940 | SRQ → BOS | Jul 7, 02:12 UTC | Jul 7, 23:45 UTC | 21h 33m |
| 2026-07-06 | JBU1941 | BOS → SRQ | Jul 6, 21:43 UTC | Jul 7, 20:35 UTC | 22h 53m |
| 2026-07-06 | JBU1159 | - | Jul 6, 10:25 UTC | Jul 6, 11:35 UTC | 1h 10m |
| 2026-07-06 | JBU1159 | BOS → PHL | Jul 6, 10:25 UTC | Jul 7, 05:30 UTC | 19h 6m |
| 2026-07-05 | JBU562 | SJU → BOS | Jul 5, 10:07 UTC | Jul 6, 02:10 UTC | 16h 3m |
| 2026-07-05 | JBU1433 | MCO → SJU | Jul 5, 02:12 UTC | Jul 6, 00:45 UTC | 22h 33m |
| 2026-07-04 | JBU1889 | EWR → SJU | Jul 4, 17:34 UTC | Jul 5, 16:45 UTC | 23h 12m |
| 2026-07-04 | JBU2890 | SJU → EWR | Jul 4, 12:05 UTC | Jul 5, 10:25 UTC | 22h 21m |
| 2026-07-04 | JBU1903 | RDU → SJU | Jul 4, 00:02 UTC | Jul 4, 22:20 UTC | 22h 19m |
| 2026-07-03 | JBU404 | SJU → RDU | Jul 3, 19:10 UTC | Jul 4, 18:20 UTC | 23h 10m |
| 2026-07-03 | JBU548 | TPA → HPN | Jul 3, 01:25 UTC | Jul 4, 00:35 UTC | 23h 10m |
| 2026-07-02 | JBU225 | JFK → TPA | Jul 2, 10:44 UTC | Jul 3, 03:50 UTC | 17h 7m |
| 2026-07-01 | JBU8364 | DCA → BOS | Jul 1, 22:30 UTC | Jul 1, 22:45 UTC | 15m |
| 2026-07-01 | JBU8364 | DCA → BOS | Jul 1, 22:28 UTC | Jul 2, 16:45 UTC | 18h 17m |
| 2026-07-01 | JBU275 | - | Jul 1, 21:05 UTC | Jul 1, 21:25 UTC | 20m |
| 2026-07-01 | JBU275 | - | Jul 1, 18:00 UTC | Jul 1, 18:40 UTC | 40m |
| 2026-07-01 | JBU438 | MCO → BDL | Jul 1, 02:35 UTC | Jul 1, 04:55 UTC | 2h 20m |
| 2026-06-30 | JBU1778 | - | Jun 30, 23:15 UTC | Jul 1, 00:10 UTC | 55m |
| 2026-06-30 | JBU1778 | MCO → FLL | Jun 30, 12:20 UTC | Jun 30, 18:50 UTC | 6h 30m |
| 2026-06-29 | JBU234 | SJU → MCO | Jun 29, 06:54 UTC | Jun 29, 18:44 UTC | 11h 51m |
| 2026-06-28 | JBU761 | BOS → SJU | Jun 28, 10:07 UTC | Jun 29, 08:44 UTC | 22h 38m |
| 2026-06-28 | JBU761 | BOS → SJU | Jun 28, 10:10 UTC | Jun 28, 14:14 UTC | 4h 5m |
| 2026-06-28 | JBU462 | - | Jun 28, 04:25 UTC | Jun 28, 06:05 UTC | 1h 40m |
| 2026-06-28 | JBU462 | - | Jun 28, 02:10 UTC | Jun 28, 02:20 UTC | 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 N659JB page for operator, model, and routing details .