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 |
|---|---|---|---|---|---|
| VLJ609Q | route not resolved | 9 Jan 2017, 19:139 Jan 2017 | 9 Jan 2017, 19:45 | 26,000 ft | no position received |
| VLJ609P | route not resolved | 4 Jan 2017, 11:354 Jan 2017 | 4 Jan 2017, 11:47 | 28,400 ft | no position received |
| not transmitted | route not resolved | 3 Jan 2017, 12:593 Jan 2017 | 3 Jan 2017, 13:01 | not transmitted | no position received |
| VLJ609M | route not resolved | 3 Jan 2017, 09:503 Jan 2017 | 3 Jan 2017, 10:06 | 28,975 ft | no position received |
| VLJ616L | route not resolved | 27 Dec 2016, 13:3227 Dec 2016 | 27 Dec 2016, 13:45 | 34,975 ft | no position received |
| VLJ614P | route not resolved | 23 Dec 2016, 13:5123 Dec 2016 | 23 Dec 2016, 14:17 | 21,975 ft | no position received |
| VLJ614N | route not resolved | 23 Dec 2016, 10:4223 Dec 2016 | 23 Dec 2016, 11:17 | 3,375 ft | no position received |
| VLJ614M | route not resolved | 22 Dec 2016, 15:1622 Dec 2016 | 22 Dec 2016, 15:56 | 29,450 ft | no position received |
| VLJ613M | route not resolved | 20 Dec 2016, 16:5220 Dec 2016 | 20 Dec 2016, 17:22 | 24,425 ft | no position received |
| VLJ613L | route not resolved | 19 Dec 2016, 17:1619 Dec 2016 | 19 Dec 2016, 17:43 | 32,950 ft | no position received |
| VLJ539M | route not resolved | 1 Dec 2016, 19:461 Dec 2016 | 1 Dec 2016, 20:22 | 23,875 ft | no position received |
| VLJ539P | route not resolved | 1 Dec 2016, 15:421 Dec 2016 | 1 Dec 2016, 16:13 | 27,000 ft | no position received |
| VLJ539N | route not resolved | 24 Nov 2016, 13:5324 Nov 2016 | 24 Nov 2016, 14:19 | 23,800 ft | no position received |
| VLJ539L | route not resolved | 24 Nov 2016, 10:4724 Nov 2016 | 24 Nov 2016, 11:13 | 28,075 ft | no position received |
| VLJ558M | route not resolved | 18 Nov 2016, 20:3118 Nov 2016 | 18 Nov 2016, 21:02 | 29,475 ft | no position received |
| VLJ559M | route not resolved | 16 Nov 2016, 13:5116 Nov 2016 | 16 Nov 2016, 14:28 | 27,225 ft | no position received |
| VLJ531M | route not resolved | 13 Nov 2016, 18:4813 Nov 2016 | 13 Nov 2016, 19:24 | 23,600 ft | no position received |
| VLJ531L | route not resolved | 11 Nov 2016, 10:1111 Nov 2016 | 11 Nov 2016, 10:48 | 34,925 ft | no position received |
| VLJ532M | route not resolved | 4 Nov 2016, 08:174 Nov 2016 | 4 Nov 2016, 08:53 | 21,825 ft | no position received |
| VLJ532L | route not resolved | 3 Nov 2016, 08:453 Nov 2016 | 3 Nov 2016, 09:13 | 29,975 ft | no position received |
| VLJ528N | route not resolved | 1 Nov 2016, 18:441 Nov 2016 | 1 Nov 2016, 19:13 | 24,000 ft | no position received |
| VLJ528L | route not resolved | 28 Oct 2016, 16:3428 Oct 2016 | 28 Oct 2016, 16:54 | 32,925 ft | no position received |
| VLJ530N | route not resolved | 27 Oct 2016, 17:4727 Oct 2016 | 27 Oct 2016, 18:21 | 23,000 ft | no position received |
| VLJ530M | route not resolved | 27 Oct 2016, 08:5127 Oct 2016 | 27 Oct 2016, 09:30 | 875 ft | no position received |
| VLJ505M | route not resolved | 17 Oct 2016, 17:5717 Oct 2016 | 17 Oct 2016, 18:23 | 23,625 ft | no position received |
