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 |
|---|---|---|---|---|---|
| TLJ999P | route not resolved | 8 Sept 2025, 14:128 Sept 2025 | 8 Sept 2025, 14:37 | 24,000 ft | 732 |
| TLJ999P | route not resolved | 8 Sept 2025, 11:178 Sept 2025 | 8 Sept 2025, 11:47 | 23,000 ft | 348 |
| not transmitted | route not resolved | 8 Sept 2025, 10:288 Sept 2025 | 8 Sept 2025, 10:28 | not transmitted | no position received |
| TLJ268A | route not resolved | 7 Sept 2025, 13:437 Sept 2025 | 7 Sept 2025, 14:15 | not transmitted | 2,150 |
| TLJ333E | route not resolved | 6 Sept 2025, 15:176 Sept 2025 | 6 Sept 2025, 15:37 | 25,700 ft | 1,081 |
| TLJ333E | route not resolved | 6 Sept 2025, 13:026 Sept 2025 | 6 Sept 2025, 13:20 | 34,175 ft | 653 |
| TLJ352C | route not resolved | 5 Sept 2025, 20:045 Sept 2025 | 5 Sept 2025, 20:24 | 22,925 ft | 1,417 |
| TLJ352C | route not resolved | 4 Sept 2025, 06:594 Sept 2025 | 4 Sept 2025, 07:31 | 36,575 ft | 1,820 |
| TLJ977H | route not resolved | 1 Sept 2025, 10:051 Sept 2025 | 1 Sept 2025, 10:21 | 39,000 ft | 127 |
| TLJ905M | route not resolved | 31 Aug 2025, 14:4831 Aug 2025 | 31 Aug 2025, 15:14 | 25,475 ft | 790 |
| TLJ084J | route not resolved | 30 Aug 2025, 12:0830 Aug 2025 | 30 Aug 2025, 12:36 | 39,000 ft | 1,236 |
| TLJ537S | route not resolved | 29 Aug 2025, 20:2329 Aug 2025 | 29 Aug 2025, 20:49 | 30,125 ft | 1,498 |
| TLJ537S | route not resolved | 29 Aug 2025, 16:4029 Aug 2025 | 29 Aug 2025, 16:55 | 33,675 ft | 642 |
| TLJ088A | route not resolved | 28 Aug 2025, 15:2428 Aug 2025 | 28 Aug 2025, 15:47 | 26,250 ft | 1,104 |
| TLJ115Y | route not resolved | 27 Aug 2025, 11:2127 Aug 2025 | 27 Aug 2025, 11:27 | 19,275 ft | 15 |
| not transmitted | route not resolved | 26 Aug 2025, 09:3126 Aug 2025 | 26 Aug 2025, 09:31 | not transmitted | no position received |
| TLJ892N | route not resolved | 23 Aug 2025, 13:2923 Aug 2025 | 23 Aug 2025, 13:45 | 34,675 ft | 675 |
| TLJ166F | route not resolved | 18 Aug 2025, 13:5318 Aug 2025 | 18 Aug 2025, 14:14 | 30,125 ft | 1,139 |
| TLJ695L | route not resolved | 16 Aug 2025, 21:1716 Aug 2025 | 16 Aug 2025, 21:37 | 24,275 ft | 1,427 |
| TLJ023A | route not resolved | 12 Aug 2025, 16:4612 Aug 2025 | 12 Aug 2025, 17:15 | 39,000 ft | 1,307 |
| TLJ922W | route not resolved | 11 Aug 2025, 15:4911 Aug 2025 | 11 Aug 2025, 16:10 | 27,950 ft | 1,078 |
| TLJ922W | route not resolved | 10 Aug 2025, 13:5010 Aug 2025 | 10 Aug 2025, 14:07 | 31,300 ft | 639 |
| TLJ409T | route not resolved | 9 Aug 2025, 21:109 Aug 2025 | 9 Aug 2025, 21:34 | 23,750 ft | 1,297 |
| TLJ048P | route not resolved | 7 Aug 2025, 14:227 Aug 2025 | 7 Aug 2025, 14:30 | 21,925 ft | 205 |
| TLJ253Y | route not resolved | 6 Aug 2025, 16:066 Aug 2025 | 6 Aug 2025, 16:28 | 7,925 ft | 1,407 |