Back to the log
Aircraft
F-GPYO
Regularnot seen for 8 years
The station's story
Address not received since 16 Apr 2018. The marker states the absence, it does not say why.
- Cumulative contact time
- 124 h
- Distinct days
- 140
- Highest captured altitude
- 31,800 ft
- 2 corrupted frame(s) excluded from this maximum
- Discovery rank
- #9,103 of 57,441
- Longest contact
- 0 h 52 min
Observed callsigns
HOP (326 contacts, 2016-2018)
Operator as per the registry of 29 Jul 2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| HOP52TQ | route not resolved | 15 Sept 2016, 09:1815 Sept 2016 | 15 Sept 2016, 09:35 | 15,050 ft | no position received |
| HOP432G | route not resolved | 15 Sept 2016, 06:5915 Sept 2016 | 15 Sept 2016, 07:32 | 9,775 ft | no position received |
| HOP4328 | route not resolved | 14 Sept 2016, 20:2214 Sept 2016 | 14 Sept 2016, 20:48 | 18,050 ft | no position received |
| HOP57AE | route not resolved | 14 Sept 2016, 18:4014 Sept 2016 | 14 Sept 2016, 18:44 | 10,525 ft | no position received |
| HOP40RK | route not resolved | 14 Sept 2016, 15:4814 Sept 2016 | 14 Sept 2016, 15:56 | 13,650 ft | no position received |
| HOP53AE | route not resolved | 14 Sept 2016, 14:1814 Sept 2016 | 14 Sept 2016, 14:26 | 10,000 ft | no position received |
| HOP52TQ | route not resolved | 14 Sept 2016, 09:2314 Sept 2016 | 14 Sept 2016, 09:40 | 17,000 ft | no position received |
| not transmitted | route not resolved | 14 Sept 2016, 07:2914 Sept 2016 | 14 Sept 2016, 07:29 | 19,050 ft | no position received |
| HOP48YT | route not resolved | 13 Sept 2016, 20:5413 Sept 2016 | 13 Sept 2016, 21:18 | 18,050 ft | no position received |
| HOP47KT | route not resolved | 13 Sept 2016, 18:2113 Sept 2016 | 13 Sept 2016, 18:31 | 19,000 ft | no position received |
| HOP46YT | route not resolved | 13 Sept 2016, 16:0213 Sept 2016 | 13 Sept 2016, 16:32 | 18,050 ft | no position received |
| HOP53AE | route not resolved | 13 Sept 2016, 14:1813 Sept 2016 | 13 Sept 2016, 14:27 | 10,475 ft | no position received |
| HOP52TQ | route not resolved | 13 Sept 2016, 08:5813 Sept 2016 | 13 Sept 2016, 09:13 | 15,000 ft | no position received |
| HOP432G | route not resolved | 13 Sept 2016, 06:5213 Sept 2016 | 13 Sept 2016, 07:26 | 8,475 ft | no position received |
| HOP4328 | route not resolved | 12 Sept 2016, 20:2912 Sept 2016 | 12 Sept 2016, 21:01 | 18,000 ft | no position received |
| HOP57AE | route not resolved | 12 Sept 2016, 18:2712 Sept 2016 | 12 Sept 2016, 18:38 | 10,050 ft | no position received |
| HOP40RK | route not resolved | 12 Sept 2016, 16:0512 Sept 2016 | 12 Sept 2016, 16:15 | 15,000 ft | no position received |
| HOP53AE | route not resolved | 12 Sept 2016, 14:1912 Sept 2016 | 12 Sept 2016, 14:28 | 9,900 ft | no position received |
| HOP52TQ | route not resolved | 12 Sept 2016, 09:1412 Sept 2016 | 12 Sept 2016, 09:25 | 15,000 ft | no position received |
| HOP432G | route not resolved | 12 Sept 2016, 07:0912 Sept 2016 | 12 Sept 2016, 07:53 | 8,625 ft | no position received |
| HOP4328 | route not resolved | 11 Sept 2016, 20:2411 Sept 2016 | 11 Sept 2016, 20:48 | 18,025 ft | no position received |
| HOP537X | route not resolved | 11 Sept 2016, 18:3911 Sept 2016 | 11 Sept 2016, 18:55 | 7,675 ft | no position received |
| HOP536J | route not resolved | 11 Sept 2016, 15:3311 Sept 2016 | 11 Sept 2016, 15:56 | 22,350 ft | no position received |
| HOP432G | route not resolved | 10 Sept 2016, 08:0510 Sept 2016 | 10 Sept 2016, 08:41 | 4,900 ft | no position received |
| HOP4328 | route not resolved | 9 Sept 2016, 21:059 Sept 2016 | 9 Sept 2016, 21:33 | 18,025 ft | no position received |
