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