Not currently tracked · last seen 1d ago
- Flights observed
- 125 showing last 50
- Avg flight time
- 1h 12m
- Typical route
- GYR → GYR
- Last seen
- 1d ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-13 | GYR → GYR | Jul 13, 16:30 UTC | Jul 13, 18:50 UTC | 2h 20m |
| 2026-07-13 | - | Jul 13, 14:45 UTC | Jul 13, 15:15 UTC | 30m |
| 2026-07-13 | GYR → BXK | Jul 13, 12:35 UTC | Jul 13, 14:15 UTC | 1h 40m |
| 2026-07-12 | GYR → GYR | Jul 12, 23:25 UTC | Jul 13, 00:55 UTC | 1h 30m |
| 2026-07-12 | - | Jul 12, 21:10 UTC | Jul 12, 22:10 UTC | 1h 0m |
| 2026-07-11 | GYR → GYR | Jul 11, 18:25 UTC | Jul 11, 19:50 UTC | 1h 25m |
| 2026-07-11 | GYR → GYR | Jul 11, 15:35 UTC | Jul 11, 17:30 UTC | 1h 55m |
| 2026-07-11 | GYR → GYR | Jul 11, 01:25 UTC | Jul 11, 03:15 UTC | 1h 50m |
| 2026-07-10 | - | Jul 10, 18:45 UTC | Jul 10, 20:50 UTC | 2h 5m |
| 2026-07-10 | GYR → GYR | Jul 10, 18:30 UTC | Jul 10, 18:40 UTC | 10m |
| 2026-07-10 | GYR → GYR | Jul 10, 15:55 UTC | Jul 10, 17:30 UTC | 1h 35m |
| 2026-07-10 | GYR → GYR | Jul 10, 15:40 UTC | Jul 10, 15:50 UTC | 10m |
| 2026-07-10 | GYR → GYR | Jul 10, 12:45 UTC | Jul 10, 14:30 UTC | 1h 45m |
| 2026-07-10 | - | Jul 10, 04:20 UTC | Jul 10, 04:55 UTC | 35m |
| 2026-07-10 | GYR → GYR | Jul 10, 03:45 UTC | Jul 10, 04:15 UTC | 30m |
| 2026-07-09 | GYR → GYR | Jul 9, 23:10 UTC | Jul 10, 00:50 UTC | 1h 40m |
| 2026-07-09 | - | Jul 9, 20:30 UTC | Jul 9, 20:35 UTC | 5m |
| 2026-07-09 | GYR → GYR | Jul 9, 18:45 UTC | Jul 9, 20:25 UTC | 1h 40m |
| 2026-07-09 | - | Jul 9, 15:35 UTC | Jul 9, 16:10 UTC | 35m |
| 2026-07-09 | GYR → GYR | Jul 9, 12:35 UTC | Jul 9, 14:30 UTC | 1h 55m |
| 2026-07-07 | GYR → GYR | Jul 7, 15:25 UTC | Jul 7, 17:10 UTC | 1h 45m |
| 2026-07-07 | GYR → GYR | Jul 7, 12:40 UTC | Jul 7, 14:30 UTC | 1h 50m |
| 2026-07-06 | GYR → GYR | Jul 6, 21:20 UTC | Jul 6, 22:20 UTC | 1h 0m |
| 2026-07-06 | GYR → GYR | Jul 6, 15:20 UTC | Jul 6, 16:25 UTC | 1h 5m |
| 2026-07-02 | GYR → GYR | Jul 2, 16:10 UTC | Jul 2, 17:45 UTC | 1h 35m |
| 2026-07-02 | - | Jul 2, 04:50 UTC | Jul 2, 05:30 UTC | 40m |
| 2026-07-02 | - | Jul 2, 03:20 UTC | Jul 2, 04:00 UTC | 40m |
| 2026-07-02 | - | Jul 2, 02:30 UTC | Jul 2, 03:10 UTC | 40m |
| 2026-07-02 | - | Jul 2, 01:20 UTC | Jul 2, 02:00 UTC | 40m |
| 2026-07-01 | GYR → GYR | Jul 1, 17:35 UTC | Jul 1, 19:50 UTC | 2h 15m |
| 2026-07-01 | - | Jul 1, 04:15 UTC | Jul 1, 05:10 UTC | 55m |
| 2026-07-01 | - | Jul 1, 01:10 UTC | Jul 1, 01:55 UTC | 45m |
| 2026-06-30 | GYR → GYR | Jun 30, 22:20 UTC | Jul 1, 00:00 UTC | 1h 40m |
| 2026-06-27 | GYR → GYR | Jun 27, 15:45 UTC | Jun 27, 17:04 UTC | 1h 20m |
| 2026-06-27 | - | Jun 27, 12:29 UTC | Jun 27, 14:25 UTC | 1h 55m |
| 2026-06-26 | - | Jun 26, 03:50 UTC | Jun 26, 05:50 UTC | 2h 0m |
| 2026-06-26 | - | Jun 26, 03:05 UTC | Jun 26, 03:45 UTC | 40m |
| 2026-06-26 | - | Jun 26, 01:54 UTC | Jun 26, 02:30 UTC | 35m |
| 2026-06-25 | - | Jun 25, 22:24 UTC | Jun 25, 23:44 UTC | 1h 20m |
| 2026-06-25 | GYR → GYR | Jun 25, 22:14 UTC | Jun 25, 22:20 UTC | 5m |
| 2026-06-25 | GYR → GYR | Jun 25, 18:19 UTC | Jun 25, 19:20 UTC | 1h 0m |
| 2026-06-23 | GYR → GYR | Jun 23, 13:09 UTC | Jun 23, 13:59 UTC | 50m |
| 2026-06-22 | GYR → GYR | Jun 22, 12:49 UTC | Jun 22, 14:34 UTC | 1h 45m |
| 2026-06-22 | BXK → GYR | Jun 22, 04:24 UTC | Jun 22, 04:44 UTC | 20m |
| 2026-06-22 | GYR → BXK | Jun 22, 03:54 UTC | Jun 22, 04:09 UTC | 15m |
| 2026-06-22 | GYR → GYR | Jun 22, 00:44 UTC | Jun 22, 02:40 UTC | 1h 55m |
| 2026-06-21 | GYR → GYR | Jun 21, 15:59 UTC | Jun 21, 16:44 UTC | 45m |
| 2026-06-21 | GYR → GYR | Jun 21, 13:34 UTC | Jun 21, 14:34 UTC | 1h 0m |
| 2026-06-20 | GYR → GYR | Jun 20, 12:39 UTC | Jun 20, 14:35 UTC | 1h 55m |
| 2026-06-19 | GYR → GYR | Jun 19, 20:40 UTC | Jun 19, 22:09 UTC | 1h 30m |
Specifications
| Registration | N386AV |
| Operator | PIPER AIRCRAFT INC |
| Mode-S code | A471A8 · 51070650 (octal) |
Looking for transponder-level data? View the Mode-S A471A8 page for country allocation, callsign history, and ADS-B signal details.
N386AV frequently asked
Who operates N386AV?
N386AV is operated by PIPER AIRCRAFT INC.
What is the Mode-S transponder code for N386AV?
N386AV broadcasts on Mode-S (ICAO 24-bit) address A471A8 (octal 51070650). View the transponder page.
What route does N386AV typically fly?
N386AV most frequently flies between GYR and GYR based on observed flights.
Where is N386AV right now?
N386AV is not currently being tracked; last seen 1d ago.