5 Jul 2020: Piper PA32 300 — Zahasky Richard

5 Jul 2020: Piper PA32 300 (N4079R) — Zahasky Richard

No fatalities • Eveleth, MN, United States

Probable cause

The seizure of the airplane’s engine-driven fuel pump due to internal contamination, which led to a total loss of engine power. The source of the contamination could not be determined based on available evidence.

— NTSB Determination

Accident narrative

On July 5, 2020, about 1200 central daylight time, a Piper PA-32-300, N4079R, was destroyed when it was involved in an accident near Eveleth, Minnesota. The pilot and passenger sustained minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

The pilot reported that the airplane had about 55 gallons of fuel onboard before the flight began, including 14 gallons in the left-tip tank. The pilot also reported that he started the engine with a main tank and then switched to the left-tip tank for takeoff; he did not recall switching fuel tanks after that. After takeoff, the airplane climbed to 7,500 ft mean sea level and leveled off. Shortly afterward, the engine lost total power. The pilot’s attempts to restart the engine were not successful, so he decided to glide the airplane to the nearest airport. When the pilot realized that the airplane had insufficient altitude to reach the target airport, he executed a forced landing to a wooded area. During the forced landing, both wings separated from the airplane; the fuselage and tail surfaces were impact damaged; and various parts of the airplane, including the cabin section, were damaged by postimpact fire.

Postaccident examination of the airplane revealed that the drive coupling on the engine-driven fuel pump had fractured. No other anomalies were found during the examination.

Subsequent laboratory examination of the engine-driven fuel pump found that the drive coupling fracture surface had features consistent with torsional overstress. Additional features resembling ratchet marks were observed around the shaft. No evidence of fatigue was noted, but smearing was found on the outer edge of the fracture surface.

Disassembly of the pump revealed difficulty rotating the input shaft by hand and that the input shaft, once freed, could only be rotated about 90° before it seized. The disassembly of the pump also revealed that the spring for the bypass valve was missing. Wear marks indicated that the spring had been present at some time during the life of the pump. Material consistent with rust was found on several internal components of the pump. The ends of the rotor vanes that interfaced with the pump sidewalls showed evidence of smeared material, transfer marks, and other oxidized particles, which were consistent with adhesive wear and ferrous wear debris. The rotor shaft had a discolored region consistent with heat discoloration, which was consistent with frictional heating of the shaft. The rotor shaft also had areas of pitting and missing material on the outside edge of the rotor, which was consistent with spalling.

The part number identified on the engine-driven fuel pump was subject to Textron Lycoming Mandatory Service Bulletin No. 539A, issued November 22, 2000, which was a reprint of Crane/Lear Romec Service Bulletin No. RG9080-73-001, issued November 29, 1999. The Crane/Lear Romec service bulletin introduced pump design enhancements to improve relief valve housing sealing characteristics. These enhancements included actions to ensure that valve cover screws are tightened to correct torque values. Materials examination of the pump showed the gaskets were consistent with unmodified original components indicating the accident fuel pump had not been modified in accordance with the service bulletin.

The pilot reported that the airplane’s maintenance records were in the airplane at the time of the accident. The maintenance records were not subsequently found.

Contributing factors

  • Fuel pumps — Failure
  • Not serviced/maintained

Conditions

Weather
VMC, wind 200/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.