Back to the log
Aircraft
F-HREX
Common
The station's story
Address not received since 11 Aug 2022. The marker states the absence, it does not say why.
- Cumulative contact time
- 201 h
- Distinct days
- 394
- Highest captured altitude
- 41,050 ft
- 1 corrupted frame(s) excluded from this maximum
- Discovery rank
- #7,349 of 57,155
- Longest contact
- 1 h 24 min
Observed callsigns
VLJ (558 contacts, 2016-2022) · VMJ (1 contacts, 2016) · WLJ (1 contacts, 2017)
Operator as per the registry of 12 Aug 2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| VLJ280E | route not resolved | 27 Apr 2018, 18:1327 Apr 2018 | 27 Apr 2018, 18:36 | 26,125 ft | no position received |
| VLJ280E | route not resolved | 27 Apr 2018, 13:1427 Apr 2018 | 27 Apr 2018, 13:31 | 20,000 ft | no position received |
| VLJ009E | route not resolved | 6 Jan 2018, 12:226 Jan 2018 | 6 Jan 2018, 12:43 | 27,700 ft | no position received |
| VLJ009E | route not resolved | 5 Jan 2018, 10:345 Jan 2018 | 5 Jan 2018, 10:53 | 39,000 ft | no position received |
| VLJ681E | route not resolved | 27 Dec 2017, 20:1627 Dec 2017 | 27 Dec 2017, 20:46 | 23,800 ft | no position received |
| WLJ681E | route not resolved | 27 Dec 2017, 09:2327 Dec 2017 | 27 Dec 2017, 09:52 | 38,975 ft | no position received |
| VLJ685E | route not resolved | 24 Dec 2017, 10:3924 Dec 2017 | 24 Dec 2017, 10:58 | 18,000 ft | no position received |
| VLJ685E | route not resolved | 24 Dec 2017, 09:2724 Dec 2017 | 24 Dec 2017, 10:00 | 850 ft | no position received |
| VLJ651E | route not resolved | 15 Dec 2017, 11:3815 Dec 2017 | 15 Dec 2017, 12:00 | 39,000 ft | no position received |
| VLJ651E | route not resolved | 14 Dec 2017, 14:4114 Dec 2017 | 14 Dec 2017, 15:03 | 1,625 ft | no position received |
| VLJ575 | route not resolved | 28 Nov 2017, 16:2428 Nov 2017 | 28 Nov 2017, 16:57 | 23,075 ft | no position received |
| VLJ575 | route not resolved | 27 Nov 2017, 13:1327 Nov 2017 | 27 Nov 2017, 13:38 | 28,175 ft | no position received |
| VLJ624 | route not resolved | 26 Nov 2017, 20:0326 Nov 2017 | 26 Nov 2017, 20:35 | 23,250 ft | no position received |
| VLJ624 | route not resolved | 24 Nov 2017, 10:0124 Nov 2017 | 24 Nov 2017, 10:27 | 28,125 ft | no position received |
| VLJ594 | route not resolved | 9 Nov 2017, 16:269 Nov 2017 | 9 Nov 2017, 16:46 | 23,175 ft | no position received |
| VLJ594 | route not resolved | 9 Nov 2017, 08:259 Nov 2017 | 9 Nov 2017, 08:58 | 1,125 ft | no position received |
| VLJ581 | route not resolved | 8 Nov 2017, 11:308 Nov 2017 | 8 Nov 2017, 11:49 | 36,025 ft | no position received |
| VLJ581 | route not resolved | 5 Nov 2017, 09:275 Nov 2017 | 5 Nov 2017, 09:53 | 37,025 ft | no position received |
| VLJ579 | route not resolved | 2 Nov 2017, 12:462 Nov 2017 | 2 Nov 2017, 13:06 | 34,000 ft | no position received |
| VLJ514 | route not resolved | 29 Sept 2017, 18:2729 Sept 2017 | 29 Sept 2017, 18:43 | 30,775 ft | no position received |
| VLJ460 | route not resolved | 15 Sept 2017, 12:1015 Sept 2017 | 15 Sept 2017, 12:23 | 38,000 ft | no position received |
| VLJ460 | route not resolved | 11 Sept 2017, 09:4211 Sept 2017 | 11 Sept 2017, 10:07 | 39,025 ft | no position received |
| VLJ412 | route not resolved | 10 Sept 2017, 18:3710 Sept 2017 | 10 Sept 2017, 19:11 | 22,600 ft | no position received |
| VLJ412L | route not resolved | 8 Sept 2017, 13:348 Sept 2017 | 8 Sept 2017, 14:08 | 2,412 ft | no position received |
| VLJ448 | route not resolved | 4 Sept 2017, 18:334 Sept 2017 | 4 Sept 2017, 18:53 | 38,025 ft | no position received |
