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,380
- 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 |
|---|---|---|---|---|---|
| HOP48YT | route not resolved | 9 Feb 2017, 20:159 Feb 2017 | 9 Feb 2017, 21:00 | 17,025 ft | no position received |
| HOP47KT | route not resolved | 9 Feb 2017, 18:189 Feb 2017 | 9 Feb 2017, 19:02 | 7,025 ft | no position received |
| HOP46YT | route not resolved | 9 Feb 2017, 15:539 Feb 2017 | 9 Feb 2017, 16:18 | 18,050 ft | no position received |
| HOP73PD | route not resolved | 9 Feb 2017, 14:169 Feb 2017 | 9 Feb 2017, 14:22 | 10,725 ft | no position received |
| not transmitted | route not resolved | 9 Feb 2017, 09:199 Feb 2017 | 9 Feb 2017, 09:21 | 19,925 ft | no position received |
| HOP71SC | route not resolved | 9 Feb 2017, 07:499 Feb 2017 | 9 Feb 2017, 07:55 | 10,900 ft | no position received |
| HOP07ZF | route not resolved | 8 Feb 2017, 18:488 Feb 2017 | 8 Feb 2017, 19:05 | 6,000 ft | no position received |
| HOP4503 | route not resolved | 8 Feb 2017, 14:018 Feb 2017 | 8 Feb 2017, 14:16 | 6,600 ft | no position received |
| HOP502U | route not resolved | 8 Feb 2017, 09:018 Feb 2017 | 8 Feb 2017, 09:16 | 28,000 ft | no position received |
| HOP71SC | route not resolved | 8 Feb 2017, 07:348 Feb 2017 | 8 Feb 2017, 07:39 | 11,550 ft | no position received |
| HOP47KT | route not resolved | 7 Feb 2017, 18:227 Feb 2017 | 7 Feb 2017, 19:11 | 7,325 ft | no position received |
| HOP46YT | route not resolved | 7 Feb 2017, 15:287 Feb 2017 | 7 Feb 2017, 16:03 | 21,025 ft | no position received |
| HOP73PD | route not resolved | 7 Feb 2017, 13:597 Feb 2017 | 7 Feb 2017, 14:27 | 9,000 ft | no position received |
| HOP71SC | route not resolved | 7 Feb 2017, 07:227 Feb 2017 | 7 Feb 2017, 07:43 | 7,000 ft | no position received |
| HOP07ZF | route not resolved | 6 Feb 2017, 18:526 Feb 2017 | 6 Feb 2017, 19:02 | 9,200 ft | no position received |
| not transmitted | route not resolved | 6 Feb 2017, 14:176 Feb 2017 | 6 Feb 2017, 14:20 | 11,475 ft | no position received |
| HOP41VY | route not resolved | 6 Feb 2017, 07:216 Feb 2017 | 6 Feb 2017, 07:54 | 5,975 ft | no position received |
| HOP48YT | route not resolved | 5 Feb 2017, 20:115 Feb 2017 | 5 Feb 2017, 20:43 | 19,500 ft | no position received |
| HOP4503 | route not resolved | 5 Feb 2017, 13:565 Feb 2017 | 5 Feb 2017, 14:19 | 35,000 ft | no position received |
| HOP508H | LFLL > LIMC | 3 Feb 2017, 20:193 Feb 2017 | 3 Feb 2017, 20:39 | 21,025 ft | no position received |
| HOP47KT | route not resolved | 3 Feb 2017, 18:273 Feb 2017 | 3 Feb 2017, 19:04 | 10,350 ft | no position received |
| HOP46YT | route not resolved | 3 Feb 2017, 15:483 Feb 2017 | 3 Feb 2017, 16:27 | 21,000 ft | no position received |
| HOP73PD | route not resolved | 3 Feb 2017, 14:033 Feb 2017 | 3 Feb 2017, 14:12 | 10,050 ft | no position received |
| HOP72LD | LFLL > LFBP | 3 Feb 2017, 09:073 Feb 2017 | 3 Feb 2017, 09:30 | 23,025 ft | no position received |
| HOP71SC | route not resolved | 3 Feb 2017, 07:303 Feb 2017 | 3 Feb 2017, 07:40 | 28,075 ft | no position received |
