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