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,219 of 57,185
- 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 12 Aug 2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| HOP51AE | route not resolved | 2 Mar 2017, 07:232 Mar 2017 | 2 Mar 2017, 07:38 | 10,000 ft | no position received |
| HOP58RK | route not resolved | 1 Mar 2017, 20:201 Mar 2017 | 1 Mar 2017, 20:35 | 19,050 ft | no position received |
| HOP95WI | LFJL > LFLL | 1 Mar 2017, 13:561 Mar 2017 | 1 Mar 2017, 14:26 | 9,125 ft | no position received |
| HOP42ZX | route not resolved | 1 Mar 2017, 09:001 Mar 2017 | 1 Mar 2017, 09:40 | 18,050 ft | no position received |
| HOP47KT | route not resolved | 28 Feb 2017, 18:2228 Feb 2017 | 28 Feb 2017, 18:58 | 9,875 ft | no position received |
| HOP46YT | route not resolved | 28 Feb 2017, 15:3328 Feb 2017 | 28 Feb 2017, 16:01 | 18,050 ft | no position received |
| HOP51AE | route not resolved | 28 Feb 2017, 07:3028 Feb 2017 | 28 Feb 2017, 07:42 | 10,025 ft | no position received |
| HOP58RK | route not resolved | 27 Feb 2017, 20:2927 Feb 2017 | 27 Feb 2017, 20:42 | 15,050 ft | no position received |
| HOP507R | route not resolved | 27 Feb 2017, 19:0127 Feb 2017 | 27 Feb 2017, 19:11 | 7,400 ft | no position received |
| HOP506G | route not resolved | 27 Feb 2017, 15:5327 Feb 2017 | 27 Feb 2017, 16:14 | 18,000 ft | no position received |
| HOP95WI | LFJL > LFLL | 27 Feb 2017, 13:5127 Feb 2017 | 27 Feb 2017, 14:30 | 10,050 ft | no position received |
| HOP42ZX | route not resolved | 27 Feb 2017, 08:5427 Feb 2017 | 27 Feb 2017, 09:14 | 18,000 ft | no position received |
| HOP41VY | route not resolved | 27 Feb 2017, 07:0727 Feb 2017 | 27 Feb 2017, 07:42 | 8,950 ft | no position received |
| HOP48YT | route not resolved | 26 Feb 2017, 20:3226 Feb 2017 | 26 Feb 2017, 21:10 | 17,775 ft | no position received |
| HOP07ZF | route not resolved | 26 Feb 2017, 18:5226 Feb 2017 | 26 Feb 2017, 19:02 | 10,000 ft | no position received |
| HOP53AE | route not resolved | 26 Feb 2017, 14:1126 Feb 2017 | 26 Feb 2017, 14:22 | 10,000 ft | no position received |
| HOP58RK | route not resolved | 24 Feb 2017, 21:1424 Feb 2017 | 24 Feb 2017, 21:25 | 15,050 ft | no position received |
| HOP507R | route not resolved | 24 Feb 2017, 18:4924 Feb 2017 | 24 Feb 2017, 19:04 | 7,025 ft | no position received |
| HOP506G | route not resolved | 24 Feb 2017, 15:5124 Feb 2017 | 24 Feb 2017, 16:09 | 21,000 ft | no position received |
| HOP72LD | LFLL > LFBP | 24 Feb 2017, 09:0624 Feb 2017 | 24 Feb 2017, 09:12 | 21,000 ft | no position received |
| HOP513D | route not resolved | 23 Feb 2017, 14:1023 Feb 2017 | 23 Feb 2017, 14:25 | 7,500 ft | no position received |
| HOP512K | route not resolved | 23 Feb 2017, 09:1123 Feb 2017 | 23 Feb 2017, 09:31 | 21,050 ft | no position received |
| not transmitted | route not resolved | 23 Feb 2017, 07:2423 Feb 2017 | 23 Feb 2017, 07:30 | 8,350 ft | no position received |
| HOP58RK | route not resolved | 22 Feb 2017, 20:2422 Feb 2017 | 22 Feb 2017, 20:35 | 15,050 ft | no position received |
| HOP507R | route not resolved | 22 Feb 2017, 18:5322 Feb 2017 | 22 Feb 2017, 19:10 | 6,375 ft | no position received |
