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