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,304
- 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 | 15 Jun 2017, 18:5315 Jun 2017 | 15 Jun 2017, 19:00 | 9,625 ft | no position received |
| HOP51AE | route not resolved | 15 Jun 2017, 07:4815 Jun 2017 | 15 Jun 2017, 07:52 | 8,250 ft | no position received |
| not transmitted | route not resolved | 14 Jun 2017, 20:3214 Jun 2017 | 14 Jun 2017, 20:35 | 14,950 ft | no position received |
| HOP07QB | route not resolved | 14 Jun 2017, 19:0114 Jun 2017 | 14 Jun 2017, 19:06 | 10,950 ft | no position received |
| HOP76LU | route not resolved | 14 Jun 2017, 16:0514 Jun 2017 | 14 Jun 2017, 16:23 | 20,200 ft | no position received |
| HOP58RK | route not resolved | 13 Jun 2017, 20:3213 Jun 2017 | 13 Jun 2017, 20:52 | 15,000 ft | no position received |
| HOP47FX | route not resolved | 13 Jun 2017, 18:1613 Jun 2017 | 13 Jun 2017, 19:03 | 13,625 ft | no position received |
| HOP46YT | route not resolved | 13 Jun 2017, 15:4413 Jun 2017 | 13 Jun 2017, 16:05 | 18,050 ft | no position received |
| HOP4503 | route not resolved | 13 Jun 2017, 14:0713 Jun 2017 | 13 Jun 2017, 14:17 | 7,475 ft | no position received |
| HOP502U | route not resolved | 13 Jun 2017, 09:0313 Jun 2017 | 13 Jun 2017, 09:26 | 21,000 ft | no position received |
| HOP58RK | route not resolved | 12 Jun 2017, 20:2512 Jun 2017 | 12 Jun 2017, 20:37 | 17,050 ft | no position received |
| not transmitted | route not resolved | 12 Jun 2017, 19:0112 Jun 2017 | 12 Jun 2017, 19:01 | 13,700 ft | no position received |
| HOP4503 | route not resolved | 12 Jun 2017, 13:5212 Jun 2017 | 12 Jun 2017, 14:12 | 25,000 ft | no position received |
| HOP502U | route not resolved | 12 Jun 2017, 09:1312 Jun 2017 | 12 Jun 2017, 09:36 | 20,325 ft | no position received |
| not transmitted | route not resolved | 11 Jun 2017, 20:4911 Jun 2017 | 11 Jun 2017, 21:03 | 16,575 ft | no position received |
| HOP87AK | LFBZ > LFLL | 11 Jun 2017, 19:2311 Jun 2017 | 11 Jun 2017, 19:26 | 16,750 ft | no position received |
| not transmitted | route not resolved | 9 Jun 2017, 18:519 Jun 2017 | 9 Jun 2017, 18:55 | 7,150 ft | no position received |
| HOP506G | route not resolved | 9 Jun 2017, 15:479 Jun 2017 | 9 Jun 2017, 16:08 | 21,000 ft | no position received |
| HOP73PD | route not resolved | 9 Jun 2017, 14:059 Jun 2017 | 9 Jun 2017, 14:16 | 10,000 ft | no position received |
| HOP71SC | route not resolved | 9 Jun 2017, 07:309 Jun 2017 | 9 Jun 2017, 07:34 | 14,475 ft | no position received |
| HOP4503 | route not resolved | 8 Jun 2017, 14:068 Jun 2017 | 8 Jun 2017, 14:27 | 6,500 ft | no position received |
| HOP502U | route not resolved | 8 Jun 2017, 09:048 Jun 2017 | 8 Jun 2017, 09:23 | 12,025 ft | no position received |
| not transmitted | route not resolved | 7 Jun 2017, 18:317 Jun 2017 | 7 Jun 2017, 18:43 | 7,175 ft | no position received |
| HOP506G | route not resolved | 7 Jun 2017, 15:427 Jun 2017 | 7 Jun 2017, 16:03 | 21,000 ft | no position received |
| not transmitted | route not resolved | 7 Jun 2017, 07:477 Jun 2017 | 7 Jun 2017, 07:49 | 10,675 ft | no position received |
