CEN17LA263 · Cirrus Design Corp SR22
Cirrus Design Corp SR22 · Accident: loss of engine power (total) during initial climb
From Corydon Airport (0E9) to Centerville Municipal Airport (TVK)
Event
- NTSB case
- CEN17LA263
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cirrus Design Corp SR22
- Aircraft type
- Cirrus SR22
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N929DE
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Corydon Airport (0E9), Corydon, IATo Centerville Municipal Airport (TVK), Centerville, IA
- Aircraft age
- About 15 years (built 2002)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Initial climb
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of engine power (total)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Before takeoff, the private pilot completed an engine run-up and noted no anomalies. However, witnesses and the passenger described the engine as "pinging," "popping," and "skipping a beat" during the takeoff roll and shortly after takeoff. The pilot turned the airplane on course toward the destination when the "engine started sputtering and died." The pilot attempted an engine restart by turning on the fuel boost pump, switching fuel tanks, checking the mixture lever, and cycling the magneto switch; he was unable to restart the engine. Due to the low altitude at the time of the loss of engine power, the pilot did not deploy the airframe parachute system and instead performed a forced landing to a wooded area. Damage to the crankshaft prevented a functional test of the engine; however, a teardown examination revealed no mechanical anomalies that would have precluded normal operation.
Probable cause
A total loss of engine power for reasons that could not be determined because postaccident examination of the engine and airframe did not reveal any anomalies that would have precluded normal operation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN17LA263
- Event ID
- 20170711X30650
- Case number
- CEN17LA263
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: c970d97c03ee0b99bc5d29dbeebf1b674c44d5ee382f2513b34dafa8185f9f70; retrieved 2026-09-16T05:31:50.019Z.