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 |
|---|---|---|---|---|---|
| HOP58RK | route not resolved | 15 Feb 2018, 20:2815 Feb 2018 | 15 Feb 2018, 20:30 | 10,750 ft | no position received |
| HOP07QB | route not resolved | 15 Feb 2018, 18:4515 Feb 2018 | 15 Feb 2018, 18:55 | 10,050 ft | no position received |
| HOP16RC | route not resolved | 15 Feb 2018, 16:1415 Feb 2018 | 15 Feb 2018, 16:20 | 17,050 ft | no position received |
| HOP51AE | route not resolved | 15 Feb 2018, 07:3815 Feb 2018 | 15 Feb 2018, 07:44 | 10,000 ft | no position received |
| HOP58RK | route not resolved | 14 Feb 2018, 20:3314 Feb 2018 | 14 Feb 2018, 20:38 | 14,225 ft | no position received |
| HOP07QB | route not resolved | 14 Feb 2018, 19:1014 Feb 2018 | 14 Feb 2018, 19:12 | 13,575 ft | no position received |
| HOP53AR | route not resolved | 14 Feb 2018, 09:5314 Feb 2018 | 14 Feb 2018, 10:03 | 15,000 ft | no position received |
| HOP65NZ | route not resolved | 13 Feb 2018, 20:4713 Feb 2018 | 13 Feb 2018, 21:14 | 16,000 ft | no position received |
| HOP66SI | LFLL > LFQQ | 13 Feb 2018, 16:2413 Feb 2018 | 13 Feb 2018, 16:31 | 16,050 ft | no position received |
| HOP86LH | route not resolved | 13 Feb 2018, 09:1713 Feb 2018 | 13 Feb 2018, 09:24 | 16,000 ft | no position received |
| HOP51AE | route not resolved | 13 Feb 2018, 07:2913 Feb 2018 | 13 Feb 2018, 07:37 | 10,000 ft | no position received |
| HOP58RK | route not resolved | 12 Feb 2018, 20:2112 Feb 2018 | 12 Feb 2018, 20:31 | 15,050 ft | no position received |
| HOP23ZM | route not resolved | 12 Feb 2018, 16:1312 Feb 2018 | 12 Feb 2018, 16:41 | 16,000 ft | no position received |
| HOP8003 | route not resolved | 12 Feb 2018, 07:5412 Feb 2018 | 12 Feb 2018, 08:32 | 5,500 ft | no position received |
| HOP65NZ | route not resolved | 9 Feb 2018, 20:469 Feb 2018 | 9 Feb 2018, 21:12 | 18,000 ft | no position received |
| HOP73TQ | route not resolved | 9 Feb 2018, 14:359 Feb 2018 | 9 Feb 2018, 14:47 | 12,200 ft | no position received |
| not transmitted | route not resolved | 9 Feb 2018, 07:519 Feb 2018 | 9 Feb 2018, 07:51 | not transmitted | no position received |
| HOP58RK | route not resolved | 8 Feb 2018, 20:478 Feb 2018 | 8 Feb 2018, 20:59 | 18,100 ft | no position received |
| HOP73TQ | route not resolved | 8 Feb 2018, 14:358 Feb 2018 | 8 Feb 2018, 14:38 | 12,775 ft | no position received |
| not transmitted | route not resolved | 8 Feb 2018, 08:378 Feb 2018 | 8 Feb 2018, 08:37 | not transmitted | no position received |
| HOP58RK | route not resolved | 7 Feb 2018, 21:517 Feb 2018 | 7 Feb 2018, 22:03 | 14,050 ft | no position received |
| HOP95WI | LFJL > LFLL | 7 Feb 2018, 14:247 Feb 2018 | 7 Feb 2018, 14:54 | 8,650 ft | no position received |
| HOP42ZX | route not resolved | 7 Feb 2018, 08:497 Feb 2018 | 7 Feb 2018, 09:15 | 19,000 ft | no position received |
| HOP58RK | route not resolved | 6 Feb 2018, 20:416 Feb 2018 | 6 Feb 2018, 20:48 | 15,025 ft | no position received |
| HOP07QB | route not resolved | 6 Feb 2018, 18:546 Feb 2018 | 6 Feb 2018, 19:00 | 11,925 ft | no position received |
