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 |
|---|---|---|---|---|---|
| VLJ142M | route not resolved | 22 Feb 2018, 10:5422 Feb 2018 | 22 Feb 2018, 10:59 | 5,675 ft | no position received |
| VLJ105K | route not resolved | 18 Feb 2018, 18:4118 Feb 2018 | 18 Feb 2018, 19:03 | 26,925 ft | no position received |
| VLJ105K | route not resolved | 18 Feb 2018, 11:2118 Feb 2018 | 18 Feb 2018, 11:38 | 32,975 ft | no position received |
| VLJ109Z | route not resolved | 14 Feb 2018, 08:0314 Feb 2018 | 14 Feb 2018, 08:27 | 31,475 ft | no position received |
| VLJ110M | route not resolved | 13 Feb 2018, 12:1213 Feb 2018 | 13 Feb 2018, 13:53 | 23,300 ft | no position received |
| VLJ673K | route not resolved | 7 Jan 2018, 15:477 Jan 2018 | 7 Jan 2018, 16:04 | 28,825 ft | no position received |
| VLJ673K | route not resolved | 6 Jan 2018, 18:186 Jan 2018 | 6 Jan 2018, 18:37 | 36,150 ft | no position received |
| VLJ656K | route not resolved | 6 Jan 2018, 15:096 Jan 2018 | 6 Jan 2018, 15:33 | 29,950 ft | no position received |
| VLJ656K | route not resolved | 6 Jan 2018, 14:126 Jan 2018 | 6 Jan 2018, 14:24 | 6,350 ft | no position received |
| VLJ563 | route not resolved | 27 Oct 2017, 09:5727 Oct 2017 | 27 Oct 2017, 10:29 | 32,000 ft | no position received |
| VLJ563 | route not resolved | 26 Oct 2017, 14:5626 Oct 2017 | 26 Oct 2017, 15:15 | 34,025 ft | no position received |
| VLJ522 | route not resolved | 4 Oct 2017, 21:224 Oct 2017 | 4 Oct 2017, 21:58 | 27,875 ft | no position received |
| not transmitted | route not resolved | 4 Oct 2017, 19:314 Oct 2017 | 4 Oct 2017, 19:33 | 32,950 ft | no position received |
| VLJ515 | route not resolved | 30 Sept 2017, 19:2030 Sept 2017 | 30 Sept 2017, 19:52 | 27,125 ft | no position received |
| VLJ505 | route not resolved | 29 Sept 2017, 15:3029 Sept 2017 | 29 Sept 2017, 16:06 | 34,975 ft | no position received |
| VLJ505 | route not resolved | 26 Sept 2017, 15:0226 Sept 2017 | 26 Sept 2017, 15:39 | 21,150 ft | no position received |
| VLJ505 | route not resolved | 26 Sept 2017, 08:2326 Sept 2017 | 26 Sept 2017, 08:57 | 34,975 ft | no position received |
| VLJ439M | route not resolved | 9 Sept 2017, 13:579 Sept 2017 | 9 Sept 2017, 14:31 | 24,625 ft | no position received |
| VLJ439L | route not resolved | 9 Sept 2017, 09:449 Sept 2017 | 9 Sept 2017, 10:09 | 32,975 ft | no position received |
| VLJ422M | route not resolved | 3 Sept 2017, 18:183 Sept 2017 | 3 Sept 2017, 18:44 | 27,150 ft | no position received |
| VLJ422L | route not resolved | 3 Sept 2017, 13:263 Sept 2017 | 3 Sept 2017, 13:43 | 34,050 ft | no position received |
| VLJ429M | route not resolved | 1 Sept 2017, 22:321 Sept 2017 | 1 Sept 2017, 22:56 | 28,650 ft | no position received |
| VLJ422N | route not resolved | 1 Sept 2017, 17:481 Sept 2017 | 1 Sept 2017, 18:09 | 33,525 ft | no position received |
| VLJ433N | route not resolved | 31 Aug 2017, 12:5931 Aug 2017 | 31 Aug 2017, 13:21 | 26,675 ft | no position received |
| VLJ433L | route not resolved | 30 Aug 2017, 16:3830 Aug 2017 | 30 Aug 2017, 16:44 | 38,975 ft | no position received |
