31 Oct 2016: PIPER PA32 300

31 Oct 2016: PIPER PA32 300 (N3941X) — Unknown operator

No fatalities • Bartow, FL, United States

Probable cause

A total loss of engine power during approach for reasons that could not be determined because engine examinations did not reveal any evidence of mechanical malfunctions or failures that would have precluded normal operation.

— NTSB Determination

Accident narrative

On October 31, 2016, at 1502 eastern daylight time, a privately owned and operated Piper PA-32-300, N3941X, was substantially damaged during a forced landing in Bartow, Florida. The pilot was not injured. Visual meteorological conditions prevailed, and no flight plan was filed for the personal flight that was operated under the provisions of 14 Code of Federal Regulations Part 91. The flight originated at Sanford International Airport (SFB), Orlando, Florida, and was destined for Bartow Municipal Airport (BOW), Bartow, Florida.According to the pilot, after entering a left downwind leg for the runway 05 traffic pattern at BOW, he reduced engine power and the airplane began to vibrate and shake. The engine then lost all power, while the propeller continued to windmill. He attempted to restart the engine using the emergency checklist procedures but was unsuccessful. He determined he would not be able to reach the runway and maneuvered toward a nearby pasture for an emergency landing. During the landing rollout, the airplane struck a fence damaging the left wheel hydraulic brake line which caused a loss of brake pressure. When he applied the brakes, he lost directional control and the nose landing gear collapsed.

Examination of the airplane by a Federal Aviation Administration (FAA) inspector revealed that the firewall was damaged, and the fuselage skin aft of the firewall was wrinkled. An unmeasured amount of fuel was present in all four fuel tanks, and fuel was present at the fuel injector nozzles. Oil was present in the crankcase, and cylinder compression was attained on all cylinders when the propeller was rotated by hand. While rotating the engine, a grinding/crunching noise occurred once, but was not repeatable. The magnetos made noise consistent with rotation but were not tested for spark. The engine oil filter contained some particles.

According to the FAA inspector, the engine had accrued about 2,060 total hours since overhaul, and the airplane had flown about 25 hours since the most recent annual inspection.

The engine was examined again by a National Transportation Safety Board Investigator. After removal of the lower engine cowling, and removal of the top spark plugs, the engine's crankshaft was manually rotated. The crankshaft rotated without any signs of grinding. Thumb compression was attained on all cylinders. The oil "finger" screen was removed, it was clean and clear of debris. The No. 4 cylinder was removed to gain access to the case and view the crankshaft, camshaft and internal components. The push rods were clean, and no carbon or metal was present. There was no rust present in the cylinder, no scoring from rings or any signs of rubbing. The valves were seated and no traces of overtemperature. The pushrods and rockers were clean, lubricated, and no metal was observed. The piston and rings were clean and exhibited no marks. The connecting rod was clean, moved freely and was lubricated. The camshaft, crankshaft and internal components that could be seen from this opening were clean, with no corrosion and no metal particles visible.

The oil filter was cut open during the previous examination and the filter case contained carbon deposits at the bottom of the filter case. Both magnetos were removed, manually rotated and produced spark from all leads. The fuel servo was removed and inspected for debris, the servo was clean and the finger filter was clear of debris. The air and fuel diaphragms were in intact with no tears or marks. The fuel filter in the mid center section of the airplane was removed for examination. It was also clean, absent of debris, and contained aviation gasoline. All fuel injectors were removed and inspected. They were all clean and absent of debris. The flow divider "spider" was opened for examination, it was clean and clear of debris and the diaphragm was intact. The air filter was removed and was also found clean and clear of debris.

Contributing factors

  • Contributed to outcome

Conditions

Weather
VMC, wind 060/12kt, 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.