sensors Mode-S transponder
AB355C
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N821JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORP
- Hex
- AB355C
- Octal
- 52632534
- Decimal
- 11,220,316
- Country
- US
- Tail
- N821JB
- Type
- A320
- Flights observed
- 204
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address AB355C 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 |
|---|---|---|---|
| JBU572 | JetBlue Airways | 5 | 2026-06-13 |
| JBU1475 | - | 5 | 2026-06-23 |
| JBU861 | - | 4 | 2026-07-07 |
| JBU1471 | JetBlue Airways | 3 | 2026-06-08 |
| JBU1447 | - | 3 | 2026-06-28 |
| JBU947 | - | 2 | 2026-06-25 |
| JBU8624 | JetBlue Airways | 2 | 2026-05-13 |
| JBU8598 | - | 2 | 2026-04-16 |
| JBU664 | - | 2 | 2026-07-13 |
| JBU598 | JetBlue Airways | 2 | 2026-06-05 |
| JBU562 | - | 2 | 2026-07-06 |
| JBU554 | JetBlue Airways | 2 | 2026-04-14 |
| JBU543 | - | 2 | 2026-04-13 |
| JBU525 | JetBlue Airways | 2 | 2026-05-29 |
| JBU403 | JetBlue Airways | 2 | 2026-05-27 |
| JBU2918 | JetBlue Airways | 2 | 2026-06-12 |
| JBU2884 | - | 2 | 2026-07-03 |
| JBU2760 | JetBlue Airways | 2 | 2026-04-15 |
| JBU275 | - | 2 | 2026-07-04 |
| JBU2516 | JetBlue Airways | 2 | 2026-05-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU676 | BDL → JFK | Jul 14, 10:29 UTC | Jul 15, 01:00 UTC | 14h 31m |
| 2026-07-13 | JBU664 | ORD → FLL | Jul 13, 12:15 UTC | Jul 13, 14:45 UTC | 2h 30m |
| 2026-07-13 | JBU664 | ORD → FLL | Jul 13, 12:12 UTC | Jul 14, 11:00 UTC | 22h 49m |
| 2026-07-13 | JBU863 | - | Jul 13, 01:50 UTC | Jul 13, 04:30 UTC | 2h 40m |
| 2026-07-12 | JBU1450 | - | Jul 12, 22:05 UTC | Jul 12, 23:40 UTC | 1h 35m |
| 2026-07-12 | JBU593 | - | Jul 12, 16:45 UTC | Jul 12, 18:01 UTC | 1h 15m |
| 2026-07-12 | JBU2144 | - | Jul 12, 11:55 UTC | Jul 12, 14:10 UTC | 2h 15m |
| 2026-07-11 | JBU1552 | RSW → HPN | Jul 11, 15:00 UTC | Jul 12, 13:01 UTC | 22h 1m |
| 2026-07-10 | JBU1014 | CUN → MCO | Jul 10, 19:17 UTC | Jul 11, 17:45 UTC | 22h 29m |
| 2026-07-10 | JBU2722 | MSY → FLL | Jul 10, 00:18 UTC | Jul 10, 21:25 UTC | 21h 8m |
| 2026-07-09 | JBU1204 | SDQ → EWR | Jul 9, 07:38 UTC | Jul 10, 05:45 UTC | 22h 7m |
| 2026-07-08 | JBU68 | CHS → BOS | Jul 8, 18:11 UTC | Jul 9, 17:00 UTC | 22h 50m |
| 2026-07-08 | JBU690 | FLL → BOS | Jul 8, 10:46 UTC | Jul 9, 02:50 UTC | 16h 4m |
| 2026-07-08 | JBU154 | SJU → FLL | Jul 8, 00:57 UTC | Jul 8, 22:15 UTC | 21h 19m |
| 2026-07-07 | JBU2631 | SJU → PUJ | Jul 7, 18:50 UTC | Jul 7, 19:00 UTC | 10m |
| 2026-07-07 | JBU861 | BOS → SJU | Jul 7, 13:51 UTC | Jul 8, 13:00 UTC | 23h 10m |
| 2026-07-07 | JBU861 | BOS → SJU | Jul 7, 13:55 UTC | Jul 7, 17:25 UTC | 3h 30m |
| 2026-07-07 | JBU198A | - | Jul 7, 07:25 UTC | Jul 7, 12:10 UTC | 4h 45m |
| 2026-07-06 | JBU197 | - | Jul 6, 23:40 UTC | Jul 7, 05:20 UTC | 5h 40m |
| 2026-07-06 | JBU562 | SJU → BOS | Jul 6, 10:24 UTC | Jul 7, 09:00 UTC | 22h 37m |
| 2026-07-05 | JBU83 | JFK → MCO | Jul 5, 16:28 UTC | Jul 6, 14:05 UTC | 21h 38m |
| 2026-07-04 | JBU1115 | BOS → BUF | Jul 4, 21:53 UTC | Jul 5, 18:50 UTC | 20h 58m |
| 2026-07-04 | JBU781 | BOS → RIC | Jul 4, 15:56 UTC | Jul 5, 14:35 UTC | 22h 39m |
| 2026-07-04 | JBU275 | BDL → SJU | Jul 4, 00:35 UTC | Jul 4, 04:00 UTC | 3h 25m |
| 2026-07-03 | JBU438 | MCO → BDL | Jul 3, 20:32 UTC | Jul 4, 19:00 UTC | 22h 28m |
| 2026-07-03 | JBU2884 | MCO → JFK | Jul 3, 12:30 UTC | Jul 3, 14:35 UTC | 2h 5m |
| 2026-07-03 | JBU2884 | MCO → JFK | Jul 3, 12:25 UTC | Jul 4, 11:00 UTC | 22h 36m |
| 2026-07-03 | JBU2948 | PPM → MCO | Jul 3, 01:50 UTC | Jul 3, 02:20 UTC | 30m |
| 2026-07-02 | JBU2119 | - | Jul 2, 22:15 UTC | Jul 3, 00:55 UTC | 2h 40m |
| 2026-07-02 | JBU2020 | - | Jul 2, 18:25 UTC | Jul 2, 21:10 UTC | 2h 45m |
| 2026-07-02 | JBU669 | BOS → FLL | Jul 2, 12:40 UTC | Jul 2, 15:50 UTC | 3h 10m |
| 2026-07-01 | JBU2952 | MCO → BOS | Jul 1, 15:28 UTC | Jul 2, 15:00 UTC | 23h 32m |
| 2026-06-30 | JBU551 | BOS → MCO | Jun 30, 22:04 UTC | Jul 1, 21:00 UTC | 22h 57m |
| 2026-06-30 | JBU1215 | BOS → BUF | Jun 30, 15:05 UTC | Jul 1, 14:00 UTC | 22h 55m |
| 2026-06-30 | JBU1160 | PHL → BOS | Jun 30, 12:33 UTC | Jul 1, 05:15 UTC | 16h 43m |
| 2026-06-30 | JBU1940 | SRQ → BOS | Jun 30, 00:20 UTC | Jun 30, 03:05 UTC | 2h 45m |
| 2026-06-30 | JBU1940 | SRQ → BOS | Jun 30, 00:19 UTC | Jun 30, 23:00 UTC | 22h 42m |
| 2026-06-29 | JBU1941 | - | Jun 29, 20:19 UTC | Jun 29, 23:14 UTC | 2h 55m |
| 2026-06-29 | JBU1216 | - | Jun 29, 17:45 UTC | Jun 29, 18:49 UTC | 1h 5m |
| 2026-06-29 | JBU1215 | BOS → BUF | Jun 29, 15:14 UTC | Jun 29, 16:19 UTC | 1h 5m |
| 2026-06-29 | JBU562 | SJU → BOS | Jun 29, 10:15 UTC | Jun 29, 13:49 UTC | 3h 35m |
| 2026-06-28 | JBU1751 | - | Jun 28, 15:20 UTC | Jun 28, 16:14 UTC | 55m |
| 2026-06-28 | JBU1751 | TPA → SJU | Jun 28, 15:17 UTC | Jun 29, 15:00 UTC | 23h 43m |
| 2026-06-28 | JBU1447 | - | Jun 28, 11:45 UTC | Jun 28, 13:59 UTC | 2h 15m |
| 2026-06-27 | JBU2274 | TPA → EWR | Jun 27, 14:39 UTC | Jun 27, 16:44 UTC | 2h 5m |
| 2026-06-27 | JBU2274 | TPA → EWR | Jun 27, 14:36 UTC | Jun 28, 13:00 UTC | 22h 24m |
| 2026-06-27 | JBU225 | JFK → TPA | Jun 27, 10:45 UTC | Jun 27, 13:15 UTC | 2h 30m |
| 2026-06-26 | JBU66 | ABQ → JFK | Jun 26, 05:24 UTC | Jun 27, 02:59 UTC | 21h 36m |
| 2026-06-25 | JBU947 | - | Jun 25, 11:54 UTC | Jun 25, 16:14 UTC | 4h 20m |
| 2026-06-25 | JBU947 | JFK → BZN | Jun 25, 11:54 UTC | Jun 26, 11:00 UTC | 23h 6m |
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 N821JB page for operator, model, and routing details .