Back to the log
Aircraft
F-HJMA
Common
The station's story
- Cumulative contact time
- 210 h
- Distinct days
- 433
- Highest captured altitude
- 39,025 ft
- Discovery rank
- #33,330 of 60,433
- Longest contact
- 1 h 57 min
- Contacts on this Mode S address
- 585 contacts on the address, 583 under this registration: the address has carried several identities over time.
Same airframe, also seen as
- G-HUBYfrom 12 Apr 2016 to 18 Jun 2019 · 202 contacts
These registrations share the same serial number and type according to the reference data. Serial numbers can collide, though: it is a deduction, not a certainty.
Observed callsigns
TLJ (371 contacts, 2022-2026) · VLJ (175 contacts, 2019-2023)
Operator as per the registry of 12 Oct 2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| VLJ08GJ | route not resolved | 20 Jun 2019, 12:3420 Jun 2019 | 20 Jun 2019, 13:04 | 38,000 ft | no position received |
| VLJ08GJ | route not resolved | 20 Jun 2019, 10:5720 Jun 2019 | 20 Jun 2019, 11:10 | 34,975 ft | no position received |
| VLJ87ZM | route not resolved | 17 Jun 2019, 20:3217 Jun 2019 | 17 Jun 2019, 20:58 | 22,350 ft | no position received |
| VLJ87ZM | route not resolved | 17 Jun 2019, 13:5817 Jun 2019 | 17 Jun 2019, 14:27 | 26,800 ft | no position received |
| VLJ96EJ | route not resolved | 11 Jun 2019, 21:3411 Jun 2019 | 11 Jun 2019, 21:40 | 18,000 ft | no position received |
| VLJ96EJ | route not resolved | 10 Jun 2019, 14:2010 Jun 2019 | 10 Jun 2019, 14:20 | 26,700 ft | no position received |
| VLJ17FJ | route not resolved | 9 Jun 2019, 21:479 Jun 2019 | 9 Jun 2019, 22:01 | 35,775 ft | no position received |
| VLJ17FJ | route not resolved | 7 Jun 2019, 21:537 Jun 2019 | 7 Jun 2019, 22:20 | 37,000 ft | no position received |
| VLJ94EJ | route not resolved | 6 Jun 2019, 20:336 Jun 2019 | 6 Jun 2019, 20:47 | 33,375 ft | no position received |
| VLJ94EJ | route not resolved | 3 Jun 2019, 12:043 Jun 2019 | 3 Jun 2019, 12:29 | 39,000 ft | no position received |
| VLJ93EJ | route not resolved | 2 Jun 2019, 18:212 Jun 2019 | 2 Jun 2019, 18:46 | 28,425 ft | no position received |
| VLJ93EJ | route not resolved | 31 May 2019, 13:1931 May 2019 | 31 May 2019, 13:36 | 32,625 ft | no position received |
| VLJ92EJ | route not resolved | 29 May 2019, 23:0529 May 2019 | 29 May 2019, 23:30 | 31,300 ft | no position received |
| not transmitted | route not resolved | 29 May 2019, 19:5029 May 2019 | 29 May 2019, 20:01 | 35,000 ft | no position received |
| VLJ91EJ | route not resolved | 29 May 2019, 17:2029 May 2019 | 29 May 2019, 17:48 | 30,700 ft | no position received |
| VLJ91EJ | route not resolved | 29 May 2019, 15:5629 May 2019 | 29 May 2019, 16:11 | 33,225 ft | no position received |
| VLJ51EJ | route not resolved | 27 May 2019, 16:4227 May 2019 | 27 May 2019, 16:48 | 35,150 ft | no position received |
| not transmitted | route not resolved | 25 May 2019, 11:3325 May 2019 | 25 May 2019, 11:37 | 33,950 ft | no position received |
| VLJ61EJ | route not resolved | 23 May 2019, 11:0223 May 2019 | 23 May 2019, 11:26 | 26,575 ft | no position received |
| VLJ61EJ | route not resolved | 22 May 2019, 17:0522 May 2019 | 22 May 2019, 17:24 | 3,042 ft | no position received |
| VLJ07DR | route not resolved | 19 May 2019, 17:5319 May 2019 | 19 May 2019, 18:10 | 30,025 ft | no position received |
| VLJ07DR | route not resolved | 17 May 2019, 14:1817 May 2019 | 17 May 2019, 14:36 | 33,700 ft | no position received |
| VLJ26EJ | route not resolved | 12 May 2019, 18:1112 May 2019 | 12 May 2019, 18:41 | 28,025 ft | no position received |
| VLJ26EJ | route not resolved | 12 May 2019, 16:0712 May 2019 | 12 May 2019, 16:22 | 32,275 ft | no position received |
| VLJ83DJ | route not resolved | 11 May 2019, 18:1411 May 2019 | 11 May 2019, 18:25 | 36,400 ft | no position received |
