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,312
- 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 |
|---|---|---|---|---|---|
| HOP507R | route not resolved | 9 May 2017, 18:369 May 2017 | 9 May 2017, 18:46 | 9,175 ft | no position received |
| HOP506G | route not resolved | 9 May 2017, 15:339 May 2017 | 9 May 2017, 15:54 | 21,000 ft | no position received |
| HOP73PD | route not resolved | 9 May 2017, 14:099 May 2017 | 9 May 2017, 14:12 | 11,200 ft | no position received |
| AFR74UE | route not resolved | 9 May 2017, 07:359 May 2017 | 9 May 2017, 07:57 | 26,000 ft | no position received |
| HOP58RK | route not resolved | 8 May 2017, 20:368 May 2017 | 8 May 2017, 20:43 | 14,675 ft | no position received |
| not transmitted | route not resolved | 8 May 2017, 18:498 May 2017 | 8 May 2017, 18:52 | 12,000 ft | no position received |
| not transmitted | route not resolved | 8 May 2017, 15:478 May 2017 | 8 May 2017, 15:51 | 18,625 ft | no position received |
| HOP73PD | route not resolved | 8 May 2017, 14:128 May 2017 | 8 May 2017, 14:19 | 10,100 ft | no position received |
| HOP8600 | route not resolved | 6 May 2017, 12:006 May 2017 | 6 May 2017, 12:10 | 18,050 ft | no position received |
| HOP71SC | route not resolved | 6 May 2017, 08:236 May 2017 | 6 May 2017, 08:27 | 15,275 ft | no position received |
| HOP47FX | route not resolved | 5 May 2017, 18:195 May 2017 | 5 May 2017, 19:00 | 28,000 ft | no position received |
| HOP46YT | route not resolved | 5 May 2017, 16:075 May 2017 | 5 May 2017, 16:36 | 16,825 ft | no position received |
| HOP95WI | LFJL > LFLL | 5 May 2017, 13:445 May 2017 | 5 May 2017, 14:21 | 5,500 ft | no position received |
| HOP42ZX | route not resolved | 5 May 2017, 09:145 May 2017 | 5 May 2017, 09:43 | 17,000 ft | no position received |
| not transmitted | route not resolved | 4 May 2017, 16:124 May 2017 | 4 May 2017, 16:12 | not transmitted | no position received |
| HOP73PD | route not resolved | 4 May 2017, 14:124 May 2017 | 4 May 2017, 14:32 | 6,775 ft | no position received |
| HOP72LD | LFLL > LFBP | 4 May 2017, 08:504 May 2017 | 4 May 2017, 09:11 | 25,375 ft | no position received |
| HOP71SC | route not resolved | 4 May 2017, 07:264 May 2017 | 4 May 2017, 07:36 | 10,000 ft | no position received |
| not transmitted | route not resolved | 3 May 2017, 20:193 May 2017 | 3 May 2017, 20:29 | 32,000 ft | no position received |
| HOP47FX | route not resolved | 3 May 2017, 18:143 May 2017 | 3 May 2017, 18:45 | 10,100 ft | no position received |
| HOP42ZX | route not resolved | 3 May 2017, 09:223 May 2017 | 3 May 2017, 09:49 | 18,000 ft | no position received |
| HOP47FX | route not resolved | 2 May 2017, 18:062 May 2017 | 2 May 2017, 18:40 | 10,075 ft | no position received |
| HOP46YT | route not resolved | 2 May 2017, 15:462 May 2017 | 2 May 2017, 16:20 | 18,050 ft | no position received |
| HOP4503 | route not resolved | 2 May 2017, 13:572 May 2017 | 2 May 2017, 14:16 | 4,950 ft | no position received |
| HOP502U | route not resolved | 2 May 2017, 09:382 May 2017 | 2 May 2017, 09:54 | 21,000 ft | no position received |
