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,172
- 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 |
|---|---|---|---|---|---|
| VLJ046L | route not resolved | 3 Feb 2017, 10:013 Feb 2017 | 3 Feb 2017, 10:30 | 17,100 ft | no position received |
| VLJ020M | route not resolved | 20 Jan 2017, 18:3920 Jan 2017 | 20 Jan 2017, 19:08 | 22,500 ft | no position received |
| VLJ015M | route not resolved | 20 Jan 2017, 15:3320 Jan 2017 | 20 Jan 2017, 15:59 | 23,100 ft | no position received |
| VLJ015L | route not resolved | 20 Jan 2017, 12:2020 Jan 2017 | 20 Jan 2017, 12:53 | 900 ft | no position received |
| VLJ015N | route not resolved | 20 Jan 2017, 09:5920 Jan 2017 | 20 Jan 2017, 10:28 | 22,600 ft | no position received |
| VLJ020L | route not resolved | 20 Jan 2017, 08:0320 Jan 2017 | 20 Jan 2017, 08:42 | 28,900 ft | no position received |
| VLJ030N | route not resolved | 18 Jan 2017, 12:3418 Jan 2017 | 18 Jan 2017, 13:08 | 22,900 ft | no position received |
| VLJ030M | route not resolved | 18 Jan 2017, 08:1918 Jan 2017 | 18 Jan 2017, 08:57 | 1,000 ft | no position received |
| VLJ504M | route not resolved | 1 Jan 2017, 14:431 Jan 2017 | 1 Jan 2017, 15:12 | 23,900 ft | no position received |
| VLJ504L | route not resolved | 26 Dec 2016, 12:3926 Dec 2016 | 26 Dec 2016, 13:00 | 33,000 ft | no position received |
| VLJ615M | route not resolved | 24 Dec 2016, 17:1924 Dec 2016 | 24 Dec 2016, 18:31 | 18,000 ft | no position received |
| VLJ557M | route not resolved | 20 Nov 2016, 18:2420 Nov 2016 | 20 Nov 2016, 18:58 | 23,600 ft | no position received |
| VLJ557L | route not resolved | 18 Nov 2016, 17:5718 Nov 2016 | 18 Nov 2016, 18:29 | 33,000 ft | no position received |
| VLJ549M | route not resolved | 17 Nov 2016, 18:0117 Nov 2016 | 17 Nov 2016, 18:34 | 26,900 ft | no position received |
| VLJ494M | route not resolved | 15 Nov 2016, 11:1015 Nov 2016 | 15 Nov 2016, 11:50 | 27,300 ft | no position received |
| VLJ554M | route not resolved | 12 Nov 2016, 18:1912 Nov 2016 | 12 Nov 2016, 19:42 | 24,000 ft | no position received |
| VLJ509M | route not resolved | 25 Oct 2016, 22:2725 Oct 2016 | 25 Oct 2016, 22:56 | 26,700 ft | no position received |
| VLJ509L | route not resolved | 25 Oct 2016, 16:0425 Oct 2016 | 25 Oct 2016, 16:26 | 28,200 ft | no position received |
| VLJ519M | route not resolved | 22 Oct 2016, 14:2722 Oct 2016 | 22 Oct 2016, 15:06 | 26,000 ft | no position received |
| VLJ519L | route not resolved | 20 Oct 2016, 15:0420 Oct 2016 | 20 Oct 2016, 15:37 | 33,000 ft | no position received |
| VLJ518M | route not resolved | 20 Oct 2016, 09:5920 Oct 2016 | 20 Oct 2016, 11:08 | 36,000 ft | no position received |
| VLJ518L | route not resolved | 20 Oct 2016, 08:2520 Oct 2016 | 20 Oct 2016, 08:54 | 1,300 ft | no position received |
| VLJ508N | route not resolved | 13 Oct 2016, 19:4813 Oct 2016 | 13 Oct 2016, 20:43 | 33,000 ft | no position received |
| VLJ508M | route not resolved | 13 Oct 2016, 08:4313 Oct 2016 | 13 Oct 2016, 09:22 | 16,100 ft | no position received |
| not transmitted | route not resolved | 11 Oct 2016, 17:0611 Oct 2016 | 11 Oct 2016, 17:11 | 22,000 ft | no position received |
