Accident Piper PA-22-135 Tri-Pacer N2591A,
ASN logo
ASN Wikibase Occurrence # 198355
 
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:Monday 14 August 2017
Time:10:17
Type:Silhouette image of generic PA22 model; specific model in this crash may look slightly different    
Piper PA-22-135 Tri-Pacer
Owner/operator:Private
Registration: N2591A
MSN: 22-876
Year of manufacture:1952
Total airframe hrs:1986 hours
Engine model:Lycoming O-290-D2
Fatalities:Fatalities: 0 / Occupants: 1
Aircraft damage: Substantial
Category:Accident
Location:Panola County SSW of Marshall, TX -   United States of America
Phase: Landing
Nature:Survey
Departure airport:Jefferson, TX (24F)
Destination airport:Gladewater, TX (07F)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The commercial pilot reported that, about 2 hours into the pipeline surveillance flight, the engine began running roughly. He initially established a course to a nearby airport; however, the engine was not producing enough power to maintain altitude. He subsequently executed a forced landing to a pasture, which resulted in substantial damage to the left wing.

A postaccident engine examination revealed that the No. 3 cylinder exhaust valve fractured at the stem seat. Metallurgical examination revealed that the fracture features were consistent with torsional loading at fracture. The stem was tapered adjacent to the fracture, and interconnected voids and surface oxidation were observed at the fracture surface. The presence of voids, tapering of the stem, and oxidation are consistent with high-temperature deformation under stress. Further examination revealed grain structure and subsurface oxidation consistent with exposure to elevated temperatures over an extended period of time, consistent with a stuck valve condition.

Factors leading to stuck exhaust valves include excessive engine temperature, dirty or contaminated engine oil, high lead content fuels, hot engine shut-downs, and poor engine baffling. Running engines past the recommended overhaul interval or at elevated temperatures risks creating an exhaust valve fatigue event. The investigation was unable to determine the exact combination of elements that led to the stuck valve. However, based on the available maintenance records, the most recent engine overhaul was completed in 1968, and it is likely that the extended 49-year interval contributed to the stuck valve. While this exceeded the engine manufacturer's 12-year or 1,500-hour time between overhaul interval, the operator was not required to comply under current regulations due to the type of operation.



Probable Cause: A stuck exhaust valve, which resulted in the failure of the valve and a loss of engine power. Contributing to the valve failure and loss of engine power was the extended time since the last overhaul.

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

Sources:

NTSB

FAA register: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=2591A

Location

Revision history:

Date/timeContributorUpdates
14-Aug-2017 21:58 Geno Added
15-Jul-2019 18:07 ASN Update Bot Updated [Time, Operator, 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