Loss of control Accident Piper PA-34-220T Seneca III N263DM,
ASN logo
ASN Wikibase Occurrence # 201866
 
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 25 November 2017
Time:13:45
Type:Silhouette image of generic PA34 model; specific model in this crash may look slightly different    
Piper PA-34-220T Seneca III
Owner/operator:Private
Registration: N263DM
MSN: 348133101
Year of manufacture:1981
Total airframe hrs:3502 hours
Engine model:Continental LTSIO-360-KB
Fatalities:Fatalities: 0 / Occupants: 4
Aircraft damage: Substantial
Category:Accident
Location:Cambria County, WSW of Ebensburg, PA -   United States of America
Phase: Landing
Nature:Private
Departure airport:Washington-Daviess County Airport, IN (KDCY)
Destination airport:Ebensburg, PA (9G8)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The private pilot stated that the airplane's left engine had recently started to leak a significant amount of oil; however, two mechanics looked at the engine the day before the accident flight, and the source of the leak could not be located. On the day of the accident, the pilot topped off his fuel tanks and put 2 quarts of oil in the left engine, bringing the oil level up to 7 quarts. He then departed on a long cross-country personal flight. About 10 to 15 miles from the destination airport, the left engine low-oil-pressure light came on. When the airplane was 5 miles from the airport, the left engine lost total power, and the propeller feathered. The pilot chose to land downwind due to having only one working engine; however, his approach was too fast and too high, so he decided to go around. As the airplane began a shallow climb, the pilot entered a left turn to avoid mountains. While in the turn, he realized that he was not going to make it back to the airport and increased the right engine's throttle to full power. This overboosted the turbocharger-equipped engine, which stopped producing power. The airplane stalled and impacted trees.

A postaccident examination of the airplane revealed streaks of oil on the top and under the left engine cowling just aft of the oil filler door. Oil was also observed under the left wing. The left engine's oil filler cap was still on the filler neck but did not seat properly and would partially lift off the seat if it was pulled upward. The cap's locking mechanism was corroded, and the locking tangs were bent. A teardown examination of the left engine revealed that the No.1 and No. 2 connecting rods had failed, and their associated crankshaft journals displayed heat distress, consistent with oil starvation. The No.1 piston exhibited signatures of detonation. It was not determined what caused the piston to detonate, but a download of the onboard engine analyzer revealed that the cylinder head temperature was higher on that cylinder for most of the accident flight. The exact source of the oil leak could not be determined based on available evidence. The pilot made an improper decision to fly the airplane with a known oil leak, which ultimately led to the total loss of engine power due to oil starvation. Further, although the pilot decided to land downwind due to having only one working engine, the tailwind was significant, and this decision led to his attempted go-around and loss of control.

Probable Cause: The pilot's improper decision to fly an airplane with a known oil leak, which led to a total loss of engine power due to oil starvation. Contributing to the accident was the pilot's decision to land with a tailwind, which led to his attempted go-around and subsequent loss of control.

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

Sources:

NTSB

Location

Images:


Photo: NTSB

Revision history:

Date/timeContributorUpdates
25-Nov-2017 23:39 Geno Added
26-Nov-2017 01:19 Geno Updated [Aircraft type, Registration, Cn, Operator, Source, Narrative]
09-Dec-2017 03:44 Geno Updated [Time, Phase, Departure airport, Destination airport, Source, Narrative]
01-Oct-2019 18:08 ASN Update Bot Updated [Operator, Country, Nature, Departure airport, Destination airport, Source, Narrative, Accident report, ]
01-Oct-2019 19:42 harro Updated [Country, Departure airport, Source, Narrative, Photo, 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