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 |
|---|---|---|---|---|---|
| VLJ18AJ | route not resolved | 1 Aug 2019, 21:061 Aug 2019 | 1 Aug 2019, 21:31 | 36,175 ft | no position received |
| VLJ12AJ | route not resolved | 29 Jul 2019, 15:3229 Jul 2019 | 29 Jul 2019, 15:34 | 35,000 ft | no position received |
| VLJ14AJ | route not resolved | 29 Jul 2019, 12:0529 Jul 2019 | 29 Jul 2019, 12:26 | 25,975 ft | no position received |
| VLJ11AJ | route not resolved | 25 Jul 2019, 15:4525 Jul 2019 | 25 Jul 2019, 16:07 | 28,300 ft | no position received |
| VLJ10AJ | route not resolved | 24 Jul 2019, 16:0424 Jul 2019 | 24 Jul 2019, 16:37 | 39,025 ft | no position received |
| VLJ05AJ | route not resolved | 22 Jul 2019, 12:5622 Jul 2019 | 22 Jul 2019, 13:33 | 18,025 ft | no position received |
| VLJ10AJ | route not resolved | 21 Jul 2019, 15:3021 Jul 2019 | 21 Jul 2019, 15:57 | 1,175 ft | no position received |
| VLJ10AJ | route not resolved | 21 Jul 2019, 09:2321 Jul 2019 | 21 Jul 2019, 09:37 | 39,000 ft | no position received |
| 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 |
