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,241
- Longest contact
- 1 h 1 min
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| FGYPQ | route not resolved | 5 Feb 2020, 08:035 Feb 2020 | 5 Feb 2020, 08:35 | 20,025 ft | no position received |
| FGYPQ | route not resolved | 24 Jan 2020, 09:0924 Jan 2020 | 24 Jan 2020, 09:31 | 15,575 ft | no position received |
| not transmitted | route not resolved | 18 Dec 2019, 15:3818 Dec 2019 | 18 Dec 2019, 15:49 | 14,700 ft | no position received |
| FGYPQ | route not resolved | 18 Dec 2019, 09:0318 Dec 2019 | 18 Dec 2019, 09:21 | 18,025 ft | no position received |
| FGYPQ | route not resolved | 8 Dec 2019, 15:358 Dec 2019 | 8 Dec 2019, 15:58 | 25,975 ft | no position received |
| FGYPQ | route not resolved | 8 Dec 2019, 13:058 Dec 2019 | 8 Dec 2019, 13:35 | 14,675 ft | no position received |
| FGYPQ | route not resolved | 6 Dec 2019, 17:126 Dec 2019 | 6 Dec 2019, 17:29 | 14,025 ft | no position received |
| FGYPQ | route not resolved | 27 Nov 2019, 20:2227 Nov 2019 | 27 Nov 2019, 21:11 | 9,975 ft | no position received |
| FGYPQ | route not resolved | 24 Nov 2019, 15:1024 Nov 2019 | 24 Nov 2019, 15:33 | 14,650 ft | no position received |
| FGYPQ | route not resolved | 22 Nov 2019, 17:0622 Nov 2019 | 22 Nov 2019, 17:27 | 17,950 ft | no position received |
| FGYPQ | route not resolved | 19 Nov 2019, 18:0519 Nov 2019 | 19 Nov 2019, 18:14 | 10,000 ft | no position received |
| FGYPQ | route not resolved | 19 Nov 2019, 07:4519 Nov 2019 | 19 Nov 2019, 08:09 | 20,975 ft | no position received |
| FGYPQ | route not resolved | 11 Nov 2019, 07:4611 Nov 2019 | 11 Nov 2019, 08:08 | 25,025 ft | no position received |
| FGYPQ | route not resolved | 10 Nov 2019, 15:2510 Nov 2019 | 10 Nov 2019, 15:51 | 15,200 ft | no position received |
| FGYPQ | route not resolved | 20 Oct 2019, 15:2420 Oct 2019 | 20 Oct 2019, 16:14 | 9,400 ft | no position received |
| FGYPQ | route not resolved | 18 Oct 2019, 18:5318 Oct 2019 | 18 Oct 2019, 19:21 | 21,050 ft | no position received |
| FGYPQ | route not resolved | 18 Oct 2019, 16:5018 Oct 2019 | 18 Oct 2019, 16:56 | 17,150 ft | no position received |
| FGYPQ | route not resolved | 16 Oct 2019, 07:5416 Oct 2019 | 16 Oct 2019, 08:18 | 22,025 ft | no position received |
| FGYPQ | route not resolved | 15 Oct 2019, 08:1215 Oct 2019 | 15 Oct 2019, 08:14 | 26,025 ft | no position received |
| FGYPQ | route not resolved | 12 Sept 2019, 11:0512 Sept 2019 | 12 Sept 2019, 11:35 | 14,450 ft | no position received |
| FGYPQ | route not resolved | 11 Sept 2019, 04:2211 Sept 2019 | 11 Sept 2019, 04:41 | 24,025 ft | no position received |
| FGYPQ | route not resolved | 1 Sept 2019, 12:031 Sept 2019 | 1 Sept 2019, 12:17 | 18,700 ft | no position received |
| FGYPQ | route not resolved | 26 Aug 2019, 09:2926 Aug 2019 | 26 Aug 2019, 09:55 | 25,025 ft | no position received |
| FGYPQ | route not resolved | 3 Jul 2019, 06:303 Jul 2019 | 3 Jul 2019, 06:55 | 24,025 ft | no position received |
| FGYPQ | route not resolved | 27 Jun 2019, 17:5627 Jun 2019 | 27 Jun 2019, 18:07 | 19,025 ft | no position received |
