sensors Mode-S transponder
A3871E
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N3261J · operated by JETBLUE AIRWAYS CORP
- Hex
- A3871E
- Octal
- 50703436
- Decimal
- 10,716,958
- Country
- US
- Tail
- N3261J
- Type
- BCS3
- Flights observed
- 292
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 14m ago
Current position
Country allocation
The ICAO 24-bit address A3871E 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 |
|---|---|---|---|
| JBU502 | JetBlue Airways | 7 | 2026-05-04 |
| JBU159 | JetBlue Airways | 7 | 2026-05-20 |
| JBU401 | - | 5 | 2026-06-17 |
| JBU400 | JetBlue Airways | 5 | 2026-06-17 |
| JBU1303 | JetBlue Airways | 5 | 2026-05-11 |
| JBU994 | JetBlue Airways | 4 | 2026-06-09 |
| JBU822 | JetBlue Airways | 4 | 2026-05-02 |
| JBU2033 | - | 4 | 2026-07-09 |
| JBU1375 | JetBlue Airways | 4 | 2026-05-16 |
| JBU1281 | - | 4 | 2026-07-13 |
| JBU741 | JetBlue Airways | 3 | 2026-06-22 |
| JBU640 | - | 3 | 2026-06-22 |
| JBU501 | JetBlue Airways | 3 | 2026-05-26 |
| JBU2602 | - | 3 | 2026-06-13 |
| JBU249 | JetBlue Airways | 3 | 2026-06-01 |
| JBU2467 | JetBlue Airways | 3 | 2026-05-18 |
| JBU2255 | JetBlue Airways | 3 | 2026-05-07 |
| JBU2064 | JetBlue Airways | 3 | 2026-04-15 |
| JBU201 | - | 3 | 2026-07-02 |
| JBU184 | - | 3 | 2026-07-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JBU2024 | MCO → DCA | Jul 14, 12:51 UTC | Jul 14, 19:30 UTC | 6h 40m |
| 2026-07-14 | JBU2876 | PVD → MCO | Jul 14, 00:57 UTC | Jul 14, 19:30 UTC | 18h 34m |
| 2026-07-13 | JBU2875 | MCO → PVD | Jul 13, 21:39 UTC | Jul 14, 19:30 UTC | 21h 52m |
| 2026-07-13 | JBU51 | BOS → MCO | Jul 13, 16:36 UTC | Jul 14, 14:45 UTC | 22h 10m |
| 2026-07-13 | JBU1281 | - | Jul 13, 11:10 UTC | Jul 13, 12:25 UTC | 1h 15m |
| 2026-07-13 | JBU1281 | BOS → RIC | Jul 13, 11:10 UTC | Jul 14, 09:30 UTC | 22h 21m |
| 2026-07-13 | JBU1281 | BOS → BOS | Jul 13, 10:40 UTC | Jul 13, 10:45 UTC | 5m |
| 2026-07-13 | JBU2066 | BOS → BOS | Jul 13, 07:45 UTC | Jul 13, 07:50 UTC | 5m |
| 2026-07-12 | JBU207 | PQI → BOS | Jul 12, 09:58 UTC | Jul 13, 09:30 UTC | 23h 33m |
| 2026-07-12 | JBU207 | PQI → BOS | Jul 12, 10:01 UTC | Jul 12, 10:55 UTC | 55m |
| 2026-07-12 | JBU206 | BOS → PQI | Jul 12, 02:05 UTC | Jul 12, 03:01 UTC | 55m |
| 2026-07-11 | JBU394 | - | Jul 11, 21:00 UTC | Jul 12, 00:30 UTC | 3h 30m |
| 2026-07-11 | JBU793 | BOS → DEN | Jul 11, 15:35 UTC | Jul 11, 19:30 UTC | 3h 55m |
| 2026-07-11 | JBU1896 | ATL → BOS | Jul 11, 11:30 UTC | Jul 11, 13:40 UTC | 2h 10m |
| 2026-07-10 | JBU1413 | MVY → DCA | Jul 10, 19:22 UTC | Jul 11, 17:30 UTC | 22h 9m |
| 2026-07-10 | JBU95 | BOS → PDX | Jul 10, 01:03 UTC | Jul 10, 23:30 UTC | 22h 28m |
| 2026-07-09 | JBU2033 | BOS → IAH | Jul 9, 13:33 UTC | Jul 10, 11:30 UTC | 21h 57m |
| 2026-07-09 | JBU2033 | - | Jul 9, 13:35 UTC | Jul 9, 17:05 UTC | 3h 30m |
| 2026-07-08 | JBU2033 | - | Jul 8, 13:35 UTC | Jul 8, 17:00 UTC | 3h 25m |
| 2026-07-08 | JBU2033 | BOS → IAH | Jul 8, 13:32 UTC | Jul 9, 10:55 UTC | 21h 24m |
| 2026-07-08 | JBU1484 | RDU → BOS | Jul 8, 10:05 UTC | Jul 8, 11:30 UTC | 1h 25m |
| 2026-07-07 | JBU1154 | - | Jul 7, 15:00 UTC | Jul 7, 17:05 UTC | 2h 5m |
| 2026-07-07 | JBU1154 | PBI → JFK | Jul 7, 14:56 UTC | Jul 8, 13:30 UTC | 22h 35m |
| 2026-07-07 | JBU953 | - | Jul 7, 10:45 UTC | Jul 7, 13:00 UTC | 2h 15m |
| 2026-07-06 | JBU237 | JFK → STI | Jul 6, 14:54 UTC | Jul 7, 13:00 UTC | 22h 7m |
| 2026-07-05 | JBU192 | ACK → JFK | Jul 5, 21:07 UTC | Jul 6, 15:40 UTC | 18h 33m |
| 2026-07-05 | JBU1868 | - | Jul 5, 14:25 UTC | Jul 5, 16:30 UTC | 2h 5m |
| 2026-07-05 | JBU1868 | DAB → JFK | Jul 5, 14:22 UTC | Jul 6, 10:40 UTC | 20h 18m |
| 2026-07-05 | JBU1867 | HPN → PBI | Jul 5, 11:10 UTC | Jul 5, 13:15 UTC | 2h 5m |
| 2026-07-04 | JBU184 | - | Jul 4, 15:25 UTC | Jul 4, 17:40 UTC | 2h 15m |
| 2026-07-03 | JBU2134 | SJU → MCO | Jul 3, 20:28 UTC | Jul 4, 17:45 UTC | 21h 17m |
| 2026-07-03 | JBU1516 | JFK → SYR | Jul 3, 03:33 UTC | Jul 4, 01:30 UTC | 21h 57m |
| 2026-07-03 | JBU1516 | - | Jul 3, 03:35 UTC | Jul 3, 04:15 UTC | 40m |
| 2026-07-03 | JBU342 | - | Jul 3, 00:00 UTC | Jul 3, 01:45 UTC | 1h 45m |
| 2026-07-02 | JBU341 | - | Jul 2, 20:45 UTC | Jul 2, 22:25 UTC | 1h 40m |
| 2026-07-02 | JBU201 | BUF → JFK | Jul 2, 01:00 UTC | Jul 2, 22:25 UTC | 21h 25m |
| 2026-07-01 | JBU1736 | STI → JFK | Jul 1, 16:31 UTC | Jul 2, 15:00 UTC | 22h 29m |
| 2026-07-01 | JBU1736 | JFK → JFK | Jul 1, 11:50 UTC | Jul 1, 19:55 UTC | 8h 5m |
| 2026-07-01 | JBU359 | BUR → JFK | Jul 1, 04:30 UTC | Jul 1, 09:25 UTC | 4h 55m |
| 2026-06-30 | JBU358 | - | Jun 30, 21:15 UTC | Jul 1, 02:45 UTC | 5h 30m |
| 2026-06-30 | JBU80 | - | Jun 30, 14:45 UTC | Jun 30, 19:30 UTC | 4h 45m |
| 2026-06-29 | JBU81 | - | Jun 29, 23:29 UTC | Jun 30, 04:55 UTC | 5h 26m |
| 2026-06-29 | JBU1716 | - | Jun 29, 18:44 UTC | Jun 29, 20:54 UTC | 2h 10m |
| 2026-06-29 | JBU805 | JFK → ORD | Jun 29, 00:30 UTC | Jun 29, 23:29 UTC | 23h 0m |
| 2026-06-29 | JBU805 | - | Jun 29, 00:34 UTC | Jun 29, 02:35 UTC | 2h 0m |
| 2026-06-28 | JBU1716 | - | Jun 28, 18:25 UTC | Jun 28, 20:34 UTC | 2h 10m |
| 2026-06-27 | JBU317 | BOS → JFK | Jun 27, 22:15 UTC | Jun 27, 23:00 UTC | 45m |
| 2026-06-27 | JBU317 | BOS → JFK | Jun 27, 22:14 UTC | Jun 28, 20:39 UTC | 22h 26m |
| 2026-06-27 | JBU494 | - | Jun 27, 17:14 UTC | Jun 27, 20:39 UTC | 3h 25m |
| 2026-06-27 | JBU493 | - | Jun 27, 11:20 UTC | Jun 27, 15:24 UTC | 4h 5m |
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 N3261J page for operator, model, and routing details .