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,539 of 57,079
- 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 |
|---|---|---|---|---|---|
| HOP18CN | LFLL > LFBI | 2 Mar 2017, 20:072 Mar 2017 | 2 Mar 2017, 20:12 | 16,450 ft | no position received |
| not transmitted | route not resolved | 2 Mar 2017, 09:162 Mar 2017 | 2 Mar 2017, 09:18 | 15,025 ft | no position received |
| not transmitted | route not resolved | 26 Feb 2017, 20:2026 Feb 2017 | 26 Feb 2017, 20:22 | 16,025 ft | no position received |
| not transmitted | route not resolved | 23 Feb 2017, 20:0223 Feb 2017 | 23 Feb 2017, 20:03 | 16,000 ft | no position received |
| HOP18CN | LFLL > LFBI | 22 Feb 2017, 20:0222 Feb 2017 | 22 Feb 2017, 20:06 | 16,025 ft | no position received |
| not transmitted | route not resolved | 22 Feb 2017, 18:2322 Feb 2017 | 22 Feb 2017, 18:31 | 7,875 ft | no position received |
| HOP40RK | route not resolved | 22 Feb 2017, 15:5422 Feb 2017 | 22 Feb 2017, 16:05 | 15,025 ft | no position received |
| HOP53AE | route not resolved | 22 Feb 2017, 14:2222 Feb 2017 | 22 Feb 2017, 14:28 | 9,825 ft | no position received |
| HOP52TQ | route not resolved | 22 Feb 2017, 09:0222 Feb 2017 | 22 Feb 2017, 09:15 | 17,025 ft | no position received |
| HOP432G | route not resolved | 22 Feb 2017, 06:5322 Feb 2017 | 22 Feb 2017, 07:26 | 7,000 ft | no position received |
| HOP4328 | route not resolved | 21 Feb 2017, 20:2021 Feb 2017 | 21 Feb 2017, 20:52 | 20,025 ft | no position received |
| not transmitted | route not resolved | 20 Feb 2017, 14:2120 Feb 2017 | 20 Feb 2017, 14:25 | 11,525 ft | no position received |
| HOP52TQ | route not resolved | 20 Feb 2017, 09:0920 Feb 2017 | 20 Feb 2017, 09:22 | 17,025 ft | no position received |
| HOP432G | route not resolved | 20 Feb 2017, 07:0220 Feb 2017 | 20 Feb 2017, 07:36 | 6,000 ft | no position received |
| HOP4328 | route not resolved | 19 Feb 2017, 20:2219 Feb 2017 | 19 Feb 2017, 20:58 | 20,000 ft | no position received |
| not transmitted | route not resolved | 19 Feb 2017, 18:0319 Feb 2017 | 19 Feb 2017, 18:04 | 11,325 ft | no position received |
| HOP52TQ | route not resolved | 16 Feb 2017, 09:0416 Feb 2017 | 16 Feb 2017, 09:13 | 15,950 ft | no position received |
| HOP511G | route not resolved | 16 Feb 2017, 07:5116 Feb 2017 | 16 Feb 2017, 08:06 | 5,750 ft | no position received |
| HOP4518 | LFLL > LIPE | 15 Feb 2017, 20:5315 Feb 2017 | 15 Feb 2017, 21:14 | 21,000 ft | no position received |
| HOP57AE | route not resolved | 15 Feb 2017, 19:4715 Feb 2017 | 15 Feb 2017, 19:54 | 10,725 ft | no position received |
| HOP40RK | route not resolved | 15 Feb 2017, 18:1115 Feb 2017 | 15 Feb 2017, 18:25 | 15,025 ft | no position received |
| HOP513D | route not resolved | 15 Feb 2017, 13:5015 Feb 2017 | 15 Feb 2017, 14:04 | 6,150 ft | no position received |
| HOP512K | route not resolved | 15 Feb 2017, 09:0515 Feb 2017 | 15 Feb 2017, 09:26 | 21,025 ft | no position received |
| not transmitted | route not resolved | 13 Feb 2017, 11:4113 Feb 2017 | 13 Feb 2017, 11:41 | not transmitted | no position received |
| not transmitted | route not resolved | 10 Feb 2017, 20:0510 Feb 2017 | 10 Feb 2017, 20:05 | not transmitted | no position received |
