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,065
- Longest contact
- 1 h 40 min
Observed callsigns
VLJ (187 contacts, 2016-2017)
Operator as per the registry of 21.07.2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| VLJ540 | route not resolved | 13 Oct 2017, 17:0013 Oct 2017 | 13 Oct 2017, 17:44 | 37,400 ft | no position received |
| VLJ540 | route not resolved | 12 Oct 2017, 14:0612 Oct 2017 | 12 Oct 2017, 14:34 | 33,000 ft | no position received |
| VLJ521 | route not resolved | 6 Oct 2017, 10:406 Oct 2017 | 6 Oct 2017, 11:32 | 32,000 ft | no position received |
| VLJ521 | route not resolved | 4 Oct 2017, 11:344 Oct 2017 | 4 Oct 2017, 12:12 | 34,000 ft | no position received |
| VLJ480 | route not resolved | 27 Sept 2017, 17:0727 Sept 2017 | 27 Sept 2017, 17:43 | 23,800 ft | no position received |
| VLJ480 | route not resolved | 26 Sept 2017, 08:2926 Sept 2017 | 26 Sept 2017, 09:03 | 27,500 ft | no position received |
| VLJ462 | route not resolved | 24 Sept 2017, 20:3324 Sept 2017 | 24 Sept 2017, 20:43 | 24,100 ft | no position received |
| not transmitted | route not resolved | 12 Aug 2017, 10:0712 Aug 2017 | 12 Aug 2017, 10:07 | not transmitted | no position received |
| VLJ405M | route not resolved | 8 Aug 2017, 17:018 Aug 2017 | 8 Aug 2017, 17:27 | 27,700 ft | no position received |
| VLJ405L | route not resolved | 8 Aug 2017, 14:268 Aug 2017 | 8 Aug 2017, 14:48 | 30,800 ft | no position received |
| VLJ392O | route not resolved | 4 Aug 2017, 18:364 Aug 2017 | 4 Aug 2017, 20:16 | 23,800 ft | no position received |
| VLJ392M | route not resolved | 3 Aug 2017, 11:153 Aug 2017 | 3 Aug 2017, 12:53 | 22,000 ft | no position received |
| VLJ383N | route not resolved | 1 Aug 2017, 12:381 Aug 2017 | 1 Aug 2017, 13:00 | 36,000 ft | no position received |
| VLJ383A | route not resolved | 29 Jul 2017, 22:3429 Jul 2017 | 29 Jul 2017, 22:38 | 35,000 ft | no position received |
| VLJ383L | route not resolved | 29 Jul 2017, 19:4929 Jul 2017 | 29 Jul 2017, 20:08 | 32,000 ft | no position received |
| VLJ393L | route not resolved | 29 Jul 2017, 16:5429 Jul 2017 | 29 Jul 2017, 17:14 | 33,000 ft | no position received |
| VLJ391P | route not resolved | 28 Jul 2017, 19:1728 Jul 2017 | 28 Jul 2017, 19:39 | 22,100 ft | no position received |
| VLJ391N | route not resolved | 28 Jul 2017, 18:2628 Jul 2017 | 28 Jul 2017, 18:49 | 3,800 ft | no position received |
| VLJ361N | route not resolved | 28 Jul 2017, 16:0428 Jul 2017 | 28 Jul 2017, 16:45 | 26,600 ft | no position received |
| VLJ361L | route not resolved | 26 Jul 2017, 08:4326 Jul 2017 | 26 Jul 2017, 09:19 | 34,000 ft | no position received |
| VLJ375N | route not resolved | 23 Jul 2017, 13:0023 Jul 2017 | 23 Jul 2017, 13:01 | 32,000 ft | no position received |
| VLJ375M | route not resolved | 22 Jul 2017, 12:1822 Jul 2017 | 22 Jul 2017, 12:34 | 31,100 ft | no position received |
| VLJ376M | route not resolved | 21 Jul 2017, 12:4821 Jul 2017 | 21 Jul 2017, 13:06 | 37,000 ft | no position received |
| VLJ348P | route not resolved | 19 Jul 2017, 23:4419 Jul 2017 | 20 Jul 2017, 00:18 | 22,200 ft | no position received |
| VLJ348L | route not resolved | 19 Jul 2017, 07:4319 Jul 2017 | 19 Jul 2017, 08:14 | 22,700 ft | no position received |
