Back to the log
Aircraft
CS-TKY
Regular
- Mode S hex
- 495179
- Manufacturer
- Airbus
- Serial number
- 1929
- Year built
- 2019
- Operator
- HiFly (HFY)
- Country of registration
Portugal
- First contact
- 16 Sept 2019, 18:40
- Last contact
- 4 Jul 2022, 07:28
- Logged visits
- 93
The station's story
Address not received since 4 Jul 2022. The marker states the absence, it does not say why.
- Cumulative contact time
- 25 h
- Distinct days
- 79
- Highest captured altitude
- 41,000 ft
- Discovery rank
- #36,103 of 57,065
- Longest contact
- 0 h 52 min
Same airframe, also seen as
- CS-TCFfrom 9 Mar 2024 to 29 May 2025 · 8 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
HFM (39 contacts, 2021) · MDG (27 contacts, 2022) · HFY (14 contacts, 2019-2022)
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 |
|---|---|---|---|---|---|
| MDG050 | route not resolved | 4 Jul 2022, 07:244 Jul 2022 | 4 Jul 2022, 07:28 | 38,000 ft | 11 |
| MDG050 | route not resolved | 30 Jun 2022, 07:3830 Jun 2022 | 30 Jun 2022, 07:54 | 31,900 ft | 867 |
| MDG051 | route not resolved | 27 Jun 2022, 22:1527 Jun 2022 | 27 Jun 2022, 22:23 | 35,000 ft | 82 |
| MDG050 | route not resolved | 27 Jun 2022, 07:0727 Jun 2022 | 27 Jun 2022, 07:24 | 30,525 ft | 958 |
| MDG050 | route not resolved | 23 Jun 2022, 07:1623 Jun 2022 | 23 Jun 2022, 07:18 | 34,000 ft | 19 |
| MDG051 | route not resolved | 20 Jun 2022, 21:0020 Jun 2022 | 20 Jun 2022, 21:13 | 37,000 ft | 99 |
| MDG050 | route not resolved | 20 Jun 2022, 06:4920 Jun 2022 | 20 Jun 2022, 07:14 | 34,450 ft | 977 |
| MDG051 | route not resolved | 17 Jun 2022, 21:2017 Jun 2022 | 17 Jun 2022, 21:33 | 35,000 ft | 216 |
| not transmitted | route not resolved | 16 Jun 2022, 07:4116 Jun 2022 | 16 Jun 2022, 07:43 | 38,000 ft | 3 |
| MDG051 | route not resolved | 13 Jun 2022, 20:5513 Jun 2022 | 13 Jun 2022, 21:06 | 37,000 ft | 227 |
| MDG050 | route not resolved | 13 Jun 2022, 07:2513 Jun 2022 | 13 Jun 2022, 07:41 | 33,200 ft | 1,181 |
| MDG051 | route not resolved | 10 Jun 2022, 21:3110 Jun 2022 | 10 Jun 2022, 21:39 | 37,000 ft | 139 |
| MDG050 | route not resolved | 7 Jun 2022, 19:547 Jun 2022 | 7 Jun 2022, 20:15 | 35,075 ft | 1,258 |
| MDG051 | route not resolved | 6 Jun 2022, 20:596 Jun 2022 | 6 Jun 2022, 21:14 | 32,075 ft | 46 |
| MDG051 | route not resolved | 30 May 2022, 21:0330 May 2022 | 30 May 2022, 21:08 | 35,000 ft | 85 |
| MDG050 | route not resolved | 30 May 2022, 07:2430 May 2022 | 30 May 2022, 07:44 | 32,525 ft | 1,089 |
| MDG051 | route not resolved | 27 May 2022, 21:4727 May 2022 | 27 May 2022, 21:59 | 35,025 ft | 142 |
| HFY430P | LPPT > LTCC | 9 May 2022, 21:359 May 2022 | 9 May 2022, 21:50 | 38,000 ft | 761 |
| MDG050 | route not resolved | 9 May 2022, 08:599 May 2022 | 9 May 2022, 09:22 | 34,250 ft | 1,379 |
| MDG051 | route not resolved | 6 May 2022, 21:176 May 2022 | 6 May 2022, 21:30 | 35,000 ft | 599 |
| MDG050 | route not resolved | 2 May 2022, 09:272 May 2022 | 2 May 2022, 09:51 | 32,000 ft | 1,728 |
| MD051 | route not resolved | 29 Apr 2022, 21:2629 Apr 2022 | 29 Apr 2022, 21:32 | 35,000 ft | 174 |
| not transmitted | route not resolved | 26 Apr 2022, 00:0126 Apr 2022 | 26 Apr 2022, 00:11 | 40,000 ft | no position received |
| MDG050 | route not resolved | 25 Apr 2022, 09:2825 Apr 2022 | 25 Apr 2022, 09:38 | 37,475 ft | 84 |
| MDG051 | route not resolved | 22 Apr 2022, 21:1422 Apr 2022 | 22 Apr 2022, 21:19 | 33,000 ft | 141 |
