sensors Mode-S transponder
A35592
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N3139J · AIRBUS A220-300 · operated by JETBLUE AIRWAYS CORP
- Hex
- A35592
- Octal
- 50652622
- Decimal
- 10,704,274
- Country
- US
- Tail
- N3139J
- Type
- BCS3
- Flights observed
- 305
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 3h ago
Current position
Country allocation
The ICAO 24-bit address A35592 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 |
|---|---|---|---|
| JBU1003 | JetBlue Airways | 7 | 2026-05-05 |
| JBU2467 | - | 5 | 2026-07-11 |
| JBU1851 | JetBlue Airways | 5 | 2026-05-31 |
| JBU1604 | JetBlue Airways | 5 | 2026-06-06 |
| JBU2271 | JetBlue Airways | 4 | 2026-05-19 |
| JBU854 | JetBlue Airways | 3 | 2026-06-22 |
| JBU740 | - | 3 | 2026-04-13 |
| JBU706 | JetBlue Airways | 3 | 2026-04-17 |
| JBU579 | JetBlue Airways | 3 | 2026-04-16 |
| JBU401 | JetBlue Airways | 3 | 2026-05-24 |
| JBU400 | JetBlue Airways | 3 | 2026-05-24 |
| JBU2722 | JetBlue Airways | 3 | 2026-05-17 |
| JBU2584 | JetBlue Airways | 3 | 2026-06-07 |
| JBU2448 | JetBlue Airways | 3 | 2026-05-20 |
| JBU2285 | JetBlue Airways | 3 | 2026-06-13 |
| JBU2272 | JetBlue Airways | 3 | 2026-05-19 |
| JBU204 | JetBlue Airways | 3 | 2026-06-04 |
| JBU203 | JetBlue Airways | 3 | 2026-06-05 |
| JBU2011 | - | 3 | 2026-06-25 |
| JBU1716 | - | 3 | 2026-06-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU2474 | CHS → JFK | Jul 13, 20:05 UTC | Jul 14, 16:40 UTC | 20h 36m |
| 2026-07-13 | JBU626 | TPA → JFK | Jul 13, 13:30 UTC | Jul 14, 12:30 UTC | 23h 1m |
| 2026-07-12 | JBU717 | BOS → JFK | Jul 12, 18:19 UTC | Jul 13, 15:50 UTC | 21h 32m |
| 2026-07-12 | JBU2041 | BOS → CLE | Jul 12, 11:19 UTC | Jul 13, 04:00 UTC | 16h 42m |
| 2026-07-11 | JBU2467 | - | Jul 11, 19:55 UTC | Jul 11, 22:10 UTC | 2h 15m |
| 2026-07-11 | JBU2467 | BOS → CHS | Jul 11, 19:51 UTC | Jul 12, 18:30 UTC | 22h 40m |
| 2026-07-11 | JBU1310 | - | Jul 11, 16:00 UTC | Jul 11, 18:25 UTC | 2h 25m |
| 2026-07-11 | JBU109 | - | Jul 11, 12:40 UTC | Jul 11, 14:55 UTC | 2h 15m |
| 2026-07-11 | JBU994 | DEN → BOS | Jul 11, 05:55 UTC | Jul 11, 09:10 UTC | 3h 15m |
| 2026-07-11 | JBU97 | JFK → DEN | Jul 11, 00:25 UTC | Jul 11, 04:25 UTC | 4h 0m |
| 2026-07-10 | JBU36 | JFK → JFK | Jul 10, 13:50 UTC | Jul 10, 22:00 UTC | 8h 11m |
| 2026-07-10 | JBU372 | SLC → JFK | Jul 10, 06:30 UTC | Jul 10, 10:45 UTC | 4h 15m |
| 2026-07-10 | JBU71 | JFK → SLC | Jul 10, 00:00 UTC | Jul 10, 04:40 UTC | 4h 40m |
| 2026-07-09 | JBU1054 | - | Jul 9, 19:30 UTC | Jul 9, 21:45 UTC | 2h 15m |
| 2026-07-08 | JBU1096 | - | Jul 8, 22:45 UTC | Jul 9, 00:50 UTC | 2h 5m |
| 2026-07-08 | JBU1096 | ATL → BOS | Jul 8, 22:41 UTC | Jul 9, 21:45 UTC | 23h 4m |
| 2026-07-08 | JBU897 | BOS → ATL | Jul 8, 19:10 UTC | Jul 8, 21:20 UTC | 2h 10m |
| 2026-07-08 | JBU1310 | - | Jul 8, 15:15 UTC | Jul 8, 17:25 UTC | 2h 10m |
| 2026-07-08 | JBU109 | - | Jul 8, 11:35 UTC | Jul 8, 13:55 UTC | 2h 20m |
| 2026-07-08 | JBU1012 | - | Jul 8, 03:40 UTC | Jul 8, 05:40 UTC | 2h 0m |
| 2026-07-07 | JBU811 | - | Jul 7, 23:40 UTC | Jul 8, 02:00 UTC | 2h 20m |
| 2026-07-07 | JBU811 | - | Jul 7, 18:10 UTC | Jul 7, 20:45 UTC | 2h 35m |
| 2026-07-07 | JBU1955 | - | Jul 7, 13:10 UTC | Jul 7, 15:50 UTC | 2h 40m |
| 2026-07-06 | JBU2467 | BOS → BOS | Jul 6, 18:30 UTC | Jul 6, 18:35 UTC | 5m |
| 2026-07-06 | JBU312 | ORD → BOS | Jul 6, 16:25 UTC | Jul 6, 18:15 UTC | 1h 50m |
| 2026-07-05 | JBU1231 | BOS → VRB | Jul 5, 13:06 UTC | Jul 6, 04:35 UTC | 15h 30m |
| 2026-07-04 | JBU95 | BOS → PDX | Jul 4, 23:55 UTC | Jul 5, 05:35 UTC | 5h 40m |
| 2026-07-04 | JBU95 | BOS → PDX | Jul 4, 23:55 UTC | Jul 5, 22:30 UTC | 22h 36m |
| 2026-07-04 | JBU2184 | RDU → BOS | Jul 4, 19:35 UTC | Jul 4, 21:05 UTC | 1h 30m |
| 2026-07-04 | JBU810 | - | Jul 4, 01:10 UTC | Jul 4, 03:25 UTC | 2h 15m |
| 2026-07-04 | JBU810 | JAX → BOS | Jul 4, 01:07 UTC | Jul 5, 00:30 UTC | 23h 23m |
| 2026-07-03 | JBU509 | - | Jul 3, 21:55 UTC | Jul 4, 00:20 UTC | 2h 25m |
| 2026-07-03 | JBU494 | - | Jul 3, 16:50 UTC | Jul 3, 20:30 UTC | 3h 40m |
| 2026-07-03 | JBU493 | BOS → DEN | Jul 3, 11:30 UTC | Jul 3, 15:20 UTC | 3h 50m |
| 2026-07-02 | JBU2468 | - | Jul 2, 23:45 UTC | Jul 3, 01:35 UTC | 1h 50m |
| 2026-07-02 | JBU392 | TPA → BOS | Jul 2, 01:08 UTC | Jul 3, 00:30 UTC | 23h 22m |
| 2026-07-01 | JBU391 | BOS → TPA | Jul 1, 20:32 UTC | Jul 2, 18:30 UTC | 21h 58m |
| 2026-07-01 | JBU1896 | ATL → BOS | Jul 1, 11:29 UTC | Jul 2, 10:30 UTC | 23h 2m |
| 2026-06-30 | JBU1238 | - | Jun 30, 15:25 UTC | Jun 30, 19:15 UTC | 3h 50m |
| 2026-06-30 | JBU1238 | AUS → BOS | Jun 30, 15:24 UTC | Jul 1, 14:30 UTC | 23h 7m |
| 2026-06-30 | JBU638 | BOS → AUS | Jun 30, 10:15 UTC | Jun 30, 13:50 UTC | 3h 35m |
| 2026-06-29 | JBU639 | BOS → AUS | Jun 29, 18:00 UTC | Jun 30, 14:30 UTC | 20h 31m |
| 2026-06-28 | JBU1632 | - | Jun 28, 23:09 UTC | Jun 29, 02:30 UTC | 3h 20m |
| 2026-06-28 | JBU1632 | IAH → BOS | Jun 28, 23:07 UTC | Jun 29, 22:30 UTC | 23h 23m |
| 2026-06-28 | JBU933 | - | Jun 28, 17:30 UTC | Jun 28, 21:04 UTC | 3h 35m |
| 2026-06-27 | JBU135 | JFK → PHX | Jun 27, 23:39 UTC | Jun 28, 21:04 UTC | 21h 26m |
| 2026-06-27 | JBU1716 | VRB → JFK | Jun 27, 18:35 UTC | Jun 28, 18:29 UTC | 23h 55m |
| 2026-06-26 | JBU805 | - | Jun 26, 23:44 UTC | Jun 27, 00:29 UTC | 45m |
| 2026-06-26 | JBU805 | JFK → ORD | Jun 26, 23:41 UTC | Jun 27, 21:10 UTC | 21h 29m |
| 2026-06-26 | JBU1716 | - | Jun 26, 19:00 UTC | Jun 26, 21:10 UTC | 2h 10m |
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 N3139J page for operator, model, and routing details .