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
- 259 h
- Distinct days
- 553
- Highest captured altitude
- 42,600 ft
- 2 corrupted frame(s) excluded from this maximum
- Discovery rank
- #37,714 of 60,056
- Longest contact
- 1 h 13 min
- Contacts on this Mode S address
- 812 contacts on the address, 772 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 (440 contacts, 2022-2026) · VLJ (290 contacts, 2020-2023)
Operator as per the registry of 21 Sept 2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| TLJ004T | route not resolved | 21 Sept 2026, 16:1321 Sept 2026 | 21 Sept 2026, 16:38 | 25,100 ft | 713 |
| TLJ004T | route not resolved | 21 Sept 2026, 04:0321 Sept 2026 | 21 Sept 2026, 04:29 | 35,050 ft | 2,666 |
| TLJ004T | route not resolved | 12 Sept 2026, 14:1212 Sept 2026 | 12 Sept 2026, 14:26 | 39,000 ft | 290 |
| TLJ990H | route not resolved | 10 Sept 2026, 18:2710 Sept 2026 | 10 Sept 2026, 18:52 | 27,000 ft | 1,156 |
| TLJ167T | route not resolved | 7 Sept 2026, 12:567 Sept 2026 | 7 Sept 2026, 13:21 | 39,000 ft | 792 |
| TLJ853M | route not resolved | 6 Sept 2026, 16:396 Sept 2026 | 6 Sept 2026, 16:59 | 28,000 ft | 1,102 |
| TLJ853M | route not resolved | 6 Sept 2026, 14:086 Sept 2026 | 6 Sept 2026, 14:25 | 31,000 ft | 378 |
| TLJ882J | route not resolved | 5 Sept 2026, 20:115 Sept 2026 | 5 Sept 2026, 20:26 | 41,000 ft | 205 |
| TLJ128S | route not resolved | 5 Sept 2026, 15:455 Sept 2026 | 5 Sept 2026, 16:03 | 26,000 ft | 887 |
| TLJ128S | route not resolved | 5 Sept 2026, 12:205 Sept 2026 | 5 Sept 2026, 12:37 | 13,700 ft | 603 |
| TLJ657S | route not resolved | 31 Aug 2026, 16:0731 Aug 2026 | 31 Aug 2026, 16:36 | 40,000 ft | 917 |
| TLJ657S | route not resolved | 31 Aug 2026, 13:0231 Aug 2026 | 31 Aug 2026, 13:18 | 33,200 ft | 377 |
| TLJ666D | route not resolved | 28 Aug 2026, 12:5428 Aug 2026 | 28 Aug 2026, 13:23 | 40,000 ft | 1,178 |
| TLJ832A | route not resolved | 27 Aug 2026, 11:1727 Aug 2026 | 27 Aug 2026, 11:36 | 25,000 ft | 531 |
| TLJ832A | route not resolved | 27 Aug 2026, 09:2027 Aug 2026 | 27 Aug 2026, 09:31 | 5,275 ft | 288 |
| TLJ813R | route not resolved | 23 Aug 2026, 11:1623 Aug 2026 | 23 Aug 2026, 11:43 | 39,000 ft | 999 |
| TLJ497P | route not resolved | 22 Aug 2026, 15:5822 Aug 2026 | 22 Aug 2026, 16:27 | 21,475 ft | 1,172 |
| TLJ497P | route not resolved | 22 Aug 2026, 14:3822 Aug 2026 | 22 Aug 2026, 15:13 | not transmitted | 2,104 |
| TLJ572F | route not resolved | 21 Aug 2026, 20:0721 Aug 2026 | 21 Aug 2026, 20:20 | 15,775 ft | 854 |
| TLJ150J | route not resolved | 21 Aug 2026, 13:1921 Aug 2026 | 21 Aug 2026, 13:47 | 25,450 ft | 1,128 |
| TLJ077K | route not resolved | 15 Aug 2026, 16:4815 Aug 2026 | 15 Aug 2026, 17:16 | 23,550 ft | 1,034 |
| TLJ932N | route not resolved | 14 Aug 2026, 15:1614 Aug 2026 | 14 Aug 2026, 15:31 | 33,050 ft | 306 |
| TLJ371V | route not resolved | 12 Aug 2026, 16:1012 Aug 2026 | 12 Aug 2026, 16:49 | 39,000 ft | 1,587 |
| TLJ484P | route not resolved | 8 Aug 2026, 13:538 Aug 2026 | 8 Aug 2026, 14:20 | 39,950 ft | 1,044 |
| TLJ706N | route not resolved | 3 Aug 2026, 21:573 Aug 2026 | 3 Aug 2026, 22:15 | 25,175 ft | 1,136 |
