Back to the log
Aircraft
F-HSTB
Regular
Identity resolved on 13 Aug 2026: the aircraft was too recent for the registry at the time of the first contact, on 12 Mar 2020. What this page shows comes from a later registry; each contact keeps what was known on the day it was heard.
The station's story
- Cumulative contact time
- 251 h
- Distinct days
- 540
- Highest captured altitude
- 42,600 ft
- 2 corrupted frame(s) excluded from this maximum
- Discovery rank
- #37,603 of 57,371
- Longest contact
- 1 h 13 min
- Contacts on this Mode S address
- 790 contacts on the address, 751 under this registration: the address has carried several identities over time.
Same airframe, also seen as
- M-CPRSfrom 10 Apr 2016 to 25 Sept 2019 · 55 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 (419 contacts, 2022-2026) · VLJ (290 contacts, 2020-2023)
Operator as per the registry of 12 Aug 2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| TLJ335Y | route not resolved | 1 May 2023, 07:191 May 2023 | 1 May 2023, 07:47 | 27,400 ft | 1,640 |
| TLJ335Y | route not resolved | 21 Apr 2023, 14:3121 Apr 2023 | 21 Apr 2023, 14:49 | 39,000 ft | 850 |
| TLJ335Y | route not resolved | 20 Apr 2023, 17:1620 Apr 2023 | 20 Apr 2023, 17:39 | 18,000 ft | 1,391 |
| TLJ919A | route not resolved | 19 Apr 2023, 12:1019 Apr 2023 | 19 Apr 2023, 12:35 | not transmitted | 1,986 |
| TLJ839Y | route not resolved | 7 Apr 2023, 19:417 Apr 2023 | 7 Apr 2023, 19:57 | 32,525 ft | 1,155 |
| TLJ882K | route not resolved | 28 Mar 2023, 09:3628 Mar 2023 | 28 Mar 2023, 10:05 | 23,125 ft | 1,732 |
| TLJ882K | route not resolved | 26 Mar 2023, 08:4826 Mar 2023 | 26 Mar 2023, 09:08 | 39,000 ft | 1,649 |
| TLJ429U | route not resolved | 18 Mar 2023, 13:2618 Mar 2023 | 18 Mar 2023, 13:46 | 28,675 ft | 1,390 |
| TLJ488Y | route not resolved | 18 Mar 2023, 00:2018 Mar 2023 | 18 Mar 2023, 00:40 | 31,400 ft | 2,045 |
| TLJ293W | route not resolved | 9 Mar 2023, 09:469 Mar 2023 | 9 Mar 2023, 10:02 | 18,000 ft | 1,052 |
| TLJ293W | route not resolved | 8 Mar 2023, 17:378 Mar 2023 | 8 Mar 2023, 17:52 | 14,275 ft | 1,255 |
| TLJ293W | route not resolved | 8 Mar 2023, 14:028 Mar 2023 | 8 Mar 2023, 14:23 | 27,550 ft | 1,648 |
| TLJ242G | route not resolved | 8 Mar 2023, 12:438 Mar 2023 | 8 Mar 2023, 12:54 | 6,000 ft | 638 |
| TLJ500R | route not resolved | 18 Feb 2023, 11:2318 Feb 2023 | 18 Feb 2023, 11:50 | 38,000 ft | 1,292 |
| TLJ125T | route not resolved | 17 Feb 2023, 19:4517 Feb 2023 | 17 Feb 2023, 19:52 | 4,600 ft | 590 |
| TLJ674R | route not resolved | 17 Feb 2023, 00:2117 Feb 2023 | 17 Feb 2023, 00:49 | 25,275 ft | 2,259 |
| TLJ674R | route not resolved | 16 Feb 2023, 15:3416 Feb 2023 | 16 Feb 2023, 15:56 | 24,125 ft | 1,231 |
| TLJ362J | route not resolved | 14 Feb 2023, 22:2214 Feb 2023 | 14 Feb 2023, 22:39 | 39,000 ft | 959 |
| TLJ363G | route not resolved | 10 Feb 2023, 16:2010 Feb 2023 | 10 Feb 2023, 16:29 | 34,025 ft | 516 |
| TLJ638C | route not resolved | 9 Feb 2023, 00:179 Feb 2023 | 9 Feb 2023, 00:41 | 29,300 ft | 2,531 |
| TLJ638C | route not resolved | 8 Feb 2023, 17:358 Feb 2023 | 8 Feb 2023, 17:52 | 26,175 ft | 1,130 |
| TLJ502S | route not resolved | 8 Feb 2023, 14:028 Feb 2023 | 8 Feb 2023, 14:27 | 25,000 ft | 1,648 |
| TLJ805F | route not resolved | 7 Feb 2023, 16:267 Feb 2023 | 7 Feb 2023, 16:34 | 23,000 ft | 164 |
| TLJ805F | route not resolved | 7 Feb 2023, 11:537 Feb 2023 | 7 Feb 2023, 12:04 | 10,350 ft | 1,005 |
| TLJ238G | route not resolved | 25 Jan 2023, 17:3025 Jan 2023 | 25 Jan 2023, 17:49 | 26,025 ft | 1,263 |
