Back to the log
Aircraft
F-GPYF
Regularnot seen for 7 years
The station's story
Address not received since 2 Jan 2019. The marker states the absence, it does not say why.
- Cumulative contact time
- 125 h
- Distinct days
- 146
- Highest captured altitude
- 34,825 ft
- 4 corrupted frame(s) excluded from this maximum
- Discovery rank
- #5,538 of 57,065
- Longest contact
- 0 h 48 min
Observed callsigns
HOP (365 contacts, 2016-2019) · AFR (7 contacts, 2017-2018)
Operator as per the registry of 21.07.2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| HOP8000 | EDDS > LFPG | 2 Jan 2019, 16:132 Jan 2019 | 2 Jan 2019, 16:20 | 18,000 ft | no position received |
| HOP205M | route not resolved | 30 Sept 2018, 19:0830 Sept 2018 | 30 Sept 2018, 19:35 | 10,725 ft | no position received |
| HOP636Q | route not resolved | 30 Sept 2018, 16:1330 Sept 2018 | 30 Sept 2018, 16:51 | 20,000 ft | no position received |
| HOP8621 | route not resolved | 29 Sept 2018, 12:5229 Sept 2018 | 29 Sept 2018, 13:22 | 6,850 ft | no position received |
| not transmitted | route not resolved | 27 Jun 2018, 13:1727 Jun 2018 | 27 Jun 2018, 13:17 | 18,000 ft | no position received |
| AFR7331 | route not resolved | 21 Feb 2018, 06:5421 Feb 2018 | 21 Feb 2018, 07:09 | 18,000 ft | no position received |
| not transmitted | route not resolved | 8 Feb 2018, 16:378 Feb 2018 | 8 Feb 2018, 16:37 | not transmitted | no position received |
| not transmitted | route not resolved | 8 Feb 2018, 14:438 Feb 2018 | 8 Feb 2018, 14:44 | 11,350 ft | no position received |
| HOP53AR | route not resolved | 8 Feb 2018, 11:108 Feb 2018 | 8 Feb 2018, 11:22 | 17,000 ft | no position received |
| HOP41VY | route not resolved | 8 Feb 2018, 09:118 Feb 2018 | 8 Feb 2018, 09:42 | 8,550 ft | no position received |
| HOP65NZ | route not resolved | 7 Feb 2018, 22:477 Feb 2018 | 7 Feb 2018, 23:14 | 18,000 ft | no position received |
| HOP53AR | route not resolved | 7 Feb 2018, 09:577 Feb 2018 | 7 Feb 2018, 10:09 | 15,000 ft | no position received |
| HOP41VY | route not resolved | 7 Feb 2018, 08:217 Feb 2018 | 7 Feb 2018, 08:53 | 7,000 ft | no position received |
| HOP65NZ | route not resolved | 6 Feb 2018, 21:476 Feb 2018 | 6 Feb 2018, 22:05 | 18,000 ft | no position received |
| HOP8810 | route not resolved | 13 Jan 2018, 13:0113 Jan 2018 | 13 Jan 2018, 13:06 | 17,000 ft | no position received |
| HOP57AE | route not resolved | 12 Jan 2018, 18:4612 Jan 2018 | 12 Jan 2018, 18:47 | 8,375 ft | no position received |
| HOP40RK | route not resolved | 12 Jan 2018, 16:0012 Jan 2018 | 12 Jan 2018, 16:10 | 17,000 ft | no position received |
| not transmitted | route not resolved | 12 Jan 2018, 14:4912 Jan 2018 | 12 Jan 2018, 14:52 | 9,125 ft | no position received |
| HOP8600 | route not resolved | 6 Dec 2017, 09:036 Dec 2017 | 6 Dec 2017, 09:39 | 24,000 ft | no position received |
| not transmitted | route not resolved | 6 Dec 2017, 07:566 Dec 2017 | 6 Dec 2017, 07:58 | 9,125 ft | no position received |
| HOP58RK | route not resolved | 5 Dec 2017, 20:255 Dec 2017 | 5 Dec 2017, 20:39 | 15,000 ft | no position received |
| not transmitted | route not resolved | 4 Dec 2017, 20:084 Dec 2017 | 4 Dec 2017, 20:09 | 14,625 ft | no position received |
| not transmitted | route not resolved | 30 Nov 2017, 09:1230 Nov 2017 | 30 Nov 2017, 09:12 | 16,000 ft | no position received |
| HOP8100 | route not resolved | 29 Nov 2017, 11:3829 Nov 2017 | 29 Nov 2017, 11:39 | 17,000 ft | no position received |
| HOP71SC | route not resolved | 27 Nov 2017, 07:3827 Nov 2017 | 27 Nov 2017, 07:48 | 7,225 ft | no position received |
