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,065
- 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 |
|---|---|---|---|---|---|
| VLJ355Z | route not resolved | 24 May 2018, 16:5524 May 2018 | 24 May 2018, 17:01 | 22,875 ft | no position received |
| VLJ287Z | route not resolved | 21 May 2018, 19:3621 May 2018 | 21 May 2018, 19:58 | 28,600 ft | no position received |
| VLJ287Z | route not resolved | 21 May 2018, 13:5021 May 2018 | 21 May 2018, 14:09 | 32,975 ft | no position received |
| VLJ287Z | route not resolved | 21 May 2018, 11:2221 May 2018 | 21 May 2018, 11:27 | 23,975 ft | no position received |
| VLJ287Z | route not resolved | 18 May 2018, 14:0518 May 2018 | 18 May 2018, 14:13 | 24,975 ft | no position received |
| VLJ328M | route not resolved | 14 May 2018, 16:1014 May 2018 | 14 May 2018, 16:13 | 33,975 ft | no position received |
| VLJ289K | route not resolved | 13 May 2018, 20:1313 May 2018 | 13 May 2018, 20:28 | 27,975 ft | no position received |
| VLJ289K | route not resolved | 13 May 2018, 10:2513 May 2018 | 13 May 2018, 10:57 | 1,475 ft | no position received |
| VLJ282M | route not resolved | 11 May 2018, 12:2611 May 2018 | 11 May 2018, 12:36 | 18,025 ft | no position received |
| VLJ318K | route not resolved | 9 May 2018, 16:029 May 2018 | 9 May 2018, 16:47 | 23,200 ft | no position received |
| VLJ296E | route not resolved | 9 May 2018, 15:069 May 2018 | 9 May 2018, 15:35 | 1,525 ft | no position received |
| VLJ296Z | route not resolved | 7 May 2018, 10:557 May 2018 | 7 May 2018, 11:10 | 35,000 ft | no position received |
| VLJ276M | route not resolved | 4 May 2018, 12:114 May 2018 | 4 May 2018, 12:43 | 27,625 ft | no position received |
| VLJ276M | route not resolved | 4 May 2018, 10:364 May 2018 | 4 May 2018, 11:10 | 34,000 ft | no position received |
| VLJ174K | route not resolved | 13 Mar 2018, 12:4313 Mar 2018 | 13 Mar 2018, 13:04 | 35,950 ft | no position received |
| VLJ174K | route not resolved | 11 Mar 2018, 00:0911 Mar 2018 | 11 Mar 2018, 00:27 | 35,975 ft | no position received |
| VLJ149Z | route not resolved | 4 Mar 2018, 13:244 Mar 2018 | 4 Mar 2018, 13:44 | 27,800 ft | no position received |
| VLJ149Z | route not resolved | 3 Mar 2018, 09:383 Mar 2018 | 3 Mar 2018, 09:55 | 34,975 ft | no position received |
| VLJ121M | route not resolved | 1 Mar 2018, 17:491 Mar 2018 | 1 Mar 2018, 18:20 | 24,700 ft | no position received |
| VLJ155 | route not resolved | 1 Mar 2018, 09:011 Mar 2018 | 1 Mar 2018, 09:33 | 33,025 ft | no position received |
| VLJ145Z | route not resolved | 27 Feb 2018, 11:5727 Feb 2018 | 27 Feb 2018, 12:26 | 33,975 ft | no position received |
| VLJ145Z | route not resolved | 27 Feb 2018, 07:4427 Feb 2018 | 27 Feb 2018, 08:17 | 34,975 ft | no position received |
| VLJ091M | route not resolved | 24 Feb 2018, 13:5524 Feb 2018 | 24 Feb 2018, 14:20 | 24,650 ft | no position received |
| VLJ091M | route not resolved | 24 Feb 2018, 11:1924 Feb 2018 | 24 Feb 2018, 11:44 | 18,775 ft | no position received |
| VLJ142M | route not resolved | 22 Feb 2018, 11:3522 Feb 2018 | 22 Feb 2018, 11:56 | 21,950 ft | no position received |
