CEN22LA117 · Cirrus Design Corp SR22T
Cirrus Design Corp SR22T · Accident: powerplant system/component malfunction/failure en route
From Indianapolis Executive Airport (TYQ) to Lincoln Airport (LNK)
Event
- NTSB case
- CEN22LA117
- 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
- Event fatalities
- Unknown
- 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 SR22T
- 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
- N317KJ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Indianapolis Executive Airport (TYQ), Zionsville, INTo Lincoln Airport (LNK), Lincoln, NE
- Aircraft age
- About 3 years (built 2019)
- 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
- En route
- 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
- Powerplant system/component malfunction/failure
- 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
- Aircraft › Aircraft power plant
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that the engine start, taxi, and run-up were normal. The night flight proceeded uneventfully until about 60 nm from the destination airport when the engine briefly stuttered and started to run rough. The pilot stated that he told air traffic control that the engine was running rough and requested to divert to an airport located about 39 nautical miles (nm) east of the destination airport. About 40 nm from the destination airport, the pilot told air traffic that the engine smoothed out and he wanted to continue the flight to the destination airport. About 6 nm from the destination airport, the pilot told air traffic that he would be unable to make it to the runway due to engine power loss and was going to look for a field where he could land. He located a field and deployed the airframe parachute. The airplane landed, under parachute, in the field and sustained substantial damage to the fuselage. Recorded avionics data for the flight showed that the abnormal engine indications began about 100 nm from the destination airport and continued to the end of the flight. The pilot continued the flight and passed two airports where a safe precautionary landing could have been performed while operating in night light conditions, which increased the risk of finding a safe area to perform an off-airport landing. Postaccident examination of the engine revealed a catastrophic engine failure. The No. 4 and 5 cylinders were not connected to their respective crankpins. The No. 5 cylinder crankpin surface lacked the deformation and scoring found on the No. 4 cylinder crankpin, suggesting that the No. 5 piston connecting rod separated from its crankpin and that material from the No. 5 cylinder induced foreign object damage and subsequent failure to the remaining portions of the engine.
Probable cause
The pilot’s decision to continue the flight with abnormal engine indications and the subsequent failure of the No. 5 cylinder connecting rod for unknown reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN22LA117
- Event ID
- 20220211104629
- Case number
- CEN22LA117
- 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: local date, investigation status, coordinates, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2022-02-11.
- API snapshot SHA-256: 4db2c1da439e68b38dca283351f52185a12026efb3cb8e1a57e53270d7bba521; retrieved 2026-09-16T14:57:10.181Z.