sensors Mode-S transponder
A34978
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N3102J · AIRBUS A220-300 · operated by JETBLUE AIRWAYS CORP
- Hex
- A34978
- Octal
- 50644570
- Decimal
- 10,701,176
- Country
- US
- Tail
- N3102J
- Type
- BCS3
- Flights observed
- 291
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 14m ago
Current position
Country allocation
The ICAO 24-bit address A34978 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 |
|---|---|---|---|
| JBU934 | - | 6 | 2026-07-01 |
| JBU716 | JetBlue Airways | 4 | 2026-05-26 |
| JBU579 | JetBlue Airways | 4 | 2026-04-26 |
| JBU2133 | - | 4 | 2026-07-01 |
| JBU128 | JetBlue Airways | 4 | 2026-07-01 |
| JBU641 | - | 3 | 2026-07-02 |
| JBU640 | - | 3 | 2026-07-02 |
| JBU450 | - | 3 | 2026-04-13 |
| JBU401 | JetBlue Airways | 3 | 2026-05-02 |
| JBU374 | - | 3 | 2026-07-10 |
| JBU303 | JetBlue Airways | 3 | 2026-04-15 |
| JBU2954 | JetBlue Airways | 3 | 2026-06-09 |
| JBU259 | JetBlue Airways | 3 | 2026-04-23 |
| JBU249 | - | 3 | 2026-04-13 |
| JBU2454 | - | 3 | 2026-07-02 |
| JBU2272 | JetBlue Airways | 3 | 2026-05-14 |
| JBU1896 | - | 3 | 2026-07-03 |
| JBU1781 | JetBlue Airways | 3 | 2026-05-18 |
| JBU1727 | - | 3 | 2026-06-30 |
| JBU160 | JetBlue Airways | 3 | 2026-04-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU1202 | JFK → BUF | Jul 13, 23:07 UTC | Jul 14, 14:00 UTC | 14h 54m |
| 2026-07-13 | JBU2902 | JFK → BUF | Jul 13, 18:18 UTC | Jul 14, 14:00 UTC | 19h 43m |
| 2026-07-13 | JBU519 | JFK → ATL | Jul 13, 11:48 UTC | Jul 14, 04:50 UTC | 17h 3m |
| 2026-07-12 | JBU65 | JFK → ABQ | Jul 12, 23:49 UTC | Jul 13, 21:40 UTC | 21h 52m |
| 2026-07-12 | JBU1964 | JFK → HYA | Jul 12, 19:16 UTC | Jul 13, 16:40 UTC | 21h 25m |
| 2026-07-12 | JBU142 | SAV → JFK | Jul 12, 16:14 UTC | Jul 13, 16:00 UTC | 23h 47m |
| 2026-07-11 | JBU772 | CUN → BOS | Jul 11, 20:10 UTC | Jul 11, 23:55 UTC | 3h 45m |
| 2026-07-11 | JBU772 | CUN → BOS | Jul 11, 20:10 UTC | Jul 12, 20:01 UTC | 23h 51m |
| 2026-07-11 | JBU771 | BOS → CUN | Jul 11, 14:45 UTC | Jul 11, 18:40 UTC | 3h 55m |
| 2026-07-10 | JBU374 | SYR → BOS | Jul 10, 11:01 UTC | Jul 11, 09:45 UTC | 22h 45m |
| 2026-07-09 | JBU717 | BOS → JFK | Jul 9, 21:06 UTC | Jul 10, 20:00 UTC | 22h 54m |
| 2026-07-09 | JBU2116 | - | Jul 9, 16:05 UTC | Jul 9, 17:00 UTC | 55m |
| 2026-07-09 | JBU2116 | BUF → BOS | Jul 9, 16:01 UTC | Jul 10, 13:15 UTC | 21h 14m |
| 2026-07-09 | JBU2115 | - | Jul 9, 12:15 UTC | Jul 9, 13:20 UTC | 1h 5m |
| 2026-07-09 | JBU248 | SLC → BOS | Jul 9, 06:00 UTC | Jul 9, 09:55 UTC | 3h 55m |
| 2026-07-08 | JBU1207 | BOS → BNA | Jul 8, 10:15 UTC | Jul 9, 10:00 UTC | 23h 46m |
| 2026-07-08 | JBU8048 | DTW → BOS | Jul 8, 04:00 UTC | Jul 9, 02:00 UTC | 22h 1m |
| 2026-07-07 | JBU8047 | BOS → SLC | Jul 7, 15:19 UTC | Jul 8, 14:00 UTC | 22h 42m |
| 2026-07-07 | JBU8047 | BOS → SLC | Jul 7, 15:20 UTC | Jul 7, 20:10 UTC | 4h 50m |
| 2026-07-06 | JBU2283 | BOS → RDU | Jul 6, 16:26 UTC | Jul 7, 16:00 UTC | 23h 35m |
| 2026-07-06 | JBU554 | DCA → BOS | Jul 6, 13:44 UTC | Jul 7, 12:00 UTC | 22h 17m |
| 2026-07-05 | JBU386 | PIT → BOS | Jul 5, 17:37 UTC | Jul 6, 16:00 UTC | 22h 23m |
| 2026-07-05 | JBU2255 | BOS → DCA | Jul 5, 10:20 UTC | Jul 6, 10:00 UTC | 23h 40m |
| 2026-07-05 | JBU1096 | BOS → BOS | Jul 5, 09:05 UTC | Jul 5, 09:10 UTC | 5m |
| 2026-07-04 | JBU109 | BOS → JAX | Jul 4, 11:30 UTC | Jul 5, 10:00 UTC | 22h 31m |
| 2026-07-04 | JBU2754 | DCA → BOS | Jul 4, 07:11 UTC | Jul 5, 06:00 UTC | 22h 50m |
| 2026-07-04 | JBU1413 | MVY → DCA | Jul 4, 02:49 UTC | Jul 5, 02:00 UTC | 23h 12m |
| 2026-07-03 | JBU1499 | BOS → DAB | Jul 3, 14:49 UTC | Jul 4, 13:45 UTC | 22h 57m |
| 2026-07-03 | JBU1896 | ATL → BOS | Jul 3, 11:10 UTC | Jul 3, 13:15 UTC | 2h 5m |
| 2026-07-03 | JBU1896 | ATL → BOS | Jul 3, 11:10 UTC | Jul 4, 10:00 UTC | 22h 50m |
| 2026-07-03 | JBU1897 | BOS → ATL | Jul 3, 00:30 UTC | Jul 3, 02:40 UTC | 2h 10m |
| 2026-07-02 | JBU640 | - | Jul 2, 21:40 UTC | Jul 2, 23:00 UTC | 1h 20m |
| 2026-07-02 | JBU641 | - | Jul 2, 19:00 UTC | Jul 2, 20:25 UTC | 1h 25m |
| 2026-07-02 | JBU2454 | DCA → BOS | Jul 2, 16:45 UTC | Jul 2, 17:50 UTC | 1h 5m |
| 2026-07-01 | JBU128 | MCO → EWR | Jul 1, 19:30 UTC | Jul 1, 21:45 UTC | 2h 15m |
| 2026-07-01 | JBU128 | MCO → EWR | Jul 1, 19:30 UTC | Jul 2, 18:00 UTC | 22h 30m |
| 2026-07-01 | JBU934 | - | Jul 1, 17:10 UTC | Jul 1, 18:05 UTC | 55m |
| 2026-07-01 | JBU934 | - | Jul 1, 15:25 UTC | Jul 1, 15:40 UTC | 15m |
| 2026-07-01 | JBU2133 | - | Jul 1, 13:50 UTC | Jul 1, 14:10 UTC | 20m |
| 2026-07-01 | JBU2133 | - | Jul 1, 11:40 UTC | Jul 1, 12:15 UTC | 35m |
| 2026-06-30 | JBU934 | - | Jun 30, 17:10 UTC | Jun 30, 18:45 UTC | 1h 35m |
| 2026-06-30 | JBU934 | - | Jun 30, 15:25 UTC | Jun 30, 15:35 UTC | 10m |
| 2026-06-30 | JBU934 | SJU → FLL | Jun 30, 15:24 UTC | Jul 1, 14:00 UTC | 22h 36m |
| 2026-06-30 | JBU2133 | - | Jun 30, 13:25 UTC | Jun 30, 13:45 UTC | 20m |
| 2026-06-30 | JBU2133 | - | Jun 30, 11:10 UTC | Jun 30, 11:50 UTC | 40m |
| 2026-06-30 | JBU1727 | EWR → MCO | Jun 30, 00:04 UTC | Jun 30, 02:05 UTC | 2h 1m |
| 2026-06-29 | JBU128 | MCO → EWR | Jun 29, 20:19 UTC | Jun 29, 22:30 UTC | 2h 10m |
| 2026-06-29 | JBU2876 | - | Jun 29, 02:39 UTC | Jun 29, 05:04 UTC | 2h 25m |
| 2026-06-29 | JBU2876 | PVD → MCO | Jun 29, 02:36 UTC | Jun 30, 02:00 UTC | 23h 25m |
| 2026-06-28 | JBU2875 | - | Jun 28, 20:54 UTC | Jun 28, 23:20 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 N3102J page for operator, model, and routing details .