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 |
|---|---|---|---|---|---|
| VLJ419M | route not resolved | 28 Aug 2017, 11:4528 Aug 2017 | 28 Aug 2017, 12:19 | 25,950 ft | no position received |
| VLJ419L | route not resolved | 28 Aug 2017, 09:0728 Aug 2017 | 28 Aug 2017, 09:27 | 32,025 ft | no position received |
| VLJ429L | route not resolved | 24 Aug 2017, 12:5124 Aug 2017 | 24 Aug 2017, 13:26 | 32,975 ft | no position received |
| VLJ417L | route not resolved | 15 Aug 2017, 10:3415 Aug 2017 | 15 Aug 2017, 10:39 | 33,975 ft | no position received |
| VLJ417L | route not resolved | 15 Aug 2017, 08:0515 Aug 2017 | 15 Aug 2017, 08:27 | 29,675 ft | no position received |
| VLJ401M | route not resolved | 13 Aug 2017, 18:1913 Aug 2017 | 13 Aug 2017, 18:42 | 25,875 ft | no position received |
| VLJ404M | route not resolved | 12 Aug 2017, 21:5112 Aug 2017 | 12 Aug 2017, 21:56 | 34,975 ft | no position received |
| VLJ404 | route not resolved | 12 Aug 2017, 13:5612 Aug 2017 | 12 Aug 2017, 14:15 | 32,025 ft | no position received |
| VLJ401L | route not resolved | 11 Aug 2017, 17:3311 Aug 2017 | 11 Aug 2017, 17:53 | 34,050 ft | no position received |
| FGLTK | route not resolved | 6 Aug 2017, 21:146 Aug 2017 | 6 Aug 2017, 21:45 | 25,925 ft | no position received |
| VLJ368M | route not resolved | 6 Aug 2017, 19:246 Aug 2017 | 6 Aug 2017, 19:42 | 30,975 ft | no position received |
| VLJ368M | route not resolved | 6 Aug 2017, 10:566 Aug 2017 | 6 Aug 2017, 11:26 | 34,000 ft | no position received |
| VLJ368L | route not resolved | 6 Aug 2017, 08:336 Aug 2017 | 6 Aug 2017, 08:58 | 31,000 ft | no position received |
| VLJ380M | route not resolved | 5 Aug 2017, 16:525 Aug 2017 | 5 Aug 2017, 17:20 | 31,975 ft | no position received |
| VLJ298P | route not resolved | 5 Aug 2017, 10:235 Aug 2017 | 5 Aug 2017, 10:43 | 31,000 ft | no position received |
| VLJ298M | route not resolved | 5 Aug 2017, 08:455 Aug 2017 | 5 Aug 2017, 09:05 | 5,550 ft | no position received |
| VLJ340M | route not resolved | 30 Jul 2017, 17:2230 Jul 2017 | 30 Jul 2017, 17:53 | 33,975 ft | no position received |
| VLJ340L | route not resolved | 30 Jul 2017, 13:3330 Jul 2017 | 30 Jul 2017, 13:57 | 34,975 ft | no position received |
| VLJ360P | route not resolved | 26 Jul 2017, 16:1126 Jul 2017 | 26 Jul 2017, 16:45 | 20,125 ft | no position received |
| VLJ360 | route not resolved | 24 Jul 2017, 12:0224 Jul 2017 | 24 Jul 2017, 12:23 | 31,000 ft | no position received |
| VLJ366L | route not resolved | 20 Jul 2017, 19:4620 Jul 2017 | 20 Jul 2017, 20:14 | 33,075 ft | no position received |
| VLJ362P | route not resolved | 16 Jul 2017, 18:1916 Jul 2017 | 16 Jul 2017, 18:45 | 26,575 ft | no position received |
| VLJ340M | route not resolved | 15 Jul 2017, 15:1615 Jul 2017 | 15 Jul 2017, 15:37 | 36,975 ft | no position received |
| VLJ358Q | route not resolved | 10 Jul 2017, 18:0510 Jul 2017 | 10 Jul 2017, 18:43 | 22,900 ft | no position received |
| not transmitted | route not resolved | 5 Jul 2017, 16:455 Jul 2017 | 5 Jul 2017, 16:47 | 34,975 ft | no position received |
