sensors Mode-S transponder
A34D98
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N3115J · AIRBUS A220-300 · operated by JETBLUE AIRWAYS CORP
- Hex
- A34D98
- Octal
- 50646630
- Decimal
- 10,702,232
- Country
- US
- Tail
- N3115J
- Type
- BCS3
- Flights observed
- 301
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address A34D98 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 |
|---|---|---|---|
| JBU1813 | JetBlue Airways | 5 | 2026-06-13 |
| JBU1012 | JetBlue Airways | 5 | 2026-06-19 |
| JBU2587 | JetBlue Airways | 4 | 2026-05-15 |
| JBU2432 | - | 4 | 2026-06-27 |
| JBU2024 | JetBlue Airways | 4 | 2026-05-04 |
| JBU1286 | - | 4 | 2026-06-26 |
| JBU92 | JetBlue Airways | 3 | 2026-06-14 |
| JBU855 | JetBlue Airways | 3 | 2026-06-02 |
| JBU811 | - | 3 | 2026-06-18 |
| JBU626 | - | 3 | 2026-07-07 |
| JBU53 | - | 3 | 2026-06-30 |
| JBU471 | JetBlue Airways | 3 | 2026-06-01 |
| JBU2754 | - | 3 | 2026-06-25 |
| JBU2324 | - | 3 | 2026-06-23 |
| JBU226 | JetBlue Airways | 3 | 2026-05-14 |
| JBU1955 | - | 3 | 2026-06-25 |
| JBU1941 | - | 3 | 2026-04-17 |
| JBU184 | - | 3 | 2026-07-11 |
| JBU1782 | - | 3 | 2026-06-29 |
| JBU176 | - | 3 | 2026-07-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU625 | JFK → TPA | Jul 13, 20:39 UTC | Jul 14, 03:10 UTC | 6h 32m |
| 2026-07-13 | JBU1060 | KIN → JFK | Jul 13, 14:24 UTC | Jul 14, 03:10 UTC | 12h 47m |
| 2026-07-13 | JBU59 | - | Jul 13, 09:25 UTC | Jul 13, 17:50 UTC | 8h 25m |
| 2026-07-13 | JBU282 | - | Jul 13, 00:25 UTC | Jul 13, 03:55 UTC | 3h 30m |
| 2026-07-12 | JBU281 | - | Jul 12, 18:45 UTC | Jul 12, 22:30 UTC | 3h 45m |
| 2026-07-11 | JBU184 | - | Jul 11, 15:35 UTC | Jul 11, 17:50 UTC | 2h 15m |
| 2026-07-11 | JBU737 | - | Jul 11, 11:35 UTC | Jul 11, 14:00 UTC | 2h 25m |
| 2026-07-11 | JBU338 | MCO → BDL | Jul 11, 02:25 UTC | Jul 11, 04:45 UTC | 2h 20m |
| 2026-07-10 | JBU229 | - | Jul 10, 19:05 UTC | Jul 11, 00:55 UTC | 5h 50m |
| 2026-07-10 | JBU934 | - | Jul 10, 16:10 UTC | Jul 10, 17:10 UTC | 1h 0m |
| 2026-07-09 | JBU1498 | - | Jul 9, 20:35 UTC | Jul 9, 23:55 UTC | 3h 20m |
| 2026-07-09 | JBU1498 | DEN → SYR | Jul 9, 20:31 UTC | Jul 10, 19:40 UTC | 23h 9m |
| 2026-07-09 | JBU1497 | JFK → DEN | Jul 9, 15:10 UTC | Jul 9, 19:05 UTC | 3h 55m |
| 2026-07-09 | JBU854 | - | Jul 9, 11:00 UTC | Jul 9, 13:25 UTC | 2h 25m |
| 2026-07-08 | JBU2474 | - | Jul 8, 16:25 UTC | Jul 8, 17:50 UTC | 1h 25m |
| 2026-07-08 | JBU2474 | CHS → JFK | Jul 8, 16:20 UTC | Jul 9, 16:00 UTC | 23h 40m |
| 2026-07-08 | JBU1273 | - | Jul 8, 13:20 UTC | Jul 8, 14:55 UTC | 1h 35m |
| 2026-07-08 | JBU359 | BUR → JFK | Jul 8, 04:50 UTC | Jul 8, 09:45 UTC | 4h 55m |
| 2026-07-07 | JBU358 | JFK → BUR | Jul 7, 21:15 UTC | Jul 8, 02:35 UTC | 5h 20m |
| 2026-07-07 | JBU626 | TPA → JFK | Jul 7, 12:55 UTC | Jul 7, 15:10 UTC | 2h 15m |
| 2026-07-06 | JBU125 | JFK → TPA | Jul 6, 17:55 UTC | Jul 7, 15:10 UTC | 21h 16m |
| 2026-07-06 | JBU286 | RDU → JFK | Jul 6, 11:52 UTC | Jul 6, 22:35 UTC | 10h 44m |
| 2026-07-05 | JBU1500 | DAB → BOS | Jul 5, 19:04 UTC | Jul 6, 18:00 UTC | 22h 57m |
| 2026-07-05 | JBU1897 | BOS → ATL | Jul 5, 01:15 UTC | Jul 5, 03:55 UTC | 2h 40m |
| 2026-07-05 | JBU1897 | BOS → ATL | Jul 5, 01:15 UTC | Jul 5, 22:30 UTC | 21h 16m |
| 2026-07-04 | JBU818 | JFK → BOS | Jul 4, 23:10 UTC | Jul 4, 23:50 UTC | 40m |
| 2026-07-04 | JBU176 | MSY → JFK | Jul 4, 18:20 UTC | Jul 4, 21:30 UTC | 3h 10m |
| 2026-07-04 | JBU75 | JFK → MSY | Jul 4, 13:45 UTC | Jul 4, 16:55 UTC | 3h 10m |
| 2026-07-04 | JBU254 | DCA → JFK | Jul 4, 10:30 UTC | Jul 4, 11:10 UTC | 40m |
| 2026-07-04 | JBU955 | JFK → DCA | Jul 4, 02:40 UTC | Jul 4, 03:20 UTC | 40m |
| 2026-07-03 | JBU678 | - | Jul 3, 21:50 UTC | Jul 3, 23:40 UTC | 1h 50m |
| 2026-07-03 | JBU677 | - | Jul 3, 18:30 UTC | Jul 3, 20:25 UTC | 1h 55m |
| 2026-07-03 | JBU1868 | - | Jul 3, 14:50 UTC | Jul 3, 16:55 UTC | 2h 5m |
| 2026-07-02 | JBU625 | JFK → TPA | Jul 2, 19:42 UTC | Jul 3, 16:55 UTC | 21h 13m |
| 2026-07-02 | JBU184 | - | Jul 2, 15:20 UTC | Jul 2, 17:40 UTC | 2h 20m |
| 2026-07-02 | JBU184 | MCO → JFK | Jul 2, 15:18 UTC | Jul 3, 13:45 UTC | 22h 27m |
| 2026-07-02 | JBU737 | BDL → MCO | Jul 2, 11:25 UTC | Jul 2, 13:45 UTC | 2h 20m |
| 2026-07-01 | JBU183 | BOS → RDU | Jul 1, 12:28 UTC | Jul 2, 12:00 UTC | 23h 32m |
| 2026-06-30 | JBU53 | JFK → PBI | Jun 30, 18:04 UTC | Jul 1, 17:25 UTC | 23h 22m |
| 2026-06-30 | JBU53 | - | Jun 30, 18:05 UTC | Jun 30, 20:30 UTC | 2h 25m |
| 2026-06-30 | JBU2786 | - | Jun 30, 15:00 UTC | Jun 30, 16:10 UTC | 1h 10m |
| 2026-06-30 | JBU2285 | JFK → RDU | Jun 30, 12:45 UTC | Jun 30, 13:50 UTC | 1h 5m |
| 2026-06-30 | JBU1198 | PIT → JFK | Jun 30, 10:15 UTC | Jun 30, 11:20 UTC | 1h 5m |
| 2026-06-30 | JBU1785 | BOS → PIT | Jun 30, 01:19 UTC | Jun 30, 02:40 UTC | 1h 20m |
| 2026-06-29 | JBU1782 | - | Jun 29, 21:14 UTC | Jun 29, 23:54 UTC | 2h 40m |
| 2026-06-29 | JBU349 | BOS → SAV | Jun 29, 01:22 UTC | Jun 30, 00:00 UTC | 22h 38m |
| 2026-06-28 | JBU1336 | DTW → BOS | Jun 28, 22:31 UTC | Jun 29, 22:00 UTC | 23h 29m |
| 2026-06-28 | JBU1281 | BOS → RIC | Jun 28, 11:06 UTC | Jun 29, 07:30 UTC | 20h 24m |
| 2026-06-27 | JBU2432 | - | Jun 27, 17:44 UTC | Jun 27, 18:20 UTC | 35m |
| 2026-06-27 | JBU2432 | LGA → ACK | Jun 27, 17:42 UTC | Jun 28, 16:00 UTC | 22h 18m |
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 N3115J page for operator, model, and routing details .