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,746 of 60,218
- 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 28 Sept 2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| VLJ831C | route not resolved | 5 Mar 2022, 10:095 Mar 2022 | 5 Mar 2022, 10:21 | 30,975 ft | 111 |
| VLJ831C | route not resolved | 5 Mar 2022, 07:375 Mar 2022 | 5 Mar 2022, 08:07 | 7,800 ft | 2,403 |
| VLJ384R | route not resolved | 27 Feb 2022, 22:5727 Feb 2022 | 27 Feb 2022, 23:07 | 17,950 ft | 922 |
| VLJ384R | route not resolved | 27 Feb 2022, 21:3027 Feb 2022 | 27 Feb 2022, 21:54 | 8,000 ft | 1,291 |
| VLJ384R | route not resolved | 26 Feb 2022, 15:5426 Feb 2022 | 26 Feb 2022, 16:23 | 39,000 ft | 2,089 |
| VLJ384R | route not resolved | 26 Feb 2022, 14:1626 Feb 2022 | 26 Feb 2022, 14:19 | 19,650 ft | 272 |
| VLJ982T | route not resolved | 26 Feb 2022, 11:4226 Feb 2022 | 26 Feb 2022, 11:59 | 17,950 ft | 1,016 |
| VLJ605T | route not resolved | 20 Feb 2022, 18:3520 Feb 2022 | 20 Feb 2022, 18:59 | 25,800 ft | 1,275 |
| VLJ605T | route not resolved | 19 Feb 2022, 16:5019 Feb 2022 | 19 Feb 2022, 16:55 | 12,700 ft | 270 |
| VLJ268V | route not resolved | 19 Feb 2022, 15:2419 Feb 2022 | 19 Feb 2022, 15:40 | 1,275 ft | 1,277 |
| VLJ589E | route not resolved | 11 Feb 2022, 05:5811 Feb 2022 | 11 Feb 2022, 06:18 | 32,675 ft | 1,340 |
| VLJ589E | route not resolved | 8 Feb 2022, 09:238 Feb 2022 | 8 Feb 2022, 09:28 | 39,000 ft | 51 |
| VLJ452S | route not resolved | 2 Feb 2022, 21:182 Feb 2022 | 2 Feb 2022, 21:39 | 28,850 ft | 1,668 |
| VLJ553P | route not resolved | 27 Jan 2022, 23:4027 Jan 2022 | 28 Jan 2022, 00:08 | 29,550 ft | 2,593 |
| VLJ944A | route not resolved | 18 Jan 2022, 06:4418 Jan 2022 | 18 Jan 2022, 06:55 | 41,000 ft | 65 |
| VLJ465S | route not resolved | 16 Jan 2022, 18:3916 Jan 2022 | 16 Jan 2022, 18:47 | 18,000 ft | 126 |
| VLJ465S | route not resolved | 16 Jan 2022, 17:2816 Jan 2022 | 16 Jan 2022, 17:34 | 1,125 ft | 177 |
| VLJ465S | route not resolved | 12 Jan 2022, 09:2912 Jan 2022 | 12 Jan 2022, 09:53 | 29,775 ft | 1,060 |
| VLJ465S | route not resolved | 12 Jan 2022, 07:2912 Jan 2022 | 12 Jan 2022, 07:56 | 850 ft | 2,279 |
| VLJ789R | route not resolved | 10 Jan 2022, 07:0110 Jan 2022 | 10 Jan 2022, 07:20 | 27,900 ft | 954 |
| VLJ597Y | route not resolved | 9 Jan 2022, 16:379 Jan 2022 | 9 Jan 2022, 16:43 | 1,725 ft | 249 |
| VLJ248J | route not resolved | 4 Jan 2022, 20:594 Jan 2022 | 4 Jan 2022, 21:08 | 38,000 ft | 358 |
| VLJ248J | route not resolved | 3 Jan 2022, 14:423 Jan 2022 | 3 Jan 2022, 14:57 | 39,025 ft | 543 |
| VLJ683J | route not resolved | 2 Jan 2022, 10:472 Jan 2022 | 2 Jan 2022, 11:16 | 33,525 ft | 1,134 |
| VLJ683J | route not resolved | 2 Jan 2022, 09:012 Jan 2022 | 2 Jan 2022, 09:28 | 1,050 ft | 1,503 |
