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
- 539
- Highest captured altitude
- 42,600 ft
- 2 corrupted frame(s) excluded from this maximum
- Discovery rank
- #37,594 of 57,261
- Longest contact
- 1 h 13 min
- Contacts on this Mode S address
- 789 contacts on the address, 750 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 (418 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 |
|---|---|---|---|---|---|
| TLJ681X | route not resolved | 29 Apr 2024, 12:0529 Apr 2024 | 29 Apr 2024, 12:13 | 18,000 ft | 161 |
| not transmitted | route not resolved | 28 Apr 2024, 18:2428 Apr 2024 | 28 Apr 2024, 18:26 | 7,650 ft | no position received |
| TLJ913J | route not resolved | 10 Apr 2024, 11:3610 Apr 2024 | 10 Apr 2024, 12:07 | 37,025 ft | 1,415 |
| TLJ913J | route not resolved | 10 Apr 2024, 09:2310 Apr 2024 | 10 Apr 2024, 09:39 | 12,625 ft | 996 |
| TLJ583H | route not resolved | 1 Apr 2024, 16:481 Apr 2024 | 1 Apr 2024, 17:13 | 30,200 ft | 686 |
| TLJ583H | route not resolved | 29 Mar 2024, 21:1729 Mar 2024 | 29 Mar 2024, 21:50 | 41,000 ft | 1,840 |
| TLJ729B | route not resolved | 29 Mar 2024, 13:4929 Mar 2024 | 29 Mar 2024, 14:13 | 30,775 ft | 1,432 |
| TLJ023V | route not resolved | 25 Mar 2024, 13:5925 Mar 2024 | 25 Mar 2024, 14:27 | 24,225 ft | 1,244 |
| TLJ358F | route not resolved | 14 Mar 2024, 13:1314 Mar 2024 | 14 Mar 2024, 13:32 | 27,400 ft | 1,167 |
| not transmitted | route not resolved | 12 Mar 2024, 08:4512 Mar 2024 | 12 Mar 2024, 08:57 | 31,000 ft | 4 |
| TLJ504X | route not resolved | 10 Mar 2024, 08:5110 Mar 2024 | 10 Mar 2024, 08:55 | 13,000 ft | 93 |
| TLJ309Y | route not resolved | 5 Mar 2024, 16:455 Mar 2024 | 5 Mar 2024, 17:02 | 24,000 ft | 1,080 |
| TLJ621Y | route not resolved | 2 Mar 2024, 09:022 Mar 2024 | 2 Mar 2024, 09:24 | 41,000 ft | 1,251 |
| TLJ951Y | route not resolved | 29 Feb 2024, 13:2929 Feb 2024 | 29 Feb 2024, 13:50 | 27,750 ft | 1,386 |
| TLJ433F | route not resolved | 29 Feb 2024, 11:3529 Feb 2024 | 29 Feb 2024, 11:52 | 23,000 ft | 463 |
| TLJ433F | route not resolved | 29 Feb 2024, 10:1829 Feb 2024 | 29 Feb 2024, 10:45 | not transmitted | 1,762 |
| TLJ254W | route not resolved | 28 Feb 2024, 19:0628 Feb 2024 | 28 Feb 2024, 19:27 | 28,825 ft | 1,545 |
| TLJ254W | route not resolved | 28 Feb 2024, 17:3428 Feb 2024 | 28 Feb 2024, 17:51 | 32,950 ft | 736 |
| TLJ564K | route not resolved | 24 Feb 2024, 20:0724 Feb 2024 | 24 Feb 2024, 20:40 | 18,000 ft | 1,397 |
| TLJ175W | route not resolved | 24 Feb 2024, 07:0324 Feb 2024 | 24 Feb 2024, 07:29 | not transmitted | 1,582 |
| TLJ517P | route not resolved | 22 Feb 2024, 20:0422 Feb 2024 | 22 Feb 2024, 20:05 | 39,000 ft | 43 |
| TLJ820S | route not resolved | 7 Feb 2024, 19:017 Feb 2024 | 7 Feb 2024, 19:33 | 18,000 ft | 1,591 |
| TLJ820S | route not resolved | 6 Feb 2024, 07:596 Feb 2024 | 6 Feb 2024, 08:16 | 31,000 ft | 1,347 |
| TLJ744A | route not resolved | 4 Feb 2024, 23:254 Feb 2024 | 4 Feb 2024, 23:34 | 40,000 ft | 341 |
| TLJ778G | route not resolved | 14 Jan 2024, 17:4614 Jan 2024 | 14 Jan 2024, 18:16 | 26,275 ft | 609 |
