sensors Mode-S transponder
A8C796
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N665JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORP
- Hex
- A8C796
- Octal
- 52143626
- Decimal
- 11,061,142
- Country
- US
- Tail
- N665JB
- Type
- A320
- Flights observed
- 260
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 7h ago
Current position
Country allocation
The ICAO 24-bit address A8C796 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 |
|---|---|---|---|
| JBU1952 | - | 4 | 2026-07-05 |
| JBU1241 | - | 4 | 2026-06-18 |
| JBU873 | JetBlue Airways | 3 | 2026-06-11 |
| JBU743 | - | 3 | 2026-07-13 |
| JBU438 | JetBlue Airways | 3 | 2026-04-16 |
| JBU268 | JetBlue Airways | 3 | 2026-05-10 |
| JBU2052 | - | 3 | 2026-06-28 |
| JBU1990 | - | 3 | 2026-07-06 |
| JBU1715 | - | 3 | 2026-04-13 |
| JBU1230 | - | 3 | 2026-07-07 |
| JBU1142 | JetBlue Airways | 3 | 2026-06-06 |
| JBU1026 | - | 3 | 2026-04-13 |
| JBU1004 | JetBlue Airways | 3 | 2026-04-30 |
| JBU996 | JetBlue Airways | 2 | 2026-06-10 |
| JBU969 | - | 2 | 2026-06-24 |
| JBU914 | JetBlue Airways | 2 | 2026-05-30 |
| JBU879 | - | 2 | 2026-04-15 |
| JBU85 | - | 2 | 2026-06-16 |
| JBU719 | JetBlue Airways | 2 | 2026-05-26 |
| JBU714 | JetBlue Airways | 2 | 2026-06-11 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU1009 | - | Jul 14, 14:35 UTC | Jul 14, 15:20 UTC | 45m |
| 2026-07-14 | JBU1678 | - | Jul 14, 10:15 UTC | Jul 14, 12:10 UTC | 1h 55m |
| 2026-07-14 | JBU1677 | - | Jul 14, 02:05 UTC | Jul 14, 03:55 UTC | 1h 50m |
| 2026-07-13 | JBU740 | - | Jul 13, 22:55 UTC | Jul 13, 23:40 UTC | 45m |
| 2026-07-13 | JBU743 | - | Jul 13, 15:10 UTC | Jul 13, 15:45 UTC | 35m |
| 2026-07-11 | JBU455 | BOS → DCA | Jul 11, 01:52 UTC | Jul 11, 12:10 UTC | 10h 19m |
| 2026-07-11 | JBU455 | BOS → DCA | Jul 11, 01:55 UTC | Jul 11, 03:10 UTC | 1h 15m |
| 2026-07-10 | JBU257 | BOS → BOS | Jul 10, 13:05 UTC | Jul 10, 22:40 UTC | 9h 35m |
| 2026-07-09 | JBU1701 | JFK → FLL | Jul 9, 01:40 UTC | Jul 9, 17:45 UTC | 16h 5m |
| 2026-07-08 | JBU105 | EWR → FLL | Jul 8, 16:44 UTC | Jul 9, 15:20 UTC | 22h 36m |
| 2026-07-08 | JBU2144 | - | Jul 8, 12:05 UTC | Jul 8, 14:20 UTC | 2h 15m |
| 2026-07-08 | JBU2144 | PBI → EWR | Jul 8, 12:02 UTC | Jul 9, 11:30 UTC | 23h 28m |
| 2026-07-08 | JBU143 | EWR → PBI | Jul 8, 00:10 UTC | Jul 8, 02:40 UTC | 2h 30m |
| 2026-07-07 | JBU1230 | CUN → EWR | Jul 7, 18:10 UTC | Jul 7, 21:20 UTC | 3h 10m |
| 2026-07-06 | JBU1607 | SJU → STI | Jul 6, 23:55 UTC | Jul 7, 21:30 UTC | 21h 36m |
| 2026-07-06 | JBU2332 | PUJ → SJU | Jul 6, 17:40 UTC | Jul 7, 16:30 UTC | 22h 51m |
| 2026-07-06 | JBU1990 | - | Jul 6, 02:20 UTC | Jul 6, 03:10 UTC | 50m |
| 2026-07-05 | JBU1990 | - | Jul 5, 23:50 UTC | Jul 6, 00:05 UTC | 15m |
| 2026-07-05 | JBU1990 | SJU → EWR | Jul 5, 23:46 UTC | Jul 6, 18:15 UTC | 18h 29m |
| 2026-07-05 | JBU1453 | - | Jul 5, 22:15 UTC | Jul 5, 22:25 UTC | 10m |
| 2026-07-05 | JBU1952 | - | Jul 5, 02:15 UTC | Jul 5, 04:45 UTC | 2h 30m |
| 2026-07-05 | JBU1952 | MCO → BOS | Jul 5, 02:11 UTC | Jul 6, 00:05 UTC | 21h 55m |
| 2026-07-04 | JBU483 | - | Jul 4, 22:25 UTC | Jul 5, 00:50 UTC | 2h 25m |
| 2026-07-04 | JBU852 | CUN → JFK | Jul 4, 16:50 UTC | Jul 4, 20:05 UTC | 3h 15m |
| 2026-07-04 | JBU851 | JFK → CUN | Jul 4, 12:00 UTC | Jul 4, 15:20 UTC | 3h 20m |
| 2026-07-04 | JBU1850 | - | Jul 4, 03:05 UTC | Jul 4, 03:50 UTC | 45m |
| 2026-07-03 | JBU1850 | JFK → BOS | Jul 3, 16:30 UTC | Jul 4, 01:15 UTC | 8h 45m |
| 2026-07-02 | JBU472 | FLL → LGA | Jul 2, 22:51 UTC | Jul 3, 17:15 UTC | 18h 25m |
| 2026-07-02 | JBU40 | MDE → FLL | Jul 2, 17:28 UTC | Jul 3, 14:40 UTC | 21h 12m |
| 2026-07-01 | JBU2098 | FLL → ATL | Jul 1, 21:54 UTC | Jul 2, 20:35 UTC | 22h 41m |
| 2026-07-01 | JBU552 | MCO → BOS | Jul 1, 12:38 UTC | Jul 2, 10:15 UTC | 21h 37m |
| 2026-07-01 | JBU552 | MCO → BOS | Jul 1, 12:40 UTC | Jul 1, 15:15 UTC | 2h 35m |
| 2026-07-01 | JBU451 | - | Jul 1, 03:35 UTC | Jul 1, 06:05 UTC | 2h 30m |
| 2026-06-30 | JBU252 | MCO → BOS | Jun 30, 22:50 UTC | Jul 1, 01:25 UTC | 2h 35m |
| 2026-06-30 | JBU655 | - | Jun 30, 13:50 UTC | Jun 30, 16:10 UTC | 2h 20m |
| 2026-06-30 | JBU656 | - | Jun 30, 10:15 UTC | Jun 30, 12:35 UTC | 2h 20m |
| 2026-06-29 | JBU2028 | MCO → EWR | Jun 29, 14:11 UTC | Jun 30, 12:35 UTC | 22h 25m |
| 2026-06-28 | JBU2076 | TPA → FLL | Jun 28, 19:19 UTC | Jun 29, 16:35 UTC | 21h 16m |
| 2026-06-28 | JBU2052 | MCO → BOS | Jun 28, 01:59 UTC | Jun 29, 01:29 UTC | 23h 31m |
| 2026-06-28 | JBU2052 | MCO → BOS | Jun 28, 01:59 UTC | Jun 28, 04:44 UTC | 2h 45m |
| 2026-06-27 | JBU240 | - | Jun 27, 20:09 UTC | Jun 27, 20:55 UTC | 45m |
| 2026-06-27 | JBU462 | - | Jun 27, 01:35 UTC | Jun 27, 05:25 UTC | 3h 50m |
| 2026-06-27 | JBU462 | SJU → BOS | Jun 27, 01:33 UTC | Jun 27, 23:14 UTC | 21h 42m |
| 2026-06-26 | JBU1743 | - | Jun 26, 21:24 UTC | Jun 27, 00:14 UTC | 2h 50m |
| 2026-06-26 | JBU1742 | - | Jun 26, 18:49 UTC | Jun 26, 20:04 UTC | 1h 15m |
| 2026-06-26 | JBU1742 | - | Jun 26, 17:09 UTC | Jun 26, 17:19 UTC | 10m |
| 2026-06-26 | JBU635 | - | Jun 26, 11:09 UTC | Jun 26, 14:59 UTC | 3h 50m |
| 2026-06-26 | JBU102 | - | Jun 26, 03:24 UTC | Jun 26, 04:20 UTC | 55m |
| 2026-06-25 | JBU743 | - | Jun 25, 14:14 UTC | Jun 25, 23:55 UTC | 9h 40m |
| 2026-06-25 | JBU699 | LGA → MCO | Jun 25, 01:50 UTC | Jun 25, 23:30 UTC | 21h 40m |
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 N665JB page for operator, model, and routing details .