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 |
|---|---|---|---|---|---|
| not transmitted | route not resolved | 17 Jul 2018, 19:0717 Jul 2018 | 17 Jul 2018, 19:07 | 7,000 ft | no position received |
| HOP40RK | route not resolved | 17 Jul 2018, 17:0417 Jul 2018 | 17 Jul 2018, 17:19 | 17,000 ft | no position received |
| HOP58RK | route not resolved | 11 Jul 2018, 20:2711 Jul 2018 | 11 Jul 2018, 20:42 | 16,550 ft | no position received |
| HOP40RK | route not resolved | 11 Jul 2018, 16:4711 Jul 2018 | 11 Jul 2018, 17:02 | 19,025 ft | no position received |
| HOP4503 | route not resolved | 11 Jul 2018, 14:5311 Jul 2018 | 11 Jul 2018, 15:04 | 7,475 ft | no position received |
| HOP502U | route not resolved | 11 Jul 2018, 11:0511 Jul 2018 | 11 Jul 2018, 11:27 | 21,000 ft | no position received |
| HOP12UM | route not resolved | 10 Jul 2018, 21:4410 Jul 2018 | 10 Jul 2018, 22:03 | 18,600 ft | no position received |
| not transmitted | route not resolved | 10 Jul 2018, 17:2910 Jul 2018 | 10 Jul 2018, 17:34 | 20,025 ft | no position received |
| HOP95WI | LFJL > LFLL | 10 Jul 2018, 14:2610 Jul 2018 | 10 Jul 2018, 15:00 | 6,225 ft | no position received |
| HOP42ZX | route not resolved | 10 Jul 2018, 10:0110 Jul 2018 | 10 Jul 2018, 10:25 | 18,025 ft | no position received |
| HOP58RK | route not resolved | 9 Jul 2018, 22:339 Jul 2018 | 9 Jul 2018, 22:40 | 11,675 ft | no position received |
| HOP95WI | LFJL > LFLL | 9 Jul 2018, 14:389 Jul 2018 | 9 Jul 2018, 15:12 | 5,275 ft | no position received |
| HOP42ZX | route not resolved | 9 Jul 2018, 09:309 Jul 2018 | 9 Jul 2018, 09:43 | 17,025 ft | no position received |
| not transmitted | route not resolved | 8 Jul 2018, 20:588 Jul 2018 | 8 Jul 2018, 21:02 | 9,550 ft | no position received |
| HOP205M | route not resolved | 8 Jul 2018, 19:258 Jul 2018 | 8 Jul 2018, 19:58 | 5,250 ft | no position received |
| HOP636Q | route not resolved | 8 Jul 2018, 16:258 Jul 2018 | 8 Jul 2018, 17:04 | 18,025 ft | no position received |
| not transmitted | route not resolved | 8 Jul 2018, 12:538 Jul 2018 | 8 Jul 2018, 13:01 | 21,000 ft | no position received |
| HOP3333 | LFML > LFRK | 8 Jul 2018, 09:008 Jul 2018 | 8 Jul 2018, 09:19 | 22,000 ft | no position received |
| HOP34TU | route not resolved | 7 Jul 2018, 21:387 Jul 2018 | 7 Jul 2018, 21:52 | 17,025 ft | no position received |
| not transmitted | route not resolved | 7 Jul 2018, 19:097 Jul 2018 | 7 Jul 2018, 19:10 | 18,000 ft | no position received |
| HOP29LQ | route not resolved | 7 Jul 2018, 18:397 Jul 2018 | 7 Jul 2018, 18:43 | 18,000 ft | no position received |
| not transmitted | route not resolved | 7 Jul 2018, 15:527 Jul 2018 | 7 Jul 2018, 15:57 | 21,025 ft | no position received |
| HOP8000 | EDDS > LFPG | 17 Jun 2018, 16:0517 Jun 2018 | 17 Jun 2018, 16:06 | 19,675 ft | no position received |
| HOP8610 | LFPO > LFRU | 13 Jun 2018, 13:3113 Jun 2018 | 13 Jun 2018, 14:01 | 8,600 ft | no position received |
| AFR79ZK | LFSB > LFPO | 13 Apr 2018, 18:5213 Apr 2018 | 13 Apr 2018, 19:09 | 18,000 ft | no position received |
