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,065
- 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 21.07.2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| HOP8500 | route not resolved | 31 Jan 2018, 14:1331 Jan 2018 | 31 Jan 2018, 14:41 | 25,000 ft | no position received |
| HOP27ZY | route not resolved | 18 Dec 2017, 19:2118 Dec 2017 | 18 Dec 2017, 20:17 | 17,500 ft | no position received |
| HOP23VG | route not resolved | 18 Dec 2017, 16:5718 Dec 2017 | 18 Dec 2017, 17:46 | 116,500 ft | no position received |
| HOP8810 | route not resolved | 15 Dec 2017, 11:1315 Dec 2017 | 15 Dec 2017, 11:23 | 18,050 ft | no position received |
| HOP07QB | route not resolved | 12 Dec 2017, 18:5712 Dec 2017 | 12 Dec 2017, 19:04 | 10,450 ft | no position received |
| HOP73TQ | route not resolved | 12 Dec 2017, 14:3512 Dec 2017 | 12 Dec 2017, 14:43 | 6,900 ft | no position received |
| not transmitted | route not resolved | 10 Dec 2017, 21:1610 Dec 2017 | 10 Dec 2017, 21:23 | 15,900 ft | no position received |
| HOP16RC | route not resolved | 10 Dec 2017, 16:5410 Dec 2017 | 10 Dec 2017, 16:58 | 17,000 ft | no position received |
| HOP838J | LIPE > LFLL | 8 Dec 2017, 14:288 Dec 2017 | 8 Dec 2017, 14:44 | 7,025 ft | no position received |
| HOP512K | route not resolved | 8 Dec 2017, 09:058 Dec 2017 | 8 Dec 2017, 09:20 | 21,000 ft | no position received |
| HOP51AE | route not resolved | 8 Dec 2017, 07:408 Dec 2017 | 8 Dec 2017, 07:51 | 10,000 ft | no position received |
| HOP58RK | route not resolved | 7 Dec 2017, 20:187 Dec 2017 | 7 Dec 2017, 20:34 | 15,025 ft | no position received |
| HOP04HA | route not resolved | 7 Dec 2017, 18:217 Dec 2017 | 7 Dec 2017, 18:53 | 7,750 ft | no position received |
| HOP23ZM | route not resolved | 7 Dec 2017, 16:327 Dec 2017 | 7 Dec 2017, 17:04 | 16,950 ft | no position received |
| HOP838J | LIPE > LFLL | 7 Dec 2017, 14:297 Dec 2017 | 7 Dec 2017, 14:47 | 7,400 ft | no position received |
| HOP512K | route not resolved | 7 Dec 2017, 09:037 Dec 2017 | 7 Dec 2017, 09:24 | 21,025 ft | no position received |
| HOP73TQ | route not resolved | 5 Dec 2017, 14:295 Dec 2017 | 5 Dec 2017, 14:39 | 8,000 ft | no position received |
| HOP8005 | route not resolved | 5 Dec 2017, 07:205 Dec 2017 | 5 Dec 2017, 07:28 | 9,725 ft | no position received |
| HOP04HA | route not resolved | 1 Dec 2017, 18:261 Dec 2017 | 1 Dec 2017, 19:04 | 6,050 ft | no position received |
| HOP23ZM | route not resolved | 1 Dec 2017, 16:321 Dec 2017 | 1 Dec 2017, 16:57 | 17,950 ft | no position received |
| HOP95WI | LFJL > LFLL | 1 Dec 2017, 14:141 Dec 2017 | 1 Dec 2017, 14:53 | 5,675 ft | no position received |
| HOP42ZX | route not resolved | 1 Dec 2017, 09:261 Dec 2017 | 1 Dec 2017, 09:57 | 19,450 ft | no position received |
| HOP41VY | route not resolved | 1 Dec 2017, 07:231 Dec 2017 | 1 Dec 2017, 08:03 | 7,125 ft | no position received |
| HOP65NZ | route not resolved | 30 Nov 2017, 20:2630 Nov 2017 | 30 Nov 2017, 20:49 | 18,000 ft | no position received |
| HOP07QB | route not resolved | 30 Nov 2017, 18:5430 Nov 2017 | 30 Nov 2017, 19:05 | 10,050 ft | no position received |
