Skip to content

Atlas / NTSB / ERA20LA272

NTSB CAROL · Event

Event ERA20LA272

2020-08-02 Alabaster, Alabama, United States Airport · EET None 1 aircraft Status: Completed

Registry · N7750Y

FAA Aircraft Registry record.

Make / Model

PIPER PA-30

Year of manufacture

1965 · 55 years old at event

TCDS

A1EA · PIPER AIRCRAFT INC

Engine

LYCOMING IO-320 SERIES (150 hp)

Seats / Engines

6 seats · 2 engines

Last airworthiness date

19651213

ADS-B equipped

Yes — Mode-S AA7E09

Registrant of record

WELDEN CHARLES R

Source: FAA Aircraft Registry (releasable master file).

Aircraft involved

Probable cause & findings

A loss of control and lack of climb performance shortly after takeoff for reasons that could not be determined based on available evidence, resulting in a collision with terrain.

Factual narrative

On August 2, 2020, about 1010 central daylight time, a Piper PA-30, N7750Y, was substantially damaged when it was involved in an accident at Shelby County Airport (EET), Alabaster, Alabama. The flight instructor and pilot receiving instruction were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 instructional flight. The flight instructor reported that he was providing instruction to a commercial pilot for a multiengine rating. They briefed the procedures for a simulated short-field takeoff. The pilot receiving instruction taxied onto runway 16, applied brakes, then applied full power. Following an uneventful takeoff roll, the pilot receiving instruction rotated and raised the landing gear selector. The airplane then yawed to the right toward a line of trees. The instructor took the controls and attempted to correct with left rudder and aileron inputs; however, altitude could not be maintained, and the airplane descended to the ground. After touchdown, the landing gear collapsed, and the airplane came to rest against a fence and trees. The flight instructor reported in an interview that he did not recall any unusual engine indications or sounds and there was not time to feather a propeller. After applying rudder and aileron to counter the yaw to the right, the airplane “quit flying.” After the accident, while securing the airplane, he placed the fuel tank selectors to the OFF positions. An inspector with the Federal Aviation Administration responded to the accident site and examined the wreckage. He reported that there was structural damage to the airplane's wings, fuselage, and empennage. The wreckage was examined by the National Transportation Safety Board investigator-in-charge on October 6, 2020, at the wreckage recovery facility. Flight control continuity was confirmed from the cockpit controls to the ailerons, rudder, and stabilator. The left and right fuel tank selector handles were in the OFF positions. Both engines were examined, and no pre-impact anomalies were noted with either engine. Both the left and right propellers exhibited leading edge gouges and chordwise scratches. The flight instructor was providing instruction to a commercial pilot toward a multiengine rating. The pilot receiving instruction taxied onto the runway for a simulated short-field takeoff. Following an uneventful takeoff roll, the pilot receiving instruction rotated and raised the landing gear selector. The airplane then yawed to the right toward a line of trees. The instructor took the controls and attempted to correct with left rudder and aileron inputs; however, altitude could not be maintained, and the airplane descended to the ground. After touchdown, the landing gear collapsed, and the airplane came to rest against a fence and trees, resulting in substantial damage to the airframe. The pilots did not recall any abnormal engine indications or sounds other than the right yaw, and there was insufficient time to feather an engine before the airplane contacted the ground. Examination of the airframe revealed no evidence of a malfunction or anomaly with the flight controls. The propellers on both engines exhibited signatures consistent with power at impact. An examination of both engines revealed no evidence of an anomaly or malfunction that would have precluded normal operation. The reason for the right yaw and lack of climb performance could not be determined. 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).

  • Not determined-Not determined-(general)-(general)-Unknown/Not determined
  • Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Yaw control-Attain/maintain not possible
  • Aircraft-Aircraft oper/perf/capability-Aircraft capability-Climb capability-Attain/maintain not possible

Verbatim from NTSB's published report. Source file NTSB_2020_ERA20LA272.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.

Related research

What the literature says.

Academic papers and agency reports matching this event's aircraft type or causal vocabulary (loss of control). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.

Browse the full corpus — academia portal ↗