NTSB CAROL · Event
Event ERA20LA274
Registry · N3025L
FAA Aircraft Registry record.
Make / Model
PIPER PA-32RT-300T
Engine
LYCOMING TIO 540 SER (250 hp)
Seats / Engines
7 seats · 1 engine
Last airworthiness date
19790917
ADS-B equipped
Yes — Mode-S A329D2
Registrant of record
BEACON AVIATION FLIGHT SERVICES LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
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.
Factual 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. The pilot and four passengers boarded the airplane for a personal cross-country flight. Although the pilot reported that the airplane veered to the left uncontrollably during the takeoff roll, security camera video showed that the airplane tracked the runway heading until the airplane’s pitch attitude increased to the point where a tail strike occurred about 1,660 ft down the 2,986-ft-long runway. 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 postaccident examination of the airplane. According to the pilot’s preflight performance calculations, the airplane was about 127.3 pounds below maximum gross weight; the density altitude was 1,227 ft; and the airplane’s estimated takeoff ground roll was 1,500 to 1,600 ft. Review of the weather conditions present at the time of the accident indicated that the density altitude was 2,622 ft. According to the performance charts for the airplane, at a density altitude of 2,622 ft and the airplane weight calculated by the pilot, the airplane’s takeoff ground roll would be about 1,630 ft. A Koch chart indicated that for the accident conditions as compared to standard temperature sea level values, a 28% increase in takeoff distance should have been anticipated by the pilot along with a 21% decrease in climb rate. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- — Personnel issues-Task performance-Planning/preparation-Performance calculations-Pilot
- — Environmental issues-Conditions/weather/phenomena-Temp/humidity/pressure-High density altitude-Effect on operation
- — Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot
Verbatim from NTSB's published report. Source file
NTSB_2020_ERA20LA274.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (runway excursion). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- SKYbrary (Eurocontrol) 2024 · SKYbrary article
Runway Excursion — SKYbrary Knowledge Base
SKYbrary runway excursion review — RE-OE (overruns) + RE-LO (lateral). Risk drivers: long landing, high approach speed, contaminated surface, tailwind, mis-set autobrakes.
- NTSB Aircraft Accident Reports 2019 · Accident report
Embraer ERJ 175 Runway Excursion at Charlotte Douglas
Republic Airline ERJ-175 runway excursion CLT, January 2018. Examines a low-energy runway excursion involving misuse of autobrakes + thrust reverser response after a high-crosswind landing on a contam…
- NASA NTRS 2025 · Presentation
Uncovering Resilient Behavior in the Aviation Safety Reporting System Using Large Language Models
Resiliency is present in everyday life, both in system design and exhibited by the operators that function within these systems.
- NASA NTRS 2025 · Conference Paper
Uncovering Resilient Behavior in the Aviation Safety Reporting System Using Large Language Models
Resiliency is present in everyday life, both in system design and exhibited by the operators that function within these systems.
- Flight Safety Foundation 2024 · FSF / AeroSafety World
Runway Safety Initiative Final Report (RSI)
Foundation Runway Safety Initiative final report — comprehensive analysis of runway excursion + incursion risk drivers worldwide.
- Semantic Scholar 2020 · Article
Towards online prediction of safety-critical landing metrics in aviation using supervised machine learning
Abstract In recent years, due to the increased availability of data and improvements in computing power, application of machine learning techniques to various aviation safety problems for identifying,…
Browse the full corpus — academia portal ↗