Back to the log
Aircraft
F-GYPQ
Common
Identity resolved on 13 Aug 2026: the aircraft was too recent for the registry at the time of the first contact, on 7 Apr 2016. What this page shows comes from a later registry; each contact keeps what was known on the day it was heard.
The station's story
- Cumulative contact time
- 139 h
- Distinct days
- 318
- Highest captured altitude
- 35,000 ft
- 3 corrupted frame(s) excluded from this maximum
- Discovery rank
- #2,545 of 57,255
- Longest contact
- 1 h 1 min
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| FGYPQ | route not resolved | 8 May 2017, 18:198 May 2017 | 8 May 2017, 18:38 | 12,550 ft | no position received |
| FGYPQ | route not resolved | 29 Apr 2017, 19:2029 Apr 2017 | 29 Apr 2017, 19:31 | 11,525 ft | no position received |
| FGYPQ | route not resolved | 27 Apr 2017, 19:1127 Apr 2017 | 27 Apr 2017, 19:26 | 11,325 ft | no position received |
| FGYPQ | route not resolved | 26 Apr 2017, 19:0326 Apr 2017 | 26 Apr 2017, 19:24 | 16,950 ft | no position received |
| FGYPQ | route not resolved | 25 Apr 2017, 17:0025 Apr 2017 | 25 Apr 2017, 17:59 | 10,025 ft | no position received |
| FGYPQ | route not resolved | 20 Mar 2017, 08:3820 Mar 2017 | 20 Mar 2017, 09:23 | 28,025 ft | no position received |
| FGYPQ | route not resolved | 19 Mar 2017, 14:3519 Mar 2017 | 19 Mar 2017, 14:51 | 6,525 ft | no position received |
| FGYPQ | route not resolved | 19 Mar 2017, 11:1019 Mar 2017 | 19 Mar 2017, 11:30 | 18,375 ft | no position received |
| FGYPQ | route not resolved | 2 Mar 2017, 16:542 Mar 2017 | 2 Mar 2017, 17:20 | 9,000 ft | no position received |
| FGYPQ | route not resolved | 1 Mar 2017, 10:111 Mar 2017 | 1 Mar 2017, 10:46 | 26,050 ft | no position received |
| FGYPQ | route not resolved | 27 Feb 2017, 16:0927 Feb 2017 | 27 Feb 2017, 16:57 | 9,825 ft | no position received |
| FGYPQ | route not resolved | 28 Nov 2016, 07:5128 Nov 2016 | 28 Nov 2016, 08:29 | 26,950 ft | no position received |
| FGYPQ | route not resolved | 23 Nov 2016, 12:3723 Nov 2016 | 23 Nov 2016, 13:13 | 9,975 ft | no position received |
| FGYPQ | route not resolved | 22 Nov 2016, 17:2022 Nov 2016 | 22 Nov 2016, 17:48 | 22,000 ft | no position received |
| FGYPQ | route not resolved | 17 Nov 2016, 15:5617 Nov 2016 | 17 Nov 2016, 16:51 | 9,175 ft | no position received |
| FGYPQ | route not resolved | 17 Nov 2016, 07:2017 Nov 2016 | 17 Nov 2016, 08:08 | 26,000 ft | no position received |
| FGYPQ | route not resolved | 6 Nov 2016, 15:296 Nov 2016 | 6 Nov 2016, 16:11 | 9,825 ft | no position received |
| FGYPQ | route not resolved | 4 Nov 2016, 17:094 Nov 2016 | 4 Nov 2016, 17:34 | 16,850 ft | no position received |
| FGYPQ | route not resolved | 31 Oct 2016, 17:1431 Oct 2016 | 31 Oct 2016, 17:28 | 13,300 ft | no position received |
| FGYPQ | route not resolved | 29 Oct 2016, 09:0729 Oct 2016 | 29 Oct 2016, 09:38 | 18,000 ft | no position received |
| FGYPQ | route not resolved | 27 Oct 2016, 10:2027 Oct 2016 | 27 Oct 2016, 10:36 | 26,975 ft | no position received |
| FGYPQ | route not resolved | 26 Oct 2016, 15:2726 Oct 2016 | 26 Oct 2016, 16:06 | 9,100 ft | no position received |
| FGYPQ | route not resolved | 24 Oct 2016, 08:1524 Oct 2016 | 24 Oct 2016, 08:38 | 24,025 ft | no position received |
| FGYPQ | route not resolved | 23 Oct 2016, 15:3723 Oct 2016 | 23 Oct 2016, 16:21 | 10,075 ft | no position received |
| FGYPQ | route not resolved | 21 Oct 2016, 18:2121 Oct 2016 | 21 Oct 2016, 18:57 | 120,100 ft | no position received |
