Accident Piper PA-32R-301 Saratoga N35590,
ASN logo
ASN Wikibase Occurrence # 177192
 
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 22 June 2015
Time:05:15
Type:Silhouette image of generic P32R model; specific model in this crash may look slightly different    
Piper PA-32R-301 Saratoga
Owner/operator:Harry Silsby Md P C
Registration: N35590
MSN: 32R-8013020
Year of manufacture:1979
Total airframe hrs:3136 hours
Engine model:Lycoming IO-540-K1G5D
Fatalities:Fatalities: 0 / Occupants: 4
Aircraft damage: Substantial
Category:Accident
Location:Special Events Beach, Lake Mead, NV -   United States of America
Phase: En route
Nature:Private
Departure airport:Las Vegas, NV (VGT)
Destination airport:El Paso, TX (KELP)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The private pilot reported that, while in cruise flight during the personal flight, the engine started to “sputter” and lose power. During troubleshooting efforts, the engine lost total power. The pilot then attempted to restart the engine without success and subsequently initiated a forced landing on a nearby beach.
A postaccident engine examination revealed that the engine crankshaft would not rotate manually. Disassembly of the engine revealed evidence of wear and heat damage to the Nos. 1 and 2 crankshaft bearing halves. The oil filter contained no contaminants or metallic particles. No further evidence of a preexisting mechanical malfunction was noted during the examination of the engine and airframe.
Damage to main bearings can occur from multiple sources, including oil contamination, excessive loads, or disruption of the lubrication between the bearing face and the main journal. Given that the Nos. 1 and 2 bearings were the only damaged bearings throughout the engine, it is unlikely that oil contamination caused the damage. In addition, given that the Nos. 1 and 2 bearings are located in the forward area of the engine and experience lighter loads than those located in the aft area of the engine, it is unlikely that excessive loads caused the damage. Although a propeller strike could result in an abnormal loading and lubrication of the bearings, a review of the airframe and engine maintenance records revealed no evidence of a reported propeller strike.
Absent one of the above issues, it is likely that a disruption of the lubrication between the bearing face and the main journal resulted in the wear of the Nos. 1 and 2 bearing halves. However, no evidence of oil passage blockage, leaks, or excessive clearance between the bearings and the crankshaft journals was observed; therefore, the reason for the likely lubrication disruption or whether it caused the loss of engine power could not be determined. In addition, the accident bearings had an aluminum-tin intermediate layer, which makes the bearings less robust than those with a copper-alloy intermediate layer; thus, the wear and heat damage could have been preceded by delamination of the aluminum-tin intermediate layer. However, postaccident examination could not determine whether this occurred.
 

Probable Cause: A total loss of engine power during cruise flight for reasons that could not be determined based on the available evidence.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: WPR15LA196
Status: Investigation completed
Duration:
Download report: Final report

Sources:

NTSB
FAA register: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=35590

https://flightaware.com/live/flight/N35590/history/20150622/1144Z/KVGT/KELP

Location

Revision history:

Date/timeContributorUpdates
22-Jun-2015 16:03 Geno Added
28-Jun-2015 01:03 Geno Updated [Time, Source, Damage, Narrative]
21-Dec-2016 19:30 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
01-Dec-2017 13:43 ASN Update Bot Updated [Operator, Other fatalities, Departure airport, Destination airport, Source, Narrative]

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