sensors Mode-S transponder
A37FB0
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N3241J · AIRBUS A220-300 · operated by JETBLUE AIRWAYS CORP
- Hex
- A37FB0
- Octal
- 50677660
- Decimal
- 10,715,056
- Country
- US
- Tail
- N3241J
- Type
- BCS3
- Flights observed
- 293
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address A37FB0 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 |
|---|---|---|---|
| JBU845 | - | 5 | 2026-07-08 |
| JBU109 | JetBlue Airways | 5 | 2026-05-12 |
| JBU400 | JetBlue Airways | 4 | 2026-06-17 |
| JBU312 | JetBlue Airways | 4 | 2026-06-23 |
| JBU2784 | JetBlue Airways | 4 | 2026-05-20 |
| JBU1310 | JetBlue Airways | 4 | 2026-06-06 |
| JBU934 | - | 3 | 2026-06-20 |
| JBU883 | JetBlue Airways | 3 | 2026-05-20 |
| JBU717 | - | 3 | 2026-07-11 |
| JBU618 | JetBlue Airways | 3 | 2026-06-05 |
| JBU541 | JetBlue Airways | 3 | 2026-04-25 |
| JBU53 | - | 3 | 2026-07-06 |
| JBU401 | - | 3 | 2026-06-16 |
| JBU392 | JetBlue Airways | 3 | 2026-04-16 |
| JBU374 | - | 3 | 2026-06-16 |
| JBU311 | - | 3 | 2026-06-23 |
| JBU2783 | JetBlue Airways | 3 | 2026-05-02 |
| JBU2473 | - | 3 | 2026-06-25 |
| JBU2091 | - | 3 | 2026-07-13 |
| JBU2064 | JetBlue Airways | 3 | 2026-04-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU1963 | - | Jul 13, 21:05 UTC | Jul 13, 21:50 UTC | 45m |
| 2026-07-13 | JBU1963 | HYA → JFK | Jul 13, 21:04 UTC | Jul 14, 04:00 UTC | 6h 57m |
| 2026-07-13 | JBU1964 | - | Jul 13, 18:35 UTC | Jul 13, 19:20 UTC | 45m |
| 2026-07-13 | JBU92 | - | Jul 13, 16:10 UTC | Jul 13, 16:45 UTC | 35m |
| 2026-07-13 | JBU2091 | - | Jul 13, 14:05 UTC | Jul 13, 14:45 UTC | 40m |
| 2026-07-13 | JBU286 | - | Jul 13, 10:55 UTC | Jul 13, 12:05 UTC | 1h 10m |
| 2026-07-13 | JBU185 | JFK → RDU | Jul 13, 01:55 UTC | Jul 13, 03:05 UTC | 1h 10m |
| 2026-07-12 | JBU36 | - | Jul 12, 14:45 UTC | Jul 12, 22:50 UTC | 8h 5m |
| 2026-07-11 | JBU1173 | JFK → BNA | Jul 11, 20:49 UTC | Jul 12, 15:25 UTC | 18h 37m |
| 2026-07-11 | JBU717 | - | Jul 11, 17:45 UTC | Jul 11, 18:40 UTC | 55m |
| 2026-07-11 | JBU717 | BOS → JFK | Jul 11, 17:45 UTC | Jul 12, 15:25 UTC | 21h 41m |
| 2026-07-11 | JBU1192 | TPA → BOS | Jul 11, 10:35 UTC | Jul 11, 13:15 UTC | 2h 40m |
| 2026-07-10 | JBU625 | JFK → TPA | Jul 10, 19:20 UTC | Jul 10, 21:40 UTC | 2h 20m |
| 2026-07-10 | JBU2012 | - | Jul 10, 15:00 UTC | Jul 10, 17:05 UTC | 2h 5m |
| 2026-07-10 | JBU2011 | - | Jul 10, 11:30 UTC | Jul 10, 13:40 UTC | 2h 10m |
| 2026-07-09 | JBU59 | JFK → KIN | Jul 9, 10:53 UTC | Jul 10, 03:25 UTC | 16h 32m |
| 2026-07-08 | JBU1530 | RSW → JFK | Jul 8, 16:38 UTC | Jul 9, 13:15 UTC | 20h 37m |
| 2026-07-08 | JBU845 | - | Jul 8, 04:50 UTC | Jul 8, 05:35 UTC | 45m |
| 2026-07-08 | JBU845 | BOS → SYR | Jul 8, 04:45 UTC | Jul 9, 02:05 UTC | 21h 21m |
| 2026-07-07 | JBU22 | - | Jul 7, 23:55 UTC | Jul 8, 03:30 UTC | 3h 35m |
| 2026-07-06 | JBU53 | JFK → PBI | Jul 6, 18:36 UTC | Jul 6, 21:55 UTC | 3h 19m |
| 2026-07-06 | JBU53 | - | Jul 6, 18:40 UTC | Jul 6, 21:55 UTC | 3h 15m |
| 2026-07-05 | JBU92 | ACK → JFK | Jul 5, 17:00 UTC | Jul 6, 10:50 UTC | 17h 51m |
| 2026-07-05 | JBU2091 | - | Jul 5, 14:25 UTC | Jul 5, 15:00 UTC | 35m |
| 2026-07-05 | JBU2091 | JFK → ACK | Jul 5, 14:24 UTC | Jul 6, 10:50 UTC | 20h 27m |
| 2026-07-04 | JBU493 | BOS → DEN | Jul 4, 10:30 UTC | Jul 5, 04:35 UTC | 18h 6m |
| 2026-07-03 | JBU896 | ATL → BOS | Jul 3, 16:16 UTC | Jul 4, 16:00 UTC | 23h 45m |
| 2026-07-03 | JBU201 | - | Jul 3, 01:15 UTC | Jul 3, 02:00 UTC | 45m |
| 2026-07-03 | JBU201 | BUF → JFK | Jul 3, 01:14 UTC | Jul 4, 00:00 UTC | 22h 47m |
| 2026-07-02 | JBU1202 | JFK → BUF | Jul 2, 23:10 UTC | Jul 3, 00:05 UTC | 55m |
| 2026-07-02 | JBU1382 | - | Jul 2, 18:20 UTC | Jul 2, 21:35 UTC | 3h 15m |
| 2026-07-02 | JBU1381 | - | Jul 2, 12:55 UTC | Jul 2, 15:55 UTC | 3h 0m |
| 2026-07-01 | JBU59 | JFK → KIN | Jul 1, 09:15 UTC | Jul 2, 01:55 UTC | 16h 40m |
| 2026-07-01 | JBU201 | BUF → JFK | Jul 1, 00:04 UTC | Jul 2, 00:00 UTC | 23h 57m |
| 2026-06-30 | JBU1737 | - | Jun 30, 11:50 UTC | Jun 30, 12:35 UTC | 45m |
| 2026-06-30 | JBU1737 | JFK → STI | Jun 30, 11:50 UTC | Jul 1, 10:00 UTC | 22h 10m |
| 2026-06-30 | JBU917 | BOS → JFK | Jun 30, 09:20 UTC | Jun 30, 10:00 UTC | 40m |
| 2026-06-29 | JBU1318 | - | Jun 29, 03:20 UTC | Jun 29, 04:04 UTC | 45m |
| 2026-06-28 | JBU1382 | - | Jun 28, 17:25 UTC | Jun 28, 20:39 UTC | 3h 15m |
| 2026-06-27 | JBU22 | PBI → BOS | Jun 27, 23:00 UTC | Jun 28, 20:39 UTC | 21h 40m |
| 2026-06-27 | JBU53 | JFK → PBI | Jun 27, 18:47 UTC | Jun 28, 18:00 UTC | 23h 13m |
| 2026-06-27 | JBU1198 | - | Jun 27, 14:39 UTC | Jun 27, 15:45 UTC | 1h 5m |
| 2026-06-27 | JBU1198 | PIT → JFK | Jun 27, 14:35 UTC | Jun 28, 13:59 UTC | 23h 25m |
| 2026-06-26 | JBU150 | - | Jun 26, 13:45 UTC | Jun 26, 15:45 UTC | 2h 0m |
| 2026-06-26 | JBU150 | SAV → BOS | Jun 26, 13:39 UTC | Jun 27, 02:50 UTC | 13h 11m |
| 2026-06-26 | JBU741 | BOS → SRQ | Jun 26, 10:30 UTC | Jun 26, 12:14 UTC | 1h 45m |
| 2026-06-26 | JBU1274 | - | Jun 26, 00:59 UTC | Jun 26, 02:24 UTC | 1h 25m |
| 2026-06-25 | JBU2473 | - | Jun 25, 22:29 UTC | Jun 25, 23:59 UTC | 1h 30m |
| 2026-06-25 | JBU1054 | - | Jun 25, 18:39 UTC | Jun 25, 20:49 UTC | 2h 10m |
| 2026-06-25 | JBU21 | MCO → MBJ | Jun 25, 13:14 UTC | Jun 25, 16:09 UTC | 2h 55m |
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 N3241J page for operator, model, and routing details .