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,363
- 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 |
|---|---|---|---|---|---|
| HOP4328 | route not resolved | 18 Jan 2017, 20:2818 Jan 2017 | 18 Jan 2017, 21:09 | 20,000 ft | no position received |
| HOP507R | route not resolved | 18 Jan 2017, 18:4118 Jan 2017 | 18 Jan 2017, 19:02 | 33,000 ft | no position received |
| HOP46YT | route not resolved | 18 Jan 2017, 16:0718 Jan 2017 | 18 Jan 2017, 16:23 | 21,050 ft | no position received |
| HOP83AJ | route not resolved | 18 Jan 2017, 14:3818 Jan 2017 | 18 Jan 2017, 14:42 | 12,075 ft | no position received |
| HOP71SC | route not resolved | 18 Jan 2017, 07:4718 Jan 2017 | 18 Jan 2017, 07:52 | 11,850 ft | no position received |
| HOP43SC | route not resolved | 17 Jan 2017, 13:4917 Jan 2017 | 17 Jan 2017, 14:25 | 5,500 ft | no position received |
| HOP42ZX | route not resolved | 17 Jan 2017, 09:2217 Jan 2017 | 17 Jan 2017, 09:45 | 18,050 ft | no position received |
| HOP41VY | route not resolved | 17 Jan 2017, 07:1617 Jan 2017 | 17 Jan 2017, 07:57 | 7,000 ft | no position received |
| HOP48YT | route not resolved | 16 Jan 2017, 20:1916 Jan 2017 | 16 Jan 2017, 21:02 | 25,000 ft | no position received |
| HOP512K | route not resolved | 16 Jan 2017, 10:0416 Jan 2017 | 16 Jan 2017, 10:44 | 8,050 ft | no position received |
| not transmitted | route not resolved | 13 Jan 2017, 18:4913 Jan 2017 | 13 Jan 2017, 19:08 | 29,025 ft | no position received |
| HOP40RK | route not resolved | 13 Jan 2017, 16:5413 Jan 2017 | 13 Jan 2017, 17:06 | 15,000 ft | no position received |
| HOP8004 | route not resolved | 13 Jan 2017, 12:4513 Jan 2017 | 13 Jan 2017, 13:19 | 5,450 ft | no position received |
| HOP48YT | route not resolved | 12 Jan 2017, 20:2612 Jan 2017 | 12 Jan 2017, 20:46 | 33,975 ft | no position received |
| HOP47KT | route not resolved | 12 Jan 2017, 18:4612 Jan 2017 | 12 Jan 2017, 19:23 | 10,225 ft | no position received |
| HOP46YT | route not resolved | 12 Jan 2017, 15:3612 Jan 2017 | 12 Jan 2017, 16:10 | 18,050 ft | no position received |
| HOP41VY | route not resolved | 12 Jan 2017, 07:0312 Jan 2017 | 12 Jan 2017, 07:32 | 9,625 ft | no position received |
| HOP48YT | route not resolved | 11 Jan 2017, 20:1511 Jan 2017 | 11 Jan 2017, 20:55 | 18,000 ft | no position received |
| HOP47KT | route not resolved | 11 Jan 2017, 18:3211 Jan 2017 | 11 Jan 2017, 19:00 | 10,000 ft | no position received |
| HOP42ZX | route not resolved | 11 Jan 2017, 09:1911 Jan 2017 | 11 Jan 2017, 09:56 | 18,050 ft | no position received |
| HOP73PD | route not resolved | 10 Jan 2017, 14:1710 Jan 2017 | 10 Jan 2017, 14:22 | 11,575 ft | no position received |
| HOP41VY | route not resolved | 10 Jan 2017, 08:0710 Jan 2017 | 10 Jan 2017, 08:33 | 10,125 ft | no position received |
| HOP48YT | route not resolved | 9 Jan 2017, 20:379 Jan 2017 | 9 Jan 2017, 21:08 | 18,000 ft | no position received |
| HOP66SI | LFLL > LFQQ | 9 Jan 2017, 15:549 Jan 2017 | 9 Jan 2017, 16:00 | 18,150 ft | no position received |
| HOP73PD | route not resolved | 9 Jan 2017, 14:129 Jan 2017 | 9 Jan 2017, 14:20 | 10,325 ft | no position received |
