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,331 of 60,444
- 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 |
|---|---|---|---|---|---|
| FHJMA | route not resolved | 10 Apr 2024, 09:0710 Apr 2024 | 10 Apr 2024, 09:31 | 37,000 ft | 1,555 |
| TLJ887H | route not resolved | 8 Apr 2024, 17:488 Apr 2024 | 8 Apr 2024, 18:14 | not transmitted | 1,800 |
| TLJ470H | route not resolved | 4 Apr 2024, 17:064 Apr 2024 | 4 Apr 2024, 17:31 | 28,375 ft | 1,717 |
| TLJ470H | route not resolved | 4 Apr 2024, 07:364 Apr 2024 | 4 Apr 2024, 07:50 | 34,325 ft | 810 |
| TLJ310N | route not resolved | 3 Apr 2024, 19:193 Apr 2024 | 3 Apr 2024, 19:48 | 24,325 ft | 929 |
| TLJ310N | route not resolved | 2 Apr 2024, 07:312 Apr 2024 | 2 Apr 2024, 07:57 | 35,000 ft | 1,351 |
| TLJ528L | route not resolved | 1 Apr 2024, 20:481 Apr 2024 | 1 Apr 2024, 21:18 | 28,050 ft | 1,050 |
| TLJ528L | route not resolved | 29 Mar 2024, 18:1929 Mar 2024 | 29 Mar 2024, 18:40 | 39,000 ft | 1,340 |
| TLJ445W | route not resolved | 26 Mar 2024, 18:1626 Mar 2024 | 26 Mar 2024, 18:36 | 24,000 ft | 1,062 |
| TLJ445W | route not resolved | 25 Mar 2024, 18:0525 Mar 2024 | 25 Mar 2024, 18:16 | 24,000 ft | 554 |
| TLJ143P | route not resolved | 2 Mar 2024, 19:032 Mar 2024 | 2 Mar 2024, 19:23 | 28,475 ft | 1,590 |
| TLJ143P | route not resolved | 1 Mar 2024, 07:521 Mar 2024 | 1 Mar 2024, 08:10 | 31,000 ft | 876 |
| TLJ291H | route not resolved | 9 Feb 2024, 12:449 Feb 2024 | 9 Feb 2024, 13:12 | 24,275 ft | 1,020 |
| TLJ291H | route not resolved | 8 Feb 2024, 07:558 Feb 2024 | 8 Feb 2024, 08:18 | 35,000 ft | 1,626 |
| TLJ441H | route not resolved | 5 Feb 2024, 20:435 Feb 2024 | 5 Feb 2024, 21:07 | 23,700 ft | 1,007 |
| TLJ441H | route not resolved | 29 Jan 2024, 17:2729 Jan 2024 | 29 Jan 2024, 17:43 | 31,000 ft | 1,063 |
| TLJ255V | route not resolved | 18 Jan 2024, 19:1218 Jan 2024 | 18 Jan 2024, 19:37 | 23,575 ft | 1,375 |
| TLJ255V | route not resolved | 17 Jan 2024, 08:1217 Jan 2024 | 17 Jan 2024, 08:34 | 23,275 ft | 1,796 |
| TLJ255V | route not resolved | 16 Jan 2024, 19:1216 Jan 2024 | 16 Jan 2024, 19:39 | 27,050 ft | 2,289 |
| TLJ255V | route not resolved | 15 Jan 2024, 19:0215 Jan 2024 | 15 Jan 2024, 19:16 | 31,975 ft | 944 |
| VLJ371W | route not resolved | 23 Dec 2023, 12:2223 Dec 2023 | 23 Dec 2023, 12:41 | 18,000 ft | 1,541 |
| VLJ371W | route not resolved | 23 Dec 2023, 10:5623 Dec 2023 | 23 Dec 2023, 11:31 | not transmitted | 2,932 |
| VLJ553X | route not resolved | 21 Dec 2023, 18:2421 Dec 2023 | 21 Dec 2023, 18:59 | 28,425 ft | 2,368 |
| VLJ553X | route not resolved | 19 Dec 2023, 19:0319 Dec 2023 | 19 Dec 2023, 19:28 | 35,000 ft | 1,526 |
| VLJ765X | route not resolved | 15 Dec 2023, 13:2615 Dec 2023 | 15 Dec 2023, 13:51 | 22,900 ft | 1,243 |
