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 29 Jul 2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| HOP51AE | route not resolved | 6 Nov 2017, 07:556 Nov 2017 | 6 Nov 2017, 07:57 | 11,975 ft | no position received |
| HOP58RK | route not resolved | 5 Nov 2017, 21:125 Nov 2017 | 5 Nov 2017, 21:24 | 15,050 ft | no position received |
| HOP07QB | route not resolved | 5 Nov 2017, 19:205 Nov 2017 | 5 Nov 2017, 19:28 | 9,850 ft | no position received |
| HOP73TQ | route not resolved | 5 Nov 2017, 14:355 Nov 2017 | 5 Nov 2017, 14:37 | 13,800 ft | no position received |
| not transmitted | route not resolved | 4 Nov 2017, 11:114 Nov 2017 | 4 Nov 2017, 11:14 | 14,275 ft | no position received |
| HOP07QB | route not resolved | 3 Nov 2017, 18:583 Nov 2017 | 3 Nov 2017, 19:02 | 13,125 ft | no position received |
| HOP73TQ | route not resolved | 3 Nov 2017, 14:263 Nov 2017 | 3 Nov 2017, 14:32 | 11,450 ft | no position received |
| HOP507R | route not resolved | 2 Nov 2017, 18:322 Nov 2017 | 2 Nov 2017, 19:09 | 26,000 ft | no position received |
| HOP502U | route not resolved | 2 Nov 2017, 09:002 Nov 2017 | 2 Nov 2017, 09:12 | 18,850 ft | no position received |
| HOP450T | route not resolved | 2 Nov 2017, 07:202 Nov 2017 | 2 Nov 2017, 07:33 | 7,425 ft | no position received |
| HOP502U | route not resolved | 1 Nov 2017, 09:011 Nov 2017 | 1 Nov 2017, 09:24 | 21,050 ft | no position received |
| HOP04HA | route not resolved | 31 Oct 2017, 18:1431 Oct 2017 | 31 Oct 2017, 18:51 | 31,000 ft | no position received |
| HOP23ZM | route not resolved | 31 Oct 2017, 16:1031 Oct 2017 | 31 Oct 2017, 16:41 | 16,250 ft | no position received |
| HOP73TQ | route not resolved | 31 Oct 2017, 14:4631 Oct 2017 | 31 Oct 2017, 14:53 | 8,900 ft | no position received |
| not transmitted | route not resolved | 30 Oct 2017, 18:4730 Oct 2017 | 30 Oct 2017, 18:58 | 7,025 ft | no position received |
| HOP502U | route not resolved | 30 Oct 2017, 09:1430 Oct 2017 | 30 Oct 2017, 09:21 | 14,250 ft | no position received |
| HOP58RK | route not resolved | 29 Oct 2017, 20:3729 Oct 2017 | 29 Oct 2017, 20:49 | 15,050 ft | no position received |
| not transmitted | route not resolved | 29 Oct 2017, 18:5129 Oct 2017 | 29 Oct 2017, 19:00 | 11,250 ft | no position received |
| HOP508H | LFLL > LIMC | 27 Oct 2017, 20:3327 Oct 2017 | 27 Oct 2017, 21:00 | 21,000 ft | no position received |
| HOP07QB | route not resolved | 27 Oct 2017, 18:5527 Oct 2017 | 27 Oct 2017, 19:02 | 10,250 ft | no position received |
| HOP73PD | route not resolved | 27 Oct 2017, 14:0927 Oct 2017 | 27 Oct 2017, 14:15 | 12,550 ft | no position received |
| HOP71SC | route not resolved | 27 Oct 2017, 07:2527 Oct 2017 | 27 Oct 2017, 07:35 | 8,375 ft | no position received |
| HOP507R | route not resolved | 26 Oct 2017, 18:4326 Oct 2017 | 26 Oct 2017, 19:01 | 6,850 ft | no position received |
| HOP506G | route not resolved | 26 Oct 2017, 15:4426 Oct 2017 | 26 Oct 2017, 16:32 | 18,025 ft | no position received |
| HOP73PD | route not resolved | 26 Oct 2017, 14:0926 Oct 2017 | 26 Oct 2017, 14:19 | 9,025 ft | no position received |
