Back to the log
Aircraft
F-GLTK
Common
The station's story
Address not received since 13 Mar 2023. The marker states the absence, it does not say why.
- Cumulative contact time
- 223 h
- Distinct days
- 367
- Highest captured altitude
- 40,975 ft
- 1 corrupted frame(s) excluded from this maximum
- Discovery rank
- #3,476 of 57,441
- Longest contact
- 1 h 47 min
Observed callsigns
VLJ (504 contacts, 2016-2023) · DBT (23 contacts, 2023)
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 |
|---|---|---|---|---|---|
| VLJ07EK | route not resolved | 10 May 2019, 09:2910 May 2019 | 10 May 2019, 09:37 | 32,975 ft | no position received |
| VLJ12EK | route not resolved | 7 May 2019, 20:347 May 2019 | 7 May 2019, 21:22 | 23,350 ft | no position received |
| VLJ12EK | route not resolved | 7 May 2019, 18:277 May 2019 | 7 May 2019, 18:57 | 32,950 ft | no position received |
| VLJ88DK | route not resolved | 29 Apr 2019, 08:3729 Apr 2019 | 29 Apr 2019, 09:02 | 27,175 ft | no position received |
| VLJ88DK | route not resolved | 29 Apr 2019, 02:1129 Apr 2019 | 29 Apr 2019, 02:28 | 34,950 ft | no position received |
| VLJ67CM | route not resolved | 30 Mar 2019, 16:3930 Mar 2019 | 30 Mar 2019, 17:05 | 29,350 ft | no position received |
| VLJ67CM | route not resolved | 29 Mar 2019, 11:1829 Mar 2019 | 29 Mar 2019, 11:40 | 34,975 ft | no position received |
| VLJ53BR | route not resolved | 28 Mar 2019, 16:4828 Mar 2019 | 28 Mar 2019, 17:10 | 35,950 ft | no position received |
| VLJ53BR | route not resolved | 28 Mar 2019, 14:5728 Mar 2019 | 28 Mar 2019, 15:14 | 10,675 ft | no position received |
| VLJ63CM | route not resolved | 27 Mar 2019, 16:2427 Mar 2019 | 27 Mar 2019, 16:40 | 18,025 ft | no position received |
| VLJ63CM | route not resolved | 27 Mar 2019, 09:2027 Mar 2019 | 27 Mar 2019, 09:34 | 9,500 ft | no position received |
| VLJ48CM | route not resolved | 25 Mar 2019, 19:4625 Mar 2019 | 25 Mar 2019, 20:06 | 29,050 ft | no position received |
| VLJ48CM | route not resolved | 25 Mar 2019, 10:3625 Mar 2019 | 25 Mar 2019, 10:42 | 34,975 ft | no position received |
| VLJ41CG | route not resolved | 23 Mar 2019, 08:3723 Mar 2019 | 23 Mar 2019, 08:40 | 16,700 ft | no position received |
| VLJ25BK | route not resolved | 24 Feb 2019, 17:1524 Feb 2019 | 24 Feb 2019, 17:32 | 34,000 ft | no position received |
| VLJ52BK | route not resolved | 23 Feb 2019, 12:3523 Feb 2019 | 23 Feb 2019, 13:06 | 31,975 ft | no position received |
| VLJ52BK | route not resolved | 23 Feb 2019, 10:2123 Feb 2019 | 23 Feb 2019, 10:55 | 16,575 ft | no position received |
| VLJ782Z | route not resolved | 16 Oct 2018, 17:2516 Oct 2018 | 16 Oct 2018, 17:43 | 17,975 ft | no position received |
| VLJ782Z | route not resolved | 16 Oct 2018, 16:3616 Oct 2018 | 16 Oct 2018, 16:54 | 7,000 ft | no position received |
| not transmitted | route not resolved | 13 Oct 2018, 22:2813 Oct 2018 | 13 Oct 2018, 22:51 | 27,850 ft | no position received |
| VLJ779G | route not resolved | 13 Oct 2018, 13:4113 Oct 2018 | 13 Oct 2018, 14:16 | 1,200 ft | no position received |
| VLJ725K | route not resolved | 3 Oct 2018, 00:133 Oct 2018 | 3 Oct 2018, 00:21 | 31,975 ft | no position received |
| VLJ672K | route not resolved | 27 Sept 2018, 17:0027 Sept 2018 | 27 Sept 2018, 17:30 | 20,900 ft | no position received |
| VLJ672K | route not resolved | 27 Sept 2018, 09:3127 Sept 2018 | 27 Sept 2018, 09:56 | 32,950 ft | no position received |
| VLJ702Z | route not resolved | 26 Sept 2018, 17:5726 Sept 2018 | 26 Sept 2018, 18:28 | 23,625 ft | no position received |
