Back to the log
Aircraft
F-HTIO
Common
The station's story
- Cumulative contact time
- 196 h
- Distinct days
- 269
- Highest captured altitude
- 36,000 ft
- 2 corrupted frame(s) excluded from this maximum
- Discovery rank
- #7,247 of 57,065
- Longest contact
- 1 h 8 min
Observed callsigns
VLJ (124 contacts, 2016-2018)
Operator as per the registry of 21.07.2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| VLJ442L | route not resolved | 4 Sept 2017, 11:394 Sept 2017 | 4 Sept 2017, 12:18 | 17,875 ft | no position received |
| VLJ345M | route not resolved | 26 Aug 2017, 11:1126 Aug 2017 | 26 Aug 2017, 11:44 | 20,850 ft | no position received |
| VLJ345L | route not resolved | 26 Aug 2017, 10:0926 Aug 2017 | 26 Aug 2017, 10:37 | 11,625 ft | no position received |
| VLJ344M | route not resolved | 6 Aug 2017, 13:046 Aug 2017 | 6 Aug 2017, 13:41 | 22,700 ft | no position received |
| VLJ344L | route not resolved | 6 Aug 2017, 11:326 Aug 2017 | 6 Aug 2017, 12:07 | 16,550 ft | no position received |
| VLJ343M | route not resolved | 30 Jul 2017, 11:1030 Jul 2017 | 30 Jul 2017, 11:43 | 21,400 ft | no position received |
| VLJ343L | route not resolved | 30 Jul 2017, 10:1530 Jul 2017 | 30 Jul 2017, 10:43 | 10,300 ft | no position received |
| VLJ160M | route not resolved | 16 Jul 2017, 13:1016 Jul 2017 | 16 Jul 2017, 13:47 | 22,275 ft | no position received |
| VLJ160L | route not resolved | 16 Jul 2017, 11:5716 Jul 2017 | 16 Jul 2017, 12:33 | 16,725 ft | no position received |
| VLJ151N | route not resolved | 13 Jul 2017, 15:5913 Jul 2017 | 13 Jul 2017, 16:42 | 21,150 ft | no position received |
| VLJ151L | route not resolved | 3 Jul 2017, 12:283 Jul 2017 | 3 Jul 2017, 12:51 | 29,000 ft | no position received |
| VLJ318M | route not resolved | 25 Jun 2017, 19:3625 Jun 2017 | 25 Jun 2017, 20:08 | 27,075 ft | no position received |
| VLJ318L | route not resolved | 25 Jun 2017, 13:2425 Jun 2017 | 25 Jun 2017, 13:47 | 31,000 ft | no position received |
| VLJ325 | route not resolved | 24 Jun 2017, 17:4024 Jun 2017 | 24 Jun 2017, 18:16 | 24,825 ft | no position received |
| VLJ158P | route not resolved | 24 Jun 2017, 09:5324 Jun 2017 | 24 Jun 2017, 10:31 | 22,525 ft | no position received |
| VLJ158N | route not resolved | 24 Jun 2017, 08:4324 Jun 2017 | 24 Jun 2017, 09:12 | 11,300 ft | no position received |
| VLJ288N | route not resolved | 23 Jun 2017, 18:0823 Jun 2017 | 23 Jun 2017, 18:50 | 22,850 ft | no position received |
| VLJ288M | route not resolved | 23 Jun 2017, 15:5523 Jun 2017 | 23 Jun 2017, 16:29 | 28,500 ft | no position received |
| VLJ282M | route not resolved | 12 Jun 2017, 17:0412 Jun 2017 | 12 Jun 2017, 17:25 | 18,000 ft | no position received |
| VLJ282L | route not resolved | 10 Jun 2017, 08:5510 Jun 2017 | 10 Jun 2017, 09:27 | 3,700 ft | no position received |
| VLJ260R | route not resolved | 9 Jun 2017, 16:189 Jun 2017 | 9 Jun 2017, 16:24 | 23,000 ft | no position received |
| VLJ260Q | route not resolved | 9 Jun 2017, 15:149 Jun 2017 | 9 Jun 2017, 15:45 | 11,850 ft | no position received |
| VLJ260P | route not resolved | 9 Jun 2017, 12:339 Jun 2017 | 9 Jun 2017, 13:03 | 31,000 ft | no position received |
| VLJ260N | route not resolved | 3 Jun 2017, 19:573 Jun 2017 | 3 Jun 2017, 20:40 | 23,600 ft | no position received |
| VLJ260M | route not resolved | 3 Jun 2017, 17:163 Jun 2017 | 3 Jun 2017, 17:51 | 29,000 ft | no position received |
