sensors Mode-S transponder
A83108
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N627JB · AIRBUS A-320 · operated by JETBLUE AIRWAYS CORP
- Hex
- A83108
- Octal
- 52030410
- Decimal
- 11,022,600
- Country
- US
- Tail
- N627JB
- Type
- A320
- Flights observed
- 285
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address A83108 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 |
|---|---|---|---|
| JBU548 | JetBlue Airways | 5 | 2026-06-10 |
| JBU1368 | - | 5 | 2026-07-12 |
| JBU533 | JetBlue Airways | 4 | 2026-06-10 |
| JBU83 | JetBlue Airways | 3 | 2026-05-27 |
| JBU759 | - | 3 | 2026-07-06 |
| JBU525 | JetBlue Airways | 3 | 2026-05-25 |
| JBU473 | - | 3 | 2026-04-13 |
| JBU2851 | JetBlue Airways | 3 | 2026-06-20 |
| JBU24 | - | 3 | 2026-07-12 |
| JBU1742 | JetBlue Airways | 3 | 2026-05-25 |
| JBU1730 | JetBlue Airways | 3 | 2026-05-16 |
| JBU1434 | JetBlue Airways | 3 | 2026-05-11 |
| JBU1367 | JetBlue Airways | 3 | 2026-05-17 |
| JBU1144 | - | 3 | 2026-07-03 |
| JBU1103 | JetBlue Airways | 3 | 2026-05-14 |
| JBU1048 | JetBlue Airways | 3 | 2026-05-28 |
| JBU894 | - | 2 | 2026-06-25 |
| JBU831 | JetBlue Airways | 2 | 2026-05-30 |
| JBU791 | JetBlue Airways | 2 | 2026-05-08 |
| JBU729 | JetBlue Airways | 2 | 2026-06-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU1115 | BOS → BUF | Jul 14, 22:07 UTC | Jul 15, 02:00 UTC | 3h 53m |
| 2026-07-14 | JBU2895 | BOS → PUJ | Jul 14, 09:59 UTC | Jul 15, 02:00 UTC | 16h 1m |
| 2026-07-13 | JBU1193 | BOS → MBJ | Jul 13, 15:40 UTC | Jul 14, 10:50 UTC | 19h 11m |
| 2026-07-13 | JBU322 | - | Jul 13, 11:04 UTC | Jul 14, 10:00 UTC | 22h 57m |
| 2026-07-12 | JBU24 | - | Jul 12, 18:35 UTC | Jul 12, 20:50 UTC | 2h 15m |
| 2026-07-12 | JBU24 | - | Jul 12, 18:31 UTC | Jul 13, 18:00 UTC | 23h 30m |
| 2026-07-12 | JBU1167 | - | Jul 12, 14:45 UTC | Jul 12, 17:05 UTC | 2h 20m |
| 2026-07-12 | JBU1368 | - | Jul 12, 10:45 UTC | Jul 12, 13:10 UTC | 2h 25m |
| 2026-07-11 | JBU403 | JFK → SJU | Jul 11, 09:12 UTC | Jul 12, 03:30 UTC | 18h 19m |
| 2026-07-10 | JBU1869 | JFK → PUJ | Jul 10, 14:10 UTC | Jul 11, 12:20 UTC | 22h 11m |
| 2026-07-10 | JBU1869 | - | Jul 10, 14:10 UTC | Jul 10, 14:55 UTC | 45m |
| 2026-07-10 | JBU18 | - | Jul 10, 00:20 UTC | Jul 10, 04:50 UTC | 4h 30m |
| 2026-07-09 | JBU308 | JFK → PWM | Jul 9, 03:21 UTC | Jul 10, 01:50 UTC | 22h 30m |
| 2026-07-08 | JBU257 | BOS → BZN | Jul 8, 13:00 UTC | Jul 9, 04:05 UTC | 15h 6m |
| 2026-07-08 | JBU257 | - | Jul 8, 13:00 UTC | Jul 8, 16:50 UTC | 3h 50m |
| 2026-07-07 | JBU1005 | FLL → TPA | Jul 7, 16:58 UTC | Jul 8, 16:00 UTC | 23h 3m |
| 2026-07-06 | JBU759 | BDL → FLL | Jul 6, 23:42 UTC | Jul 7, 19:40 UTC | 19h 59m |
| 2026-07-06 | JBU760 | FLL → BDL | Jul 6, 19:13 UTC | Jul 7, 17:50 UTC | 22h 38m |
| 2026-07-06 | JBU1474 | PUJ → FLL | Jul 6, 15:32 UTC | Jul 7, 13:40 UTC | 22h 9m |
| 2026-07-06 | JBU2895 | BOS → PUJ | Jul 6, 10:17 UTC | Jul 7, 02:50 UTC | 16h 33m |
| 2026-07-06 | JBU1952 | MCO → BOS | Jul 6, 03:22 UTC | Jul 7, 02:00 UTC | 22h 39m |
| 2026-07-05 | JBU1072 | - | Jul 5, 10:25 UTC | Jul 5, 12:45 UTC | 2h 20m |
| 2026-07-05 | JBU1072 | FLL → LGA | Jul 5, 10:20 UTC | Jul 6, 09:35 UTC | 23h 16m |
| 2026-07-05 | JBU305 | - | Jul 5, 00:00 UTC | Jul 5, 02:15 UTC | 2h 15m |
| 2026-07-04 | JBU2128 | MCO → EWR | Jul 4, 02:10 UTC | Jul 5, 02:00 UTC | 23h 51m |
| 2026-07-03 | JBU1143 | MHT → MCO | Jul 3, 20:40 UTC | Jul 4, 17:30 UTC | 20h 50m |
| 2026-07-03 | JBU1144 | MCO → MHT | Jul 3, 16:56 UTC | Jul 4, 14:50 UTC | 21h 55m |
| 2026-07-03 | JBU1948 | FLL → MCO | Jul 3, 00:41 UTC | Jul 4, 00:00 UTC | 23h 20m |
| 2026-07-02 | JBU272 | - | Jul 2, 16:15 UTC | Jul 2, 18:45 UTC | 2h 30m |
| 2026-07-02 | JBU272 | FLL → LGA | Jul 2, 16:14 UTC | Jul 3, 13:05 UTC | 20h 52m |
| 2026-07-02 | JBU2117 | - | Jul 2, 13:50 UTC | Jul 2, 14:45 UTC | 55m |
| 2026-07-02 | JBU2118 | - | Jul 2, 11:45 UTC | Jul 2, 12:35 UTC | 50m |
| 2026-07-01 | JBU105 | EWR → FLL | Jul 1, 16:26 UTC | Jul 2, 14:45 UTC | 22h 19m |
| 2026-07-01 | JBU2144 | PBI → EWR | Jul 1, 11:53 UTC | Jul 2, 03:20 UTC | 15h 28m |
| 2026-06-30 | JBU698 | MCO → LGA | Jun 30, 16:29 UTC | Jul 1, 14:25 UTC | 21h 57m |
| 2026-06-30 | JBU351 | BOS → MCO | Jun 30, 12:22 UTC | Jul 1, 12:00 UTC | 23h 39m |
| 2026-06-30 | JBU351 | BOS → MCO | Jun 30, 12:25 UTC | Jun 30, 14:55 UTC | 2h 30m |
| 2026-06-29 | JBU2052 | - | Jun 29, 22:39 UTC | Jun 30, 01:09 UTC | 2h 30m |
| 2026-06-29 | JBU240 | - | Jun 29, 19:24 UTC | Jun 29, 20:09 UTC | 45m |
| 2026-06-29 | JBU241 | - | Jun 29, 16:35 UTC | Jun 29, 17:14 UTC | 40m |
| 2026-06-29 | JBU2548 | - | Jun 29, 14:09 UTC | Jun 29, 14:54 UTC | 45m |
| 2026-06-28 | JBU1383 | - | Jun 28, 19:29 UTC | Jun 28, 21:59 UTC | 2h 30m |
| 2026-06-28 | JBU1383 | GUA → FLL | Jun 28, 19:27 UTC | Jun 29, 17:14 UTC | 21h 48m |
| 2026-06-28 | JBU1380 | - | Jun 28, 15:44 UTC | Jun 28, 18:14 UTC | 2h 30m |
| 2026-06-27 | JBU1693 | FLL → NAS | Jun 27, 21:04 UTC | Jun 28, 19:44 UTC | 22h 41m |
| 2026-06-27 | JBU1494 | - | Jun 27, 19:00 UTC | Jun 27, 19:29 UTC | 30m |
| 2026-06-27 | JBU1393 | - | Jun 27, 16:10 UTC | Jun 27, 16:30 UTC | 20m |
| 2026-06-27 | JBU2005 | - | Jun 27, 12:09 UTC | Jun 27, 14:35 UTC | 2h 25m |
| 2026-06-27 | JBU2008 | - | Jun 27, 03:04 UTC | Jun 27, 05:10 UTC | 2h 5m |
| 2026-06-27 | JBU1697 | ATL → FLL | Jun 27, 00:29 UTC | Jun 27, 01:54 UTC | 1h 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 N627JB page for operator, model, and routing details .