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 |
|---|---|---|---|---|---|
| VLJ469R | route not resolved | 13 Jul 2018, 12:3213 Jul 2018 | 13 Jul 2018, 13:37 | 33,600 ft | no position received |
| VLJ469R | route not resolved | 13 Jul 2018, 07:4213 Jul 2018 | 13 Jul 2018, 07:55 | 15,400 ft | no position received |
| VLJ504K | route not resolved | 8 Jul 2018, 21:468 Jul 2018 | 8 Jul 2018, 22:00 | 21,950 ft | no position received |
| VLJ479Z | route not resolved | 8 Jul 2018, 15:108 Jul 2018 | 8 Jul 2018, 15:37 | 32,950 ft | no position received |
| VLJ440M | route not resolved | 1 Jul 2018, 16:571 Jul 2018 | 1 Jul 2018, 17:28 | 25,025 ft | no position received |
| VLJ358Z | route not resolved | 30 Jun 2018, 15:0830 Jun 2018 | 30 Jun 2018, 15:21 | 22,950 ft | no position received |
| VLJ358Z | route not resolved | 30 Jun 2018, 14:3130 Jun 2018 | 30 Jun 2018, 14:33 | 14,200 ft | no position received |
| VLJ401K | route not resolved | 29 Jun 2018, 12:1829 Jun 2018 | 29 Jun 2018, 12:50 | 23,925 ft | no position received |
| VLJ440M | route not resolved | 27 Jun 2018, 18:1527 Jun 2018 | 27 Jun 2018, 18:41 | 25,550 ft | no position received |
| VLJ440M | route not resolved | 27 Jun 2018, 15:1827 Jun 2018 | 27 Jun 2018, 15:42 | 32,950 ft | no position received |
| VLJ448K | route not resolved | 26 Jun 2018, 19:1826 Jun 2018 | 26 Jun 2018, 19:55 | 21,525 ft | no position received |
| VLJ448K | route not resolved | 26 Jun 2018, 07:5926 Jun 2018 | 26 Jun 2018, 08:37 | 34,950 ft | no position received |
| VLJ445Z | route not resolved | 24 Jun 2018, 23:1324 Jun 2018 | 24 Jun 2018, 23:54 | 27,525 ft | no position received |
| VLJ445Z | route not resolved | 24 Jun 2018, 10:4424 Jun 2018 | 24 Jun 2018, 11:02 | 32,950 ft | no position received |
| VLJ423Z | route not resolved | 21 Jun 2018, 23:0221 Jun 2018 | 21 Jun 2018, 23:04 | 37,950 ft | no position received |
| VLJ423Z | route not resolved | 20 Jun 2018, 22:0820 Jun 2018 | 20 Jun 2018, 22:35 | 34,975 ft | no position received |
| VLJ440G | route not resolved | 20 Jun 2018, 17:0920 Jun 2018 | 20 Jun 2018, 17:45 | 27,875 ft | no position received |
| VLJ439Z | route not resolved | 17 Jun 2018, 20:5217 Jun 2018 | 17 Jun 2018, 21:23 | 23,325 ft | no position received |
| VLJ439Z | route not resolved | 17 Jun 2018, 19:2017 Jun 2018 | 17 Jun 2018, 19:43 | 1,200 ft | no position received |
| VLJ376K | route not resolved | 6 Jun 2018, 17:116 Jun 2018 | 6 Jun 2018, 17:18 | 23,025 ft | no position received |
| VLJ376K | route not resolved | 4 Jun 2018, 08:314 Jun 2018 | 4 Jun 2018, 08:48 | 24,975 ft | no position received |
| VLJ371M | route not resolved | 29 May 2018, 18:3229 May 2018 | 29 May 2018, 19:06 | 23,400 ft | no position received |
| VLJ371M | route not resolved | 29 May 2018, 09:4729 May 2018 | 29 May 2018, 10:23 | 1,250 ft | no position received |
| VLJ370K | route not resolved | 27 May 2018, 13:3127 May 2018 | 27 May 2018, 13:34 | 35,975 ft | no position received |
| VLJ360M | route not resolved | 26 May 2018, 09:4826 May 2018 | 26 May 2018, 09:48 | 33,025 ft | no position received |
