Cirrus Design Corp. SR22 accident near Ogden, Utah, December 10, 2020
On December 10, 2020 at about 10:47 pm local time, a 2008 Cirrus Design Corp. SR22, registered N577CP, was substantially damaged in an accident during initial climb near Ogden, Utah (Ogden-Hinckley airport). It was a personal flight under general aviation rules (Part 91). 1 person was seriously injured. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The partial loss of engine power for reasons that cannot be determined due to lack of available evidence.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- December 10, 2020 · about 10:47 pm local time
- Place
- Ogden, Utah · Ogden-Hinckley · map
- Type
- Accident
- Injuries
- 1 person was seriously injured.
- Weather
- visual conditions (good weather)
- Aircraft
- Cirrus Design Corp. SR22, built 2008
- Registration
- N577CP · no longer on the register · serial 3345
- 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 during takeoff on runway 17, the engine ran smoothly, and the airplane became airborne “in the usual spot.” During the initial climb, the pilot noticed a loss of power that prevented the airplane from continuing to climb, and he initiated a right turn to land on runway 3. During the landing roll, he realized the airplane would not stop with maximum braking. The pilot added that he tried to pull the parachute handle, but it did not activate during the accident sequence. The pilot further stated that he used his right hand to pull the handle as he was flying with this left and could not recall how much force he was able to pull the handle with. The airplane exited the right side of the runway and came to rest upright beyond the departure end of the runway. Examination of the airframe parachute system revealed no evidence of a mechanical failure or malfunction that would have precluded normal operation. It’s likely that the parachute did not deploy due to the pilot not exerting enough force on the deployment handle. Recorded data from the avionics display showed that during takeoff, the manifold pressure had increased to 34.81 inches, and decreased to 25.55 inches about 7 seconds later. The engine rpm reduced from about 2,650 to about 2,478. The data showed that rpm remained about 2,600, with manifold pressure around 25 inches, throughout the duration of the flight until power was reduced for landing. Postaccident examination of the engine revealed that the sensing line from the left intercooler to the pressure controller was hand tight at the control unit. The right-side turbocharger shaft nut was found in the inlet of the turbine along with significant damage to the turbine inlet housing. Examination of the induction system revealed that one of the induction tubes and clamp were crushed, and the remainder were intact. The increase in manifold pressure during takeoff most likely was the result of the loose sensing line between the left intercooler and pressure controller. Furthermore, while it is possible that a loose induction tube clamp would result in a decrease in manifold pressure, it could not be determined due to post impact damage sustained to the induction system. The right-side turbocharger shaft nut found loose was most likely a result of impact damage to the turbocharger from the accident sequence.
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
- Powerplant sys/comp malf/fail during initial climb
- Off-field or emergency landing during landing
- Runway excursion during landing (landing roll)
- Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)
- Unknown or undetermined during initial climb defining event
The NTSB's findings
- Aircraft › Aircraft power plant › Turbocharging (recip only) › Turbocharger › Incorrect service/maintenance
- Aircraft › Aircraft power plant › Turbocharging (recip only) › Turbocharger › Damaged/degraded
- Not determined › Not determined › (general) › (general) › Unknown/Not determined
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 465.1 hours in all; 442.1 in this make and model; 13.4 in the last 90 days; 2.4 in the last 30 days; 465.1 as pilot in command
- Last flight review: March 22, 2019
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: serious injuries
The aircraft
- Airframe total time: 722 hours
- Last inspection: annual inspection, December 8, 2020; 0 hours since
- Maximum gross weight: 3,400 lb
- Seats: 4
- Landing gear: fixed
- Engine: Continental Motors Inc IO-550-N (piston); 722 hours total
The flight
- Destination: VGT Las Vegas NV
- Flight plan: none
- Runway 3, 8,107 ft by 150 ft
Weather at the time
- Light: daylight
- Wind: at 5 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 32°F (0°C), dew point 19°F (-7°C)
- Altimeter: 2995.00 inHg
- Observation at 2:53 pm from KOGD
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
22 documents, released by the NTSB on September 8, 2022. 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.
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
