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,667 of 57,178
- Longest contact
- 1 h 40 min
Observed callsigns
VLJ (187 contacts, 2016-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 |
|---|---|---|---|---|---|
| VLJ374L | route not resolved | 7 Aug 2016, 11:207 Aug 2016 | 7 Aug 2016, 11:39 | 31,000 ft | no position received |
| VLJ387M | route not resolved | 2 Aug 2016, 21:232 Aug 2016 | 2 Aug 2016, 21:52 | 26,000 ft | no position received |
| VLJ387L | route not resolved | 2 Aug 2016, 15:062 Aug 2016 | 2 Aug 2016, 15:24 | 32,000 ft | no position received |
| VLJ367L | route not resolved | 1 Aug 2016, 17:491 Aug 2016 | 1 Aug 2016, 18:07 | 32,000 ft | no position received |
| VLJ351L | route not resolved | 19 Jul 2016, 11:3719 Jul 2016 | 19 Jul 2016, 11:57 | 31,400 ft | no position received |
| VLJ291M | route not resolved | 17 Jul 2016, 18:1317 Jul 2016 | 17 Jul 2016, 18:41 | 26,800 ft | no position received |
| VLJ291L | route not resolved | 17 Jul 2016, 13:4617 Jul 2016 | 17 Jul 2016, 14:15 | 35,000 ft | no position received |
| VLJ333M | route not resolved | 12 Jul 2016, 18:1412 Jul 2016 | 12 Jul 2016, 18:18 | 18,000 ft | no position received |
| VLJ301N | route not resolved | 8 Jul 2016, 01:288 Jul 2016 | 8 Jul 2016, 02:07 | 28,900 ft | no position received |
| VLJ301M | route not resolved | 7 Jul 2016, 17:247 Jul 2016 | 7 Jul 2016, 17:36 | 19,000 ft | no position received |
| VLJ275M | route not resolved | 6 Jul 2016, 11:576 Jul 2016 | 6 Jul 2016, 12:40 | 32,000 ft | no position received |
| VLJ275L | route not resolved | 6 Jul 2016, 10:296 Jul 2016 | 6 Jul 2016, 10:57 | 1,200 ft | no position received |
| VLJ316N | route not resolved | 3 Jul 2016, 19:123 Jul 2016 | 3 Jul 2016, 19:39 | 26,500 ft | no position received |
| VLJ316L | route not resolved | 1 Jul 2016, 12:161 Jul 2016 | 1 Jul 2016, 12:37 | 33,000 ft | no position received |
| VLJ313M | route not resolved | 29 Jun 2016, 09:5729 Jun 2016 | 29 Jun 2016, 10:18 | 32,000 ft | no position received |
| VLJ313L | route not resolved | 28 Jun 2016, 09:2128 Jun 2016 | 28 Jun 2016, 09:38 | 29,000 ft | no position received |
| VLJ289M | route not resolved | 19 Jun 2016, 15:3219 Jun 2016 | 19 Jun 2016, 16:04 | 25,200 ft | no position received |
| VLJ289L | route not resolved | 17 Jun 2016, 11:5817 Jun 2016 | 17 Jun 2016, 12:12 | 33,000 ft | no position received |
| VLJ280M | route not resolved | 15 Jun 2016, 13:5215 Jun 2016 | 15 Jun 2016, 14:24 | 22,000 ft | no position received |
| VLJ280L | route not resolved | 15 Jun 2016, 12:3415 Jun 2016 | 15 Jun 2016, 13:03 | 1,700 ft | no position received |
| VLJ244L | route not resolved | 9 Jun 2016, 07:209 Jun 2016 | 9 Jun 2016, 08:04 | 34,000 ft | no position received |
| VLJ243L | route not resolved | 8 Jun 2016, 06:578 Jun 2016 | 8 Jun 2016, 07:28 | 28,500 ft | no position received |
| VLJ260N | route not resolved | 7 Jun 2016, 19:567 Jun 2016 | 7 Jun 2016, 20:23 | 27,000 ft | no position received |
| VLJ253M | route not resolved | 5 Jun 2016, 19:075 Jun 2016 | 5 Jun 2016, 19:38 | 26,500 ft | no position received |
| VLJ253L | route not resolved | 3 Jun 2016, 18:303 Jun 2016 | 3 Jun 2016, 18:47 | 28,300 ft | no position received |
