1 Aug 2020: Piper PA32RT 300T

1 Aug 2020: Piper PA32RT 300T (N3025L) — Unknown operator

No fatalities • Honesdale, PA, United States

Probable cause

The pilot’s premature rotation for takeoff, which resulted in a tail strike and subsequent runway excursion. Contributing to the accident was the pilot’s inadequate preflight planning, which failed to accurately determine and account for the effects of high-density altitude on performance.

— NTSB Determination

Accident narrative

On August 1, 2020, about 0750 eastern daylight time, a Piper PA-32RT-300T, N3025L, was substantially damaged when it was involved in an accident in Honesdale, Pennsylvania. The pilot and four passengers were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. According to the pilot, he was planning to fly from Cherry Ridge Airport (N30), Honesdale, Pennsylvania, to Ocean City Municipal Airport (OXB), Ocean City, Maryland. Before takeoff from runway 36, he confirmed that the electric fuel boost pump was on, and the mixture and propeller controls were full forward. He increased engine power to full throttle with the brakes held, then released the brakes and initiated the takeoff. He noticed the airplane was veering to the left, which did not correct with right rudder input. The veering became worse as the airplane accelerated. About halfway down the runway, at 70 to 71 knots, which was below rotation speed, the airplane was near the left edge of the runway, and he attempted to get airborne by pulling back on the control wheel. The airplane may have gotten slightly airborne but did not rotate. He felt the tail "bump" and noted the airplane was off the left side of the runway. The airplane subsequently came to rest in grass with the nose landing gear collapsed. Review of security camera footage indicated that the pilot back taxied to the end of the runway before takeoff. During the takeoff roll, the airplane appeared to be tracking the runway heading until the airplane’s pitch attitude increased to the point where a tail strike occurred about 1,660 ft down the runway from where the takeoff roll began. The nose of the airplane then pitched down rapidly; the nose landing gear collapsed; and the airplane veered off the left side of the runway in a nose low attitude, struck vegetation and terrain, and came to rest. No evidence of any preimpact failures or malfunctions was found during examination of the wreckage by a Federal Aviation Administration (FAA) inspector. Review of the FAA Digital Chart Supplement for N30 indicated that the field elevation was 1,357 ft above mean sea level. Runway 36 was 2,986-ft-long, had a 0.6% uphill gradient, and had trees off the departure end. Review of the pilot’s weight and balance loading form submitted on September 8, 2020, indicated that the airplane’s takeoff weight was 3,472.7 pounds, which was 127.3 pounds below maximum gross weight.

Review of the pilot’s performance planning indicated that he calculated the density altitude as 1,227 ft and estimated the airplane’s takeoff ground roll as 1,500 to 1,600 ft.

According to the weather report from Pocono Mountains Municipal Airport (MPO) located about 24 nautical miles from N30, the temperature at the time of the accident was about 22°C. Using this temperature, the density altitude at N30 was calculated to be 2,622 ft. According to the performance charts for the airplane, with no wind, at a density altitude of 2,622 ft, and an airplane weight of 3,472.7 pounds, the airplane’s takeoff ground roll would be about 1,630 ft.

A Koch chart indicated that for the accident conditions, there would be a 28% increase in takeoff distance and a 21% decrease in rate of climb as compared to standard temperature sea level values. Under these conditions, a 2,986-ft-long runway would be equivalent to a standard temperature sea level runway length of about 2,330 ft.

Contributing factors

  • Pilot
  • Pilot
  • Effect on operation

Conditions

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