ERA14LA086 · Cirrus Design Corp SR22
Cirrus Design Corp SR22 · Accident: loss of engine power (total) on approach
From Donegal Springs Airpark (N71) to Upshur County Regional Airport (W22)
Event
- NTSB case
- ERA14LA086
- 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
- N450TX
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Donegal Springs Airpark (N71), Marietta, PATo Upshur County Regional Airport (W22), Buckhannon, WV
- Aircraft age
- About 10 years (built 2004)
- 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
- Approach
- 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)
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The private pilot was conducting a personal cross-country flight. Although recorded data from the airplane's flight displays indicated that, during the cruise portion of the flight, the airplane conducted several aerobatic maneuvers for which it was not certificated and which exceeded its published limitations, the data also showed that the engine operated normally during the maneuvers; therefore, they did not contribute to the loss of engine power.
According to the pilot, when the airplane was about 5 miles from touchdown and at approach speed, he performed his "prelanding" checklist, which he later stated he knew "by heart"; verifying that the fuel boost pump was on; lowering the wing flaps to 50 percent; and setting the fuel mixture to about 60 percent. About 3 miles from the runway threshold, between about 400 and 500 ft above ground level, the pilot increased the throttle to compensate for the normal airspeed loss on final approach; however, the engine did not respond. He reported that he then "moved his hand in a manner to manipulate both throttle and mixture at the same time" and increased both to maximum, but the engine still did not respond. The pilot determined that the airplane was at, or just below, the published minimums for deploying the ballistic parachute system, and he deployed it. After the parachute was deployed, the airplane struck terrain and a motor vehicle.
During examination of the airplane, the flaps were found fully extended, which was the correct configuration for landing. The throttle was found in the "max" position; however, the mixture control was found in a position about 2 inches forward of the idle "cutoff" position, which was consistent with a cruise setting and indicated that it was not in the "maximum" position as reported by the pilot. Recorded data showed that, during the descent, both a reduction in the manifold pressure and fuel flow occurred and that, subsequently, a distinct reduction in exhaust gas temperature for all six cylinders occurred, corroborating that the mixture control was not advanced to maximum for the descent and landing. This information would have been available to the pilot on the airplane's display system and would have provided him sufficient information to note that his improper positioning of the mixture control was causing the loss of engine power.
During the postaccident engine test run, the throttle was advanced and retarded multiple times with no hesitation or stumbling noted. A magneto check was also performed with minimal drop on either magneto. The engine was then set to about 1,800 rpm to simulate an approach to landing and the mixture control was moved to its as-found position. When the throttle was advanced, the engine stumbled and would not respond when the rpm was increased. Given this evidence, it is likely that the pilot's failure to move the mixture lever to the "full rich" position during the approach to landing led to the reduction in engine power.
According to airplane manufacturer, engine manufacturer, and Federal Aviation Administration guidance, during descent, the mixture was required to be adjusted for smooth engine operation, and before landing, the mixture control was required to be placed in the "full rich" position. As noted, the mixture control was not found in the "full rich" position. Postaccident examination and interviews revealed that the airplane's quick reference handbook and the Pilot's Operating Handbook were not available for the pilot to reference during the flight. Further, although an electronic set of checklists was available for use on the airplane's multifunction display, the pilot did not indicate that he had used them. If the pilot had referenced the landing checklist (on paper or on the multifunction display) or manuals, he might have recognized the reason the engine was nonresponsive and moved the fuel control mixture to the proper position for landing and prevented the loss of engine power.
Probable cause
The pilot’s improper in-flight fuel mixture management and failure to use the appropriate checklist or manuals during approach to landing, which resulted in a loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA14LA086
- Event ID
- 20140105X43412
- Case number
- ERA14LA086
- 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: 4aad2916db82c68cea2907be3331d8658c639bd93971bd14f538267d5f288ef6; retrieved 2026-09-15T23:13:54.603Z.