25 Jan 2020: Piper PA32 260

25 Jan 2020: Piper PA32 260 (N55455) — Unknown operator

1 fatality • Lake City, FL, United States

Probable cause

The pilot's exceedance of the airplane's critical angle of attack, which resulted in an aerodynamic stall and subsequent loss of control at low altitude.

— NTSB Determination

Accident narrative

HISTORY OF FLIGHT

On January 25, 2020, about 0930 eastern standard time, a Piper PA32-260, N55455, was destroyed when was involved in an accident near Lake City, Florida. The private pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

A witness stated that the pilot flew to Cannon Creek Airpark (15FL), Lake City, Florida, the weekend before the accident. At that time, the pilot said the engine “cut out” on short final approach to the runway; however, after landing, the pilot performed an engine run-up, and the engine performed normally. The pilot and the witness subsequently opened the engine cowling and observed an oil leak. The pilot contacted a local mechanic to fix the oil leak. A couple of days later, the pilot ran the engine, and no oil leaks were noted. The night before the accident flight, the pilot and the witness taxied the airplane to the fuel tank and topped off the wing tanks and left-wing tip tank, but they did not put fuel in the right-wing tip tank because it had a fuel leak.

On the morning of the accident, the witness and pilot performed a preflight inspection of the airplane and noted no anomalies. The witness watched the airplane take off from runway 36 and noticed that the pilot “turned hard left” after the airplane cleared the trees, which was earlier than normal. The witness returned to his vehicle when he heard a loud bang and saw smoke. He drove over to the smoke and saw that the airplane was engulfed in flames.

WRECKAGE AND IMPACT INFORMATION

The airplane came to rest on the side of a house in a subdivision about 1,000 ft to the west side of the midpoint of the runway. The wreckage was oriented on a heading of 215° and there was no discernable horizontal wreckage path. A postaccident fire consumed the airplane, and only the tail section remained intact and undamaged by fire. The cockpit, instrument panel, firewall, fuselage, and wings were all destroyed by the fire, and the engine accessory case was consumed by fire; the magnetos, fuel pump, carburetor, vacuum pump, and oil filter were destroyed. All major components of the airplane were accounted for at the scene. Control cable continuity was confirmed to the respective controls.

Postaccident examination of the engine revealed the engine crankcase and cylinders were intact. The top spark plugs were removed, and a borescope examination of the cylinder walls, exhaust, intake valves and piston heads revealed no anomalies. The engine’s crankshaft was rotated by hand and thumb compression was established on all cylinders. Valve train continuity was established throughout the engine by observing movement of the rocker arms and rear accessory case gears.

Both propeller blades remained attached to the hub. One blade was bent aft about midblade, and both blades were twisted near the tip.

A witness near the airport captured the airplane engine noise on a video camera. The airplane was not captured by the video, and its position, ground track, speed, and therefore at what point during the accident sequence the captured audio occurred could not be determined. A sound spectrum analysis of the audio by the National Transportation Safety Board Vehicle Recorders Laboratory revealed that during the time audio from the accident airplane’s engine was recorded, the engine rpm was approximately 2,584 rpm, which was slightly below the maximum rated 2,700 rpm.

MEDICAL AND PATHOLOGICAL INFORMATION

An autopsy performed on the pilot by the Office of the Office of the Medical Examiner, Jacksonville, Florida, reported the cause of death as blunt force trauma.

Toxicology testing performed at the FAA Forensic Sciences Laboratory found no tested-for drugs or alcohol.

Contributing factors

  • Pilot
  • Angle of attack — Not attained/maintained

Conditions

Weather
VMC, wind 330/07kt, 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.