sensors Mode-S transponder
A83876
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N629JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS
- Hex
- A83876
- Octal
- 52034166
- Decimal
- 11,024,502
- Country
- US
- Tail
- N629JB
- Type
- A320
- Flights observed
- 147
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address A83876 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 |
|---|---|---|---|
| JBU2144 | - | 4 | 2026-06-25 |
| JBU1476 | - | 4 | 2026-06-22 |
| JBU869 | JetBlue Airways | 3 | 2026-04-19 |
| JBU762 | JetBlue Airways | 3 | 2026-06-17 |
| JBU553 | - | 3 | 2026-06-20 |
| JBU1676 | - | 3 | 2026-07-06 |
| JBU1553 | - | 3 | 2026-07-11 |
| JBU1377 | JetBlue Airways | 3 | 2026-04-13 |
| JBU1016 | - | 3 | 2026-07-03 |
| JBU1015 | - | 3 | 2026-07-03 |
| JBU891 | JetBlue Airways | 2 | 2026-04-15 |
| JBU873 | - | 2 | 2026-06-23 |
| JBU834 | JetBlue Airways | 2 | 2026-04-16 |
| JBU703 | - | 2 | 2026-06-16 |
| JBU696 | JetBlue Airways | 2 | 2026-04-14 |
| JBU548 | - | 2 | 2026-06-24 |
| JBU52 | - | 2 | 2026-04-16 |
| JBU471 | - | 2 | 2026-06-18 |
| JBU426 | - | 2 | 2026-04-15 |
| JBU404 | JetBlue Airways | 2 | 2026-06-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU1246 | - | Jul 13, 13:30 UTC | Jul 13, 15:15 UTC | 1h 45m |
| 2026-07-13 | JBU1246 | FLL → RIC | Jul 13, 13:26 UTC | Jul 13, 23:45 UTC | 10h 20m |
| 2026-07-13 | JBU379 | DCA → FLL | Jul 13, 10:10 UTC | Jul 13, 12:10 UTC | 2h 0m |
| 2026-07-12 | JBU892 | TPA → BOS | Jul 12, 13:51 UTC | Jul 13, 13:30 UTC | 23h 40m |
| 2026-07-11 | JBU238 | SDQ → SJU | Jul 11, 20:34 UTC | Jul 12, 19:25 UTC | 22h 52m |
| 2026-07-11 | JBU1937 | SJU → SDQ | Jul 11, 18:28 UTC | Jul 12, 17:30 UTC | 23h 3m |
| 2026-07-11 | JBU1553 | - | Jul 11, 16:50 UTC | Jul 11, 17:00 UTC | 10m |
| 2026-07-11 | JBU1553 | - | Jul 11, 14:50 UTC | Jul 11, 15:20 UTC | 30m |
| 2026-07-11 | JBU1553 | FLL → SJU | Jul 11, 14:50 UTC | Jul 12, 12:55 UTC | 22h 6m |
| 2026-07-11 | JBU1071 | LGA → FLL | Jul 11, 10:15 UTC | Jul 11, 12:35 UTC | 2h 20m |
| 2026-07-10 | JBU1551 | HPN → RSW | Jul 10, 10:33 UTC | Jul 11, 01:55 UTC | 15h 23m |
| 2026-07-09 | JBU1611 | FLL → AUA | Jul 9, 14:38 UTC | Jul 10, 13:15 UTC | 22h 37m |
| 2026-07-09 | JBU1 | JFK → FLL | Jul 9, 09:30 UTC | Jul 10, 02:35 UTC | 17h 5m |
| 2026-07-08 | JBU1937 | SJU → SDQ | Jul 8, 19:31 UTC | Jul 9, 17:10 UTC | 21h 39m |
| 2026-07-08 | JBU2537 | SJU → SDQ | Jul 8, 14:44 UTC | Jul 9, 11:30 UTC | 20h 46m |
| 2026-07-08 | JBU1850 | SDQ → JFK | Jul 8, 00:00 UTC | Jul 8, 23:30 UTC | 23h 31m |
| 2026-07-07 | JBU1849 | JFK → SDQ | Jul 7, 18:46 UTC | Jul 8, 15:00 UTC | 20h 15m |
| 2026-07-07 | JBU1849 | - | Jul 7, 18:50 UTC | Jul 7, 19:20 UTC | 30m |
| 2026-07-07 | JBU906 | - | Jul 7, 14:55 UTC | Jul 7, 16:35 UTC | 1h 40m |
| 2026-07-06 | JBU1568 | PUJ → JFK | Jul 6, 20:14 UTC | Jul 7, 19:20 UTC | 23h 7m |
| 2026-07-06 | JBU173 | FLL → PUJ | Jul 6, 16:43 UTC | Jul 7, 15:30 UTC | 22h 48m |
| 2026-07-06 | JBU1676 | - | Jul 6, 14:25 UTC | Jul 6, 15:00 UTC | 35m |
| 2026-07-06 | JBU1676 | KIN → FLL | Jul 6, 13:21 UTC | Jul 7, 11:30 UTC | 22h 10m |
| 2026-07-06 | JBU1675 | - | Jul 6, 10:40 UTC | Jul 6, 11:10 UTC | 30m |
| 2026-07-05 | JBU8351 | JFK → LAX | Jul 5, 10:57 UTC | Jul 5, 23:30 UTC | 12h 33m |
| 2026-07-04 | JBU304 | SJU → JFK | Jul 4, 23:21 UTC | Jul 5, 21:30 UTC | 22h 9m |
| 2026-07-04 | JBU1203 | EWR → SDQ | Jul 4, 03:37 UTC | Jul 5, 03:30 UTC | 23h 53m |
| 2026-07-03 | JBU1016 | PUJ → EWR | Jul 3, 19:08 UTC | Jul 4, 04:45 UTC | 9h 37m |
| 2026-07-03 | JBU1015 | EWR → EWR | Jul 3, 14:10 UTC | Jul 3, 22:40 UTC | 8h 30m |
| 2026-07-03 | JBU1204 | JFK → EWR | Jul 3, 03:10 UTC | Jul 3, 11:20 UTC | 8h 10m |
| 2026-07-02 | JBU1568 | PUJ → JFK | Jul 2, 17:45 UTC | Jul 3, 00:30 UTC | 6h 45m |
| 2026-07-02 | JBU1676 | FLL → FLL | Jul 2, 10:50 UTC | Jul 2, 15:10 UTC | 4h 20m |
| 2026-07-01 | JBU569 | BOS → FLL | Jul 1, 10:39 UTC | Jul 1, 22:10 UTC | 11h 32m |
| 2026-07-01 | JBU470 | - | Jul 1, 01:10 UTC | Jul 1, 01:30 UTC | 20m |
| 2026-06-30 | JBU313 | - | Jun 30, 21:10 UTC | Jun 30, 23:30 UTC | 2h 20m |
| 2026-06-30 | JBU313 | ISP → FLL | Jun 30, 21:05 UTC | Jul 1, 16:30 UTC | 19h 26m |
| 2026-06-30 | JBU544 | - | Jun 30, 17:15 UTC | Jun 30, 19:40 UTC | 2h 25m |
| 2026-06-30 | JBU1241 | - | Jun 30, 13:20 UTC | Jun 30, 15:40 UTC | 2h 20m |
| 2026-06-29 | JBU670 | MCO → RIC | Jun 29, 15:27 UTC | Jun 30, 13:30 UTC | 22h 4m |
| 2026-06-28 | JBU1115 | BOS → BUF | Jun 28, 23:29 UTC | Jun 29, 20:40 UTC | 21h 11m |
| 2026-06-28 | JBU352 | MCO → BOS | Jun 28, 10:19 UTC | Jun 28, 12:55 UTC | 2h 35m |
| 2026-06-28 | JBU352 | MCO → BOS | Jun 28, 10:17 UTC | Jun 29, 00:39 UTC | 14h 23m |
| 2026-06-27 | JBU1 | JFK → FLL | Jun 27, 09:44 UTC | Jun 28, 01:15 UTC | 15h 31m |
| 2026-06-26 | JBU1009 | JFK → SDQ | Jun 26, 14:59 UTC | Jun 27, 13:30 UTC | 22h 31m |
| 2026-06-26 | JBU2752 | - | Jun 26, 00:55 UTC | Jun 26, 03:34 UTC | 2h 40m |
| 2026-06-26 | JBU2752 | SJU → TPA | Jun 26, 00:54 UTC | Jun 26, 23:30 UTC | 22h 36m |
| 2026-06-25 | JBU1608 | - | Jun 25, 21:50 UTC | Jun 25, 21:59 UTC | 10m |
| 2026-06-25 | JBU593 | - | Jun 25, 16:20 UTC | Jun 25, 16:55 UTC | 35m |
| 2026-06-25 | JBU2144 | - | Jun 25, 11:59 UTC | Jun 25, 14:09 UTC | 2h 10m |
| 2026-06-24 | JBU367 | - | Jun 24, 20:20 UTC | Jun 24, 22:49 UTC | 2h 30m |
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 N629JB page for operator, model, and routing details .