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,298
- 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 |
|---|---|---|---|---|---|
| HOP07QB | route not resolved | 6 Jun 2017, 18:486 Jun 2017 | 6 Jun 2017, 18:54 | 11,250 ft | no position received |
| not transmitted | route not resolved | 6 Jun 2017, 15:576 Jun 2017 | 6 Jun 2017, 15:57 | not transmitted | no position received |
| HOP95WI | LFJL > LFLL | 6 Jun 2017, 13:426 Jun 2017 | 6 Jun 2017, 14:27 | 7,000 ft | no position received |
| HOP42ZX | route not resolved | 6 Jun 2017, 09:266 Jun 2017 | 6 Jun 2017, 09:53 | 18,050 ft | no position received |
| HOP51AE | route not resolved | 6 Jun 2017, 07:326 Jun 2017 | 6 Jun 2017, 07:38 | 8,275 ft | no position received |
| HOP58RK | route not resolved | 5 Jun 2017, 20:345 Jun 2017 | 5 Jun 2017, 20:52 | 15,050 ft | no position received |
| HOP07QB | route not resolved | 5 Jun 2017, 19:005 Jun 2017 | 5 Jun 2017, 19:09 | 7,400 ft | no position received |
| HOP73PD | route not resolved | 5 Jun 2017, 14:125 Jun 2017 | 5 Jun 2017, 14:20 | 9,650 ft | no position received |
| HOP71SC | route not resolved | 5 Jun 2017, 07:215 Jun 2017 | 5 Jun 2017, 07:29 | 8,000 ft | no position received |
| HOP47FX | route not resolved | 2 Jun 2017, 18:252 Jun 2017 | 2 Jun 2017, 18:56 | 9,100 ft | no position received |
| HOP46YT | route not resolved | 2 Jun 2017, 15:492 Jun 2017 | 2 Jun 2017, 16:22 | 18,050 ft | no position received |
| HOP533P | route not resolved | 2 Jun 2017, 14:072 Jun 2017 | 2 Jun 2017, 14:23 | 6,375 ft | no position received |
| HOP532J | route not resolved | 2 Jun 2017, 09:492 Jun 2017 | 2 Jun 2017, 10:09 | 20,650 ft | no position received |
| not transmitted | route not resolved | 1 Jun 2017, 20:431 Jun 2017 | 1 Jun 2017, 20:47 | 10,550 ft | no position received |
| HOP87EC | LFST > LFLL | 1 Jun 2017, 18:321 Jun 2017 | 1 Jun 2017, 19:11 | 5,025 ft | no position received |
| HOP86TP | route not resolved | 1 Jun 2017, 15:571 Jun 2017 | 1 Jun 2017, 16:32 | 13,650 ft | no position received |
| HOP73PD | route not resolved | 1 Jun 2017, 14:051 Jun 2017 | 1 Jun 2017, 14:29 | 8,025 ft | no position received |
| HOP71SC | route not resolved | 1 Jun 2017, 07:361 Jun 2017 | 1 Jun 2017, 07:46 | 26,000 ft | no position received |
| HOP95WI | LFJL > LFLL | 30 May 2017, 13:4630 May 2017 | 30 May 2017, 14:30 | 5,925 ft | no position received |
| HOP42ZX | route not resolved | 30 May 2017, 09:0530 May 2017 | 30 May 2017, 09:35 | 18,000 ft | no position received |
| HOP51AE | route not resolved | 30 May 2017, 07:4530 May 2017 | 30 May 2017, 07:51 | 10,475 ft | no position received |
| HOP58RK | route not resolved | 29 May 2017, 20:2729 May 2017 | 29 May 2017, 20:40 | 15,000 ft | no position received |
| HOP07QB | route not resolved | 29 May 2017, 18:5629 May 2017 | 29 May 2017, 19:06 | 9,850 ft | no position received |
| HOP4503 | route not resolved | 29 May 2017, 14:2729 May 2017 | 29 May 2017, 14:34 | 7,025 ft | no position received |
| HOP502U | route not resolved | 29 May 2017, 09:4529 May 2017 | 29 May 2017, 10:10 | 20,000 ft | no position received |
