sensors Mode-S transponder
A39289
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N3293J · AIRBUS A220-300 · operated by JETBLUE AIRWAYS
- Hex
- A39289
- Octal
- 50711211
- Decimal
- 10,719,881
- Country
- US
- Tail
- N3293J
- Type
- BCS3
- Flights observed
- 299
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 2h ago
Current position
Country allocation
The ICAO 24-bit address A39289 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 |
|---|---|---|---|
| JBU484 | JetBlue Airways | 5 | 2026-06-08 |
| JBU303 | JetBlue Airways | 5 | 2026-04-18 |
| JBU2121 | - | 5 | 2026-07-09 |
| JBU2283 | JetBlue Airways | 4 | 2026-05-08 |
| JBU2272 | JetBlue Airways | 4 | 2026-04-16 |
| JBU2271 | JetBlue Airways | 4 | 2026-04-16 |
| JBU1781 | - | 4 | 2026-06-27 |
| JBU1593 | JetBlue Airways | 4 | 2026-05-19 |
| JBU865 | JetBlue Airways | 3 | 2026-04-27 |
| JBU821 | - | 3 | 2026-04-13 |
| JBU519 | JetBlue Airways | 3 | 2026-05-09 |
| JBU400 | JetBlue Airways | 3 | 2026-05-11 |
| JBU391 | - | 3 | 2026-06-17 |
| JBU358 | - | 3 | 2026-07-13 |
| JBU322 | - | 3 | 2026-04-13 |
| JBU2896 | JetBlue Airways | 3 | 2026-06-10 |
| JBU259 | JetBlue Airways | 3 | 2026-04-14 |
| JBU2432 | - | 3 | 2026-07-06 |
| JBU2352 | - | 3 | 2026-07-08 |
| JBU2301 | JetBlue Airways | 3 | 2026-05-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU1198 | - | Jul 14, 10:35 UTC | Jul 14, 11:45 UTC | 1h 10m |
| 2026-07-14 | JBU1195 | JFK → PIT | Jul 14, 02:50 UTC | Jul 14, 03:50 UTC | 1h 0m |
| 2026-07-13 | JBU1382 | - | Jul 13, 22:15 UTC | Jul 14, 01:25 UTC | 3h 10m |
| 2026-07-13 | JBU1381 | - | Jul 13, 19:20 UTC | Jul 13, 19:55 UTC | 35m |
| 2026-07-13 | JBU1381 | JFK → AUS | Jul 13, 13:05 UTC | Jul 13, 17:15 UTC | 4h 10m |
| 2026-07-13 | JBU358 | BUR → JFK | Jul 13, 04:40 UTC | Jul 13, 09:45 UTC | 5h 5m |
| 2026-07-12 | JBU358 | JFK → BUR | Jul 12, 22:10 UTC | Jul 13, 03:10 UTC | 5h 0m |
| 2026-07-12 | JBU80 | - | Jul 12, 15:05 UTC | Jul 12, 20:05 UTC | 5h 0m |
| 2026-07-10 | JBU121 | JFK → NAS | Jul 10, 13:40 UTC | Jul 11, 04:25 UTC | 14h 46m |
| 2026-07-10 | JBU1355 | BOS → DCA | Jul 10, 01:18 UTC | Jul 11, 00:15 UTC | 22h 58m |
| 2026-07-09 | JBU1254 | DCA → BOS | Jul 9, 19:08 UTC | Jul 10, 18:15 UTC | 23h 8m |
| 2026-07-09 | JBU2121 | HPN → ACK | Jul 9, 13:04 UTC | Jul 10, 11:30 UTC | 22h 26m |
| 2026-07-08 | JBU2122 | ACK → HPN | Jul 8, 22:19 UTC | Jul 9, 22:15 UTC | 23h 57m |
| 2026-07-08 | JBU2352 | BOS → ACK | Jul 8, 13:35 UTC | Jul 8, 23:00 UTC | 9h 26m |
| 2026-07-07 | JBU793 | BOS → DEN | Jul 7, 19:20 UTC | Jul 7, 23:35 UTC | 4h 15m |
| 2026-07-07 | JBU793 | BOS → DEN | Jul 7, 19:20 UTC | Jul 8, 18:15 UTC | 22h 56m |
| 2026-07-07 | JBU1310 | - | Jul 7, 15:25 UTC | Jul 7, 18:00 UTC | 2h 35m |
| 2026-07-07 | JBU1151 | - | Jul 7, 11:45 UTC | Jul 7, 14:00 UTC | 2h 15m |
| 2026-07-06 | JBU2432 | LGA → ACK | Jul 6, 17:46 UTC | Jul 7, 16:15 UTC | 22h 29m |
| 2026-07-06 | JBU831 | ACK → LGA | Jul 6, 15:51 UTC | Jul 7, 14:00 UTC | 22h 10m |
| 2026-07-06 | JBU1632 | IAH → BOS | Jul 6, 00:28 UTC | Jul 6, 23:35 UTC | 23h 8m |
| 2026-07-05 | JBU372 | SLC → JFK | Jul 5, 05:35 UTC | Jul 5, 09:25 UTC | 3h 50m |
| 2026-07-05 | JBU372 | SLC → JFK | Jul 5, 05:32 UTC | Jul 6, 04:15 UTC | 22h 43m |
| 2026-07-05 | JBU71 | - | Jul 5, 03:50 UTC | Jul 5, 04:35 UTC | 45m |
| 2026-07-04 | JBU71 | - | Jul 4, 23:40 UTC | Jul 5, 03:45 UTC | 4h 5m |
| 2026-07-04 | JBU59 | JFK → JFK | Jul 4, 09:20 UTC | Jul 4, 17:35 UTC | 8h 15m |
| 2026-07-03 | JBU2922 | - | Jul 3, 18:25 UTC | Jul 3, 20:35 UTC | 2h 10m |
| 2026-07-03 | JBU121 | - | Jul 3, 13:50 UTC | Jul 3, 16:00 UTC | 2h 10m |
| 2026-07-03 | JBU286 | - | Jul 3, 11:00 UTC | Jul 3, 12:05 UTC | 1h 5m |
| 2026-07-03 | JBU185 | JFK → RDU | Jul 3, 04:25 UTC | Jul 3, 05:30 UTC | 1h 5m |
| 2026-07-03 | JBU1174 | BNA → JFK | Jul 3, 00:15 UTC | Jul 3, 02:15 UTC | 2h 0m |
| 2026-07-02 | JBU1173 | JFK → BNA | Jul 2, 20:05 UTC | Jul 2, 21:55 UTC | 1h 50m |
| 2026-07-02 | JBU59 | JFK → JFK | Jul 2, 10:00 UTC | Jul 2, 18:15 UTC | 8h 15m |
| 2026-07-01 | JBU142 | SAV → JFK | Jul 1, 14:53 UTC | Jul 2, 12:15 UTC | 21h 22m |
| 2026-07-01 | JBU249 | BOS → SAV | Jul 1, 11:48 UTC | Jul 2, 10:15 UTC | 22h 27m |
| 2026-06-30 | JBU2432 | - | Jun 30, 17:40 UTC | Jun 30, 18:15 UTC | 35m |
| 2026-06-30 | JBU2432 | LGA → ACK | Jun 30, 17:40 UTC | Jul 1, 16:15 UTC | 22h 36m |
| 2026-06-30 | JBU831 | - | Jun 30, 15:15 UTC | Jun 30, 16:00 UTC | 45m |
| 2026-06-30 | JBU1632 | - | Jun 30, 13:40 UTC | Jun 30, 14:05 UTC | 25m |
| 2026-06-29 | JBU933 | BOS → IAH | Jun 29, 17:22 UTC | Jun 30, 16:05 UTC | 22h 44m |
| 2026-06-29 | JBU1225 | - | Jun 29, 15:24 UTC | Jun 29, 15:45 UTC | 20m |
| 2026-06-29 | JBU1324 | BOS → MVY | Jun 29, 14:19 UTC | Jun 30, 14:05 UTC | 23h 46m |
| 2026-06-29 | JBU1324 | BOS → MVY | Jun 29, 14:19 UTC | Jun 29, 14:39 UTC | 20m |
| 2026-06-28 | JBU2352 | BOS → ACK | Jun 28, 13:38 UTC | Jun 29, 11:35 UTC | 21h 57m |
| 2026-06-28 | JBU1785 | BOS → PIT | Jun 28, 02:56 UTC | Jun 29, 02:14 UTC | 23h 19m |
| 2026-06-27 | JBU1782 | - | Jun 27, 23:00 UTC | Jun 28, 01:34 UTC | 2h 35m |
| 2026-06-27 | JBU1782 | VPS → BOS | Jun 27, 22:57 UTC | Jun 28, 22:15 UTC | 23h 18m |
| 2026-06-27 | JBU1781 | - | Jun 27, 16:59 UTC | Jun 27, 19:34 UTC | 2h 35m |
| 2026-06-27 | JBU150 | - | Jun 27, 14:00 UTC | Jun 27, 15:49 UTC | 1h 50m |
| 2026-06-27 | JBU741 | BOS → SRQ | Jun 27, 10:25 UTC | Jun 27, 12:04 UTC | 1h 40m |
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 N3293J page for operator, model, and routing details .