Back to the log
Aircraft
F-HBAN
Common
The station's story
- Cumulative contact time
- 116 h
- Distinct days
- 222
- Highest captured altitude
- 41,025 ft
- 1 corrupted frame(s) excluded from this maximum
- Discovery rank
- #11,172 of 57,065
- Longest contact
- 1 h 0 min
- Contacts on this Mode S address
- 356 contacts on the address, 317 under this registration: the address has carried several identities over time.
Same airframe, also seen as
- A6-ADLfrom 16 May 2016 to 5 Feb 2018 · 9 contacts
- OE-LFXfrom 11 Dec 2016 to 7 Aug 2026 · 239 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 (246 contacts, 2022-2026) · VLJ (9 contacts, 2023-2025)
Operator as per the registry of 21.07.2026; observed callsigns are the freshest measurement.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| TLJ407D | route not resolved | 25 Jan 2026, 13:1325 Jan 2026 | 25 Jan 2026, 13:26 | 30,075 ft | 82 |
| TLJ127E | route not resolved | 25 Jan 2026, 12:0325 Jan 2026 | 25 Jan 2026, 12:14 | 5,450 ft | 655 |
| TLJ915B | route not resolved | 22 Jan 2026, 18:2522 Jan 2026 | 22 Jan 2026, 18:43 | 25,875 ft | 1,017 |
| TLJ788L | route not resolved | 19 Jan 2026, 19:1819 Jan 2026 | 19 Jan 2026, 19:36 | 17,800 ft | 825 |
| TLJ407D | route not resolved | 17 Jan 2026, 16:3517 Jan 2026 | 17 Jan 2026, 16:51 | 18,000 ft | 662 |
| TLJ407D | route not resolved | 17 Jan 2026, 14:5317 Jan 2026 | 17 Jan 2026, 15:15 | 4,925 ft | 750 |
| TLJ668Z | route not resolved | 16 Jan 2026, 08:1216 Jan 2026 | 16 Jan 2026, 08:44 | 36,050 ft | 464 |
| TLJ668Z | route not resolved | 16 Jan 2026, 06:4816 Jan 2026 | 16 Jan 2026, 07:13 | not transmitted | 1,655 |
| TLJ188V | route not resolved | 15 Jan 2026, 22:2415 Jan 2026 | 15 Jan 2026, 22:29 | 41,000 ft | 162 |
| TLJ188V | route not resolved | 15 Jan 2026, 08:2715 Jan 2026 | 15 Jan 2026, 08:48 | 39,000 ft | 976 |
| TLJ240M | route not resolved | 13 Jan 2026, 12:3313 Jan 2026 | 13 Jan 2026, 13:00 | 24,675 ft | 1,047 |
| TLJ240M | route not resolved | 13 Jan 2026, 10:1013 Jan 2026 | 13 Jan 2026, 10:35 | 27,175 ft | 1,027 |
| TLJ282X | route not resolved | 4 Jan 2026, 18:174 Jan 2026 | 4 Jan 2026, 18:44 | 25,100 ft | 941 |
| TLJ528U | route not resolved | 3 Jan 2026, 18:193 Jan 2026 | 3 Jan 2026, 18:43 | 34,000 ft | 1,293 |
| TLJ528U | route not resolved | 3 Jan 2026, 16:543 Jan 2026 | 3 Jan 2026, 17:28 | 6,500 ft | 1,223 |
| VLJ282X | route not resolved | 26 Dec 2025, 09:1226 Dec 2025 | 26 Dec 2025, 09:38 | 28,650 ft | 1,113 |
| TLJ122Z | route not resolved | 20 Dec 2025, 15:3020 Dec 2025 | 20 Dec 2025, 15:55 | 40,000 ft | 1,283 |
| TLJ528U | route not resolved | 20 Dec 2025, 13:3420 Dec 2025 | 20 Dec 2025, 14:34 | 5,225 ft | 3,317 |
| TLJ160P | route not resolved | 13 Dec 2025, 11:3213 Dec 2025 | 13 Dec 2025, 11:49 | 18,000 ft | 618 |
| TLJ160P | route not resolved | 12 Dec 2025, 11:5812 Dec 2025 | 12 Dec 2025, 12:06 | 5,125 ft | 257 |
| TLJ086X | route not resolved | 5 Dec 2025, 15:105 Dec 2025 | 5 Dec 2025, 15:41 | 39,050 ft | 666 |
| TLJ126P | route not resolved | 2 Dec 2025, 11:152 Dec 2025 | 2 Dec 2025, 11:17 | 41,000 ft | 26 |
| TLJ205N | route not resolved | 1 Dec 2025, 21:531 Dec 2025 | 1 Dec 2025, 22:20 | 23,575 ft | 1,136 |
| TLJ205N | route not resolved | 1 Dec 2025, 14:231 Dec 2025 | 1 Dec 2025, 14:37 | 33,000 ft | 329 |
| TLJ550H | route not resolved | 29 Nov 2025, 16:5529 Nov 2025 | 29 Nov 2025, 17:08 | 26,000 ft | 647 |
