sensors Mode-S transponder
A883BD
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N648JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORP
- Hex
- A883BD
- Octal
- 52101675
- Decimal
- 11,043,773
- Country
- US
- Tail
- N648JB
- Type
- A320
- Flights observed
- 293
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address A883BD 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 | - | 5 | 2026-07-12 |
| JBU2334 | - | 4 | 2026-07-08 |
| JBU1103 | JetBlue Airways | 4 | 2026-05-27 |
| JBU861 | JetBlue Airways | 3 | 2026-04-28 |
| JBU703 | JetBlue Airways | 3 | 2026-05-08 |
| JBU669 | - | 3 | 2026-06-30 |
| JBU655 | JetBlue Airways | 3 | 2026-04-18 |
| JBU552 | - | 3 | 2026-07-13 |
| JBU544 | - | 3 | 2026-06-25 |
| JBU499 | JetBlue Airways | 3 | 2026-05-21 |
| JBU390 | JetBlue Airways | 3 | 2026-05-10 |
| JBU379 | - | 3 | 2026-06-19 |
| JBU257 | - | 3 | 2026-06-28 |
| JBU2266 | JetBlue Airways | 3 | 2026-04-17 |
| JBU2020 | - | 3 | 2026-06-30 |
| JBU1822 | - | 3 | 2026-07-02 |
| JBU1784 | - | 3 | 2026-07-10 |
| JBU1749 | JetBlue Airways | 3 | 2026-06-04 |
| JBU1703 | - | 3 | 2026-07-11 |
| JBU154 | - | 3 | 2026-06-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU322 | - | Jul 14, 12:14 UTC | Jul 14, 23:15 UTC | 11h 1m |
| 2026-07-14 | JBU2421 | - | Jul 14, 01:46 UTC | Jul 14, 23:15 UTC | 21h 29m |
| 2026-07-13 | JBU1136 | - | Jul 13, 22:50 UTC | Jul 13, 23:15 UTC | 25m |
| 2026-07-13 | JBU1136 | DTW → BOS | Jul 13, 22:49 UTC | Jul 14, 20:00 UTC | 21h 12m |
| 2026-07-13 | JBU1237 | - | Jul 13, 20:20 UTC | Jul 13, 21:50 UTC | 1h 30m |
| 2026-07-13 | JBU1237 | BOS → DTW | Jul 13, 20:16 UTC | Jul 14, 19:15 UTC | 23h 0m |
| 2026-07-13 | JBU552 | MCO → BOS | Jul 13, 16:00 UTC | Jul 13, 18:40 UTC | 2h 40m |
| 2026-07-12 | JBU553 | - | Jul 12, 23:55 UTC | Jul 13, 00:05 UTC | 10m |
| 2026-07-12 | JBU553 | - | Jul 12, 21:55 UTC | Jul 12, 22:25 UTC | 30m |
| 2026-07-12 | JBU553 | FLL → SJU | Jul 12, 21:55 UTC | Jul 13, 21:15 UTC | 23h 21m |
| 2026-07-12 | JBU2448 | - | Jul 12, 14:20 UTC | Jul 12, 19:45 UTC | 5h 25m |
| 2026-07-11 | JBU2594 | FLL → BWI | Jul 11, 23:27 UTC | Jul 12, 22:25 UTC | 22h 59m |
| 2026-07-11 | JBU40 | MDE → FLL | Jul 11, 18:43 UTC | Jul 12, 15:45 UTC | 21h 3m |
| 2026-07-11 | JBU1703 | SJU → MDE | Jul 11, 14:47 UTC | Jul 12, 12:35 UTC | 21h 49m |
| 2026-07-11 | JBU753 | FLL → SJU | Jul 11, 10:46 UTC | Jul 12, 01:35 UTC | 14h 50m |
| 2026-07-10 | JBU1784 | CTG → FLL | Jul 10, 18:32 UTC | Jul 11, 15:05 UTC | 20h 34m |
| 2026-07-10 | JBU1784 | - | Jul 10, 15:10 UTC | Jul 10, 21:05 UTC | 5h 55m |
| 2026-07-10 | JBU1795 | - | Jul 10, 11:35 UTC | Jul 10, 13:35 UTC | 2h 0m |
| 2026-07-10 | JBU2994 | - | Jul 10, 03:10 UTC | Jul 10, 05:05 UTC | 1h 55m |
| 2026-07-09 | JBU1171 | LGA → FLL | Jul 9, 22:50 UTC | Jul 10, 01:25 UTC | 2h 35m |
| 2026-07-09 | JBU698 | MCO → LGA | Jul 9, 16:50 UTC | Jul 9, 19:55 UTC | 3h 5m |
| 2026-07-08 | JBU49 | BOS → YVR | Jul 8, 21:30 UTC | Jul 9, 20:00 UTC | 22h 31m |
| 2026-07-08 | JBU1354 | DCA → BOS | Jul 8, 18:35 UTC | Jul 9, 17:15 UTC | 22h 41m |
| 2026-07-08 | JBU2334 | PBI → DCA | Jul 8, 15:07 UTC | Jul 9, 13:15 UTC | 22h 8m |
| 2026-07-08 | JBU455 | BOS → DCA | Jul 8, 02:09 UTC | Jul 9, 01:00 UTC | 22h 52m |
| 2026-07-08 | JBU618 | JFK → BOS | Jul 8, 00:09 UTC | Jul 8, 23:15 UTC | 23h 6m |
| 2026-07-07 | JBU302 | - | Jul 7, 11:20 UTC | Jul 7, 13:40 UTC | 2h 20m |
| 2026-07-07 | JBU302 | FLL → JFK | Jul 7, 11:19 UTC | Jul 8, 03:25 UTC | 16h 7m |
| 2026-07-06 | JBU552 | MCO → BOS | Jul 6, 12:27 UTC | Jul 7, 02:35 UTC | 14h 9m |
| 2026-07-06 | JBU552 | MCO → BOS | Jul 6, 12:30 UTC | Jul 6, 14:55 UTC | 2h 25m |
| 2026-07-06 | JBU2583 | JFK → MCO | Jul 6, 05:00 UTC | Jul 6, 07:10 UTC | 2h 10m |
| 2026-07-05 | JBU1112 | - | Jul 5, 20:15 UTC | Jul 6, 00:15 UTC | 4h 0m |
| 2026-07-04 | JBU1137 | BOS → DTW | Jul 4, 23:54 UTC | Jul 5, 23:15 UTC | 23h 21m |
| 2026-07-04 | JBU1608 | STI → SJU | Jul 4, 21:03 UTC | Jul 5, 18:30 UTC | 21h 28m |
| 2026-07-04 | JBU193 | EWR → STI | Jul 4, 05:43 UTC | Jul 5, 00:10 UTC | 18h 27m |
| 2026-07-03 | JBU106 | FLL → EWR | Jul 3, 22:49 UTC | Jul 4, 17:20 UTC | 18h 32m |
| 2026-07-03 | JBU1127 | FLL → MBJ | Jul 3, 15:03 UTC | Jul 4, 13:15 UTC | 22h 13m |
| 2026-07-02 | JBU1494 | NAS → FLL | Jul 2, 17:55 UTC | Jul 3, 15:35 UTC | 21h 40m |
| 2026-07-02 | JBU1822 | MSY → FLL | Jul 2, 12:10 UTC | Jul 2, 13:45 UTC | 1h 35m |
| 2026-07-02 | JBU1822 | MSY → FLL | Jul 2, 12:10 UTC | Jul 3, 11:15 UTC | 23h 5m |
| 2026-07-02 | JBU2823 | - | Jul 2, 00:50 UTC | Jul 2, 02:20 UTC | 1h 30m |
| 2026-07-01 | JBU1383 | - | Jul 1, 21:10 UTC | Jul 1, 22:45 UTC | 1h 35m |
| 2026-07-01 | JBU1383 | - | Jul 1, 20:30 UTC | Jul 1, 20:40 UTC | 10m |
| 2026-07-01 | JBU1383 | - | Jul 1, 17:20 UTC | Jul 1, 17:30 UTC | 10m |
| 2026-07-01 | JBU1380 | - | Jul 1, 15:10 UTC | Jul 1, 16:45 UTC | 1h 35m |
| 2026-07-01 | JBU375 | PVD → MCO | Jul 1, 11:05 UTC | Jul 1, 13:15 UTC | 2h 10m |
| 2026-06-30 | JBU2020 | - | Jun 30, 17:00 UTC | Jun 30, 17:15 UTC | 15m |
| 2026-06-30 | JBU669 | BOS → FLL | Jun 30, 12:49 UTC | Jul 1, 11:15 UTC | 22h 26m |
| 2026-06-30 | JBU669 | BOS → FLL | Jun 30, 12:50 UTC | Jun 30, 15:35 UTC | 2h 45m |
| 2026-06-30 | JBU50 | - | Jun 30, 05:00 UTC | Jun 30, 10:15 UTC | 5h 15m |
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 N648JB page for operator, model, and routing details .