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 |
|---|---|---|---|---|---|
| VLJ310L | route not resolved | 30 Jun 2017, 11:5130 Jun 2017 | 30 Jun 2017, 12:32 | 36,975 ft | no position received |
| VLJ311M | route not resolved | 26 Jun 2017, 14:0026 Jun 2017 | 26 Jun 2017, 14:23 | 27,600 ft | no position received |
| VLJ311L | route not resolved | 26 Jun 2017, 11:5826 Jun 2017 | 26 Jun 2017, 12:21 | 32,125 ft | no position received |
| VLJ312M | route not resolved | 25 Jun 2017, 20:0825 Jun 2017 | 25 Jun 2017, 20:38 | 24,650 ft | no position received |
| VLJ291M | route not resolved | 23 Jun 2017, 17:4023 Jun 2017 | 23 Jun 2017, 17:51 | 26,975 ft | no position received |
| VLJ312M | route not resolved | 22 Jun 2017, 15:3722 Jun 2017 | 22 Jun 2017, 16:15 | 24,475 ft | no position received |
| VLJ312L | route not resolved | 22 Jun 2017, 13:3622 Jun 2017 | 22 Jun 2017, 13:58 | 31,000 ft | no position received |
| VLJ307M | route not resolved | 21 Jun 2017, 16:2221 Jun 2017 | 21 Jun 2017, 16:44 | 25,975 ft | no position received |
| VLJ307L | route not resolved | 21 Jun 2017, 09:3321 Jun 2017 | 21 Jun 2017, 09:50 | 18,700 ft | no position received |
| VLJ284L | route not resolved | 16 Jun 2017, 18:1416 Jun 2017 | 16 Jun 2017, 18:35 | 32,950 ft | no position received |
| VLJ285M | route not resolved | 12 Jun 2017, 15:1912 Jun 2017 | 12 Jun 2017, 15:49 | 26,125 ft | no position received |
| VLJ285L | route not resolved | 12 Jun 2017, 10:4212 Jun 2017 | 12 Jun 2017, 11:00 | 26,475 ft | no position received |
| VLJ261M | route not resolved | 11 Jun 2017, 10:4611 Jun 2017 | 11 Jun 2017, 12:33 | 20,775 ft | no position received |
| VLJ265S | route not resolved | 10 Jun 2017, 22:0910 Jun 2017 | 10 Jun 2017, 22:45 | 21,650 ft | no position received |
| VLJ265L | route not resolved | 6 Jun 2017, 12:116 Jun 2017 | 6 Jun 2017, 12:30 | 32,950 ft | no position received |
| VLJ258N | route not resolved | 5 Jun 2017, 14:425 Jun 2017 | 5 Jun 2017, 15:15 | 27,175 ft | no position received |
| VLJ256L | route not resolved | 4 Jun 2017, 08:574 Jun 2017 | 4 Jun 2017, 09:18 | 34,975 ft | no position received |
| VLJ258M | route not resolved | 3 Jun 2017, 17:113 Jun 2017 | 3 Jun 2017, 17:43 | 25,500 ft | no position received |
| VLJ258L | route not resolved | 3 Jun 2017, 14:083 Jun 2017 | 3 Jun 2017, 14:25 | 12,775 ft | no position received |
| VLJ259N | route not resolved | 31 May 2017, 06:1831 May 2017 | 31 May 2017, 06:20 | 33,975 ft | no position received |
| VLJ259M | route not resolved | 31 May 2017, 00:5231 May 2017 | 31 May 2017, 01:25 | 37,000 ft | no position received |
| VLJ006M | route not resolved | 20 Jan 2017, 18:3520 Jan 2017 | 20 Jan 2017, 19:05 | 21,400 ft | no position received |
| VLJ006L | route not resolved | 20 Jan 2017, 10:2420 Jan 2017 | 20 Jan 2017, 10:56 | 23,050 ft | no position received |
| VLJ017M | route not resolved | 11 Jan 2017, 17:0511 Jan 2017 | 11 Jan 2017, 17:37 | 23,975 ft | no position received |
| VLJ017L | route not resolved | 11 Jan 2017, 10:0611 Jan 2017 | 11 Jan 2017, 10:37 | 1,200 ft | no position received |
