Back to the log
Aircraft
F-GVZM
Commonnot seen for 8 years
The fields of this record contradict each other: year built 1999, first flight of the type in 2009. The log is authentic; the described identity is doubtful.
The station's story
Address not received since 31 Jan 2018. The marker states the absence, it does not say why.
- Cumulative contact time
- 345 h
- Distinct days
- 358
- Highest captured altitude
- 35,000 ft
- 3 corrupted frame(s) excluded from this maximum
- Discovery rank
- #298 of 57,354
- Longest contact
- 1 h 6 min
Same airframe, also seen as
- SX-FIVfrom 29 Oct 2019 to 18 Mar 2021 · 4 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 (823 contacts, 2016-2018) · AFR (5 contacts, 2017)
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 |
|---|---|---|---|---|---|
| HOP41VY | route not resolved | 9 Jan 2017, 07:129 Jan 2017 | 9 Jan 2017, 07:56 | 10,975 ft | no position received |
| HOP48YT | route not resolved | 8 Jan 2017, 20:148 Jan 2017 | 8 Jan 2017, 20:47 | 18,050 ft | no position received |
| HOP07ZF | route not resolved | 8 Jan 2017, 18:508 Jan 2017 | 8 Jan 2017, 18:55 | 13,300 ft | no position received |
| HOP07ZF | route not resolved | 6 Jan 2017, 19:036 Jan 2017 | 6 Jan 2017, 19:08 | 11,050 ft | no position received |
| HOP43SC | route not resolved | 6 Jan 2017, 14:076 Jan 2017 | 6 Jan 2017, 14:39 | 5,575 ft | no position received |
| HOP48YT | route not resolved | 5 Jan 2017, 20:035 Jan 2017 | 5 Jan 2017, 20:44 | 16,925 ft | no position received |
| HOP47KT | route not resolved | 5 Jan 2017, 18:195 Jan 2017 | 5 Jan 2017, 18:49 | 5,525 ft | no position received |
| HOP46YT | route not resolved | 5 Jan 2017, 15:385 Jan 2017 | 5 Jan 2017, 16:20 | 18,050 ft | no position received |
| HOP43SC | route not resolved | 5 Jan 2017, 14:005 Jan 2017 | 5 Jan 2017, 14:30 | 5,400 ft | no position received |
| HOP48YT | route not resolved | 4 Jan 2017, 20:164 Jan 2017 | 4 Jan 2017, 20:53 | 18,050 ft | no position received |
| not transmitted | route not resolved | 4 Jan 2017, 09:284 Jan 2017 | 4 Jan 2017, 09:30 | 16,875 ft | no position received |
| not transmitted | route not resolved | 3 Jan 2017, 16:343 Jan 2017 | 3 Jan 2017, 16:34 | 20,000 ft | no position received |
| HOP73PD | route not resolved | 3 Jan 2017, 14:163 Jan 2017 | 3 Jan 2017, 14:23 | 10,050 ft | no position received |
| HOP507R | route not resolved | 2 Jan 2017, 19:002 Jan 2017 | 2 Jan 2017, 19:20 | 6,375 ft | no position received |
| HOP506G | route not resolved | 2 Jan 2017, 16:092 Jan 2017 | 2 Jan 2017, 16:25 | 21,000 ft | no position received |
| HOP8006 | route not resolved | 26 Dec 2016, 18:5526 Dec 2016 | 26 Dec 2016, 19:08 | 18,050 ft | no position received |
| HOP40RK | route not resolved | 15 Dec 2016, 15:5715 Dec 2016 | 15 Dec 2016, 16:01 | 11,475 ft | no position received |
| HOP48YT | route not resolved | 14 Dec 2016, 21:1014 Dec 2016 | 14 Dec 2016, 21:42 | 18,050 ft | no position received |
| HOP8630 | route not resolved | 14 Dec 2016, 14:1214 Dec 2016 | 14 Dec 2016, 14:41 | 10,000 ft | no position received |
| HOP8001 | route not resolved | 10 Nov 2016, 09:3010 Nov 2016 | 10 Nov 2016, 09:57 | 25,000 ft | no position received |
| HOP71SC | route not resolved | 9 Nov 2016, 07:299 Nov 2016 | 9 Nov 2016, 07:41 | 11,425 ft | no position received |
| HOP07ZF | route not resolved | 8 Nov 2016, 18:598 Nov 2016 | 8 Nov 2016, 19:05 | 11,700 ft | no position received |
| not transmitted | route not resolved | 8 Nov 2016, 15:488 Nov 2016 | 8 Nov 2016, 16:03 | 17,025 ft | no position received |
| HOP43SC | route not resolved | 8 Nov 2016, 13:548 Nov 2016 | 8 Nov 2016, 14:30 | 6,100 ft | no position received |
| HOP42ZX | route not resolved | 8 Nov 2016, 08:508 Nov 2016 | 8 Nov 2016, 09:19 | 18,000 ft | no position received |
