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 |
|---|---|---|---|---|---|
| VLJ48AJ | route not resolved | 7 Oct 2019, 17:537 Oct 2019 | 7 Oct 2019, 18:25 | 21,525 ft | no position received |
| VLJ48AJ | route not resolved | 7 Oct 2019, 06:517 Oct 2019 | 7 Oct 2019, 07:15 | 37,000 ft | no position received |
| VLJ32AS | route not resolved | 4 Oct 2019, 19:034 Oct 2019 | 4 Oct 2019, 19:25 | 26,275 ft | no position received |
| VLJ45AJ | route not resolved | 4 Oct 2019, 14:594 Oct 2019 | 4 Oct 2019, 15:11 | 39,000 ft | no position received |
| VLJ47AJ | route not resolved | 4 Oct 2019, 09:234 Oct 2019 | 4 Oct 2019, 09:47 | 26,675 ft | no position received |
| VLJ32AS | route not resolved | 4 Oct 2019, 07:484 Oct 2019 | 4 Oct 2019, 08:03 | 33,400 ft | no position received |
| VLJ37AH | route not resolved | 30 Sept 2019, 13:2730 Sept 2019 | 30 Sept 2019, 13:59 | 24,000 ft | no position received |
| VLJ37AH | route not resolved | 30 Sept 2019, 12:1030 Sept 2019 | 30 Sept 2019, 12:42 | 1,275 ft | no position received |
| VLJ40AJ | route not resolved | 27 Sept 2019, 16:4527 Sept 2019 | 27 Sept 2019, 16:49 | 36,025 ft | no position received |
| VLJ40AJ | route not resolved | 25 Sept 2019, 10:4525 Sept 2019 | 25 Sept 2019, 11:09 | 37,000 ft | no position received |
| VLJ43AJ | route not resolved | 24 Sept 2019, 00:3724 Sept 2019 | 24 Sept 2019, 01:06 | 29,200 ft | no position received |
| VLJ43AJ | route not resolved | 23 Sept 2019, 14:0723 Sept 2019 | 23 Sept 2019, 14:22 | 24,000 ft | no position received |
| VLJ44AJ | route not resolved | 22 Sept 2019, 16:5422 Sept 2019 | 22 Sept 2019, 17:23 | 24,525 ft | no position received |
| VLJ44AJ | route not resolved | 21 Sept 2019, 13:2021 Sept 2019 | 21 Sept 2019, 13:44 | 37,000 ft | no position received |
| VLJ29AS | route not resolved | 20 Sept 2019, 13:5220 Sept 2019 | 20 Sept 2019, 14:20 | 18,000 ft | no position received |
| VLJ29AS | route not resolved | 18 Sept 2019, 21:5118 Sept 2019 | 18 Sept 2019, 22:28 | 1,150 ft | no position received |
| VLJ41AJ | route not resolved | 15 Sept 2019, 19:2215 Sept 2019 | 15 Sept 2019, 19:48 | 36,000 ft | no position received |
| VLJ41AJ | route not resolved | 14 Sept 2019, 11:3514 Sept 2019 | 14 Sept 2019, 11:54 | 29,325 ft | no position received |
| VLJ29AJ | route not resolved | 8 Sept 2019, 21:438 Sept 2019 | 8 Sept 2019, 22:08 | 25,625 ft | no position received |
| VLJ29AJ | route not resolved | 8 Sept 2019, 20:388 Sept 2019 | 8 Sept 2019, 21:12 | 1,225 ft | no position received |
| VLJ29AJ | route not resolved | 4 Sept 2019, 12:444 Sept 2019 | 4 Sept 2019, 13:16 | 33,025 ft | no position received |
| VLJ29AJ | route not resolved | 4 Sept 2019, 11:374 Sept 2019 | 4 Sept 2019, 12:13 | 1,225 ft | no position received |
| VLJ38AJ | route not resolved | 1 Sept 2019, 22:301 Sept 2019 | 1 Sept 2019, 22:43 | 34,000 ft | no position received |
| VLJ38AJ | route not resolved | 1 Sept 2019, 19:401 Sept 2019 | 1 Sept 2019, 20:07 | 37,000 ft | no position received |
| VLJ36AJ | route not resolved | 1 Sept 2019, 17:161 Sept 2019 | 1 Sept 2019, 17:35 | 28,325 ft | no position received |