sensors Mode-S transponder
A34D52
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N3113J · AIRBUS A220-300 · operated by JETBLUE AIRWAYS CORP
- Hex
- A34D52
- Octal
- 50646522
- Decimal
- 10,702,162
- Country
- US
- Tail
- N3113J
- Type
- BCS3
- Flights observed
- 305
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address A34D52 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 |
|---|---|---|---|
| JBU1198 | - | 6 | 2026-07-01 |
| JBU95 | - | 5 | 2026-07-13 |
| JBU2754 | - | 5 | 2026-07-07 |
| JBU1596 | - | 5 | 2026-07-06 |
| JBU678 | JetBlue Airways | 4 | 2026-06-16 |
| JBU396 | JetBlue Airways | 4 | 2026-05-30 |
| JBU2185 | JetBlue Airways | 4 | 2026-06-24 |
| JBU204 | - | 4 | 2026-06-22 |
| JBU1499 | - | 4 | 2026-07-13 |
| JBU1158 | JetBlue Airways | 4 | 2026-04-17 |
| JBU933 | - | 3 | 2026-07-11 |
| JBU895 | JetBlue Airways | 3 | 2026-06-09 |
| JBU722 | - | 3 | 2026-04-14 |
| JBU639 | - | 3 | 2026-07-10 |
| JBU638 | - | 3 | 2026-07-11 |
| JBU249 | JetBlue Airways | 3 | 2026-06-14 |
| JBU2474 | JetBlue Airways | 3 | 2026-06-16 |
| JBU2468 | - | 3 | 2026-07-12 |
| JBU2283 | - | 3 | 2026-06-24 |
| JBU2255 | - | 3 | 2026-06-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU95 | BOS → PDX | Jul 13, 23:32 UTC | Jul 14, 11:40 UTC | 12h 9m |
| 2026-07-13 | JBU1500 | DAB → BOS | Jul 13, 18:23 UTC | Jul 14, 11:40 UTC | 17h 18m |
| 2026-07-13 | JBU1499 | BOS → DAB | Jul 13, 14:47 UTC | Jul 14, 11:40 UTC | 20h 54m |
| 2026-07-13 | JBU1499 | - | Jul 13, 14:50 UTC | Jul 13, 16:30 UTC | 1h 40m |
| 2026-07-12 | JBU2468 | BOS → BOS | Jul 12, 23:25 UTC | Jul 12, 23:30 UTC | 5m |
| 2026-07-12 | JBU2468 | - | Jul 12, 21:30 UTC | Jul 12, 23:15 UTC | 1h 45m |
| 2026-07-12 | JBU2467 | - | Jul 12, 18:10 UTC | Jul 12, 20:10 UTC | 2h 0m |
| 2026-07-11 | JBU933 | BOS → IAH | Jul 11, 20:40 UTC | Jul 12, 20:10 UTC | 23h 31m |
| 2026-07-11 | JBU791 | BOS → TPA | Jul 11, 11:37 UTC | Jul 12, 10:30 UTC | 22h 54m |
| 2026-07-11 | JBU638 | AUS → BOS | Jul 11, 02:18 UTC | Jul 12, 00:30 UTC | 22h 13m |
| 2026-07-11 | JBU638 | AUS → BOS | Jul 11, 02:20 UTC | Jul 11, 05:40 UTC | 3h 20m |
| 2026-07-10 | JBU639 | BOS → AUS | Jul 10, 18:50 UTC | Jul 10, 22:45 UTC | 3h 55m |
| 2026-07-10 | JBU810 | JAX → BOS | Jul 10, 00:57 UTC | Jul 11, 00:30 UTC | 23h 34m |
| 2026-07-09 | JBU252 | MCO → BOS | Jul 9, 17:05 UTC | Jul 10, 16:30 UTC | 23h 26m |
| 2026-07-09 | JBU2265 | MCO → STI | Jul 9, 09:34 UTC | Jul 10, 05:35 UTC | 20h 2m |
| 2026-07-09 | JBU451 | - | Jul 9, 09:35 UTC | Jul 9, 10:15 UTC | 40m |
| 2026-07-08 | JBU451 | BOS → MCO | Jul 8, 21:50 UTC | Jul 9, 00:30 UTC | 2h 40m |
| 2026-07-08 | JBU993 | - | Jul 8, 02:10 UTC | Jul 8, 02:30 UTC | 20m |
| 2026-07-08 | JBU993 | BOS → DEN | Jul 8, 02:07 UTC | Jul 9, 00:30 UTC | 22h 24m |
| 2026-07-07 | JBU2754 | DCA → BOS | Jul 7, 23:30 UTC | Jul 8, 00:35 UTC | 1h 5m |
| 2026-07-07 | JBU2754 | DCA → BOS | Jul 7, 23:30 UTC | Jul 8, 22:30 UTC | 23h 1m |
| 2026-07-07 | JBU1413 | - | Jul 7, 20:30 UTC | Jul 7, 21:40 UTC | 1h 10m |
| 2026-07-06 | JBU1596 | PUJ → BOS | Jul 6, 23:21 UTC | Jul 7, 21:40 UTC | 22h 20m |
| 2026-07-05 | JBU1596 | PUJ → BOS | Jul 5, 23:27 UTC | Jul 6, 19:20 UTC | 19h 53m |
| 2026-07-05 | JBU2040 | - | Jul 5, 14:35 UTC | Jul 5, 15:55 UTC | 1h 20m |
| 2026-07-05 | JBU2040 | CLE → BOS | Jul 5, 14:30 UTC | Jul 6, 11:15 UTC | 20h 45m |
| 2026-07-05 | JBU2041 | BOS → CLE | Jul 5, 11:30 UTC | Jul 5, 13:00 UTC | 1h 30m |
| 2026-07-05 | JBU932 | IAH → BOS | Jul 5, 09:55 UTC | Jul 5, 10:00 UTC | 5m |
| 2026-07-04 | JBU2033 | BOS → IAH | Jul 4, 14:23 UTC | Jul 5, 12:30 UTC | 22h 8m |
| 2026-07-04 | JBU820 | SDQ → JFK | Jul 4, 05:35 UTC | Jul 5, 04:20 UTC | 22h 45m |
| 2026-07-04 | JBU884 | MCO → JFK | Jul 4, 01:49 UTC | Jul 4, 23:40 UTC | 21h 51m |
| 2026-07-03 | JBU521 | - | Jul 3, 17:10 UTC | Jul 3, 17:55 UTC | 45m |
| 2026-07-03 | JBU521 | MCO → MBJ | Jul 3, 17:05 UTC | Jul 4, 16:30 UTC | 23h 26m |
| 2026-07-03 | JBU2265 | MCO → MCO | Jul 3, 09:30 UTC | Jul 3, 15:05 UTC | 5h 35m |
| 2026-07-02 | JBU51 | - | Jul 2, 16:20 UTC | Jul 2, 18:50 UTC | 2h 30m |
| 2026-07-02 | JBU51 | BOS → MCO | Jul 2, 16:17 UTC | Jul 3, 14:30 UTC | 22h 13m |
| 2026-07-02 | JBU1282 | - | Jul 2, 13:50 UTC | Jul 2, 15:00 UTC | 1h 10m |
| 2026-07-02 | JBU1281 | - | Jul 2, 11:10 UTC | Jul 2, 12:25 UTC | 1h 15m |
| 2026-07-01 | JBU2786 | RDU → JFK | Jul 1, 15:06 UTC | Jul 2, 14:30 UTC | 23h 24m |
| 2026-07-01 | JBU1198 | - | Jul 1, 09:35 UTC | Jul 1, 10:30 UTC | 55m |
| 2026-07-01 | JBU1198 | PIT → JFK | Jul 1, 09:32 UTC | Jul 2, 08:30 UTC | 22h 58m |
| 2026-07-01 | JBU1195 | - | Jul 1, 01:55 UTC | Jul 1, 02:50 UTC | 55m |
| 2026-06-30 | JBU1498 | - | Jun 30, 20:20 UTC | Jun 30, 23:40 UTC | 3h 20m |
| 2026-06-30 | JBU1497 | JFK → DEN | Jun 30, 14:55 UTC | Jun 30, 18:25 UTC | 3h 30m |
| 2026-06-30 | JBU854 | - | Jun 30, 10:55 UTC | Jun 30, 13:20 UTC | 2h 25m |
| 2026-06-30 | JBU1053 | - | Jun 30, 00:00 UTC | Jun 30, 02:10 UTC | 2h 10m |
| 2026-06-29 | JBU1054 | - | Jun 29, 18:34 UTC | Jun 29, 20:49 UTC | 2h 15m |
| 2026-06-29 | JBU21 | - | Jun 29, 13:34 UTC | Jun 29, 16:19 UTC | 2h 45m |
| 2026-06-29 | JBU8361 | ORF → BOS | Jun 29, 03:44 UTC | Jun 29, 04:55 UTC | 1h 10m |
| 2026-06-28 | JBU781 | - | Jun 28, 20:54 UTC | Jun 28, 22:39 UTC | 1h 45m |
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 N3113J page for operator, model, and routing details .