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