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,068
- 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 |
|---|---|---|---|---|---|
| VLJ013M | route not resolved | 11 Jan 2018, 13:1711 Jan 2018 | 11 Jan 2018, 13:21 | 17,975 ft | no position received |
| VLJ688M | route not resolved | 29 Dec 2017, 17:4629 Dec 2017 | 29 Dec 2017, 18:34 | 25,025 ft | no position received |
| VLJ689M | route not resolved | 29 Dec 2017, 14:5329 Dec 2017 | 29 Dec 2017, 15:30 | 1,400 ft | no position received |
| VLJ680M | route not resolved | 24 Dec 2017, 17:5524 Dec 2017 | 24 Dec 2017, 19:11 | 17,975 ft | no position received |
| VLJ656M | route not resolved | 23 Dec 2017, 15:2023 Dec 2017 | 23 Dec 2017, 15:34 | 17,975 ft | no position received |
| VLJ656M | route not resolved | 23 Dec 2017, 13:3423 Dec 2017 | 23 Dec 2017, 14:16 | 5,150 ft | no position received |
| VLJ674Z | route not resolved | 21 Dec 2017, 01:4521 Dec 2017 | 21 Dec 2017, 02:24 | 34,975 ft | no position received |
| VLJ631 | route not resolved | 20 Dec 2017, 17:3320 Dec 2017 | 20 Dec 2017, 17:53 | 29,975 ft | no position received |
| VLJ631 | route not resolved | 20 Dec 2017, 15:0420 Dec 2017 | 20 Dec 2017, 15:41 | 9,500 ft | no position received |
| VLJ661Z | route not resolved | 18 Dec 2017, 13:2318 Dec 2017 | 18 Dec 2017, 14:01 | 33,025 ft | no position received |
| VLJ661Z | route not resolved | 18 Dec 2017, 10:5418 Dec 2017 | 18 Dec 2017, 11:22 | 34,025 ft | no position received |
| VLJ662R | route not resolved | 16 Dec 2017, 16:5016 Dec 2017 | 16 Dec 2017, 17:24 | 29,275 ft | no position received |
| VLJ662R | route not resolved | 15 Dec 2017, 20:2415 Dec 2017 | 15 Dec 2017, 20:34 | 25,000 ft | no position received |
| VLJ657Z | route not resolved | 12 Dec 2017, 20:0812 Dec 2017 | 12 Dec 2017, 20:36 | 25,925 ft | no position received |
| VLJ657Z | route not resolved | 11 Dec 2017, 14:2511 Dec 2017 | 11 Dec 2017, 14:52 | 2,175 ft | no position received |
| VLJ643Z | route not resolved | 5 Dec 2017, 20:355 Dec 2017 | 5 Dec 2017, 21:12 | 38,000 ft | no position received |
| VLJ643Z | route not resolved | 3 Dec 2017, 18:033 Dec 2017 | 3 Dec 2017, 18:26 | 34,975 ft | no position received |
| VLJ633 | route not resolved | 3 Dec 2017, 14:563 Dec 2017 | 3 Dec 2017, 15:21 | 22,350 ft | no position received |
| VLJ633 | route not resolved | 3 Dec 2017, 11:063 Dec 2017 | 3 Dec 2017, 11:36 | 1,050 ft | no position received |
| VLJ508 | route not resolved | 2 Dec 2017, 18:142 Dec 2017 | 2 Dec 2017, 18:49 | 26,400 ft | no position received |
| VLJ508 | route not resolved | 1 Dec 2017, 07:291 Dec 2017 | 1 Dec 2017, 08:04 | 34,975 ft | no position received |
| VLJ635M | route not resolved | 24 Nov 2017, 10:1824 Nov 2017 | 24 Nov 2017, 10:45 | 24,275 ft | no position received |
| VLJ635M | route not resolved | 24 Nov 2017, 08:0924 Nov 2017 | 24 Nov 2017, 08:39 | 1,250 ft | no position received |
| VLJ561 | route not resolved | 8 Nov 2017, 19:378 Nov 2017 | 8 Nov 2017, 20:11 | 23,025 ft | no position received |
| VLJ561 | route not resolved | 8 Nov 2017, 13:078 Nov 2017 | 8 Nov 2017, 13:39 | 26,625 ft | no position received |
