sensors Mode-S transponder
A8B8BA
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N661JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORP
- Hex
- A8B8BA
- Octal
- 52134272
- Decimal
- 11,057,338
- Country
- US
- Tail
- N661JB
- Type
- A320
- Flights observed
- 187
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 4h ago
Current position
Country allocation
The ICAO 24-bit address A8B8BA 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 |
|---|---|---|---|
| JBU1098 | - | 4 | 2026-06-25 |
| JBU813 | JetBlue Airways | 3 | 2026-04-15 |
| JBU554 | JetBlue Airways | 3 | 2026-04-16 |
| JBU1553 | JetBlue Airways | 3 | 2026-04-30 |
| JBU1468 | JetBlue Airways | 3 | 2026-04-15 |
| JBU1009 | - | 3 | 2026-07-01 |
| JBU994 | JetBlue Airways | 2 | 2026-04-24 |
| JBU968 | JetBlue Airways | 2 | 2026-04-14 |
| JBU936 | JetBlue Airways | 2 | 2026-05-07 |
| JBU8597 | JetBlue Airways | 2 | 2026-05-14 |
| JBU8364 | - | 2 | 2026-07-09 |
| JBU753 | - | 2 | 2026-06-27 |
| JBU743 | - | 2 | 2026-06-30 |
| JBU726 | JetBlue Airways | 2 | 2026-04-25 |
| JBU687 | JetBlue Airways | 2 | 2026-04-19 |
| JBU677 | JetBlue Airways | 2 | 2026-05-01 |
| JBU656 | JetBlue Airways | 2 | 2026-04-27 |
| JBU655 | JetBlue Airways | 2 | 2026-04-28 |
| JBU551 | - | 2 | 2026-07-11 |
| JBU470 | - | 2 | 2026-07-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU1130 | FLL → CHS | Jul 13, 20:29 UTC | Jul 14, 00:20 UTC | 3h 52m |
| 2026-07-13 | JBU195 | HPN → MCO | Jul 13, 03:28 UTC | Jul 14, 00:20 UTC | 20h 53m |
| 2026-07-12 | JBU2920 | ALB → MCO | Jul 12, 10:15 UTC | Jul 13, 05:35 UTC | 19h 21m |
| 2026-07-12 | JBU2919 | MCO → ALB | Jul 12, 00:33 UTC | Jul 12, 22:30 UTC | 21h 58m |
| 2026-07-12 | JBU2919 | MCO → ALB | Jul 12, 00:35 UTC | Jul 12, 02:55 UTC | 2h 20m |
| 2026-07-11 | JBU551 | BOS → MCO | Jul 11, 20:05 UTC | Jul 11, 22:40 UTC | 2h 35m |
| 2026-07-11 | JBU1118 | JFK → BOS | Jul 11, 17:30 UTC | Jul 11, 18:20 UTC | 50m |
| 2026-07-10 | JBU294 | - | Jul 10, 23:45 UTC | Jul 11, 00:20 UTC | 35m |
| 2026-07-10 | JBU1693 | - | Jul 10, 21:45 UTC | Jul 10, 22:05 UTC | 20m |
| 2026-07-10 | JBU1693 | FLL → NAS | Jul 10, 21:44 UTC | Jul 11, 20:30 UTC | 22h 47m |
| 2026-07-10 | JBU1801 | JFK → FLL | Jul 10, 17:30 UTC | Jul 10, 19:55 UTC | 2h 25m |
| 2026-07-09 | JBU153 | FLL → SJU | Jul 9, 20:35 UTC | Jul 10, 19:55 UTC | 23h 21m |
| 2026-07-09 | JBU8364 | - | Jul 9, 16:40 UTC | Jul 9, 18:30 UTC | 1h 50m |
| 2026-07-09 | JBU8364 | PUJ → FLL | Jul 9, 16:16 UTC | Jul 10, 10:30 UTC | 18h 14m |
| 2026-07-08 | JBU470 | - | Jul 8, 02:25 UTC | Jul 8, 05:20 UTC | 2h 55m |
| 2026-07-08 | JBU470 | FLL → BOS | Jul 8, 02:24 UTC | Jul 8, 13:00 UTC | 10h 37m |
| 2026-07-07 | JBU313 | - | Jul 7, 21:30 UTC | Jul 7, 23:55 UTC | 2h 25m |
| 2026-07-07 | JBU544 | - | Jul 7, 17:20 UTC | Jul 7, 19:45 UTC | 2h 25m |
| 2026-07-06 | JBU276 | SJU → BDL | Jul 6, 23:16 UTC | Jul 7, 22:30 UTC | 23h 15m |
| 2026-07-06 | JBU1751 | TPA → SJU | Jul 6, 15:13 UTC | Jul 7, 14:30 UTC | 23h 18m |
| 2026-07-06 | JBU1447 | - | Jul 6, 11:45 UTC | Jul 6, 14:00 UTC | 2h 15m |
| 2026-07-06 | JBU1447 | HPN → TPA | Jul 6, 11:40 UTC | Jul 7, 02:50 UTC | 15h 10m |
| 2026-07-05 | JBU914 | - | Jul 5, 23:45 UTC | Jul 6, 02:25 UTC | 2h 40m |
| 2026-07-05 | JBU1158 | - | Jul 5, 15:15 UTC | Jul 5, 21:40 UTC | 6h 25m |
| 2026-07-04 | JBU2931 | SJU → PUJ | Jul 4, 20:53 UTC | Jul 5, 15:45 UTC | 18h 53m |
| 2026-07-04 | JBU1015 | EWR → PUJ | Jul 4, 13:47 UTC | Jul 5, 12:30 UTC | 22h 44m |
| 2026-07-04 | JBU709 | JFK → SDQ | Jul 4, 02:42 UTC | Jul 5, 02:10 UTC | 23h 28m |
| 2026-07-03 | JBU1568 | PUJ → JFK | Jul 3, 19:57 UTC | Jul 4, 15:40 UTC | 19h 44m |
| 2026-07-03 | JBU173 | FLL → PUJ | Jul 3, 16:29 UTC | Jul 4, 14:30 UTC | 22h 2m |
| 2026-07-03 | JBU1433 | - | Jul 3, 02:45 UTC | Jul 3, 05:15 UTC | 2h 30m |
| 2026-07-03 | JBU1433 | MCO → SJU | Jul 3, 02:43 UTC | Jul 4, 02:30 UTC | 23h 47m |
| 2026-07-02 | JBU551 | - | Jul 2, 22:50 UTC | Jul 3, 01:25 UTC | 2h 35m |
| 2026-07-02 | JBU618 | JFK → BOS | Jul 2, 20:30 UTC | Jul 2, 21:15 UTC | 45m |
| 2026-07-02 | JBU164 | - | Jul 2, 16:25 UTC | Jul 2, 18:50 UTC | 2h 25m |
| 2026-07-02 | JBU163 | JFK → SRQ | Jul 2, 12:45 UTC | Jul 2, 15:15 UTC | 2h 30m |
| 2026-07-01 | JBU1009 | JFK → JFK | Jul 1, 14:50 UTC | Jul 1, 16:05 UTC | 1h 15m |
| 2026-06-30 | JBU743 | - | Jun 30, 14:15 UTC | Jun 30, 17:15 UTC | 3h 0m |
| 2026-06-30 | JBU743 | JFK → ANU | Jun 30, 14:13 UTC | Jul 1, 01:00 UTC | 10h 48m |
| 2026-06-29 | JBU1799 | - | Jun 29, 16:44 UTC | Jun 29, 18:30 UTC | 1h 45m |
| 2026-06-29 | JBU1799 | ORF → FLL | Jun 29, 16:44 UTC | Jun 30, 14:30 UTC | 21h 47m |
| 2026-06-29 | JBU1800 | - | Jun 29, 13:44 UTC | Jun 29, 15:30 UTC | 1h 45m |
| 2026-06-29 | JBU1906 | TPA → FLL | Jun 29, 11:50 UTC | Jun 29, 12:29 UTC | 40m |
| 2026-06-28 | JBU1783 | - | Jun 28, 15:20 UTC | Jun 28, 15:49 UTC | 30m |
| 2026-06-28 | JBU1783 | FLL → CTG | Jun 28, 15:16 UTC | Jun 29, 14:29 UTC | 23h 14m |
| 2026-06-28 | JBU2272 | AUS → FLL | Jun 28, 11:09 UTC | Jun 28, 13:29 UTC | 2h 20m |
| 2026-06-27 | JBU2537 | SJU → SDQ | Jun 27, 14:39 UTC | Jun 27, 14:49 UTC | 10m |
| 2026-06-27 | JBU2537 | SJU → SDQ | Jun 27, 14:34 UTC | Jun 28, 13:29 UTC | 22h 56m |
| 2026-06-27 | JBU753 | - | Jun 27, 12:39 UTC | Jun 27, 12:50 UTC | 10m |
| 2026-06-27 | JBU753 | - | Jun 27, 10:45 UTC | Jun 27, 11:09 UTC | 25m |
| 2026-06-26 | JBU147 | MCO → FLL | Jun 26, 11:04 UTC | Jun 27, 02:25 UTC | 15h 21m |
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 N661JB page for operator, model, and routing details .