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,243
- Longest contact
- 1 h 24 min
Observed callsigns
VLJ (558 contacts, 2016-2022) · WLJ (1 contacts, 2017) · CCM (1 contacts, 2018)
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 |
|---|---|---|---|---|---|
| VLJ448 | route not resolved | 31 Aug 2017, 13:0431 Aug 2017 | 31 Aug 2017, 13:28 | 37,025 ft | no position received |
| VLJ298P | route not resolved | 1 Aug 2017, 12:411 Aug 2017 | 1 Aug 2017, 12:57 | 18,000 ft | no position received |
| VLJ298L | route not resolved | 1 Aug 2017, 11:551 Aug 2017 | 1 Aug 2017, 12:10 | 4,050 ft | no position received |
| VLJ387L | route not resolved | 30 Jul 2017, 11:0130 Jul 2017 | 30 Jul 2017, 11:19 | 30,300 ft | no position received |
| VLJ394M | route not resolved | 30 Jul 2017, 00:5130 Jul 2017 | 30 Jul 2017, 01:21 | 28,550 ft | no position received |
| VLJ394L | route not resolved | 29 Jul 2017, 21:4529 Jul 2017 | 29 Jul 2017, 21:47 | 37,025 ft | no position received |
| VLJ308L | route not resolved | 29 Jul 2017, 14:4829 Jul 2017 | 29 Jul 2017, 15:02 | 37,025 ft | no position received |
| VLJ386M | route not resolved | 27 Jul 2017, 11:5927 Jul 2017 | 27 Jul 2017, 12:20 | 35,625 ft | no position received |
| VLJ386L | route not resolved | 27 Jul 2017, 08:1727 Jul 2017 | 27 Jul 2017, 08:43 | 1,350 ft | no position received |
| VLJ295N | route not resolved | 19 Jul 2017, 15:5219 Jul 2017 | 19 Jul 2017, 16:18 | 32,000 ft | no position received |
| VLJ295M | route not resolved | 19 Jul 2017, 09:1019 Jul 2017 | 19 Jul 2017, 09:33 | 1,300 ft | no position received |
| VLJ295L | route not resolved | 18 Jul 2017, 17:4618 Jul 2017 | 18 Jul 2017, 18:09 | 37,000 ft | no position received |
| VLJ370Q | route not resolved | 16 Jul 2017, 21:3216 Jul 2017 | 16 Jul 2017, 22:04 | 22,700 ft | no position received |
| VLJ370N | route not resolved | 16 Jul 2017, 19:2116 Jul 2017 | 16 Jul 2017, 19:50 | 34,875 ft | no position received |
| VLJ350M | route not resolved | 16 Jul 2017, 17:1116 Jul 2017 | 16 Jul 2017, 17:40 | 20,425 ft | no position received |
| VLJ370M | route not resolved | 14 Jul 2017, 13:4214 Jul 2017 | 14 Jul 2017, 14:11 | 36,200 ft | no position received |
| VLJ370L | route not resolved | 14 Jul 2017, 11:3914 Jul 2017 | 14 Jul 2017, 12:07 | 23,950 ft | no position received |
| VLJ350L | route not resolved | 14 Jul 2017, 09:4214 Jul 2017 | 14 Jul 2017, 10:10 | 31,225 ft | no position received |
| VLJ355N | route not resolved | 13 Jul 2017, 16:2913 Jul 2017 | 13 Jul 2017, 16:58 | 23,425 ft | no position received |
| VLJ355M | route not resolved | 13 Jul 2017, 12:4713 Jul 2017 | 13 Jul 2017, 13:01 | 31,000 ft | no position received |
| VLJ349P | route not resolved | 13 Jul 2017, 10:1113 Jul 2017 | 13 Jul 2017, 10:47 | 3,875 ft | no position received |
| FHREX | route not resolved | 12 Jul 2017, 18:3512 Jul 2017 | 12 Jul 2017, 18:57 | 31,000 ft | no position received |
| VLJ349M | route not resolved | 12 Jul 2017, 16:4912 Jul 2017 | 12 Jul 2017, 17:07 | 3,775 ft | no position received |
| VLJ2A4M | route not resolved | 9 Jul 2017, 15:419 Jul 2017 | 9 Jul 2017, 16:08 | 25,950 ft | no position received |
| VLJ309L | route not resolved | 8 Jul 2017, 10:538 Jul 2017 | 8 Jul 2017, 10:54 | 37,000 ft | no position received |
