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,249
- Longest contact
- 1 h 1 min
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| FGYPQ | route not resolved | 19 Feb 2018, 08:2519 Feb 2018 | 19 Feb 2018, 09:03 | 26,025 ft | no position received |
| FGYPQ | route not resolved | 7 Feb 2018, 07:437 Feb 2018 | 7 Feb 2018, 08:04 | 22,025 ft | no position received |
| FGYPQ | route not resolved | 2 Feb 2018, 16:242 Feb 2018 | 2 Feb 2018, 16:42 | 12,225 ft | no position received |
| FGYPQ | route not resolved | 1 Feb 2018, 08:331 Feb 2018 | 1 Feb 2018, 08:49 | 25,025 ft | no position received |
| FGYPQ | route not resolved | 24 Jan 2018, 18:4624 Jan 2018 | 24 Jan 2018, 18:49 | 18,025 ft | no position received |
| FGYPQ | route not resolved | 23 Jan 2018, 19:4823 Jan 2018 | 23 Jan 2018, 20:40 | 9,675 ft | no position received |
| FGYPQ | route not resolved | 22 Jan 2018, 14:1422 Jan 2018 | 22 Jan 2018, 14:34 | 24,025 ft | no position received |
| FGYPQ | route not resolved | 20 Jan 2018, 12:5220 Jan 2018 | 20 Jan 2018, 13:05 | 10,025 ft | no position received |
| FGYPQ | route not resolved | 20 Jan 2018, 09:3720 Jan 2018 | 20 Jan 2018, 09:50 | 19,025 ft | no position received |
| FGYPQ | route not resolved | 18 Dec 2017, 16:1818 Dec 2017 | 18 Dec 2017, 16:35 | 13,350 ft | no position received |
| FGYPQ | route not resolved | 15 Dec 2017, 17:1815 Dec 2017 | 15 Dec 2017, 17:43 | 16,775 ft | no position received |
| FGYPQ | route not resolved | 5 Dec 2017, 13:415 Dec 2017 | 5 Dec 2017, 13:46 | 7,375 ft | no position received |
| FGYPQ | route not resolved | 3 Dec 2017, 15:423 Dec 2017 | 3 Dec 2017, 16:00 | 27,025 ft | no position received |
| FGYPQ | route not resolved | 26 Nov 2017, 15:2026 Nov 2017 | 26 Nov 2017, 15:46 | 12,600 ft | no position received |
| FGYPQ | route not resolved | 24 Nov 2017, 17:2424 Nov 2017 | 24 Nov 2017, 17:46 | 16,400 ft | no position received |
| FGYPQ | route not resolved | 20 Nov 2017, 15:2520 Nov 2017 | 20 Nov 2017, 15:29 | 24,025 ft | no position received |
| FGYPQ | route not resolved | 12 Nov 2017, 14:5712 Nov 2017 | 12 Nov 2017, 15:49 | 16,075 ft | no position received |
| FGYPQ | route not resolved | 10 Nov 2017, 17:2910 Nov 2017 | 10 Nov 2017, 18:06 | 18,825 ft | no position received |
| FGYPQ | route not resolved | 3 Nov 2017, 16:423 Nov 2017 | 3 Nov 2017, 16:52 | 13,875 ft | no position received |
| FGYPQ | route not resolved | 2 Nov 2017, 11:062 Nov 2017 | 2 Nov 2017, 11:31 | 16,350 ft | no position received |
| FGYPQ | route not resolved | 22 Oct 2017, 16:0222 Oct 2017 | 22 Oct 2017, 16:19 | 14,625 ft | no position received |
| FGYPQ | route not resolved | 20 Oct 2017, 18:2620 Oct 2017 | 20 Oct 2017, 18:54 | 15,975 ft | no position received |
| FGYPQ | route not resolved | 18 Oct 2017, 18:1718 Oct 2017 | 18 Oct 2017, 18:49 | 11,050 ft | no position received |
| FGYPQ | route not resolved | 18 Oct 2017, 07:4318 Oct 2017 | 18 Oct 2017, 08:16 | 21,750 ft | no position received |
| FGYPQ | route not resolved | 11 Oct 2017, 18:5311 Oct 2017 | 11 Oct 2017, 19:10 | 2,130 ft | no position received |
