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 |
|---|---|---|---|---|---|
| not transmitted | route not resolved | 3 Dec 2016, 10:303 Dec 2016 | 3 Dec 2016, 10:30 | 34,975 ft | no position received |
| VLJ588M | route not resolved | 30 Nov 2016, 00:1430 Nov 2016 | 30 Nov 2016, 00:42 | 29,300 ft | no position received |
| VLJ588L | route not resolved | 29 Nov 2016, 19:5029 Nov 2016 | 29 Nov 2016, 20:14 | 34,950 ft | no position received |
| VLJ382Q | route not resolved | 4 Aug 2016, 14:014 Aug 2016 | 4 Aug 2016, 14:18 | 31,950 ft | no position received |
| VLJ382M | route not resolved | 1 Aug 2016, 10:521 Aug 2016 | 1 Aug 2016, 11:23 | 27,675 ft | no position received |
| VLJ354M | route not resolved | 30 Jul 2016, 17:2530 Jul 2016 | 30 Jul 2016, 17:50 | 25,650 ft | no position received |
| VLJ354L | route not resolved | 30 Jul 2016, 15:2930 Jul 2016 | 30 Jul 2016, 15:49 | 31,050 ft | no position received |
| VLJ377M | route not resolved | 28 Jul 2016, 17:1828 Jul 2016 | 28 Jul 2016, 18:01 | 32,975 ft | no position received |
| VLJ355N | route not resolved | 24 Jul 2016, 14:2124 Jul 2016 | 24 Jul 2016, 14:54 | 22,775 ft | no position received |
| VLJ355M | route not resolved | 24 Jul 2016, 12:3724 Jul 2016 | 24 Jul 2016, 13:09 | 1,200 ft | no position received |
| VLJ362N | route not resolved | 22 Jul 2016, 21:3622 Jul 2016 | 22 Jul 2016, 21:57 | 26,000 ft | no position received |
| VLJ362M | route not resolved | 22 Jul 2016, 19:0222 Jul 2016 | 22 Jul 2016, 19:25 | 34,975 ft | no position received |
| VLJ349M | route not resolved | 18 Jul 2016, 17:2218 Jul 2016 | 18 Jul 2016, 17:49 | 25,675 ft | no position received |
| VLJ349L | route not resolved | 18 Jul 2016, 09:0518 Jul 2016 | 18 Jul 2016, 09:28 | 37,000 ft | no position received |
| not transmitted | route not resolved | 13 Jul 2016, 20:2213 Jul 2016 | 13 Jul 2016, 20:24 | 35,000 ft | no position received |
| VLJ347M | route not resolved | 13 Jul 2016, 17:1113 Jul 2016 | 13 Jul 2016, 17:35 | 27,125 ft | no position received |
| VLJ347L | route not resolved | 13 Jul 2016, 14:5713 Jul 2016 | 13 Jul 2016, 15:16 | 31,125 ft | no position received |
| VLJ335L | route not resolved | 11 Jul 2016, 08:3111 Jul 2016 | 11 Jul 2016, 08:57 | 23,975 ft | no position received |
| VLJ272S | route not resolved | 10 Jul 2016, 15:0310 Jul 2016 | 10 Jul 2016, 15:18 | 3,975 ft | no position received |
| not transmitted | route not resolved | 2 Jul 2016, 18:552 Jul 2016 | 2 Jul 2016, 19:34 | 22,400 ft | no position received |
| not transmitted | route not resolved | 2 Jul 2016, 13:412 Jul 2016 | 2 Jul 2016, 14:10 | 34,000 ft | no position received |
| not transmitted | route not resolved | 1 Jul 2016, 21:171 Jul 2016 | 1 Jul 2016, 21:52 | 25,625 ft | no position received |
| not transmitted | route not resolved | 1 Jul 2016, 16:361 Jul 2016 | 1 Jul 2016, 17:00 | 32,975 ft | no position received |
| not transmitted | route not resolved | 1 Jul 2016, 08:371 Jul 2016 | 1 Jul 2016, 09:09 | 38,000 ft | no position received |
| not transmitted | route not resolved | 30 Jun 2016, 17:2930 Jun 2016 | 30 Jun 2016, 17:48 | 26,475 ft | no position received |
