Back to the log
Aircraft
F-HGPG
Common
The station's story
- Cumulative contact time
- 197 h
- Distinct days
- 337
- Highest captured altitude
- 43,000 ft
- Discovery rank
- #19,568 of 57,294
- Longest contact
- 1 h 21 min
Observed callsigns
VLJ (474 contacts, 2016-2025) · VJL (1 contacts, 2019)
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 |
|---|---|---|---|---|---|
| VLJ351N | route not resolved | 12 Jul 2017, 14:4212 Jul 2017 | 12 Jul 2017, 14:59 | 18,000 ft | no position received |
| VLJ351M | route not resolved | 12 Jul 2017, 13:2412 Jul 2017 | 12 Jul 2017, 13:49 | 3,775 ft | no position received |
| VLJ352P | route not resolved | 9 Jul 2017, 18:379 Jul 2017 | 9 Jul 2017, 18:59 | 17,975 ft | no position received |
| VLJ352N | route not resolved | 9 Jul 2017, 14:059 Jul 2017 | 9 Jul 2017, 14:23 | 3,900 ft | no position received |
| VLJ352M | route not resolved | 9 Jul 2017, 10:499 Jul 2017 | 9 Jul 2017, 11:10 | 19,000 ft | no position received |
| VLJ352L | route not resolved | 9 Jul 2017, 09:189 Jul 2017 | 9 Jul 2017, 09:46 | 3,825 ft | no position received |
| VLJ337P | route not resolved | 3 Jul 2017, 16:563 Jul 2017 | 3 Jul 2017, 17:13 | 18,000 ft | no position received |
| VLJ337N | route not resolved | 2 Jul 2017, 12:422 Jul 2017 | 2 Jul 2017, 13:07 | 3,475 ft | no position received |
| VLJ337M | route not resolved | 2 Jul 2017, 10:272 Jul 2017 | 2 Jul 2017, 10:49 | 27,000 ft | no position received |
| VLJ337L | route not resolved | 30 Jun 2017, 17:1030 Jun 2017 | 30 Jun 2017, 17:38 | 4,050 ft | no position received |
| VLJ317M | route not resolved | 26 Jun 2017, 18:1226 Jun 2017 | 26 Jun 2017, 18:33 | 18,000 ft | no position received |
| VLJ317L | route not resolved | 21 Jun 2017, 18:4921 Jun 2017 | 21 Jun 2017, 19:08 | 4,250 ft | no position received |
| VLJ121N | route not resolved | 20 Mar 2017, 11:4820 Mar 2017 | 20 Mar 2017, 12:06 | 17,975 ft | no position received |
| VLJ121M | route not resolved | 17 Mar 2017, 18:0317 Mar 2017 | 17 Mar 2017, 18:28 | 3,800 ft | no position received |
| VLJ105N | route not resolved | 13 Mar 2017, 11:3413 Mar 2017 | 13 Mar 2017, 11:45 | 11,000 ft | no position received |
| VLJ105M | route not resolved | 11 Mar 2017, 16:1311 Mar 2017 | 11 Mar 2017, 16:42 | 3,975 ft | no position received |
| VLJ075M | route not resolved | 17 Feb 2017, 08:1917 Feb 2017 | 17 Feb 2017, 08:35 | 30,000 ft | no position received |
| VLJ075L | route not resolved | 16 Feb 2017, 16:2116 Feb 2017 | 16 Feb 2017, 16:56 | 3,375 ft | no position received |
| VLJ042P | route not resolved | 29 Jan 2017, 16:2229 Jan 2017 | 29 Jan 2017, 16:37 | 17,975 ft | no position received |
| VLJ042N | route not resolved | 26 Jan 2017, 18:4926 Jan 2017 | 26 Jan 2017, 19:12 | 3,675 ft | no position received |
| VLJ042M | route not resolved | 25 Jan 2017, 18:0025 Jan 2017 | 25 Jan 2017, 18:30 | 34,975 ft | no position received |
| VLJ042L | route not resolved | 25 Jan 2017, 16:4825 Jan 2017 | 25 Jan 2017, 17:21 | 3,575 ft | no position received |
| VLJ022U | route not resolved | 20 Jan 2017, 12:0420 Jan 2017 | 20 Jan 2017, 12:46 | 30,950 ft | no position received |
| VLJ022T | route not resolved | 20 Jan 2017, 10:3520 Jan 2017 | 20 Jan 2017, 11:02 | 3,475 ft | no position received |
| VLJ022Q | route not resolved | 18 Jan 2017, 11:3618 Jan 2017 | 18 Jan 2017, 12:16 | 35,875 ft | no position received |
