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,325
- 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 |
|---|---|---|---|---|---|
| HOP18TP | route not resolved | 25 Jan 2017, 20:1925 Jan 2017 | 25 Jan 2017, 21:09 | 16,900 ft | no position received |
| HOP47KT | route not resolved | 25 Jan 2017, 18:2625 Jan 2017 | 25 Jan 2017, 19:13 | 3,924 ft | no position received |
| HOP46YT | route not resolved | 25 Jan 2017, 15:5025 Jan 2017 | 25 Jan 2017, 16:16 | 21,025 ft | no position received |
| HOP73PD | route not resolved | 25 Jan 2017, 14:2425 Jan 2017 | 25 Jan 2017, 14:30 | 10,575 ft | no position received |
| HOP71SC | route not resolved | 25 Jan 2017, 07:5425 Jan 2017 | 25 Jan 2017, 08:02 | 11,400 ft | no position received |
| HOP07ZF | route not resolved | 24 Jan 2017, 18:5924 Jan 2017 | 24 Jan 2017, 19:08 | 10,750 ft | no position received |
| not transmitted | route not resolved | 24 Jan 2017, 09:3424 Jan 2017 | 24 Jan 2017, 09:53 | 14,900 ft | no position received |
| HOP41VY | route not resolved | 24 Jan 2017, 07:2424 Jan 2017 | 24 Jan 2017, 08:00 | 6,050 ft | no position received |
| HOP48YT | route not resolved | 23 Jan 2017, 20:5923 Jan 2017 | 23 Jan 2017, 21:25 | 17,675 ft | no position received |
| HOP47KT | route not resolved | 23 Jan 2017, 18:2323 Jan 2017 | 23 Jan 2017, 19:03 | 4,400 ft | no position received |
| HOP46YT | route not resolved | 23 Jan 2017, 15:5023 Jan 2017 | 23 Jan 2017, 16:10 | 21,000 ft | no position received |
| HOP513D | route not resolved | 23 Jan 2017, 14:1423 Jan 2017 | 23 Jan 2017, 14:24 | 10,325 ft | no position received |
| HOP512K | route not resolved | 23 Jan 2017, 10:0223 Jan 2017 | 23 Jan 2017, 10:29 | 35,000 ft | no position received |
| HOP51AE | route not resolved | 23 Jan 2017, 07:2323 Jan 2017 | 23 Jan 2017, 07:30 | 8,875 ft | no position received |
| HOP58RK | route not resolved | 22 Jan 2017, 20:3922 Jan 2017 | 22 Jan 2017, 20:49 | 15,650 ft | no position received |
| HOP8001 | route not resolved | 20 Jan 2017, 22:2620 Jan 2017 | 20 Jan 2017, 22:34 | 18,000 ft | no position received |
| HOP58RK | route not resolved | 20 Jan 2017, 20:3520 Jan 2017 | 20 Jan 2017, 20:45 | 15,000 ft | no position received |
| HOP507R | route not resolved | 20 Jan 2017, 19:0820 Jan 2017 | 20 Jan 2017, 19:18 | 5,975 ft | no position received |
| HOP506G | route not resolved | 20 Jan 2017, 15:5320 Jan 2017 | 20 Jan 2017, 16:34 | 18,025 ft | no position received |
| HOP73PD | route not resolved | 20 Jan 2017, 14:2920 Jan 2017 | 20 Jan 2017, 14:42 | 10,500 ft | no position received |
| HOP71SC | route not resolved | 20 Jan 2017, 07:5820 Jan 2017 | 20 Jan 2017, 08:07 | 7,900 ft | no position received |
| HOP07ZF | route not resolved | 19 Jan 2017, 19:0119 Jan 2017 | 19 Jan 2017, 19:05 | 9,875 ft | no position received |
| HOP95WI | LFJL > LFLL | 19 Jan 2017, 14:0019 Jan 2017 | 19 Jan 2017, 14:38 | 4,850 ft | no position received |
| HOP42ZX | route not resolved | 19 Jan 2017, 09:1919 Jan 2017 | 19 Jan 2017, 09:50 | 18,000 ft | no position received |
| HOP432G | route not resolved | 19 Jan 2017, 07:3919 Jan 2017 | 19 Jan 2017, 08:09 | 7,375 ft | no position received |
