sensors Mode-S transponder
A386FB
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N3260J · operated by JETBLUE AIRWAYS CORP
- Hex
- A386FB
- Octal
- 50703373
- Decimal
- 10,716,923
- Country
- US
- Tail
- N3260J
- Type
- BCS3
- Flights observed
- 315
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address A386FB 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 |
|---|---|---|---|
| JBU394 | JetBlue Airways | 5 | 2026-05-08 |
| JBU393 | JetBlue Airways | 5 | 2026-05-08 |
| JBU249 | - | 5 | 2026-07-13 |
| JBU896 | JetBlue Airways | 4 | 2026-05-27 |
| JBU400 | - | 4 | 2026-07-09 |
| JBU1814 | - | 4 | 2026-06-30 |
| JBU1813 | - | 4 | 2026-06-30 |
| JBU1337 | - | 4 | 2026-07-01 |
| JBU1310 | - | 4 | 2026-06-30 |
| JBU1286 | - | 4 | 2026-07-09 |
| JBU1083 | - | 4 | 2026-06-15 |
| JBU716 | - | 3 | 2026-07-03 |
| JBU541 | JetBlue Airways | 3 | 2026-05-22 |
| JBU502 | JetBlue Airways | 3 | 2026-05-20 |
| JBU450 | JetBlue Airways | 3 | 2026-05-09 |
| JBU401 | - | 3 | 2026-07-09 |
| JBU392 | JetBlue Airways | 3 | 2026-04-15 |
| JBU352 | - | 3 | 2026-04-13 |
| JBU2783 | JetBlue Airways | 3 | 2026-05-09 |
| JBU2769 | JetBlue Airways | 3 | 2026-05-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU2291 | - | Jul 13, 18:15 UTC | Jul 13, 18:45 UTC | 30m |
| 2026-07-13 | JBU2291 | JFK → ACK | Jul 13, 18:13 UTC | Jul 14, 02:40 UTC | 8h 28m |
| 2026-07-13 | JBU142 | SAV → JFK | Jul 13, 15:05 UTC | Jul 13, 16:50 UTC | 1h 45m |
| 2026-07-13 | JBU142 | SAV → JFK | Jul 13, 15:04 UTC | Jul 14, 02:40 UTC | 11h 37m |
| 2026-07-13 | JBU249 | - | Jul 13, 11:40 UTC | Jul 13, 13:45 UTC | 2h 5m |
| 2026-07-13 | JBU249 | BOS → BOS | Jul 13, 09:40 UTC | Jul 13, 09:45 UTC | 5m |
| 2026-07-13 | 19000000 | BOS → BOS | Jul 13, 06:25 UTC | Jul 13, 06:30 UTC | 5m |
| 2026-07-13 | JBU9999 | BOS → BOS | Jul 13, 05:50 UTC | Jul 13, 05:55 UTC | 5m |
| 2026-07-13 | JBU9999 | BOS → BOS | Jul 13, 05:31 UTC | Jul 13, 05:35 UTC | 5m |
| 2026-07-12 | JBU592 | TPA → BOS | Jul 12, 21:40 UTC | Jul 13, 00:20 UTC | 2h 40m |
| 2026-07-12 | JBU2152 | - | Jul 12, 19:10 UTC | Jul 12, 20:10 UTC | 1h 0m |
| 2026-07-11 | JBU2493 | - | Jul 11, 23:20 UTC | Jul 12, 00:35 UTC | 1h 15m |
| 2026-07-11 | JBU2493 | ACK → DCA | Jul 11, 23:18 UTC | Jul 12, 22:45 UTC | 23h 28m |
| 2026-07-11 | JBU2121 | - | Jul 11, 21:20 UTC | Jul 11, 21:50 UTC | 30m |
| 2026-07-11 | JBU2122 | - | Jul 11, 19:15 UTC | Jul 11, 19:55 UTC | 40m |
| 2026-07-10 | JBU2432 | - | Jul 10, 18:50 UTC | Jul 10, 19:30 UTC | 40m |
| 2026-07-10 | JBU831 | - | Jul 10, 16:30 UTC | Jul 10, 17:25 UTC | 55m |
| 2026-07-09 | JBU400 | MSY → BOS | Jul 9, 21:04 UTC | Jul 10, 19:30 UTC | 22h 26m |
| 2026-07-09 | JBU401 | BOS → MSY | Jul 9, 16:04 UTC | Jul 10, 14:45 UTC | 22h 41m |
| 2026-07-09 | JBU1286 | PIT → BOS | Jul 9, 13:07 UTC | Jul 10, 12:45 UTC | 23h 39m |
| 2026-07-09 | JBU560 | PHL → BOS | Jul 9, 03:05 UTC | Jul 10, 02:45 UTC | 23h 40m |
| 2026-07-08 | JBU1500 | DAB → BOS | Jul 8, 19:51 UTC | Jul 9, 18:45 UTC | 22h 54m |
| 2026-07-08 | JBU1499 | BOS → BOS | Jul 8, 14:20 UTC | Jul 8, 14:25 UTC | 5m |
| 2026-07-08 | JBU1192 | TPA → BOS | Jul 8, 11:00 UTC | Jul 8, 13:30 UTC | 2h 30m |
| 2026-07-08 | JBU1192 | TPA → BOS | Jul 8, 10:57 UTC | Jul 9, 10:45 UTC | 23h 48m |
| 2026-07-07 | JBU2152 | - | Jul 7, 19:10 UTC | Jul 7, 20:05 UTC | 55m |
| 2026-07-07 | JBU2152 | - | Jul 7, 17:25 UTC | Jul 7, 17:35 UTC | 10m |
| 2026-07-07 | JBU2133 | - | Jul 7, 14:00 UTC | Jul 7, 14:20 UTC | 20m |
| 2026-07-07 | JBU2133 | - | Jul 7, 11:50 UTC | Jul 7, 12:25 UTC | 35m |
| 2026-07-06 | JBU1086 | - | Jul 6, 13:30 UTC | Jul 6, 15:40 UTC | 2h 10m |
| 2026-07-06 | JBU1086 | MCO → BUF | Jul 6, 13:25 UTC | Jul 7, 12:25 UTC | 23h 1m |
| 2026-07-05 | JBU2523 | DCA → MCO | Jul 5, 23:45 UTC | Jul 6, 01:35 UTC | 1h 50m |
| 2026-07-05 | JBU2324 | MCO → DCA | Jul 5, 18:00 UTC | Jul 5, 19:50 UTC | 1h 50m |
| 2026-07-05 | JBU1406 | MCO → MCO | Jul 5, 09:25 UTC | Jul 5, 15:20 UTC | 5h 55m |
| 2026-07-04 | JBU1286 | PIT → BOS | Jul 4, 13:21 UTC | Jul 5, 11:05 UTC | 21h 44m |
| 2026-07-04 | JBU506 | BNA → BOS | Jul 4, 02:43 UTC | Jul 5, 00:45 UTC | 22h 2m |
| 2026-07-03 | JBU507 | BOS → BNA | Jul 3, 22:48 UTC | Jul 4, 20:45 UTC | 21h 57m |
| 2026-07-03 | JBU1151 | ACK → BOS | Jul 3, 19:45 UTC | Jul 4, 18:45 UTC | 23h 0m |
| 2026-07-03 | JBU716 | BUF → BOS | Jul 3, 09:35 UTC | Jul 3, 10:40 UTC | 1h 5m |
| 2026-07-03 | JBU716 | BUF → BOS | Jul 3, 09:35 UTC | Jul 4, 08:45 UTC | 23h 10m |
| 2026-07-03 | JBU715 | - | Jul 3, 02:45 UTC | Jul 3, 03:50 UTC | 1h 5m |
| 2026-07-02 | JBU394A | - | Jul 2, 20:15 UTC | Jul 2, 23:45 UTC | 3h 30m |
| 2026-07-02 | JBU793 | - | Jul 2, 15:05 UTC | Jul 2, 19:05 UTC | 4h 0m |
| 2026-07-01 | JBU818 | JFK → BOS | Jul 1, 21:50 UTC | Jul 1, 22:55 UTC | 1h 5m |
| 2026-07-01 | JBU818 | JFK → BOS | Jul 1, 21:47 UTC | Jul 2, 20:45 UTC | 22h 58m |
| 2026-07-01 | JBU176 | MSY → JFK | Jul 1, 17:05 UTC | Jul 1, 19:50 UTC | 2h 45m |
| 2026-07-01 | JBU75 | JFK → MSY | Jul 1, 13:20 UTC | Jul 1, 15:50 UTC | 2h 30m |
| 2026-07-01 | JBU1419 | - | Jul 1, 10:10 UTC | Jul 1, 11:30 UTC | 1h 20m |
| 2026-07-01 | JBU1337 | BOS → DTW | Jul 1, 02:10 UTC | Jul 1, 03:45 UTC | 1h 35m |
| 2026-06-30 | JBU1814 | - | Jun 30, 23:25 UTC | Jul 1, 00:40 UTC | 1h 15m |
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 N3260J page for operator, model, and routing details .