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