Back to the log
Aircraft
TC-KRM
Common
The station's story
Address not received since 19 Feb 2022. The marker states the absence, it does not say why.
- Cumulative contact time
- 17 h
- Distinct days
- 40
- Highest captured altitude
- 45,000 ft
- Discovery rank
- #10,805 of 57,065
- Longest contact
- 1 h 18 min
Same airframe, also seen as
- TC-TSSfrom 12 May 2022 to 7 Jul 2026 · 64 contacts
- TC-RMSfrom 8 Sept 2024 to 16 Jul 2026 · 24 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.
Visits
| Callsign | Route | First contact | Last contact | Altitude at end of contact | Positions |
|---|---|---|---|---|---|
| not transmitted | route not resolved | 14 Oct 2018, 10:1914 Oct 2018 | 14 Oct 2018, 10:33 | 41,000 ft | no position received |
| TCKRM | route not resolved | 28 Apr 2018, 23:3228 Apr 2018 | 29 Apr 2018, 00:08 | 29,700 ft | no position received |
| TCKRM | route not resolved | 27 Apr 2018, 21:1127 Apr 2018 | 27 Apr 2018, 21:33 | 1,450 ft | no position received |
| not transmitted | route not resolved | 27 Apr 2018, 18:3627 Apr 2018 | 27 Apr 2018, 18:36 | 35,000 ft | no position received |
| TCKRM | route not resolved | 1 Mar 2018, 15:561 Mar 2018 | 1 Mar 2018, 16:22 | 40,000 ft | no position received |
| TCKRM | route not resolved | 2 Jul 2017, 11:362 Jul 2017 | 2 Jul 2017, 11:38 | 29,000 ft | no position received |
| TCKRM | route not resolved | 21 Jun 2017, 18:0721 Jun 2017 | 21 Jun 2017, 18:12 | 40,000 ft | no position received |
| TCKRM | route not resolved | 20 Jun 2017, 18:5820 Jun 2017 | 20 Jun 2017, 19:16 | 41,000 ft | no position received |
| TCKRM | route not resolved | 11 Mar 2017, 17:2611 Mar 2017 | 11 Mar 2017, 17:50 | 41,000 ft | no position received |
| TCKRM | route not resolved | 9 Mar 2017, 13:299 Mar 2017 | 9 Mar 2017, 14:00 | 5,575 ft | no position received |
| TCKRM | route not resolved | 5 Mar 2017, 13:075 Mar 2017 | 5 Mar 2017, 13:37 | 35,000 ft | no position received |
| TCKRM | route not resolved | 4 Mar 2017, 17:384 Mar 2017 | 4 Mar 2017, 18:20 | 6,575 ft | no position received |
| TCKRM | route not resolved | 25 Feb 2017, 14:1325 Feb 2017 | 25 Feb 2017, 14:38 | 41,000 ft | no position received |
| TCKRM | route not resolved | 23 Feb 2017, 14:3623 Feb 2017 | 23 Feb 2017, 15:15 | 6,325 ft | no position received |
| TCKRM | route not resolved | 16 Feb 2017, 15:5016 Feb 2017 | 16 Feb 2017, 16:09 | 17,300 ft | no position received |
| TCKRM | route not resolved | 3 Oct 2016, 14:083 Oct 2016 | 3 Oct 2016, 14:14 | 41,000 ft | no position received |
| not transmitted | route not resolved | 28 Jun 2016, 18:2528 Jun 2016 | 28 Jun 2016, 18:56 | 34,550 ft | no position received |
| not transmitted | route not resolved | 28 Jun 2016, 11:3728 Jun 2016 | 28 Jun 2016, 12:12 | 1,200 ft | no position received |
| not transmitted | route not resolved | 15 May 2016, 19:0315 May 2016 | 15 May 2016, 19:28 | 34,850 ft | no position received |
| not transmitted | route not resolved | 14 May 2016, 17:1914 May 2016 | 14 May 2016, 17:45 | 1,375 ft | no position received |
