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,422 of 57,441
- 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 |
|---|---|---|---|---|---|
| VLJ48AZ | route not resolved | 25 Oct 2019, 17:0825 Oct 2019 | 25 Oct 2019, 17:32 | 23,550 ft | no position received |
| VLJ05AM | route not resolved | 13 Oct 2019, 20:2813 Oct 2019 | 13 Oct 2019, 20:51 | 28,375 ft | no position received |
| VLJ05AM | route not resolved | 13 Oct 2019, 07:5313 Oct 2019 | 13 Oct 2019, 08:14 | 34,150 ft | no position received |
| VLJ02AM | route not resolved | 12 Oct 2019, 19:2712 Oct 2019 | 12 Oct 2019, 19:50 | 26,275 ft | no position received |
| VLJ02AM | route not resolved | 12 Oct 2019, 11:4512 Oct 2019 | 12 Oct 2019, 12:10 | 4,275 ft | no position received |
| VLJ61AP | route not resolved | 11 Oct 2019, 18:0811 Oct 2019 | 11 Oct 2019, 18:39 | 21,950 ft | no position received |
| VLJ61AP | route not resolved | 11 Oct 2019, 10:1711 Oct 2019 | 11 Oct 2019, 10:58 | 27,125 ft | no position received |
| VLJ53FK | route not resolved | 19 Jun 2019, 15:4219 Jun 2019 | 19 Jun 2019, 16:18 | 24,350 ft | no position received |
| VLJ95FM | route not resolved | 19 Jun 2019, 13:2819 Jun 2019 | 19 Jun 2019, 13:41 | 22,975 ft | no position received |
| VLJ95FM | route not resolved | 19 Jun 2019, 12:3919 Jun 2019 | 19 Jun 2019, 12:54 | 4,425 ft | no position received |
| VLJ53FK | route not resolved | 18 Jun 2019, 08:3918 Jun 2019 | 18 Jun 2019, 09:10 | 28,000 ft | no position received |
| VLJ65FM | route not resolved | 17 Jun 2019, 20:0717 Jun 2019 | 17 Jun 2019, 20:51 | 22,875 ft | no position received |
| VLJ65FM | route not resolved | 16 Jun 2019, 20:1416 Jun 2019 | 16 Jun 2019, 20:45 | 1,200 ft | no position received |
| VLJ29FM | route not resolved | 16 Jun 2019, 08:3116 Jun 2019 | 16 Jun 2019, 09:02 | 29,900 ft | no position received |
| VLJ79FM | route not resolved | 15 Jun 2019, 11:2415 Jun 2019 | 15 Jun 2019, 12:13 | 39,000 ft | no position received |
| VLJ72FM | route not resolved | 14 Jun 2019, 17:4014 Jun 2019 | 14 Jun 2019, 18:06 | 26,675 ft | no position received |
| VLJ72FM | route not resolved | 14 Jun 2019, 09:0714 Jun 2019 | 14 Jun 2019, 09:25 | 34,975 ft | no position received |
| VLJ11FM | route not resolved | 10 Jun 2019, 08:2710 Jun 2019 | 10 Jun 2019, 08:46 | 34,000 ft | no position received |
| VLJ11FM | route not resolved | 10 Jun 2019, 06:4410 Jun 2019 | 10 Jun 2019, 06:58 | 16,675 ft | no position received |
| VLJ79EM | route not resolved | 8 Jun 2019, 00:038 Jun 2019 | 8 Jun 2019, 00:25 | 29,500 ft | no position received |
| VLJ79EM | route not resolved | 7 Jun 2019, 20:547 Jun 2019 | 7 Jun 2019, 21:15 | 32,375 ft | no position received |
| VLJ32FM | route not resolved | 7 Jun 2019, 14:277 Jun 2019 | 7 Jun 2019, 14:51 | 34,000 ft | no position received |
| VLJ43FM | route not resolved | 5 Jun 2019, 20:255 Jun 2019 | 5 Jun 2019, 20:41 | 33,000 ft | no position received |
| VLJ43FM | route not resolved | 5 Jun 2019, 11:145 Jun 2019 | 5 Jun 2019, 11:37 | 27,700 ft | no position received |
| VLJ43FM | route not resolved | 5 Jun 2019, 08:565 Jun 2019 | 5 Jun 2019, 09:21 | 29,900 ft | no position received |
