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 | 26 Jun 2019, 17:5026 Jun 2019 | 26 Jun 2019, 18:22 | 19,050 ft | no position received |
| FGYPQ | route not resolved | 26 Jun 2019, 12:1726 Jun 2019 | 26 Jun 2019, 12:56 | 11,875 ft | no position received |
| FGYPQ | route not resolved | 25 Jun 2019, 06:1225 Jun 2019 | 25 Jun 2019, 06:45 | 25,000 ft | no position received |
| FGYPQ | route not resolved | 24 Jun 2019, 13:3424 Jun 2019 | 24 Jun 2019, 13:47 | 11,400 ft | no position received |
| FGYPQ | route not resolved | 22 Jun 2019, 16:5622 Jun 2019 | 22 Jun 2019, 17:16 | 16,675 ft | no position received |
| FGYPQ | route not resolved | 16 Jun 2019, 14:0316 Jun 2019 | 16 Jun 2019, 14:27 | 14,425 ft | no position received |
| FGYPQ | route not resolved | 7 Jun 2019, 10:067 Jun 2019 | 7 Jun 2019, 10:08 | 26,025 ft | no position received |
| not transmitted | route not resolved | 5 Jun 2019, 17:535 Jun 2019 | 5 Jun 2019, 17:53 | not transmitted | no position received |
| FGYPQ | route not resolved | 27 May 2019, 07:5327 May 2019 | 27 May 2019, 08:19 | 25,025 ft | no position received |
| FGYPQ | route not resolved | 7 May 2019, 11:477 May 2019 | 7 May 2019, 11:59 | 12,875 ft | no position received |
| FGYPQ | route not resolved | 4 May 2019, 09:014 May 2019 | 4 May 2019, 09:05 | 19,025 ft | no position received |
| FGYPQ | route not resolved | 22 Apr 2019, 16:1122 Apr 2019 | 22 Apr 2019, 16:30 | 28,025 ft | no position received |
| FGYPQ | route not resolved | 19 Apr 2019, 16:5419 Apr 2019 | 19 Apr 2019, 17:12 | 10,800 ft | no position received |
| FGYPQ | route not resolved | 19 Apr 2019, 14:3919 Apr 2019 | 19 Apr 2019, 14:55 | 19,025 ft | no position received |
| FGYPQ | route not resolved | 13 Apr 2019, 13:1513 Apr 2019 | 13 Apr 2019, 13:23 | 10,275 ft | no position received |
| FGYPQ | route not resolved | 13 Apr 2019, 10:2213 Apr 2019 | 13 Apr 2019, 10:41 | 19,025 ft | no position received |
| FGYPQ | route not resolved | 12 Apr 2019, 19:4712 Apr 2019 | 12 Apr 2019, 20:28 | 13,225 ft | no position received |
| FGYPQ | route not resolved | 12 Apr 2019, 06:3612 Apr 2019 | 12 Apr 2019, 07:10 | 21,600 ft | no position received |
| not transmitted | route not resolved | 24 Mar 2019, 18:1424 Mar 2019 | 24 Mar 2019, 18:23 | 12,800 ft | no position received |
| FGYPQ | route not resolved | 22 Mar 2019, 17:3422 Mar 2019 | 22 Mar 2019, 17:51 | 19,050 ft | no position received |
| FGYPQ | route not resolved | 19 Mar 2019, 11:2619 Mar 2019 | 19 Mar 2019, 11:32 | 19,025 ft | no position received |
| FGYPQ | route not resolved | 17 Mar 2019, 16:2517 Mar 2019 | 17 Mar 2019, 16:34 | 12,125 ft | no position received |
| not transmitted | route not resolved | 28 Feb 2019, 06:5628 Feb 2019 | 28 Feb 2019, 07:02 | 19,000 ft | no position received |
| FGYPQ | route not resolved | 12 Feb 2019, 09:5712 Feb 2019 | 12 Feb 2019, 10:14 | 13,700 ft | no position received |
| FGYPQ | route not resolved | 8 Feb 2019, 10:588 Feb 2019 | 8 Feb 2019, 11:13 | 17,625 ft | no position received |
