22 Jun 2015: PIPER PA 32R-301 — HARRY SILSBY MD P C

22 Jun 2015: PIPER PA 32R-301 (N35590) — HARRY SILSBY MD P C

No fatalities • Boulder City, NV, United States

Probable cause

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

— NTSB Determination

Accident 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 filter was 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.

Contributing factors

  • Fatigue/wear/corrosion
  • Damaged/degraded

Conditions

Weather
VMC, wind 260/06kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.