Back to the log
Aircraft
F-HBMR
Regular
The station's story
Address not received since 18 Jan 2024. The marker states the absence, it does not say why.
- Cumulative contact time
- 192 h
- Distinct days
- 299
- Highest captured altitude
- 50,500 ft
- Discovery rank
- #14,424 of 57,080
- Longest contact
- 1 h 22 min
Observed callsigns
VLJ (392 contacts, 2016-2023) · DBT (18 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 |
|---|---|---|---|---|---|
| VLJ398L | route not resolved | 25 Aug 2017, 13:1325 Aug 2017 | 25 Aug 2017, 13:50 | 33,375 ft | no position received |
| VLJ413N | route not resolved | 20 Aug 2017, 18:3820 Aug 2017 | 20 Aug 2017, 19:04 | 25,275 ft | no position received |
| VLJ360P | route not resolved | 4 Aug 2017, 15:424 Aug 2017 | 4 Aug 2017, 16:02 | 32,975 ft | no position received |
| VLJ382L | route not resolved | 27 Jul 2017, 13:4127 Jul 2017 | 27 Jul 2017, 13:58 | 31,225 ft | no position received |
| VLJ366M | route not resolved | 23 Jul 2017, 10:2123 Jul 2017 | 23 Jul 2017, 11:02 | 24,075 ft | no position received |
| VLJ380M | route not resolved | 22 Jul 2017, 12:2122 Jul 2017 | 22 Jul 2017, 12:45 | 34,950 ft | no position received |
| VLJ296M | route not resolved | 21 Jul 2017, 22:4821 Jul 2017 | 21 Jul 2017, 23:19 | 27,325 ft | no position received |
| VLJ296L | route not resolved | 21 Jul 2017, 19:5721 Jul 2017 | 21 Jul 2017, 20:21 | 33,000 ft | no position received |
| VLJ369M | route not resolved | 19 Jul 2017, 18:3719 Jul 2017 | 19 Jul 2017, 19:20 | 32,650 ft | no position received |
| VLJ369L | route not resolved | 18 Jul 2017, 10:3118 Jul 2017 | 18 Jul 2017, 11:03 | 26,025 ft | no position received |
| VLJ357N | route not resolved | 17 Jul 2017, 16:0817 Jul 2017 | 17 Jul 2017, 16:44 | 33,975 ft | no position received |
| VLJ371L | route not resolved | 16 Jul 2017, 16:4416 Jul 2017 | 16 Jul 2017, 17:25 | 38,250 ft | no position received |
| VLJ373M | route not resolved | 16 Jul 2017, 14:0916 Jul 2017 | 16 Jul 2017, 14:35 | 26,200 ft | no position received |
| VLJ373L | route not resolved | 16 Jul 2017, 10:2916 Jul 2017 | 16 Jul 2017, 10:50 | 29,900 ft | no position received |
| VLJ365M | route not resolved | 14 Jul 2017, 20:5814 Jul 2017 | 14 Jul 2017, 21:27 | 26,200 ft | no position received |
| VLJ365L | route not resolved | 14 Jul 2017, 15:4514 Jul 2017 | 14 Jul 2017, 16:06 | 34,975 ft | no position received |
| VLJ270N | route not resolved | 12 Jul 2017, 13:5012 Jul 2017 | 12 Jul 2017, 14:24 | 17,600 ft | no position received |
| VLJ359M | route not resolved | 10 Jul 2017, 11:4010 Jul 2017 | 10 Jul 2017, 12:11 | 35,000 ft | no position received |
| VLJ359L | route not resolved | 10 Jul 2017, 10:0410 Jul 2017 | 10 Jul 2017, 10:26 | 31,200 ft | no position received |
| VLJ290M | route not resolved | 9 Jul 2017, 18:569 Jul 2017 | 9 Jul 2017, 19:32 | 23,975 ft | no position received |
| VLJ322N | route not resolved | 8 Jul 2017, 15:488 Jul 2017 | 8 Jul 2017, 16:25 | 18,000 ft | no position received |
| VLJ322M | route not resolved | 8 Jul 2017, 14:298 Jul 2017 | 8 Jul 2017, 15:14 | 1,250 ft | no position received |
| VLJ322L | route not resolved | 7 Jul 2017, 16:027 Jul 2017 | 7 Jul 2017, 16:41 | 32,025 ft | no position received |
| VLJ290L | route not resolved | 7 Jul 2017, 14:167 Jul 2017 | 7 Jul 2017, 14:38 | 26,800 ft | no position received |
| VLJ271N | route not resolved | 2 Jul 2017, 16:232 Jul 2017 | 2 Jul 2017, 16:51 | 29,975 ft | no position received |
