Back to the log
Aircraft
F-HAJV
Regularnot seen for 8 years
The station's story
Address not received since 13 Oct 2017. The marker states the absence, it does not say why.
- Cumulative contact time
- 89 h
- Distinct days
- 127
- Highest captured altitude
- 38,000 ft
- Discovery rank
- #1,666 of 57,078
- Longest contact
- 1 h 40 min
Observed callsigns
VLJ (187 contacts, 2016-2017)
Operator as per the registry of 29 Jul 2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| VLJ362M | route not resolved | 13 Jul 2017, 19:5113 Jul 2017 | 13 Jul 2017, 20:20 | 27,200 ft | no position received |
| VLJ362L | route not resolved | 13 Jul 2017, 18:0213 Jul 2017 | 13 Jul 2017, 18:22 | 33,200 ft | no position received |
| VLJ328M | route not resolved | 13 Jul 2017, 10:1013 Jul 2017 | 13 Jul 2017, 10:42 | 24,200 ft | no position received |
| VLJ328L | route not resolved | 13 Jul 2017, 07:3513 Jul 2017 | 13 Jul 2017, 07:56 | 34,000 ft | no position received |
| VLJ342P | route not resolved | 10 Jul 2017, 19:2710 Jul 2017 | 10 Jul 2017, 20:00 | 22,600 ft | no position received |
| VLJ342L | route not resolved | 10 Jul 2017, 14:5710 Jul 2017 | 10 Jul 2017, 15:26 | 35,000 ft | no position received |
| VLJ327M | route not resolved | 7 Jul 2017, 20:327 Jul 2017 | 7 Jul 2017, 20:52 | 30,600 ft | no position received |
| VLJ186M | route not resolved | 3 Jul 2017, 16:523 Jul 2017 | 3 Jul 2017, 17:27 | 27,500 ft | no position received |
| VLJ186L | route not resolved | 1 Jul 2017, 11:321 Jul 2017 | 1 Jul 2017, 11:53 | 33,000 ft | no position received |
| VLJ334L | route not resolved | 29 Jun 2017, 07:2829 Jun 2017 | 29 Jun 2017, 07:46 | 25,200 ft | no position received |
| VLJ303M | route not resolved | 25 Jun 2017, 18:3325 Jun 2017 | 25 Jun 2017, 19:03 | 25,900 ft | no position received |
| VLJ303P | route not resolved | 25 Jun 2017, 12:4225 Jun 2017 | 25 Jun 2017, 12:59 | 32,200 ft | no position received |
| VLJ303N | route not resolved | 23 Jun 2017, 21:0823 Jun 2017 | 23 Jun 2017, 21:37 | 23,200 ft | no position received |
| VLJ303L | route not resolved | 23 Jun 2017, 18:2023 Jun 2017 | 23 Jun 2017, 18:44 | 32,700 ft | no position received |
| VLJ275N | route not resolved | 22 Jun 2017, 18:1922 Jun 2017 | 22 Jun 2017, 18:43 | 28,100 ft | no position received |
| VLJ275M | route not resolved | 22 Jun 2017, 11:2422 Jun 2017 | 22 Jun 2017, 11:41 | 3,800 ft | no position received |
| VLJ275L | route not resolved | 22 Jun 2017, 07:2622 Jun 2017 | 22 Jun 2017, 07:48 | 34,100 ft | no position received |
| VLJ099M | route not resolved | 20 Jun 2017, 17:1720 Jun 2017 | 20 Jun 2017, 17:53 | 26,400 ft | no position received |
| VLJ099L | route not resolved | 20 Jun 2017, 09:0620 Jun 2017 | 20 Jun 2017, 09:25 | 21,400 ft | no position received |
| VLJ284N | route not resolved | 18 Jun 2017, 18:0718 Jun 2017 | 18 Jun 2017, 18:33 | 26,100 ft | no position received |
| VLJ284M | route not resolved | 18 Jun 2017, 13:1818 Jun 2017 | 18 Jun 2017, 13:40 | 33,000 ft | no position received |
| VLJ257M | route not resolved | 5 Jun 2017, 18:085 Jun 2017 | 5 Jun 2017, 18:32 | 28,800 ft | no position received |
| VLJ257P | route not resolved | 5 Jun 2017, 15:345 Jun 2017 | 5 Jun 2017, 15:56 | 31,400 ft | no position received |
| VLJ273L | route not resolved | 4 Jun 2017, 13:114 Jun 2017 | 4 Jun 2017, 13:29 | 32,700 ft | no position received |
| VLJ257N | route not resolved | 2 Jun 2017, 20:452 Jun 2017 | 2 Jun 2017, 21:13 | 23,800 ft | no position received |
