sensors Mode-S transponder
A387F0
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N3267J · operated by JETBLUE AIRWAYS CORP
- Hex
- A387F0
- Octal
- 50703760
- Decimal
- 10,717,168
- Country
- US
- Tail
- N3267J
- Type
- BCS3
- Flights observed
- 298
- Distinct callsigns
- 20
- Country
- US
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address A387F0 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 |
|---|---|---|---|
| JBU872 | JetBlue Airways | 9 | 2026-06-06 |
| JBU272 | JetBlue Airways | 9 | 2026-06-10 |
| JBU2272 | JetBlue Airways | 9 | 2026-06-04 |
| JBU1071 | JetBlue Airways | 9 | 2026-06-10 |
| JBU471 | JetBlue Airways | 6 | 2026-06-10 |
| JBU899 | JetBlue Airways | 5 | 2026-06-04 |
| JBU359 | - | 4 | 2026-06-28 |
| JBU2271 | JetBlue Airways | 4 | 2026-05-31 |
| JBU1381 | - | 4 | 2026-07-06 |
| JBU98 | - | 3 | 2026-07-06 |
| JBU934 | - | 3 | 2026-06-24 |
| JBU519 | - | 3 | 2026-06-29 |
| JBU450 | JetBlue Airways | 3 | 2026-04-30 |
| JBU2283 | JetBlue Airways | 3 | 2026-05-09 |
| JBU2184 | JetBlue Airways | 3 | 2026-05-09 |
| JBU2064 | JetBlue Airways | 3 | 2026-04-26 |
| JBU1736 | - | 3 | 2026-07-13 |
| JBU1576 | JetBlue Airways | 3 | 2026-05-13 |
| JBU1520 | - | 3 | 2026-07-09 |
| JBU1502 | JetBlue Airways | 3 | 2026-04-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | JBU803 | JFK → SJU | Jul 13, 23:45 UTC | Jul 14, 18:00 UTC | 18h 16m |
| 2026-07-13 | JBU1736 | STI → JFK | Jul 13, 17:14 UTC | Jul 14, 16:00 UTC | 22h 47m |
| 2026-07-13 | JBU1736 | JFK → JFK | Jul 13, 12:30 UTC | Jul 13, 20:40 UTC | 8h 10m |
| 2026-07-12 | JBU520 | ATL → JFK | Jul 12, 23:20 UTC | Jul 13, 01:40 UTC | 2h 20m |
| 2026-07-12 | JBU97 | JFK → DEN | Jul 12, 02:24 UTC | Jul 13, 00:01 UTC | 21h 37m |
| 2026-07-11 | JBU1963 | HYA → JFK | Jul 11, 22:55 UTC | Jul 12, 22:00 UTC | 23h 6m |
| 2026-07-11 | JBU1964 | - | Jul 11, 18:35 UTC | Jul 11, 19:10 UTC | 35m |
| 2026-07-11 | JBU1964 | JFK → HYA | Jul 11, 18:32 UTC | Jul 12, 16:45 UTC | 22h 14m |
| 2026-07-11 | JBU2474 | - | Jul 11, 15:05 UTC | Jul 11, 16:30 UTC | 1h 25m |
| 2026-07-10 | JBU1273 | JFK → CHS | Jul 10, 16:45 UTC | Jul 11, 16:00 UTC | 23h 16m |
| 2026-07-10 | JBU1206 | ORD → JFK | Jul 10, 11:06 UTC | Jul 10, 18:20 UTC | 7h 14m |
| 2026-07-09 | JBU677 | - | Jul 9, 17:45 UTC | Jul 9, 19:40 UTC | 1h 55m |
| 2026-07-09 | JBU677 | JFK → JAX | Jul 9, 17:40 UTC | Jul 10, 12:50 UTC | 19h 10m |
| 2026-07-09 | JBU1520 | ATL → JFK | Jul 9, 14:35 UTC | Jul 9, 16:20 UTC | 1h 45m |
| 2026-07-08 | JBU1538 | JFK → MVY | Jul 8, 19:17 UTC | Jul 9, 18:00 UTC | 22h 43m |
| 2026-07-08 | JBU1154 | PBI → JFK | Jul 8, 15:02 UTC | Jul 9, 12:55 UTC | 21h 54m |
| 2026-07-08 | JBU953 | JFK → PBI | Jul 8, 10:48 UTC | Jul 8, 22:30 UTC | 11h 43m |
| 2026-07-07 | JBU2473 | JFK → CHS | Jul 7, 22:10 UTC | Jul 8, 22:00 UTC | 23h 51m |
| 2026-07-07 | JBU8082 | - | Jul 7, 17:25 UTC | Jul 7, 20:35 UTC | 3h 10m |
| 2026-07-07 | JBU8082 | IAH → JFK | Jul 7, 17:23 UTC | Jul 8, 16:00 UTC | 22h 38m |
| 2026-07-06 | JBU1381 | - | Jul 6, 14:40 UTC | Jul 6, 18:15 UTC | 3h 35m |
| 2026-07-06 | JBU98 | DEN → JFK | Jul 6, 07:00 UTC | Jul 6, 10:20 UTC | 3h 20m |
| 2026-07-05 | JBU8415 | SYR → MCO | Jul 5, 04:59 UTC | Jul 5, 19:40 UTC | 14h 41m |
| 2026-07-04 | JBU638 | - | Jul 4, 23:20 UTC | Jul 5, 03:00 UTC | 3h 40m |
| 2026-07-04 | JBU638 | AUS → BOS | Jul 4, 23:19 UTC | Jul 5, 19:40 UTC | 20h 21m |
| 2026-07-04 | JBU639 | - | Jul 4, 18:10 UTC | Jul 4, 22:05 UTC | 3h 55m |
| 2026-07-04 | JBU2230 | - | Jul 4, 14:25 UTC | Jul 4, 16:20 UTC | 1h 55m |
| 2026-07-04 | JBU2229 | BOS → MKE | Jul 4, 11:25 UTC | Jul 4, 13:25 UTC | 2h 0m |
| 2026-07-04 | JBU1318 | JFK → BOS | Jul 4, 04:50 UTC | Jul 4, 05:25 UTC | 35m |
| 2026-07-04 | JBU201 | BUF → JFK | Jul 4, 01:55 UTC | Jul 4, 03:00 UTC | 1h 5m |
| 2026-07-03 | JBU1202 | JFK → BUF | Jul 3, 22:10 UTC | Jul 3, 23:15 UTC | 1h 5m |
| 2026-07-03 | JBU1382 | - | Jul 3, 17:25 UTC | Jul 3, 20:35 UTC | 3h 10m |
| 2026-07-03 | JBU1381 | - | Jul 3, 13:10 UTC | Jul 3, 16:10 UTC | 3h 0m |
| 2026-07-03 | JBU1198 | PIT → JFK | Jul 3, 09:35 UTC | Jul 3, 10:40 UTC | 1h 5m |
| 2026-07-03 | JBU1195 | - | Jul 3, 03:00 UTC | Jul 3, 04:00 UTC | 1h 0m |
| 2026-07-02 | JBU1498 | - | Jul 2, 21:15 UTC | Jul 3, 00:50 UTC | 3h 35m |
| 2026-07-02 | JBU1497 | JFK → DEN | Jul 2, 15:05 UTC | Jul 2, 18:45 UTC | 3h 40m |
| 2026-07-02 | JBU854 | - | Jul 2, 10:55 UTC | Jul 2, 13:00 UTC | 2h 5m |
| 2026-06-30 | JBU1054 | PBI → JFK | Jun 30, 18:08 UTC | Jul 1, 01:35 UTC | 7h 28m |
| 2026-06-30 | JBU21 | BOS → PBI | Jun 30, 13:15 UTC | Jul 1, 01:35 UTC | 12h 21m |
| 2026-06-30 | JBU374 | SYR → BOS | Jun 30, 10:56 UTC | Jul 1, 01:35 UTC | 14h 40m |
| 2026-06-29 | JBU22 | - | Jun 29, 21:50 UTC | Jun 29, 22:00 UTC | 10m |
| 2026-06-29 | JBU53 | - | Jun 29, 17:49 UTC | Jun 29, 20:04 UTC | 2h 15m |
| 2026-06-29 | JBU53 | JFK → PBI | Jun 29, 17:45 UTC | Jun 30, 15:55 UTC | 22h 11m |
| 2026-06-29 | JBU1520 | ATL → JFK | Jun 29, 14:04 UTC | Jun 29, 16:04 UTC | 2h 0m |
| 2026-06-29 | JBU519 | JFK → ATL | Jun 29, 10:50 UTC | Jun 29, 12:34 UTC | 1h 45m |
| 2026-06-29 | JBU201 | - | Jun 29, 00:20 UTC | Jun 29, 01:14 UTC | 55m |
| 2026-06-28 | JBU359 | BUR → JFK | Jun 28, 04:44 UTC | Jun 28, 09:25 UTC | 4h 40m |
| 2026-06-28 | JBU359 | BUR → JFK | Jun 28, 04:44 UTC | Jun 29, 01:14 UTC | 20h 31m |
| 2026-06-27 | JBU358 | BUR → JFK | Jun 27, 21:40 UTC | Jun 28, 03:19 UTC | 5h 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 N3267J page for operator, model, and routing details .