# NTSB WPR15LA196: Piper PA 32R-301, N35590, Boulder City, NV, June 22, 2015 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: June 22, 2015, 05:15 local (12:15 UTC) - Place: Boulder City, NV - Coordinates: 35.97861, -114.834724 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=35.9786&lon=-114.8347&mi=10 - Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping) - Defining event: [Enroute-cruise: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341) - Highest injury: No injuries - Injuries: 4 uninjured - Status: Completed, report June 16, 2016 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: LAS FSDO - NTSB case key (mKey): 91415 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR15LA196 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/91415/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=91415 - Page: https://openairdocs.org/ntsb/WPR15LA196 ## Probable cause A total loss of engine power during cruise flight for reasons that could not be determined based on the available evidence. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Not determined](https://openairdocs.org/ntsb-findings/05000000): Not determined › Not determined · Unknown/Not determined (probable cause); cases with it: [Piper PA-32R-301, 3 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md?model=7103218), [All aircraft, 2,247 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md) - [Engine (reciprocating)](https://openairdocs.org/ntsb-findings/01058500): Aircraft › Aircraft power plant · Fatigue/wear/corrosion; cases with it: [Piper PA-32R-301, 2 cases](https://openairdocs.org/ntsb-findings/01058500/cases.md?model=7103218), [All aircraft, 497 cases](https://openairdocs.org/ntsb-findings/01058500/cases.md) - [Engine (reciprocating)](https://openairdocs.org/ntsb-findings/01058500): Aircraft › Aircraft power plant · Damaged/degraded; cases with it: [Piper PA-32R-301, 2 cases](https://openairdocs.org/ntsb-findings/01058500/cases.md?model=7103218), [All aircraft, 497 cases](https://openairdocs.org/ntsb-findings/01058500/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Enroute-cruise: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341) (defining event); cases with it: [Piper PA-32R-301, 6 cases](https://openairdocs.org/ntsb-events/341/sequence.md?model=7103218), [All aircraft, 3,820 cases](https://openairdocs.org/ntsb-events/341/sequence.md) ## Analysis 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. ## Factual narrative On June 22, 2015, about 0515 Pacific daylight time, a Piper PA-32R-301, N35590, experienced a total loss of engine power and landed on a beach of Lake Mead near Boulder City, Nevada. The airplane was registered to an individual, and operated by the pilot under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. The pilot and 3 passengers were not injured; the airplane sustained substantial damage. Visual meteorological conditions prevailed for the flight, which operated on a visual rules flight plan. The cross-country flight originated from North Las Vegas Airport, Las Vegas, Nevada, about 0430. The pilot reported that about 20 minutes after takeoff, with the airplane leveled off at an altitude of about 7,500 feet mean sea level, the engine started to "sputter". In the attempt to regain continuous power, the pilot adjusted the mixture control to rich; however, the propeller stopped spinning. The pilot tried to restart the engine twice but was unsuccessful. Subsequently, he initiated a forced landing onto a nearby beach. The airplane wreckage was examined at Air Transport, Phoenix, Arizona, on July 29, 2015, by representatives from Piper Aircraft, Inc., Lycoming Engines, and Federal Aviation Administration under the supervision of the National Transportation Safety Board (NTSB) investigator-in-charge. Primary flight control cable continuity was established from the rudder and elevator control surfaces to the cockpit controls, and to the wing roots from the yoke for the aileron actuation cables. The engine remained attached to the engine through all four mounts, hoses, wires, and control cables. All six cylinders remained attached to the engine. The two blade variable pitch propeller remained attached to the crankshaft. Neither blade sustained any damage. All engine accessories remained attached to the engine via their respective mounts. All fuel and oil lines were intact and undamaged. The crankshaft was not able to be manually rotated using the propeller. The engine was disassembled to allow for further examination. All six cylinders remained attached to their respective cylinder bays and were undamaged. Cylinders were removed from the engine and it was noted that the cylinder, valves, and rocker arms displayed normal operating and combustion signatures. All six piston faces displayed normal operating and combustion signatures; all of the piston rings were undamaged and were free to move in their respective grooves. There were no anomalies noted with the pistons. The crankshaft remained intact, and all the connecting rods remained free of heat distress. The No. 1 and No. 2 crankshaft bearing exhibited heat signatures at the aft thrust face. Their respective crankshaft thrust surface exhibited significant coloration consistent with an elevated thermal event. There was material transfer present on the thrust surfaces at each end of the bearing; more predominately at the aft portion of the bearing surface. The oil filterwas removed and visually inspected. There were no contaminates or metallic material noted in the filter. The oil suction screen contained a few small pieces of non-ferrous metal particles. The NTSB Material Laboratory examination of the No. 1 and No. 2 bearing halves showed substantial wear with missing Babbitt, exposing the underlying aluminum-tin intermediate layer. Black tint, scoring, and flowed metal was observed at the aft end of the No. 2 bearing interior, and metal particles from Babbitt were present at the chamfer at the forward edge of the No. 1 bearing. Post accident examination of the airframe revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. The complete engine and airframe examination report is appended to this accident in the public docket. A review of maintenance records showed that the most recent annual inspection was completed on July 24, 2014, at a total aircraft time of 3,136.18 hours and tachometer time of 1,718.68 hours. The last major overhaul was dated October 8, 1991, at a total aircraft time of 2,069.5 hours and tachometer time of 573.7 hours. The maintenance record indicated that the bearings were replaced at that time; however, it did not indicate which bearings were replaced. ## Aircraft - Registration: [N35590](https://openairdocs.org/aircraft/N35590), registered now, S/N 32R-8013020, built 1979 (OpenAirDocs) - Reported make and model: PIPER PA 32R-301 - Registry model: [Piper PA-32R-301](https://openairdocs.org/model/piper-pa-32r-301) (registry code 7103218) (OpenAirDocs) - Registry engine: [Lycoming IO-540 series](https://openairdocs.org/engine/lycoming-io-540-series) (registry code 41530, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 32R-8013020 - Year built: 1979 - Airframe hours: 3136.18 - Engines: Lycoming IO-540-K1G5D 300 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Harry Silsby Md P C - Registered owner: Harry Silsby Md P C - Airworthiness certificate: Standard, Normal - Last inspection: Annual, July 24, 2015 - Departed: VGT, LAS VEGAS, NV - Destination: KELP, El Paso, TX - Flight plan: VFR ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 30; injuries: none; private; airplane ratings: single-engine land; medical: class 3, without waivers/limitations; seat: left; flight hours: 195 total, 7 in this make and model, 105 as pilot in command, 20 in the last 90 days, 9 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 260° at 6 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 84 °F, dew point 32 °F - Altimeter: 29.87 inHg - Observed at: KBVU, 2 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20150622011129A](https://openairdocs.org/incident/20150622011129A), Jun 22, 2015: Piper PA-32R-301, Boulder City, NV, Substantial damage. On 22 June 2015, a Piper aircraft, model PA-32, N35590 departed north las vegas airport (vgt) around 0430 for el paso TX, at about 7500 AGL 15 minutes into the… ## Other investigations on N35590 (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB MIA83LA056](https://openairdocs.org/ntsb/MIA83LA056), Jan 3, 1983: Piper PA-32-301R (N35590), Near Vero Beach, FL, substantial damage ## Docket (3 files) The files NTSB released with the investigation on April 26, 2016, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=91415. 1.8 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 594 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40439327&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Airframe and Engine Exam Report (item 2, .PDF, 8 photos, 976 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40439328&FileExtension=.PDF&FileName=Airframe%20and%20Engine%20Exam%20Report-Master.PDF - Materials Laboratory Factual Report 16-001 (item 3, .PDF, 1 photo, 225 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40439329&FileExtension=.PDF&FileName=Materials%20Laboratory%20Factual%20Report%2016-001-Master.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.