Accident Cessna P210N Centurion N210PF,
ASN logo
ASN Wikibase Occurrence # 214955
 
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 1 September 2018
Time:09:00
Type:Silhouette image of generic P210 model; specific model in this crash may look slightly different    
Cessna P210N Centurion
Owner/operator:Private
Registration: N210PF
MSN: P21000018
Year of manufacture:1978
Total airframe hrs:3859 hours
Engine model:Continental TSIO-550-P
Fatalities:Fatalities: 0 / Occupants: 4
Aircraft damage: Substantial
Category:Accident
Location:South of Crete Municipal Airport (KCEK), Crete, NE -   United States of America
Phase: Landing
Nature:Private
Departure airport:Crete Municipal Airport, NE (KCEK)
Destination airport:Cozad Municipal Airport, NE (KCZD)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The pilot started the "turbo-normalized" 310-horsepower engine, but then it stopped. He stated that he used the low-pressure boost pump to restart the engine and then turned off the boost pump after it had started. He indicated that he completed an engine run-up before takeoff and that the engine was operating normally. The airplane traveled about halfway down the runway before it became airborne. When the airplane had a positive rate of climb, the pilot raised the landing gear and flaps. He stated that when the airplane was about 500 ft above ground level, he heard the engine "miss," and the engine did not seem to be producing total power. He turned on the low-pressure boost pump and turned back toward the airport, but the engine eventually lost total power. He performed a gear-up forced landing to a cornfield; the airplane impacted the ground hard and slid through the cornfield on its belly.

A witness who watched the airplane take off reported that the airplane sounded like it was full throttle but was "overweight sounding" during the takeoff. He reported that the airplane "finally got in the air at the end of the runway." He stated that it was "running rich" and that he could see "dark exhaust" trailing the airplane during the takeoff. The airplane veered to the right, and he lost sight of it behind a tree line.

An engine monitor installed on the airplane indicated that the manifold pressure reached 37 inches of mercury (inHg) and fuel flow reached 48 gallons of fuel per hour (gph) during takeoff. The pilot operating handbook for the supplemental type certificated engine stated that the full rated horsepower is achieved at 31 inHg of manifold pressure and that full throttle fuel flow during takeoff is 35-37 gph.

The engine was run on the engine manufacturer's test cell and operated within normal operating specifications. There were no mechanical malfunctions or failures with the turbocharger controller, wastegate actuator, pressure relief valve, manifold pressure transducer, and fuel flow transmitter that would have precluded normal operation.

However, a static demonstration run on the same airplane model/engine conversion, with the oil line from the wastegate to the wastegate controller disconnected to simulate a wastegate stuck in the closed position, showed similar indications of manifold pressure as on the accident flight; the manifold pressure far exceeded the design criteria. Sporadic black smoke was observed coming from the turbo exhaust. The engine was rough and lost power as the mixture became richer while the throttle was held fully forward. Reducing the throttle position to reduce manifold pressure allowed more normal operation to resume and the fuel flow to reduce to a less rich mixture. The engine resumed somewhat normal operating conditions except for the wastegate still being fully closed.

Given this information, it is likely that the turbocharger wastegate was "stuck" in the closed position during the takeoff roll for reasons that could not be determined because it was not stuck or binding during the postaccident examination. The stuck wastegate resulted in high manifold pressure and high fuel flow, which caused the fuel mixture to be excessively rich. Instead of pulling back on the throttle to reduce the manifold pressure, the pilot turned on the fuel boost pump, which exacerbated the problem; the fuel mixture became too rich, and the engine stopped producing power.

Probable Cause: The stuck turbocharger wastegate in the closed position for reasons that could not be determined based on the available information. Also causal was the pilot's failure to reduce the throttle during takeoff when the manifold pressure and fuel flow exceeded the takeoff limitations and the pilot's decision to turn on the fuel boost pump, which exacerbated the excessively rich fuel mixture and resulted in a total loss of engine power.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: CEN18LA363
Status: Investigation completed
Duration: 1 year and 9 months
Download report: Final report

Sources:

NTSB
FAA register: https://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=210PF%20

History of this aircraft

Other occurrences involving this aircraft
29 May 2013 N210PF Private 0 North Texas Regional Airport - KGYI, Sherman/Denison, TX mis
Runway excursion
6 January 2014 N210PF Private 0 Highway 60, Mulberry, FL non

Location

Revision history:

Date/timeContributorUpdates
02-Sep-2018 01:41 Geno Added
05-Sep-2018 05:05 Geno Updated [Time, Aircraft type, Registration, Cn, Operator, Total fatalities, Total occupants, Other fatalities, Phase, Departure airport, Source, Narrative]
25-Sep-2018 18:56 Iceman 29 Updated [Time, Destination airport, Source, Damage, Narrative]
08-Jun-2020 08:39 ASN Update Bot Updated [Time, Operator, Nature, Departure airport, Source, Narrative, Accident report, ]
08-Jun-2020 17:24 harro Updated [Departure airport, Destination airport, Source, Narrative, Accident report, ]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org