ASN Wikibase Occurrence # 163025
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Saturday 4 January 2014 |
| Time: | 17:35 |
| Type: |  Cirrus SR22 |
| Owner/operator: | Private |
| Registration: | N450TX |
| MSN: | 1063 |
| Year of manufacture: | 2004 |
| Total airframe hrs: | 979 hours |
| Engine model: | Continental IO-550-N |
| Fatalities: | Fatalities: 0 / Occupants: 1 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | East of Upshur County Regional Airport (W22), Buckhannon, WV -
 United States of America
|
| Phase: | Approach |
| Nature: | Private |
| Departure airport: | Marietta, PA (N71) |
| Buckhannon, WV (W22) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
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 aileron rolls for which it was not certificated, yet well inside normal class G load tolerances. 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 90 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. Before exiting the plane, the pilot did set mixture to cutoff and fuel selector to the off position. Multiple people were in and out of the cockpit, and the ballistic parachute was stowed in the cabin, likely manipulating the controls. 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.
Accident investigation:
 |
|
Sources:
NTSB
FAA register: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=450TX
https://flightaware.com/live/flight/N450TX
Location
Media:
Plane makes emergency/crash landing on Brushy Fork Rd in Upshur County pic.twitter.com/bdsBx7sICY
— Chris Lawrence (@WVOutdoors) January 5, 2014Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 05-Jan-2014 03:10 | Geno | Added |
| 05-Jan-2014 03:15 | Geno | Updated [Date, Narrative] |
| 05-Jan-2014 09:52 | harro | Updated [Embed code] |
| 06-Jan-2014 17:32 | sdbeach | Updated [Registration, Embed code] |
| 17-Jan-2014 01:41 | Geno | Updated [Nature, Source, Damage, Narrative] |
| 21-Dec-2016 19:28 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 29-Nov-2017 13:22 | ASN Update Bot | Updated [Other fatalities, Departure airport, Destination airport, Source, Embed code, Narrative] |
| 25-Mar-2018 07:32 | Jamesrm | Updated [Source, Embed code, Narrative] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation