Back to the log
Aircraft
F-GVZV
Commonnot seen for 5 years
The fields of this record contradict each other: year built 2002, first flight of the type in 2009. The log is authentic; the described identity is doubtful.
The station's story
Address not received since 20 Aug 2020. The marker states the absence, it does not say why.
- Cumulative contact time
- 407 h
- Distinct days
- 463
- Highest captured altitude
- 34,975 ft
- 1 corrupted frame(s) excluded from this maximum
- Discovery rank
- #6,216 of 57,065
- Longest contact
- 0 h 54 min
Same airframe, also seen as
- SP-SPIfrom 12 Jan 2021 to 11 Aug 2026 · 529 contacts
These registrations share the same serial number and type according to the reference data. Serial numbers can collide, though: it is a deduction, not a certainty.
Observed callsigns
HOP (1,055 contacts, 2016-2019) · AFR (5 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 |
|---|---|---|---|---|---|
| HOP07QB | route not resolved | 7 Jan 2018, 19:027 Jan 2018 | 7 Jan 2018, 19:11 | 9,900 ft | no position received |
| HOP71SC | route not resolved | 6 Jan 2018, 08:236 Jan 2018 | 6 Jan 2018, 08:29 | 15,300 ft | no position received |
| not transmitted | route not resolved | 5 Jan 2018, 18:555 Jan 2018 | 5 Jan 2018, 19:06 | 13,375 ft | no position received |
| not transmitted | route not resolved | 5 Jan 2018, 16:035 Jan 2018 | 5 Jan 2018, 16:16 | 20,425 ft | no position received |
| HOP07QB | route not resolved | 4 Jan 2018, 18:574 Jan 2018 | 4 Jan 2018, 19:09 | 10,875 ft | no position received |
| HOP73TQ | route not resolved | 4 Jan 2018, 14:364 Jan 2018 | 4 Jan 2018, 14:46 | 12,500 ft | no position received |
| HOP72LD | LFLL > LFBP | 3 Jan 2018, 09:063 Jan 2018 | 3 Jan 2018, 09:17 | 21,025 ft | no position received |
| HOP41VY | route not resolved | 3 Jan 2018, 07:103 Jan 2018 | 3 Jan 2018, 07:42 | 10,525 ft | no position received |
| HOP42ZX | route not resolved | 2 Jan 2018, 09:042 Jan 2018 | 2 Jan 2018, 09:39 | 18,000 ft | no position received |
| not transmitted | route not resolved | 1 Jan 2018, 20:111 Jan 2018 | 1 Jan 2018, 20:13 | not transmitted | no position received |
| HOP95WI | LFJL > LFLL | 1 Jan 2018, 14:231 Jan 2018 | 1 Jan 2018, 14:58 | 8,300 ft | no position received |
| HOP23ZM | route not resolved | 31 Dec 2017, 16:0531 Dec 2017 | 31 Dec 2017, 16:33 | 18,050 ft | no position received |
| HOP95WI | LFJL > LFLL | 31 Dec 2017, 14:0831 Dec 2017 | 31 Dec 2017, 14:47 | 9,250 ft | no position received |
| HOP8000 | EDDS > LFPG | 31 Dec 2017, 12:1531 Dec 2017 | 31 Dec 2017, 12:45 | 18,050 ft | no position received |
| HOP04HA | route not resolved | 29 Dec 2017, 18:2429 Dec 2017 | 29 Dec 2017, 18:58 | 11,100 ft | no position received |
| HOP23ZM | route not resolved | 29 Dec 2017, 16:1229 Dec 2017 | 29 Dec 2017, 16:46 | 18,050 ft | no position received |
| HOP73TQ | route not resolved | 29 Dec 2017, 14:2829 Dec 2017 | 29 Dec 2017, 14:36 | 10,000 ft | no position received |
| HOP04HA | route not resolved | 28 Dec 2017, 18:2128 Dec 2017 | 28 Dec 2017, 18:54 | 7,050 ft | no position received |
| HOP23ZM | route not resolved | 28 Dec 2017, 16:0328 Dec 2017 | 28 Dec 2017, 16:34 | 15,725 ft | no position received |
| HOP73TQ | route not resolved | 28 Dec 2017, 14:3528 Dec 2017 | 28 Dec 2017, 14:44 | 9,400 ft | no position received |
| HOP73TQ | route not resolved | 24 Dec 2017, 14:3624 Dec 2017 | 24 Dec 2017, 14:49 | 7,650 ft | no position received |
| HOP8005 | route not resolved | 21 Dec 2017, 18:5521 Dec 2017 | 21 Dec 2017, 19:02 | 17,575 ft | no position received |
| HOP04HA | route not resolved | 18 Dec 2017, 18:1618 Dec 2017 | 18 Dec 2017, 18:52 | 6,125 ft | no position received |
| HOP23ZM | route not resolved | 18 Dec 2017, 16:1218 Dec 2017 | 18 Dec 2017, 16:35 | 17,750 ft | no position received |
| HOP95WI | LFJL > LFLL | 18 Dec 2017, 14:1518 Dec 2017 | 18 Dec 2017, 14:53 | 6,000 ft | no position received |
