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
- 541
- Highest captured altitude
- 42,600 ft
- 2 corrupted frame(s) excluded from this maximum
- Discovery rank
- #37,613 of 57,466
- Longest contact
- 1 h 13 min
- Contacts on this Mode S address
- 791 contacts on the address, 752 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 (420 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 |
|---|---|---|---|---|---|
| FHSTB00 | route not resolved | 11 Jul 2023, 09:3211 Jul 2023 | 11 Jul 2023, 09:47 | 3,975 ft | 508 |
| TLJ256P | route not resolved | 10 Jul 2023, 22:0010 Jul 2023 | 10 Jul 2023, 22:22 | 23,075 ft | 986 |
| TLJ256P | route not resolved | 10 Jul 2023, 19:4710 Jul 2023 | 10 Jul 2023, 20:08 | 25,175 ft | 305 |
| TLJ874F | route not resolved | 9 Jul 2023, 15:399 Jul 2023 | 9 Jul 2023, 15:59 | 22,900 ft | 1,404 |
| TLJ762J | route not resolved | 5 Jul 2023, 22:405 Jul 2023 | 5 Jul 2023, 22:56 | 34,825 ft | 1,021 |
| TLJ407W | route not resolved | 28 Jun 2023, 19:4128 Jun 2023 | 28 Jun 2023, 19:58 | 33,950 ft | 530 |
| TLJ407W | route not resolved | 28 Jun 2023, 17:2128 Jun 2023 | 28 Jun 2023, 17:36 | 35,875 ft | 323 |
| TLJ405H | route not resolved | 27 Jun 2023, 08:3427 Jun 2023 | 27 Jun 2023, 08:50 | 22,000 ft | 1,120 |
| TLJ405H | route not resolved | 26 Jun 2023, 18:3126 Jun 2023 | 26 Jun 2023, 18:57 | 27,575 ft | 1,265 |
| TLJ213C | route not resolved | 26 Jun 2023, 16:3426 Jun 2023 | 26 Jun 2023, 16:50 | 32,525 ft | 760 |
| TLJ836W | route not resolved | 25 Jun 2023, 12:0025 Jun 2023 | 25 Jun 2023, 12:16 | 12,200 ft | 1,006 |
| TLJ337Y | route not resolved | 22 Jun 2023, 09:1222 Jun 2023 | 22 Jun 2023, 09:25 | 34,000 ft | 97 |
| TLJ679U | route not resolved | 19 Jun 2023, 06:4519 Jun 2023 | 19 Jun 2023, 07:10 | 27,925 ft | 1,211 |
| TLJ907R | route not resolved | 10 Jun 2023, 16:0310 Jun 2023 | 10 Jun 2023, 16:31 | 35,400 ft | 1,139 |
| TLJ294X | route not resolved | 10 Jun 2023, 14:2710 Jun 2023 | 10 Jun 2023, 14:56 | not transmitted | 2,064 |
| not transmitted | route not resolved | 6 Jun 2023, 20:526 Jun 2023 | 6 Jun 2023, 20:53 | 36,075 ft | 2 |
| TLJ565Y | route not resolved | 3 Jun 2023, 13:413 Jun 2023 | 3 Jun 2023, 14:00 | 39,000 ft | 472 |
| TLJ325K | route not resolved | 1 Jun 2023, 17:581 Jun 2023 | 1 Jun 2023, 18:21 | 38,000 ft | 937 |
| TLJ382S | route not resolved | 1 Jun 2023, 07:231 Jun 2023 | 1 Jun 2023, 07:52 | 37,000 ft | 1,130 |
| TLJ402U | route not resolved | 29 May 2023, 20:2929 May 2023 | 29 May 2023, 20:58 | 29,850 ft | 1,911 |
| TLJ402U | route not resolved | 29 May 2023, 18:4429 May 2023 | 29 May 2023, 19:00 | 32,200 ft | 550 |
| TLJ486G | route not resolved | 26 May 2023, 23:5026 May 2023 | 27 May 2023, 00:16 | 30,950 ft | 2,082 |
| TLJ135V | route not resolved | 14 May 2023, 17:4914 May 2023 | 14 May 2023, 18:08 | 13,550 ft | 1,169 |
| TLJ135V | route not resolved | 14 May 2023, 11:5514 May 2023 | 14 May 2023, 12:14 | 29,175 ft | 736 |
| TLJ118V | route not resolved | 2 May 2023, 23:222 May 2023 | 2 May 2023, 23:42 | 31,775 ft | 1,335 |
