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,065
- 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 |
|---|---|---|---|---|---|
| HOP40RK | route not resolved | 9 Sept 2016, 15:519 Sept 2016 | 9 Sept 2016, 16:08 | 17,000 ft | no position received |
| not transmitted | route not resolved | 9 Sept 2016, 14:129 Sept 2016 | 9 Sept 2016, 14:18 | 7,675 ft | no position received |
| HOP532J | route not resolved | 9 Sept 2016, 08:559 Sept 2016 | 9 Sept 2016, 09:18 | 21,000 ft | no position received |
| HOP432G | route not resolved | 9 Sept 2016, 06:579 Sept 2016 | 9 Sept 2016, 07:34 | 5,975 ft | no position received |
| HOP4328 | route not resolved | 8 Sept 2016, 20:198 Sept 2016 | 8 Sept 2016, 20:49 | 18,000 ft | no position received |
| not transmitted | route not resolved | 8 Sept 2016, 18:358 Sept 2016 | 8 Sept 2016, 18:35 | not transmitted | no position received |
| HOP40RK | route not resolved | 8 Sept 2016, 15:448 Sept 2016 | 8 Sept 2016, 15:54 | 15,000 ft | no position received |
| not transmitted | route not resolved | 8 Sept 2016, 14:148 Sept 2016 | 8 Sept 2016, 14:14 | not transmitted | no position received |
| not transmitted | route not resolved | 8 Sept 2016, 09:118 Sept 2016 | 8 Sept 2016, 09:12 | 9,575 ft | no position received |
| HOP57AE | route not resolved | 7 Sept 2016, 18:347 Sept 2016 | 7 Sept 2016, 18:41 | 10,700 ft | no position received |
| HOP40RK | route not resolved | 7 Sept 2016, 15:547 Sept 2016 | 7 Sept 2016, 16:01 | 14,450 ft | no position received |
| not transmitted | route not resolved | 7 Sept 2016, 14:237 Sept 2016 | 7 Sept 2016, 14:28 | 8,875 ft | no position received |
| HOP52TQ | route not resolved | 7 Sept 2016, 09:077 Sept 2016 | 7 Sept 2016, 09:17 | 15,000 ft | no position received |
| not transmitted | route not resolved | 6 Sept 2016, 18:356 Sept 2016 | 6 Sept 2016, 18:37 | 10,975 ft | no position received |
| HOP40RK | route not resolved | 6 Sept 2016, 16:056 Sept 2016 | 6 Sept 2016, 16:21 | 17,025 ft | no position received |
| HOP52TQ | route not resolved | 6 Sept 2016, 09:066 Sept 2016 | 6 Sept 2016, 09:15 | 13,450 ft | no position received |
| HOP432G | route not resolved | 6 Sept 2016, 06:576 Sept 2016 | 6 Sept 2016, 07:30 | 5,000 ft | no position received |
| HOP4328 | route not resolved | 5 Sept 2016, 20:375 Sept 2016 | 5 Sept 2016, 21:01 | 18,000 ft | no position received |
| HOP40RK | route not resolved | 5 Sept 2016, 15:485 Sept 2016 | 5 Sept 2016, 16:01 | 15,000 ft | no position received |
| HOP52TQ | route not resolved | 5 Sept 2016, 08:585 Sept 2016 | 5 Sept 2016, 09:11 | 15,000 ft | no position received |
| HOP432G | route not resolved | 5 Sept 2016, 06:575 Sept 2016 | 5 Sept 2016, 07:33 | 4,950 ft | no position received |
| HOP4328 | route not resolved | 4 Sept 2016, 20:384 Sept 2016 | 4 Sept 2016, 21:10 | 18,000 ft | no position received |
| HOP432G | route not resolved | 3 Sept 2016, 07:483 Sept 2016 | 3 Sept 2016, 08:28 | 5,475 ft | no position received |
| HOP4328 | route not resolved | 2 Sept 2016, 20:212 Sept 2016 | 2 Sept 2016, 20:50 | 18,000 ft | no position received |
| HOP432G | route not resolved | 2 Sept 2016, 07:022 Sept 2016 | 2 Sept 2016, 07:40 | 5,125 ft | no position received |
