Back to the log
Aircraft
F-GPYD
Regularnot seen for 7 years
The station's story
Address not received since 6 Feb 2019. The marker states the absence, it does not say why.
- Cumulative contact time
- 171 h
- Distinct days
- 172
- Highest captured altitude
- 34,000 ft
- 2 corrupted frame(s) excluded from this maximum
- Discovery rank
- #7,790 of 57,142
- Longest contact
- 0 h 54 min
Observed callsigns
HOP (372 contacts, 2016-2019) · AFR (5 contacts, 2017-2018)
Operator as per the registry of 12 Aug 2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| HOP48YT | route not resolved | 4 Apr 2017, 20:124 Apr 2017 | 4 Apr 2017, 20:40 | 18,000 ft | no position received |
| HOP41VY | route not resolved | 4 Apr 2017, 06:574 Apr 2017 | 4 Apr 2017, 07:30 | 5,350 ft | no position received |
| HOP48YT | route not resolved | 3 Apr 2017, 20:183 Apr 2017 | 3 Apr 2017, 20:44 | 15,950 ft | no position received |
| not transmitted | route not resolved | 3 Apr 2017, 09:023 Apr 2017 | 3 Apr 2017, 09:02 | 15,200 ft | no position received |
| not transmitted | route not resolved | 31 Mar 2017, 08:5631 Mar 2017 | 31 Mar 2017, 08:58 | 10,150 ft | no position received |
| not transmitted | route not resolved | 30 Mar 2017, 20:0530 Mar 2017 | 30 Mar 2017, 20:05 | 16,000 ft | no position received |
| not transmitted | route not resolved | 30 Mar 2017, 09:0230 Mar 2017 | 30 Mar 2017, 09:10 | 11,375 ft | no position received |
| HOP41VY | route not resolved | 29 Mar 2017, 07:0029 Mar 2017 | 29 Mar 2017, 07:39 | 5,575 ft | no position received |
| HOP48YT | route not resolved | 28 Mar 2017, 20:3628 Mar 2017 | 28 Mar 2017, 21:03 | 17,650 ft | no position received |
| HOP8003 | route not resolved | 4 Dec 2016, 15:204 Dec 2016 | 4 Dec 2016, 15:24 | 19,000 ft | no position received |
| HOP73PD | route not resolved | 4 Dec 2016, 14:094 Dec 2016 | 4 Dec 2016, 14:18 | 8,825 ft | no position received |
| HOP432G | route not resolved | 3 Dec 2016, 07:583 Dec 2016 | 3 Dec 2016, 08:34 | 4,850 ft | no position received |
| HOP4328 | route not resolved | 2 Dec 2016, 20:232 Dec 2016 | 2 Dec 2016, 20:59 | 20,000 ft | no position received |
| not transmitted | route not resolved | 2 Dec 2016, 18:282 Dec 2016 | 2 Dec 2016, 18:30 | 9,850 ft | no position received |
| HOP40RK | route not resolved | 2 Dec 2016, 15:562 Dec 2016 | 2 Dec 2016, 16:09 | 15,000 ft | no position received |
| HOP53AE | route not resolved | 2 Dec 2016, 14:212 Dec 2016 | 2 Dec 2016, 14:27 | 10,625 ft | no position received |
| HOP52TQ | route not resolved | 2 Dec 2016, 09:132 Dec 2016 | 2 Dec 2016, 09:25 | 15,000 ft | no position received |
| HOP432G | route not resolved | 2 Dec 2016, 06:592 Dec 2016 | 2 Dec 2016, 07:31 | 6,425 ft | no position received |
| HOP4328 | route not resolved | 1 Dec 2016, 20:271 Dec 2016 | 1 Dec 2016, 21:00 | 20,000 ft | no position received |
| HOP511G | route not resolved | 1 Dec 2016, 09:431 Dec 2016 | 1 Dec 2016, 09:56 | 5,525 ft | no position received |
| HOP4518 | LFLL > LIPE | 30 Nov 2016, 21:5630 Nov 2016 | 30 Nov 2016, 22:18 | 21,000 ft | no position received |
| not transmitted | route not resolved | 30 Nov 2016, 20:2530 Nov 2016 | 30 Nov 2016, 20:33 | 8,175 ft | no position received |
| HOP40RK | route not resolved | 30 Nov 2016, 16:1030 Nov 2016 | 30 Nov 2016, 16:22 | 15,000 ft | no position received |
| not transmitted | route not resolved | 30 Nov 2016, 14:2330 Nov 2016 | 30 Nov 2016, 14:25 | 10,600 ft | no position received |
| HOP52TQ | route not resolved | 30 Nov 2016, 09:0230 Nov 2016 | 30 Nov 2016, 09:19 | 19,000 ft | no position received |
