sensors Mode-S transponder
A37FD3
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N3242J · operated by JETBLUE AIRWAYS CORP
- Hex
- A37FD3
- Octal
- 50677723
- Decimal
- 10,715,091
- Country
- US
- Tail
- N3242J
- Type
- BCS3
- Flights observed
- 307
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address A37FD3 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 |
|---|---|---|---|
| JBU68 | - | 4 | 2026-06-20 |
| JBU401 | - | 4 | 2026-06-13 |
| JBU400 | JetBlue Airways | 4 | 2026-05-04 |
| JBU312 | JetBlue Airways | 4 | 2026-06-29 |
| JBU2473 | JetBlue Airways | 4 | 2026-05-09 |
| JBU204 | - | 4 | 2026-04-16 |
| JBU1782 | - | 4 | 2026-06-28 |
| JBU95 | JetBlue Airways | 3 | 2026-06-02 |
| JBU870 | JetBlue Airways | 3 | 2026-04-13 |
| JBU810 | - | 3 | 2026-07-02 |
| JBU72 | JetBlue Airways | 3 | 2026-04-17 |
| JBU71 | JetBlue Airways | 3 | 2026-04-17 |
| JBU641 | JetBlue Airways | 3 | 2026-06-03 |
| JBU618 | JetBlue Airways | 3 | 2026-06-10 |
| JBU519 | - | 3 | 2026-04-17 |
| JBU396 | JetBlue Airways | 3 | 2026-06-02 |
| JBU391 | JetBlue Airways | 3 | 2026-06-12 |
| JBU386 | - | 3 | 2026-06-30 |
| JBU372 | - | 3 | 2026-06-18 |
| JBU311 | - | 3 | 2026-06-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU1439 | BOS → AUS | Jul 14, 10:19 UTC | Jul 14, 18:45 UTC | 8h 27m |
| 2026-07-14 | JBU1439 | BOS → AUS | Jul 14, 10:20 UTC | Jul 14, 13:50 UTC | 3h 30m |
| 2026-07-13 | JBU896 | - | Jul 13, 16:20 UTC | Jul 13, 16:45 UTC | 25m |
| 2026-07-13 | JBU1097 | - | Jul 13, 12:55 UTC | Jul 13, 15:10 UTC | 2h 15m |
| 2026-07-13 | JBU1097 | BOS → ATL | Jul 13, 12:52 UTC | Jul 14, 12:45 UTC | 23h 54m |
| 2026-07-13 | JBU207 | - | Jul 13, 10:10 UTC | Jul 13, 11:00 UTC | 50m |
| 2026-07-12 | JBU2116 | BUF → BOS | Jul 12, 14:59 UTC | Jul 13, 14:45 UTC | 23h 47m |
| 2026-07-12 | JBU506 | BNA → BOS | Jul 12, 02:03 UTC | Jul 13, 00:45 UTC | 22h 43m |
| 2026-07-11 | JBU507 | BOS → BNA | Jul 11, 22:04 UTC | Jul 12, 18:45 UTC | 20h 42m |
| 2026-07-11 | JBU507 | - | Jul 11, 22:05 UTC | Jul 12, 00:40 UTC | 2h 35m |
| 2026-07-11 | JBU494 | DEN → BOS | Jul 11, 17:00 UTC | Jul 11, 20:20 UTC | 3h 20m |
| 2026-07-10 | JBU1096 | ATL → BOS | Jul 10, 23:47 UTC | Jul 11, 22:45 UTC | 22h 59m |
| 2026-07-10 | JBU184 | MCO → JFK | Jul 10, 15:45 UTC | Jul 10, 17:55 UTC | 2h 10m |
| 2026-07-10 | JBU184 | MCO → JFK | Jul 10, 15:41 UTC | Jul 11, 14:30 UTC | 22h 50m |
| 2026-07-10 | JBU737 | - | Jul 10, 11:25 UTC | Jul 10, 13:45 UTC | 2h 20m |
| 2026-07-09 | JBU605 | - | Jul 9, 09:25 UTC | Jul 9, 10:05 UTC | 40m |
| 2026-07-09 | JBU605 | MCO → SDQ | Jul 9, 09:25 UTC | Jul 10, 02:50 UTC | 17h 26m |
| 2026-07-09 | JBU251 | JAX → MCO | Jul 9, 03:45 UTC | Jul 9, 04:15 UTC | 30m |
| 2026-07-09 | JBU251 | - | Jul 9, 00:10 UTC | Jul 9, 02:40 UTC | 2h 30m |
| 2026-07-08 | JBU715 | - | Jul 8, 05:50 UTC | Jul 8, 07:00 UTC | 1h 10m |
| 2026-07-08 | JBU715 | BOS → BUF | Jul 8, 05:48 UTC | Jul 9, 04:30 UTC | 22h 43m |
| 2026-07-08 | JBU2468 | - | Jul 8, 01:25 UTC | Jul 8, 03:30 UTC | 2h 5m |
| 2026-07-07 | JBU2467 | - | Jul 7, 20:30 UTC | Jul 7, 22:35 UTC | 2h 5m |
| 2026-07-07 | JBU1896 | ATL → BOS | Jul 7, 16:20 UTC | Jul 7, 18:35 UTC | 2h 15m |
| 2026-07-06 | JBU1310 | - | Jul 6, 15:15 UTC | Jul 6, 17:25 UTC | 2h 10m |
| 2026-07-06 | JBU1310 | JAX → BOS | Jul 6, 15:11 UTC | Jul 7, 11:30 UTC | 20h 20m |
| 2026-07-06 | JBU109 | - | Jul 6, 11:35 UTC | Jul 6, 13:55 UTC | 2h 20m |
| 2026-07-06 | JBU247 | BOS → BOS | Jul 6, 07:50 UTC | Jul 6, 07:55 UTC | 5m |
| 2026-07-04 | JBU2285 | JFK → RDU | Jul 4, 13:35 UTC | Jul 5, 12:45 UTC | 23h 10m |
| 2026-07-04 | JBU1198 | PIT → JFK | Jul 4, 09:39 UTC | Jul 5, 08:45 UTC | 23h 6m |
| 2026-07-04 | JBU1195 | JFK → PIT | Jul 4, 04:58 UTC | Jul 5, 04:45 UTC | 23h 47m |
| 2026-07-03 | JBU1497 | JFK → DEN | Jul 3, 14:55 UTC | Jul 4, 14:45 UTC | 23h 51m |
| 2026-07-03 | JBU1497 | JFK → DEN | Jul 3, 15:00 UTC | Jul 3, 18:40 UTC | 3h 40m |
| 2026-07-03 | JBU854 | - | Jul 3, 10:55 UTC | Jul 3, 13:05 UTC | 2h 10m |
| 2026-07-02 | JBU1053 | - | Jul 2, 23:20 UTC | Jul 3, 01:40 UTC | 2h 20m |
| 2026-07-02 | JBU1737 | JFK → JFK | Jul 2, 12:00 UTC | Jul 2, 19:45 UTC | 7h 45m |
| 2026-07-02 | JBU917 | - | Jul 2, 09:25 UTC | Jul 2, 10:05 UTC | 40m |
| 2026-07-02 | JBU810 | BOS → BOS | Jul 2, 08:45 UTC | Jul 2, 08:50 UTC | 5m |
| 2026-07-01 | JBU207 | PQI → BOS | Jul 1, 09:42 UTC | Jul 2, 08:45 UTC | 23h 3m |
| 2026-06-30 | JBU781 | - | Jun 30, 20:20 UTC | Jun 30, 20:40 UTC | 20m |
| 2026-06-30 | JBU386 | - | Jun 30, 17:50 UTC | Jun 30, 19:05 UTC | 1h 15m |
| 2026-06-30 | JBU386 | PIT → BOS | Jun 30, 17:47 UTC | Jul 1, 16:00 UTC | 22h 14m |
| 2026-06-30 | JBU385 | - | Jun 30, 14:35 UTC | Jun 30, 15:50 UTC | 1h 15m |
| 2026-06-29 | JBU1813 | BOS → ORF | Jun 29, 20:24 UTC | Jun 30, 18:45 UTC | 22h 22m |
| 2026-06-29 | JBU312 | ORD → BOS | Jun 29, 17:10 UTC | Jun 30, 15:50 UTC | 22h 41m |
| 2026-06-29 | JBU311 | BOS → ORD | Jun 29, 13:46 UTC | Jun 30, 12:45 UTC | 23h 0m |
| 2026-06-29 | JBU206 | BOS → PQI | Jun 29, 09:14 UTC | Jun 30, 02:50 UTC | 17h 37m |
| 2026-06-28 | JBU1782 | VPS → BOS | Jun 28, 23:14 UTC | Jun 29, 22:44 UTC | 23h 31m |
| 2026-06-28 | JBU2041 | BOS → CLE | Jun 28, 11:25 UTC | Jun 29, 08:44 UTC | 21h 20m |
| 2026-06-27 | JBU419 | JFK → ATL | Jun 27, 22:13 UTC | Jun 28, 19:55 UTC | 21h 42m |
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 N3242J page for operator, model, and routing details .