sensors Mode-S transponder
A8021B
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N615JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS
- Hex
- A8021B
- Octal
- 52001033
- Decimal
- 11,010,587
- Country
- US
- Tail
- N615JB
- Type
- A320
- Flights observed
- 310
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address A8021B 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 |
|---|---|---|---|
| JBU1383 | - | 6 | 2026-06-17 |
| JBU2389 | - | 5 | 2026-06-30 |
| JBU1505 | - | 5 | 2026-06-26 |
| JBU928 | JetBlue Airways | 4 | 2026-06-21 |
| JBU525 | - | 4 | 2026-06-21 |
| JBU2890 | - | 4 | 2026-06-25 |
| JBU929 | - | 3 | 2026-06-21 |
| JBU869 | JetBlue Airways | 3 | 2026-05-19 |
| JBU41 | JetBlue Airways | 3 | 2026-05-12 |
| JBU403 | JetBlue Airways | 3 | 2026-06-12 |
| JBU334 | JetBlue Airways | 3 | 2026-06-04 |
| JBU251 | JetBlue Airways | 3 | 2026-06-08 |
| JBU2028 | - | 3 | 2026-07-06 |
| JBU1990 | - | 3 | 2026-06-24 |
| JBU172 | - | 3 | 2026-06-26 |
| JBU1716 | JetBlue Airways | 3 | 2026-06-06 |
| JBU1604 | JetBlue Airways | 3 | 2026-04-18 |
| JBU1501 | - | 3 | 2026-06-16 |
| JBU1233 | JetBlue Airways | 3 | 2026-05-10 |
| JBU1134 | JetBlue Airways | 3 | 2026-06-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU94 | MCO → HPN | Jul 13, 13:25 UTC | Jul 13, 15:45 UTC | 2h 20m |
| 2026-07-13 | JBU94 | MCO → HPN | Jul 13, 13:21 UTC | Jul 14, 02:45 UTC | 13h 25m |
| 2026-07-13 | JBU1434 | - | Jul 13, 09:05 UTC | Jul 13, 11:40 UTC | 2h 35m |
| 2026-07-13 | JBU1903 | - | Jul 13, 01:35 UTC | Jul 13, 04:50 UTC | 3h 15m |
| 2026-07-12 | JBU404 | - | Jul 12, 21:50 UTC | Jul 12, 22:40 UTC | 50m |
| 2026-07-12 | JBU404 | - | Jul 12, 19:45 UTC | Jul 12, 20:01 UTC | 15m |
| 2026-07-12 | JBU2332 | - | Jul 12, 18:10 UTC | Jul 12, 18:20 UTC | 10m |
| 2026-07-12 | JBU2831 | - | Jul 12, 15:30 UTC | Jul 12, 15:40 UTC | 10m |
| 2026-07-12 | JBU1089 | EWR → SJU | Jul 12, 10:10 UTC | Jul 12, 13:35 UTC | 3h 25m |
| 2026-07-11 | JBU2472 | BQN → FLL | Jul 11, 09:03 UTC | Jul 12, 03:50 UTC | 18h 48m |
| 2026-07-10 | JBU326 | MBJ → FLL | Jul 10, 23:01 UTC | Jul 11, 22:45 UTC | 23h 45m |
| 2026-07-10 | JBU2097 | ATL → FLL | Jul 10, 17:26 UTC | Jul 11, 16:45 UTC | 23h 20m |
| 2026-07-10 | JBU1880 | - | Jul 10, 00:15 UTC | Jul 10, 02:25 UTC | 2h 10m |
| 2026-07-10 | JBU1880 | FLL → DCA | Jul 10, 00:14 UTC | Jul 10, 21:00 UTC | 20h 47m |
| 2026-07-09 | JBU2372 | - | Jul 9, 18:15 UTC | Jul 9, 20:30 UTC | 2h 15m |
| 2026-07-09 | JBU2371 | FLL → AUS | Jul 9, 14:10 UTC | Jul 9, 16:45 UTC | 2h 35m |
| 2026-07-09 | JBU1799 | ORF → FLL | Jul 9, 10:25 UTC | Jul 9, 12:15 UTC | 1h 50m |
| 2026-07-08 | JBU2089 | - | Jul 8, 15:25 UTC | Jul 8, 16:50 UTC | 1h 25m |
| 2026-07-08 | JBU2089 | FLL → SAP | Jul 8, 15:21 UTC | Jul 9, 14:45 UTC | 23h 24m |
| 2026-07-08 | JBU2272 | AUS → FLL | Jul 8, 11:15 UTC | Jul 8, 13:40 UTC | 2h 25m |
| 2026-07-07 | JBU2465 | BUF → FLL | Jul 7, 13:25 UTC | Jul 8, 12:45 UTC | 23h 21m |
| 2026-07-06 | JBU2028 | BWI → EWR | Jul 6, 18:14 UTC | Jul 7, 14:45 UTC | 20h 31m |
| 2026-07-06 | JBU504 | SJU → JFK | Jul 6, 00:49 UTC | Jul 7, 00:45 UTC | 23h 57m |
| 2026-07-05 | JBU2144 | - | Jul 5, 11:55 UTC | Jul 5, 14:10 UTC | 2h 15m |
| 2026-07-05 | JBU2144 | PBI → EWR | Jul 5, 11:51 UTC | Jul 6, 10:45 UTC | 22h 54m |
| 2026-07-04 | JBU307 | PWM → JFK | Jul 4, 10:26 UTC | Jul 4, 22:00 UTC | 11h 34m |
| 2026-07-04 | JBU308 | JFK → PWM | Jul 4, 03:39 UTC | Jul 4, 22:00 UTC | 18h 21m |
| 2026-07-03 | JBU1009 | - | Jul 3, 15:15 UTC | Jul 3, 16:10 UTC | 55m |
| 2026-07-03 | JBU1009 | JFK → SDQ | Jul 3, 15:11 UTC | Jul 4, 14:45 UTC | 23h 35m |
| 2026-07-03 | JBU1017 | BOS → JFK | Jul 3, 12:50 UTC | Jul 3, 13:30 UTC | 40m |
| 2026-07-02 | JBU1354 | DCA → BOS | Jul 2, 18:48 UTC | Jul 3, 16:10 UTC | 21h 23m |
| 2026-07-02 | JBU2334 | PBI → DCA | Jul 2, 15:16 UTC | Jul 3, 13:30 UTC | 22h 15m |
| 2026-07-01 | JBU1237 | BOS → DTW | Jul 1, 20:05 UTC | Jul 2, 18:45 UTC | 22h 40m |
| 2026-07-01 | JBU1160 | PHL → BOS | Jul 1, 12:36 UTC | Jul 2, 04:55 UTC | 16h 20m |
| 2026-07-01 | JBU1952 | MCO → BOS | Jul 1, 02:19 UTC | Jul 2, 00:45 UTC | 22h 27m |
| 2026-06-30 | JBU1827 | EWR → MCO | Jun 30, 22:03 UTC | Jul 1, 20:45 UTC | 22h 43m |
| 2026-06-30 | JBU2028 | MCO → EWR | Jun 30, 15:07 UTC | Jul 1, 14:45 UTC | 23h 38m |
| 2026-06-30 | JBU2028 | MCO → EWR | Jun 30, 15:10 UTC | Jun 30, 17:25 UTC | 2h 15m |
| 2026-06-30 | JBU1434 | - | Jun 30, 10:50 UTC | Jun 30, 13:25 UTC | 2h 35m |
| 2026-06-30 | JBU2389 | - | Jun 30, 05:55 UTC | Jun 30, 06:15 UTC | 20m |
| 2026-06-30 | JBU2389 | - | Jun 30, 02:45 UTC | Jun 30, 03:55 UTC | 1h 10m |
| 2026-06-29 | JBU106 | - | Jun 29, 22:19 UTC | Jun 30, 00:49 UTC | 2h 30m |
| 2026-06-29 | JBU1796 | CUN → FLL | Jun 29, 18:14 UTC | Jun 29, 19:39 UTC | 1h 25m |
| 2026-06-28 | JBU2087 | PVD → PBI | Jun 28, 20:34 UTC | Jun 29, 18:44 UTC | 22h 11m |
| 2026-06-28 | JBU1461 | LGA → PBI | Jun 28, 13:18 UTC | Jun 29, 02:59 UTC | 13h 42m |
| 2026-06-27 | JBU1014 | CUN → MCO | Jun 27, 20:27 UTC | Jun 28, 16:45 UTC | 20h 18m |
| 2026-06-27 | JBU102 | JFK → BUF | Jun 27, 02:59 UTC | Jun 27, 04:00 UTC | 1h 0m |
| 2026-06-27 | JBU102 | JFK → BUF | Jun 27, 02:57 UTC | Jun 28, 01:19 UTC | 22h 23m |
| 2026-06-26 | JBU1284 | MCO → JFK | Jun 26, 22:49 UTC | Jun 27, 01:24 UTC | 2h 35m |
| 2026-06-26 | JBU399 | LGA → MCO | Jun 26, 19:00 UTC | Jun 26, 21:24 UTC | 2h 25m |
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 N615JB page for operator, model, and routing details .