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 |
|---|---|---|---|---|---|
| VLJ527 | route not resolved | 3 Nov 2017, 15:203 Nov 2017 | 3 Nov 2017, 15:29 | 33,975 ft | no position received |
| VLJ527 | route not resolved | 3 Nov 2017, 12:193 Nov 2017 | 3 Nov 2017, 12:41 | 32,975 ft | no position received |
| VLJ527 | route not resolved | 25 Oct 2017, 14:2825 Oct 2017 | 25 Oct 2017, 14:48 | 34,950 ft | no position received |
| VLJ536 | route not resolved | 22 Oct 2017, 18:5922 Oct 2017 | 22 Oct 2017, 19:27 | 23,325 ft | no position received |
| VLJ545K | route not resolved | 20 Oct 2017, 15:4020 Oct 2017 | 20 Oct 2017, 16:35 | 39,975 ft | no position received |
| VLJ536 | route not resolved | 20 Oct 2017, 09:1120 Oct 2017 | 20 Oct 2017, 09:28 | 34,975 ft | no position received |
| VLJ530 | route not resolved | 18 Oct 2017, 19:0418 Oct 2017 | 18 Oct 2017, 19:35 | 24,675 ft | no position received |
| VLJ530 | route not resolved | 18 Oct 2017, 09:0918 Oct 2017 | 18 Oct 2017, 09:36 | 34,975 ft | no position received |
| VLJ526 | route not resolved | 16 Oct 2017, 16:4716 Oct 2017 | 16 Oct 2017, 17:13 | 31,050 ft | no position received |
| VLJ526 | route not resolved | 15 Oct 2017, 07:2515 Oct 2017 | 15 Oct 2017, 07:50 | 28,800 ft | no position received |
| VLJ538 | route not resolved | 11 Oct 2017, 17:4111 Oct 2017 | 11 Oct 2017, 18:06 | 27,900 ft | no position received |
| VLJ538 | route not resolved | 11 Oct 2017, 15:4511 Oct 2017 | 11 Oct 2017, 16:12 | 23,225 ft | no position received |
| VLJ496 | route not resolved | 7 Oct 2017, 19:337 Oct 2017 | 7 Oct 2017, 20:01 | 26,375 ft | no position received |
| VLJ523 | route not resolved | 5 Oct 2017, 09:455 Oct 2017 | 5 Oct 2017, 10:23 | 26,600 ft | no position received |
| VLJ523 | route not resolved | 5 Oct 2017, 08:225 Oct 2017 | 5 Oct 2017, 08:40 | 24,650 ft | no position received |
| VLJ511 | route not resolved | 4 Oct 2017, 12:174 Oct 2017 | 4 Oct 2017, 12:39 | 33,975 ft | no position received |
| VLJ506 | route not resolved | 2 Oct 2017, 12:462 Oct 2017 | 2 Oct 2017, 12:57 | 15,325 ft | no position received |
| VLJ471 | route not resolved | 22 Sept 2017, 15:3822 Sept 2017 | 22 Sept 2017, 16:02 | 9,875 ft | no position received |
| VLJ471 | route not resolved | 21 Sept 2017, 16:5921 Sept 2017 | 21 Sept 2017, 17:24 | 26,975 ft | no position received |
| VLJ449 | route not resolved | 5 Sept 2017, 14:135 Sept 2017 | 5 Sept 2017, 14:52 | 32,000 ft | no position received |
| VLJ449 | route not resolved | 5 Sept 2017, 11:525 Sept 2017 | 5 Sept 2017, 12:13 | 33,775 ft | no position received |
| VLJ430 | route not resolved | 4 Sept 2017, 14:324 Sept 2017 | 4 Sept 2017, 15:09 | 21,625 ft | no position received |
| VLJ430 | route not resolved | 1 Sept 2017, 22:301 Sept 2017 | 1 Sept 2017, 23:01 | 23,000 ft | no position received |
| VLJ377M | route not resolved | 29 Aug 2017, 15:2729 Aug 2017 | 29 Aug 2017, 15:51 | 26,700 ft | no position received |
| VLJ377L | route not resolved | 29 Aug 2017, 12:1029 Aug 2017 | 29 Aug 2017, 12:32 | 34,975 ft | no position received |
