sensors Mode-S transponder
A8C028
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N663JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORP
- Hex
- A8C028
- Octal
- 52140050
- Decimal
- 11,059,240
- Country
- US
- Tail
- N663JB
- Type
- A320
- Flights observed
- 299
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 23m ago
Last known position
Country allocation
The ICAO 24-bit address A8C028 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 |
|---|---|---|---|
| JBU553 | - | 4 | 2026-06-19 |
| JBU460 | JetBlue Airways | 4 | 2026-06-03 |
| JBU2476 | JetBlue Airways | 4 | 2026-05-11 |
| JBU98 | - | 3 | 2026-04-13 |
| JBU97 | JetBlue Airways | 3 | 2026-04-13 |
| JBU598 | JetBlue Airways | 3 | 2026-05-26 |
| JBU534 | JetBlue Airways | 3 | 2026-06-08 |
| JBU2752 | - | 3 | 2026-07-14 |
| JBU2662 | JetBlue Airways | 3 | 2026-04-17 |
| JBU2661 | JetBlue Airways | 3 | 2026-04-16 |
| JBU2390 | JetBlue Airways | 3 | 2026-04-15 |
| JBU1694 | JetBlue Airways | 3 | 2026-04-26 |
| JBU1638 | JetBlue Airways | 3 | 2026-05-11 |
| JBU1637 | JetBlue Airways | 3 | 2026-05-11 |
| JBU1553 | JetBlue Airways | 3 | 2026-05-16 |
| JBU1475 | JetBlue Airways | 3 | 2026-04-15 |
| JBU1461 | - | 3 | 2026-07-09 |
| JBU1252 | JetBlue Airways | 3 | 2026-05-22 |
| JBU1134 | JetBlue Airways | 3 | 2026-05-13 |
| JBU1062 | - | 3 | 2026-07-03 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU126 | TPA → JFK | Jul 14, 10:15 UTC | Jul 15, 00:00 UTC | 13h 45m |
| 2026-07-14 | JBU2752 | - | Jul 14, 01:15 UTC | Jul 14, 04:00 UTC | 2h 45m |
| 2026-07-14 | JBU2752 | SJU → TPA | Jul 14, 01:11 UTC | Jul 15, 00:00 UTC | 22h 49m |
| 2026-07-13 | JBU1704 | - | Jul 13, 23:15 UTC | Jul 13, 23:30 UTC | 15m |
| 2026-07-13 | JBU1704 | - | Jul 13, 22:10 UTC | Jul 13, 22:30 UTC | 20m |
| 2026-07-13 | JBU41 | - | Jul 13, 16:35 UTC | Jul 13, 19:25 UTC | 2h 50m |
| 2026-07-13 | JBU2995 | - | Jul 13, 12:05 UTC | Jul 13, 14:10 UTC | 2h 5m |
| 2026-07-12 | JBU2489 | DTW → FLL | Jul 12, 10:06 UTC | Jul 13, 01:40 UTC | 15h 35m |
| 2026-07-11 | JBU681 | FLL → BNA | Jul 11, 16:41 UTC | Jul 12, 15:45 UTC | 23h 5m |
| 2026-07-11 | JBU8352 | - | Jul 11, 00:35 UTC | Jul 11, 01:05 UTC | 30m |
| 2026-07-11 | JBU8352 | - | Jul 11, 00:32 UTC | Jul 12, 00:01 UTC | 23h 29m |
| 2026-07-09 | JBU2087 | - | Jul 9, 20:05 UTC | Jul 9, 23:05 UTC | 3h 0m |
| 2026-07-09 | JBU388 | LAX → BOS | Jul 9, 15:25 UTC | Jul 9, 18:55 UTC | 3h 30m |
| 2026-07-09 | JBU1461 | - | Jul 9, 11:35 UTC | Jul 9, 14:10 UTC | 2h 35m |
| 2026-07-08 | JBU1551 | HPN → RSW | Jul 8, 10:45 UTC | Jul 9, 02:00 UTC | 15h 16m |
| 2026-07-07 | JBU1971 | - | Jul 7, 15:25 UTC | Jul 7, 17:50 UTC | 2h 25m |
| 2026-07-07 | JBU1971 | FLL → AUS | Jul 7, 15:22 UTC | Jul 8, 13:20 UTC | 21h 59m |
| 2026-07-07 | JBU2272 | AUS → FLL | Jul 7, 11:15 UTC | Jul 7, 13:35 UTC | 2h 20m |
| 2026-07-07 | JBU2271 | - | Jul 7, 02:40 UTC | Jul 7, 05:00 UTC | 2h 20m |
| 2026-07-07 | JBU2076 | TPA → FLL | Jul 7, 00:40 UTC | Jul 7, 01:25 UTC | 45m |
| 2026-07-06 | JBU1005 | - | Jul 6, 22:40 UTC | Jul 6, 23:25 UTC | 45m |
| 2026-07-06 | JBU1488 | - | Jul 6, 19:25 UTC | Jul 6, 20:10 UTC | 45m |
| 2026-07-06 | JBU1488 | - | Jul 6, 15:15 UTC | Jul 6, 18:15 UTC | 3h 0m |
| 2026-07-06 | JBU1088 | - | Jul 6, 11:15 UTC | Jul 6, 13:45 UTC | 2h 30m |
| 2026-07-05 | JBU1698 | - | Jul 5, 15:35 UTC | Jul 5, 17:00 UTC | 1h 25m |
| 2026-07-05 | JBU1698 | FLL → ATL | Jul 5, 15:34 UTC | Jul 6, 13:45 UTC | 22h 12m |
| 2026-07-05 | JBU1776 | - | Jul 5, 13:40 UTC | Jul 5, 14:10 UTC | 30m |
| 2026-07-05 | JBU1775 | - | Jul 5, 03:40 UTC | Jul 5, 04:05 UTC | 25m |
| 2026-07-04 | JBU2119 | - | Jul 4, 21:00 UTC | Jul 4, 23:40 UTC | 2h 40m |
| 2026-07-04 | JBU2020 | - | Jul 4, 17:35 UTC | Jul 4, 20:05 UTC | 2h 30m |
| 2026-07-04 | JBU1739 | SYR → FLL | Jul 4, 01:10 UTC | Jul 4, 23:40 UTC | 22h 30m |
| 2026-07-03 | JBU1738 | FLL → SYR | Jul 3, 20:50 UTC | Jul 4, 20:00 UTC | 23h 10m |
| 2026-07-03 | JBU1062 | - | Jul 3, 11:55 UTC | Jul 3, 14:00 UTC | 2h 5m |
| 2026-07-03 | JBU1062 | PBI → LGA | Jul 3, 11:52 UTC | Jul 4, 08:45 UTC | 20h 53m |
| 2026-07-02 | JBU143 | - | Jul 2, 23:45 UTC | Jul 3, 02:00 UTC | 2h 15m |
| 2026-07-02 | JBU1230 | CUN → EWR | Jul 2, 18:15 UTC | Jul 2, 21:35 UTC | 3h 20m |
| 2026-07-02 | JBU2795 | - | Jul 2, 15:30 UTC | Jul 2, 16:50 UTC | 1h 20m |
| 2026-07-02 | JBU1145 | RIC → FLL | Jul 2, 11:25 UTC | Jul 2, 13:25 UTC | 2h 0m |
| 2026-07-01 | JBU1085 | BUF → MCO | Jul 1, 15:30 UTC | Jul 1, 17:40 UTC | 2h 10m |
| 2026-07-01 | JBU1085 | BUF → MCO | Jul 1, 15:27 UTC | Jul 2, 13:25 UTC | 21h 59m |
| 2026-07-01 | JBU1086 | MCO → BUF | Jul 1, 12:05 UTC | Jul 1, 14:20 UTC | 2h 15m |
| 2026-06-29 | JBU2032 | - | Jun 29, 19:39 UTC | Jun 29, 20:19 UTC | 40m |
| 2026-06-29 | JBU2032 | BDA → JFK | Jun 29, 18:24 UTC | Jun 30, 04:45 UTC | 10h 22m |
| 2026-06-29 | JBU1931 | - | Jun 29, 15:09 UTC | Jun 29, 15:39 UTC | 30m |
| 2026-06-28 | JBU126 | TPA → JFK | Jun 28, 10:21 UTC | Jun 29, 01:00 UTC | 14h 39m |
| 2026-06-28 | JBU2752 | SJU → TPA | Jun 28, 02:17 UTC | Jun 29, 01:00 UTC | 22h 43m |
| 2026-06-27 | JBU1797 | ATL → FLL | Jun 27, 11:25 UTC | Jun 27, 12:45 UTC | 1h 20m |
| 2026-06-27 | JBU1797 | ATL → FLL | Jun 27, 11:23 UTC | Jun 28, 05:04 UTC | 17h 42m |
| 2026-06-27 | JBU1798 | - | Jun 27, 00:25 UTC | Jun 27, 01:49 UTC | 1h 25m |
| 2026-06-26 | JBU1869 | JFK → FLL | Jun 26, 13:45 UTC | Jun 26, 20:55 UTC | 7h 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 N663JB page for operator, model, and routing details .