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,540 of 57,080
- Longest contact
- 0 h 48 min
Observed callsigns
HOP (365 contacts, 2016-2019) · AFR (7 contacts, 2017-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 |
|---|---|---|---|---|---|
| not transmitted | route not resolved | 13 Jan 2017, 14:3113 Jan 2017 | 13 Jan 2017, 14:34 | 11,150 ft | no position received |
| HOP52TQ | route not resolved | 13 Jan 2017, 09:0213 Jan 2017 | 13 Jan 2017, 09:12 | 15,025 ft | no position received |
| HOP432G | route not resolved | 13 Jan 2017, 07:2413 Jan 2017 | 13 Jan 2017, 08:03 | 5,925 ft | no position received |
| HOP4328 | route not resolved | 12 Jan 2017, 20:3712 Jan 2017 | 12 Jan 2017, 21:10 | 20,000 ft | no position received |
| HOP53AE | route not resolved | 12 Jan 2017, 14:2212 Jan 2017 | 12 Jan 2017, 14:29 | 7,325 ft | no position received |
| HOP52TQ | route not resolved | 12 Jan 2017, 08:5812 Jan 2017 | 12 Jan 2017, 09:10 | 29,000 ft | no position received |
| HOP432G | route not resolved | 12 Jan 2017, 06:5612 Jan 2017 | 12 Jan 2017, 07:26 | 8,450 ft | no position received |
| HOP4328 | route not resolved | 11 Jan 2017, 20:2011 Jan 2017 | 11 Jan 2017, 21:02 | 20,025 ft | no position received |
| HOP57AE | route not resolved | 11 Jan 2017, 18:2711 Jan 2017 | 11 Jan 2017, 18:34 | 10,000 ft | no position received |
| HOP40RK | route not resolved | 11 Jan 2017, 15:5411 Jan 2017 | 11 Jan 2017, 16:02 | 15,000 ft | no position received |
| HOP53AE | route not resolved | 11 Jan 2017, 14:3511 Jan 2017 | 11 Jan 2017, 14:38 | 9,675 ft | no position received |
| HOP52TQ | route not resolved | 11 Jan 2017, 09:2011 Jan 2017 | 11 Jan 2017, 09:33 | 17,025 ft | no position received |
| HOP71SC | route not resolved | 11 Jan 2017, 07:5411 Jan 2017 | 11 Jan 2017, 08:01 | 11,325 ft | no position received |
| not transmitted | route not resolved | 10 Jan 2017, 19:0010 Jan 2017 | 10 Jan 2017, 19:01 | 12,775 ft | no position received |
| HOP83AJ | route not resolved | 10 Jan 2017, 14:2910 Jan 2017 | 10 Jan 2017, 14:36 | 11,400 ft | no position received |
| HOP82JC | route not resolved | 10 Jan 2017, 10:0010 Jan 2017 | 10 Jan 2017, 10:11 | 37,975 ft | no position received |
| HOP57KS | LFBZ > LFLL | 10 Jan 2017, 07:4510 Jan 2017 | 10 Jan 2017, 07:55 | 10,100 ft | no position received |
| HOP47KT | route not resolved | 9 Jan 2017, 18:279 Jan 2017 | 9 Jan 2017, 18:58 | 6,225 ft | no position received |
| HOP46YT | route not resolved | 9 Jan 2017, 16:399 Jan 2017 | 9 Jan 2017, 17:08 | 18,025 ft | no position received |
| HOP53AE | route not resolved | 9 Jan 2017, 14:259 Jan 2017 | 9 Jan 2017, 14:32 | 8,900 ft | no position received |
| HOP52TQ | route not resolved | 9 Jan 2017, 09:339 Jan 2017 | 9 Jan 2017, 09:48 | 19,025 ft | no position received |
| HOP432G | route not resolved | 9 Jan 2017, 07:539 Jan 2017 | 9 Jan 2017, 08:23 | 7,850 ft | no position received |
| HOP4328 | route not resolved | 8 Jan 2017, 21:428 Jan 2017 | 8 Jan 2017, 22:21 | 20,000 ft | no position received |
| HOP9241 | route not resolved | 8 Jan 2017, 02:548 Jan 2017 | 8 Jan 2017, 03:03 | 9,675 ft | no position received |
| not transmitted | route not resolved | 4 Jan 2017, 20:244 Jan 2017 | 4 Jan 2017, 20:28 | 17,000 ft | no position received |
