The U.S. aircraft register, updated daily
Accidents · NTSB ERA14LA086 · Final report

Cirrus Design CORP SR22 accident near Buckhannon, West Virginia, January 4, 2014

On January 4, 2014 at about 10:35 pm local time, a 2004 Cirrus Design CORP SR22, registered N450TX, was substantially damaged in an accident during approach near Buckhannon, West Virginia (Upshur County Regional 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 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.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
January 4, 2014 · about 10:35 pm local time
Place
Buckhannon, West Virginia · Upshur County Regional Airport · map
Type
Accident
Injuries
1 person had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Cirrus Design CORP SR22, built 2004
Registration
N450TX · registry record · serial 1063
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

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

  1. Miscellaneous/other during enroute (descent)
  2. Loss of engine power (total) during approach defining event
  3. Off-field or emergency landing during emergency descent

The NTSB's findings

  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • cause Personnel issues › Task performance › Use of equip/info › Use of manual › Pilot
  • cause Personnel issues › Task performance › Use of equip/info › Use of checklist › Pilot
  • cause Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot
  • cause Aircraft › Aircraft power plant › Engine controls › Mixture control › Incorrect use/operation
  • Environmental issues › Physical environment › Terrain › (general) › Contributed to outcome
  • Environmental issues › Physical environment › Object/animal/substance › Ground vehicle › Contributed to outcome

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 544 hours in all; 501 in this make and model; 58 in the last 90 days; 13 in the last 30 days; 364 as pilot in command
  • Last flight review: May 3, 2013
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: minor injuries

The aircraft

  • Airframe total time: 979 hours
  • Last inspection: annual inspection, February 20, 2013
  • Maximum gross weight: 3,400 lb
  • Seats: 4
  • Landing gear: retractable
  • Engine: Cont Motor IO-550-N (piston); 979 hours total

The flight

  • Departed from: N71 Marietta PA at 8:23 pm
  • Destination: W22 Buckhannon WV
  • Flight plan: none
  • Runway 29, 4,201 ft by 75 ft

Weather at the time

  • Light: dusk
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 43°F (6°C), dew point 23°F (-5°C)
  • Altimeter: 30.09 inHg
  • Observation at 10:35 pm from W22, 1 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

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.