Cirrus Design CORP SR22 accident near Twin Lakes, Colorado, April 13, 2022
On April 13, 2022 at about 1:04 pm local time, a 2010 Cirrus Design CORP SR22, registered N112TR, was substantially damaged in an accident during enroute (cruise) near Twin Lakes, Colorado (N/A airport). It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The failure of the left turbocharger at FL230, which resulted in a rapid loss of manifold pressure and subsequent complete loss of engine power due to an overly rich fuel-air mixture setting. Contributing was the smoke in the cabin in IMC, which caused the pilot to proactively shut down the engine and deploy the airframe parachute.
Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- April 13, 2022 · about 1:04 pm local time
- Place
- Twin Lakes, Colorado · N/A · map
- Type
- Accident
- Injuries
- 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Cirrus Design CORP SR22, built 2010
- Registration
- N112TR · registry record · serial 3669
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot reported that he initially leveled off at 17,000 ft mean sea level (msl) but ultimately climbed to flight level (FL) 230 to stay above the cloud tops. During the climb to FL230, the pilot recalled a brief alternate air indication on the primary flight display (PFD). The engine was performing normally and producing full power at that time. Upon leveling off, he reduced engine power to approximately 65% to 75% and adjusted the fuel flow. The alternate air indication extinguished, and all engine indications were normal. The pilot noted that, after leveling off at FL230, a “drastic reduction” in engine power occurred, and he observed an indication of 10% to 15% engine power. He immediately set the mixture to full rich and the fuel pump to high boost. He then adjusted the power lever in an attempt to restore engine power. None of the actions had any effect. During the descent the flight reentered instrument meteorological conditions (IMC). After declaring an emergency and establishing best glide airspeed, the pilot established a course toward a valley east of the current position. About that time, smoke started to enter the cabin and he recalled thinking that restarting the engine was not going to be possible. As the airplane descended through the minimum safe altitude for the mountainous terrain in the area, he noticed a small circle of yellow/mountain peak appear on the multi-function display (MFD) indicating terrain was near; he decided to set the engine mixture control to idle/cutoff and deploy the Cirrus Airframe Parachute System (CAPS). Once the parachute fully deployed, he turned off the electrical system and secured the cabin for touchdown. He recalled contacting the ground “hard” a few seconds later. Review of the available engine data revealed initial reductions in engine power that were likely associated with the airplane leveling off at cruise altitudes. However, three of those power reductions were accompanied by further momentary reductions that appeared to be consistent with the pilot’s attempts to close the alternate air door. Each consisted of a single power reduction followed by a return to cruise engine speed, indicating that the alternate air door likely closed and the indication cleared. A subsequent fluctuation in engine power occurred that lasted about 90 seconds. This fluctuation was accompanied by a substantial loss in manifold pressure, exhaust gas temperatures (EGT), and turbine inlet temperatures (TIT). Afterward, the engine speed stabilized about 2,600 rpm and then gradually increased until it abruptly decreased and went to zero consistent with the pilot shutting down the engine. (This is when the pilot decided to shut down the engine due to cabin smoke and approaching terrain.) The subsequent increase in engine speed and relatively stable fuel flow suggest that engine power may have been recovering as the pilot leaned the mixture. This would be consistent with a complete loss of engine power due to an overly rich fuel-air mixture. Although leaning would potentially have restored a proper fuel-air mixture and allowed the engine to regain power, the pilot’s decision to shut down the engine precluded this possibility. A postaccident examination of the right turbocharger assembly revealed that it appeared intact and was unremarkable. However, the examination of the left turbocharger revealed that the left turbocharger compressor vanes were curled with corresponding scraping damage to the housing inlet consistent with contact while the vanes were rotating. The turbine vanes appeared intact with no scraping damage noted. The compressor and turbine vanes rotated freely; however, the shaft exhibited a slight amount of axial play. The curled blade tips and scraping damage to the housing inlet suggest that the damage occurred when the engine was operating. The engine was not operating during ground impact since the pilot had shut down the engine. Had the turbocharger hit sufficiently hard to make contact marks, it is likely that the impact marks would be static in nature, with single impact marks for each blade, and not showing rotation like the scraping marks. Therefore, it is likely that the turbocharger failed in flight. The cause of the initial reductions in engine power were likely the result of an inadvertent opening of the alternate air door and intentional power adjustments made by the pilot when leveling at cruise altitudes. The subsequent failure of the left turbocharger after reaching FL230 likely resulted in a loss of engine power as a result the failure combined with the rapid reduction of manifold pressure and rich mixture setting. However, the pilot’s action of establishing a full rich mixture and activating the fuel pump on high boost may have contributed to an overly rich fuel-air mixture and a complete loss of engine power. There was no evidence of an engine fire or oil leak and the source of the cabin smoke was not determined, although it may have been associated with the rotational damage of the left turbocharger. Under the circumstances, the pilot’s decision to shut down the engine and deploy the airframe parachute was reasonable.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Fire/smoke (non-impact) during enroute (cruise)
- Off-field or emergency landing during emergency descent
- Loss of engine power (partial) during enroute (change of cruise level)
- Loss of engine power (total) during enroute (cruise) defining event
The NTSB's findings
- Not determined › Not determined › (general) › (general) › Unknown/Not determined
- Aircraft › Aircraft power plant › Turbocharging (recip only) › Turbocharger › Failure
- Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
- Environmental issues › Physical environment › Terrain › Mountainous/hilly terrain › Decision related to condition
Pilot
- Certificate: commercial pilot
- Ratings: single-engine land; single-engine sea; instrument: airplane
- Flight time: 4,122 hours in all; 830 in this make and model; 119 in the last 90 days; 46 in the last 30 days; 3,999 as pilot in command
- Last flight review: September 14, 2021
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: left
- Injury: minor injuries
The aircraft
- Airframe total time: 2,071.8 hours
- Last inspection: annual inspection, January 22, 2022; 42.4 hours since
- Maximum gross weight: 3,400 lb
- Seats: 4
- Landing gear: fixed
- Engine: Continental IO-550-N (piston); 2,878 hours total
The flight
- Departed from: GJT Grand Junction CO at 6:21 am
- Destination: APA Englewood CO
- Flight plan: IFR
Weather at the time
- Light: daylight
- Wind: from 340° at 5 knots
- Visibility: 0.8 statute miles
- Sky: overcast at 2,900 ft
- Temperature: 7°F (-14°C), dew point 1°F (-17°C)
- Altimeter: 29.71 inHg
- Observation at 7:03 am from KLXV, 8 miles away
Weather report (METAR): SPECI KLXV 131303Z AUTO 34005KT 1 3/4SM -SN OVC029 M14/M17 A2971 RMK AO2 P0000 T11391167=
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
10 documents, released by the NTSB on July 5, 2024. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 11 pages | View Download |
| 2 | Accident Photos | PDF, 10 pages | View Download |
| 3 | Airplane Examination Summary | PDF, 3 pages | View Download |
| 4 | Plots of Flight and Engine Data | PDF, 4 pages | View Download |
| 5 | Maintenance Records -- Airframe | PDF, 9 pages | View Download |
| 6 | Maintenance Records -- Engine | PDF, 9 pages | View Download |
| 7 | Maintenance Records -- Propeller | PDF, 10 pages | View Download |
| 8 | Flight Manual Supplement -- Turbonormalizing System | PDF, 21 pages | View Download |
| 9 | Statement of Party Representatives to NTSB Investigation | PDF, 1 page | View Download |
| 10 | Release of Aircraft Wreckage, NTSB Form 6120.15 | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
About this page
Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The documents and photographs are the NTSB's docket, the folder of records gathered during the investigation, shown as the NTSB released them (the NTSB redacts some personal details first) and listed under the NTSB's own titles. This site's own text never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number CEN22LA176.
