Back to the log
Aircraft
F-HJMA
Common
The station's story
- Cumulative contact time
- 207 h
- Distinct days
- 426
- Highest captured altitude
- 39,025 ft
- Discovery rank
- #33,140 of 57,441
- Longest contact
- 1 h 57 min
- Contacts on this Mode S address
- 577 contacts on the address, 575 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 (363 contacts, 2022-2026) · VLJ (175 contacts, 2019-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 |
|---|---|---|---|---|---|
| FHIMA | route not resolved | 19 Jul 2019, 12:0919 Jul 2019 | 19 Jul 2019, 12:29 | 25,925 ft | no position received |
| VLJ24GJ | route not resolved | 12 Jul 2019, 14:1912 Jul 2019 | 12 Jul 2019, 14:34 | 37,000 ft | no position received |
| VLJ77FJ | route not resolved | 10 Jul 2019, 19:3010 Jul 2019 | 10 Jul 2019, 19:43 | 21,250 ft | no position received |
| VLJ04AJ | route not resolved | 6 Jul 2019, 16:036 Jul 2019 | 6 Jul 2019, 16:38 | 30,000 ft | no position received |
| VLJ03AJ | route not resolved | 5 Jul 2019, 16:585 Jul 2019 | 5 Jul 2019, 18:56 | 3,186 ft | no position received |
| VLJ77FJ | route not resolved | 3 Jul 2019, 09:523 Jul 2019 | 3 Jul 2019, 10:22 | 39,000 ft | no position received |
| VLJ02AJ | route not resolved | 2 Jul 2019, 22:472 Jul 2019 | 2 Jul 2019, 23:14 | 23,550 ft | no position received |
| VLJ02AJ | route not resolved | 2 Jul 2019, 21:312 Jul 2019 | 2 Jul 2019, 21:47 | 23,150 ft | no position received |
| VLJ02AJ | route not resolved | 1 Jul 2019, 18:511 Jul 2019 | 1 Jul 2019, 19:18 | 24,200 ft | no position received |
| VLJ02AJ | route not resolved | 1 Jul 2019, 15:541 Jul 2019 | 1 Jul 2019, 16:09 | 21,925 ft | no position received |
| VLJ87EJ | route not resolved | 30 Jun 2019, 23:5630 Jun 2019 | 1 Jul 2019, 00:20 | 38,000 ft | no position received |
| VLJ45GJ | route not resolved | 29 Jun 2019, 17:2129 Jun 2019 | 29 Jun 2019, 17:40 | 22,000 ft | no position received |
| VLJ45GJ | route not resolved | 28 Jun 2019, 12:1628 Jun 2019 | 28 Jun 2019, 12:46 | 1,200 ft | no position received |
| VLJ43GJ | route not resolved | 27 Jun 2019, 18:1427 Jun 2019 | 27 Jun 2019, 18:44 | 26,625 ft | no position received |
| VLJ43GJ | route not resolved | 27 Jun 2019, 12:3227 Jun 2019 | 27 Jun 2019, 13:00 | 33,000 ft | no position received |
| VLJ87EJ | route not resolved | 26 Jun 2019, 13:3426 Jun 2019 | 26 Jun 2019, 14:03 | 24,275 ft | no position received |
| VLJ87EJ | route not resolved | 26 Jun 2019, 09:1526 Jun 2019 | 26 Jun 2019, 09:47 | 39,000 ft | no position received |
| 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 |