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 |
|---|---|---|---|---|---|
| not transmitted | route not resolved | 7 Nov 2017, 07:367 Nov 2017 | 7 Nov 2017, 07:36 | not transmitted | no position received |
| HOP58RK | route not resolved | 6 Nov 2017, 20:286 Nov 2017 | 6 Nov 2017, 20:40 | 15,000 ft | no position received |
| HOP04HA | route not resolved | 6 Nov 2017, 18:236 Nov 2017 | 6 Nov 2017, 19:01 | 6,700 ft | no position received |
| HOP23ZM | route not resolved | 6 Nov 2017, 16:306 Nov 2017 | 6 Nov 2017, 16:55 | 18,050 ft | no position received |
| HOP73TQ | route not resolved | 6 Nov 2017, 14:476 Nov 2017 | 6 Nov 2017, 14:53 | 11,275 ft | no position received |
| HOP04HA | route not resolved | 5 Nov 2017, 18:235 Nov 2017 | 5 Nov 2017, 19:02 | 9,150 ft | no position received |
| HOP20EY | route not resolved | 3 Nov 2017, 20:383 Nov 2017 | 3 Nov 2017, 21:07 | 18,050 ft | no position received |
| HOP04HA | route not resolved | 3 Nov 2017, 18:323 Nov 2017 | 3 Nov 2017, 19:08 | 9,600 ft | no position received |
| HOP23ZM | route not resolved | 3 Nov 2017, 16:343 Nov 2017 | 3 Nov 2017, 17:01 | 17,525 ft | no position received |
| HOP95WI | LFJL > LFLL | 3 Nov 2017, 14:173 Nov 2017 | 3 Nov 2017, 14:57 | 5,775 ft | no position received |
| HOP20EY | route not resolved | 2 Nov 2017, 20:312 Nov 2017 | 2 Nov 2017, 21:04 | 16,150 ft | no position received |
| HOP07QB | route not resolved | 2 Nov 2017, 18:542 Nov 2017 | 2 Nov 2017, 19:05 | 10,050 ft | no position received |
| HOP04HA | route not resolved | 1 Nov 2017, 18:131 Nov 2017 | 1 Nov 2017, 18:46 | 7,550 ft | no position received |
| HOP20EY | route not resolved | 31 Oct 2017, 20:2031 Oct 2017 | 31 Oct 2017, 20:50 | 17,800 ft | no position received |
| HOP07QB | route not resolved | 31 Oct 2017, 18:4731 Oct 2017 | 31 Oct 2017, 18:53 | 10,075 ft | no position received |
| HOP95WI | LFJL > LFLL | 31 Oct 2017, 14:1731 Oct 2017 | 31 Oct 2017, 14:51 | 5,100 ft | no position received |
| HOP23ZM | route not resolved | 30 Oct 2017, 16:1230 Oct 2017 | 30 Oct 2017, 16:44 | 16,250 ft | no position received |
| HOP95WI | LFJL > LFLL | 30 Oct 2017, 14:1830 Oct 2017 | 30 Oct 2017, 14:53 | 6,950 ft | no position received |
| HOP42ZX | route not resolved | 30 Oct 2017, 09:0430 Oct 2017 | 30 Oct 2017, 09:37 | 18,000 ft | no position received |
| HOP71SC | route not resolved | 30 Oct 2017, 07:3530 Oct 2017 | 30 Oct 2017, 07:40 | 9,900 ft | no position received |
| HOP04HA | route not resolved | 29 Oct 2017, 18:2229 Oct 2017 | 29 Oct 2017, 18:58 | 6,075 ft | no position received |
| HOP48YT | route not resolved | 27 Oct 2017, 20:1827 Oct 2017 | 27 Oct 2017, 20:52 | 18,050 ft | no position received |
| not transmitted | route not resolved | 27 Oct 2017, 18:3527 Oct 2017 | 27 Oct 2017, 18:53 | 7,900 ft | no position received |
| HOP506G | route not resolved | 27 Oct 2017, 15:4827 Oct 2017 | 27 Oct 2017, 16:10 | 21,050 ft | no position received |
| not transmitted | route not resolved | 27 Oct 2017, 14:2627 Oct 2017 | 27 Oct 2017, 14:40 | 6,775 ft | no position received |
