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,065
- 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 |
|---|---|---|---|---|---|
| VLJ98AZ | route not resolved | 15 Mar 2019, 13:1815 Mar 2019 | 15 Mar 2019, 13:42 | 34,725 ft | no position received |
| VLJ98AZ | route not resolved | 15 Mar 2019, 11:2115 Mar 2019 | 15 Mar 2019, 11:28 | 32,975 ft | no position received |
| not transmitted | route not resolved | 14 Mar 2019, 22:2914 Mar 2019 | 14 Mar 2019, 22:29 | 33,975 ft | no position received |
| VLJ98BM | route not resolved | 11 Mar 2019, 23:2011 Mar 2019 | 12 Mar 2019, 00:05 | 34,000 ft | no position received |
| not transmitted | route not resolved | 11 Mar 2019, 18:1911 Mar 2019 | 11 Mar 2019, 18:24 | 33,050 ft | no position received |
| VLJ25BK | route not resolved | 10 Mar 2019, 12:3510 Mar 2019 | 10 Mar 2019, 12:48 | 17,975 ft | no position received |
| VLJ36BZ | route not resolved | 2 Mar 2019, 13:412 Mar 2019 | 2 Mar 2019, 13:56 | 17,975 ft | no position received |
| VLJ44BH | route not resolved | 28 Feb 2019, 16:1028 Feb 2019 | 28 Feb 2019, 16:34 | 30,575 ft | no position received |
| VLJ44BH | route not resolved | 27 Feb 2019, 09:1727 Feb 2019 | 27 Feb 2019, 09:38 | 30,975 ft | no position received |
| VLJ65BM | route not resolved | 26 Feb 2019, 21:5426 Feb 2019 | 26 Feb 2019, 22:19 | 30,200 ft | no position received |
| VLJ65BM | route not resolved | 26 Feb 2019, 14:3526 Feb 2019 | 26 Feb 2019, 15:08 | 28,775 ft | no position received |
| VLJ057A | route not resolved | 30 Jan 2019, 20:2630 Jan 2019 | 30 Jan 2019, 20:52 | 25,975 ft | no position received |
| VLJ057A | route not resolved | 30 Jan 2019, 08:5330 Jan 2019 | 30 Jan 2019, 09:07 | 5,275 ft | no position received |
| VLJ054A | route not resolved | 24 Jan 2019, 18:2324 Jan 2019 | 24 Jan 2019, 18:42 | 21,975 ft | no position received |
| VLJ054A | route not resolved | 22 Jan 2019, 08:5522 Jan 2019 | 22 Jan 2019, 09:30 | 33,950 ft | no position received |
| VLJ043A | route not resolved | 17 Jan 2019, 19:4417 Jan 2019 | 17 Jan 2019, 19:52 | 17,950 ft | no position received |
| VLJ043A | route not resolved | 17 Jan 2019, 11:4117 Jan 2019 | 17 Jan 2019, 11:50 | 1,625 ft | no position received |
| VLJ020A | route not resolved | 8 Jan 2019, 13:218 Jan 2019 | 8 Jan 2019, 13:40 | 21,950 ft | no position received |
| VLJ020A | route not resolved | 8 Jan 2019, 08:328 Jan 2019 | 8 Jan 2019, 08:54 | 1,000 ft | no position received |
| VLJ946G | route not resolved | 21 Dec 2018, 22:0621 Dec 2018 | 21 Dec 2018, 22:24 | 27,925 ft | no position received |
| not transmitted | route not resolved | 21 Dec 2018, 20:5721 Dec 2018 | 21 Dec 2018, 20:57 | 18,075 ft | no position received |
| VLJ943G | route not resolved | 20 Dec 2018, 18:0620 Dec 2018 | 20 Dec 2018, 18:25 | 23,950 ft | no position received |
| VLJ919M | route not resolved | 7 Dec 2018, 17:367 Dec 2018 | 7 Dec 2018, 17:57 | 31,250 ft | no position received |
| not transmitted | route not resolved | 2 Dec 2018, 10:512 Dec 2018 | 2 Dec 2018, 10:57 | 32,975 ft | no position received |
| VLJ841M | route not resolved | 8 Nov 2018, 08:228 Nov 2018 | 8 Nov 2018, 08:35 | 33,525 ft | no position received |
