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 |
|---|---|---|---|---|---|
| HOP42ZX | route not resolved | 13 Mar 2017, 09:0713 Mar 2017 | 13 Mar 2017, 09:37 | 18,000 ft | no position received |
| HOP41VY | route not resolved | 13 Mar 2017, 07:0913 Mar 2017 | 13 Mar 2017, 07:51 | 6,025 ft | no position received |
| HOP48YT | route not resolved | 12 Mar 2017, 20:4012 Mar 2017 | 12 Mar 2017, 21:00 | 18,050 ft | no position received |
| HOP07ZF | route not resolved | 12 Mar 2017, 19:0612 Mar 2017 | 12 Mar 2017, 19:12 | 11,350 ft | no position received |
| not transmitted | route not resolved | 12 Mar 2017, 14:2312 Mar 2017 | 12 Mar 2017, 14:26 | 10,875 ft | no position received |
| HOP58RK | route not resolved | 10 Mar 2017, 21:5610 Mar 2017 | 10 Mar 2017, 22:03 | 12,975 ft | no position received |
| HOP47KT | route not resolved | 10 Mar 2017, 18:3010 Mar 2017 | 10 Mar 2017, 19:04 | 5,150 ft | no position received |
| HOP46YT | route not resolved | 10 Mar 2017, 16:0410 Mar 2017 | 10 Mar 2017, 16:32 | 18,050 ft | no position received |
| HOP73PD | route not resolved | 10 Mar 2017, 14:1810 Mar 2017 | 10 Mar 2017, 14:52 | 28,975 ft | no position received |
| HOP71SC | route not resolved | 10 Mar 2017, 07:3810 Mar 2017 | 10 Mar 2017, 07:56 | 9,550 ft | no position received |
| HOP71SC | route not resolved | 9 Mar 2017, 07:359 Mar 2017 | 9 Mar 2017, 07:42 | 10,225 ft | no position received |
| HOP76LU | route not resolved | 8 Mar 2017, 15:438 Mar 2017 | 8 Mar 2017, 15:51 | 19,050 ft | no position received |
| HOP41VY | route not resolved | 8 Mar 2017, 07:408 Mar 2017 | 8 Mar 2017, 08:08 | 10,175 ft | no position received |
| HOP48YT | route not resolved | 7 Mar 2017, 21:107 Mar 2017 | 7 Mar 2017, 21:42 | 18,000 ft | no position received |
| HOP47KT | route not resolved | 7 Mar 2017, 18:407 Mar 2017 | 7 Mar 2017, 19:12 | 6,225 ft | no position received |
| HOP46YT | route not resolved | 7 Mar 2017, 16:547 Mar 2017 | 7 Mar 2017, 17:28 | 18,075 ft | no position received |
| not transmitted | route not resolved | 7 Mar 2017, 15:367 Mar 2017 | 7 Mar 2017, 15:37 | 13,575 ft | no position received |
| HOP47KT | route not resolved | 3 Mar 2017, 18:283 Mar 2017 | 3 Mar 2017, 19:04 | 9,200 ft | no position received |
| HOP46YT | route not resolved | 3 Mar 2017, 15:453 Mar 2017 | 3 Mar 2017, 16:13 | 18,050 ft | no position received |
| HOP513D | route not resolved | 3 Mar 2017, 13:583 Mar 2017 | 3 Mar 2017, 14:17 | 7,025 ft | no position received |
| HOP13VP | route not resolved | 3 Mar 2017, 08:593 Mar 2017 | 3 Mar 2017, 09:29 | 28,000 ft | no position received |
| HOP51AE | route not resolved | 3 Mar 2017, 07:293 Mar 2017 | 3 Mar 2017, 07:38 | 10,000 ft | no position received |
| HOP58RK | route not resolved | 2 Mar 2017, 20:232 Mar 2017 | 2 Mar 2017, 20:33 | 15,000 ft | no position received |
| HOP95WI | LFJL > LFLL | 2 Mar 2017, 13:502 Mar 2017 | 2 Mar 2017, 14:25 | 7,600 ft | no position received |
| HOP42ZX | route not resolved | 2 Mar 2017, 08:472 Mar 2017 | 2 Mar 2017, 09:14 | 18,050 ft | no position received |
