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,441
- Longest contact
- 0 h 54 min
Same airframe, also seen as
- SP-SPIfrom 12 Jan 2021 to 30 Jul 2026 · 528 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 |
|---|---|---|---|---|---|
| HOP73TQ | route not resolved | 6 Feb 2018, 14:286 Feb 2018 | 6 Feb 2018, 14:31 | 13,775 ft | no position received |
| HOP72LD | LFLL > LFBP | 6 Feb 2018, 08:586 Feb 2018 | 6 Feb 2018, 09:03 | 19,975 ft | no position received |
| HOP58RK | route not resolved | 5 Feb 2018, 20:375 Feb 2018 | 5 Feb 2018, 20:50 | 15,050 ft | no position received |
| HOP07QB | route not resolved | 5 Feb 2018, 19:135 Feb 2018 | 5 Feb 2018, 19:18 | 11,875 ft | no position received |
| HOP73TQ | route not resolved | 5 Feb 2018, 14:395 Feb 2018 | 5 Feb 2018, 14:43 | 13,050 ft | no position received |
| not transmitted | route not resolved | 2 Feb 2018, 19:152 Feb 2018 | 2 Feb 2018, 19:19 | 12,875 ft | no position received |
| HOP73TQ | route not resolved | 2 Feb 2018, 14:322 Feb 2018 | 2 Feb 2018, 14:43 | 10,675 ft | no position received |
| HOP71SC | route not resolved | 2 Feb 2018, 07:232 Feb 2018 | 2 Feb 2018, 07:32 | 9,525 ft | no position received |
| HOP07QB | route not resolved | 1 Feb 2018, 18:441 Feb 2018 | 1 Feb 2018, 18:52 | 9,300 ft | no position received |
| HOP73TQ | route not resolved | 1 Feb 2018, 14:261 Feb 2018 | 1 Feb 2018, 14:30 | 12,425 ft | no position received |
| HOP72LD | LFLL > LFBP | 1 Feb 2018, 09:041 Feb 2018 | 1 Feb 2018, 09:11 | 21,050 ft | no position received |
| HOP71SC | route not resolved | 1 Feb 2018, 07:321 Feb 2018 | 1 Feb 2018, 07:37 | 14,875 ft | no position received |
| HOP78LR | route not resolved | 31 Jan 2018, 20:2031 Jan 2018 | 31 Jan 2018, 20:36 | 21,025 ft | no position received |
| HOP07QB | route not resolved | 31 Jan 2018, 18:5631 Jan 2018 | 31 Jan 2018, 19:06 | 13,600 ft | no position received |
| HOP16RC | route not resolved | 31 Jan 2018, 16:1231 Jan 2018 | 31 Jan 2018, 16:17 | 16,950 ft | no position received |
| HOP73TQ | route not resolved | 31 Jan 2018, 14:2931 Jan 2018 | 31 Jan 2018, 14:38 | 12,275 ft | no position received |
| HOP71SC | route not resolved | 31 Jan 2018, 07:4131 Jan 2018 | 31 Jan 2018, 07:46 | 12,325 ft | no position received |
| HOP07QB | route not resolved | 30 Jan 2018, 18:5630 Jan 2018 | 30 Jan 2018, 19:03 | 11,200 ft | no position received |
| HOP95WI | LFJL > LFLL | 30 Jan 2018, 14:0730 Jan 2018 | 30 Jan 2018, 14:43 | 7,050 ft | no position received |
| HOP42ZX | route not resolved | 30 Jan 2018, 09:0930 Jan 2018 | 30 Jan 2018, 09:34 | 18,050 ft | no position received |
| HOP41VY | route not resolved | 30 Jan 2018, 07:0930 Jan 2018 | 30 Jan 2018, 07:45 | 5,250 ft | no position received |
| HOP65NZ | route not resolved | 29 Jan 2018, 20:2329 Jan 2018 | 29 Jan 2018, 20:53 | 18,000 ft | no position received |
| HOP07QB | route not resolved | 29 Jan 2018, 18:5429 Jan 2018 | 29 Jan 2018, 19:01 | 11,650 ft | no position received |
| HOP73TQ | route not resolved | 29 Jan 2018, 14:3829 Jan 2018 | 29 Jan 2018, 14:50 | 8,025 ft | no position received |
| HOP71SC | route not resolved | 29 Jan 2018, 07:5429 Jan 2018 | 29 Jan 2018, 07:57 | 12,575 ft | no position received |
