Skip to content

Atlas / NTSB / WPR20LA111

NTSB CAROL · Event

Event WPR20LA111

2020-03-18 Eagle Creek, Oregon, United States Airport · OR65 Serious 1 aircraft Status: Completed

Registry · N7155Y

FAA Aircraft Registry record.

Make / Model

PIPER PA-30

Year of manufacture

1963 · 57 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

19631031

ADS-B equipped

Yes — Mode-S A991BE

Registrant of record

SHEASLEY GEORGE

Source: FAA Aircraft Registry (releasable master file).

Aircraft involved

Probable cause & findings

The pilot's loss of airplane control during takeoff due to his left shoe’s interference with the rudder pedal.

Factual narrative

On March 18, 2020, about 1700 Pacific daylight time, a Piper PA-30 airplane, N7155Y, was destroyed when it was involved in an accident near Estacada, Oregon. The pilot was seriously injured. The airplane was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 personal flight. The pilot reported that he had just finished minor maintenance on the airplane. He conducted a thorough run-up with no anomalies and proceeded to the runway. He positioned the airplane just left of the centerline and held the brakes for a short-field takeoff. After adding full power, he released the brakes and directed the airplane toward the center of the runway. Once the airplane was centered, he attempted to realign the nose of the airplane with the runway; however, the airplane kept turning left. At the same time, the airplane reached 80 knots and lifted off the runway. The pilot attempted to add right rudder, but the airplane would not turn; he noted that his left shoe was stuck between the rudder pedals. The airplane continued to turn left, so he reduced power on the right engine in attempt to straighten the airplane. By the time his foot was freed from the rudder pedal, the airplane was headed directly towards a large tree along the left side of the runway. He pulled back on the yoke and attempted to climb, but the airplane struck several trees and a postimpact fire ensued. The pilot reported there were no mechanical failures or malfunctions that would have precluded normal operation. Security cameras captured the accident airplane taking off and impacting trees. The video of the accident was consistent with the pilot’s description of the accident flight. On scene examination by a Federal Aviation Administration inspector revealed the debris path was about 150 feet long. The airplane was heavily fragmented, and several portions exhibited thermal damage. The first identified point of impact was a tree located about 300 southwest of the runway. The next pieces of debris were the left wingtip, outboard left wing, and outboard right wing. Continuing along the debris path was the left engine, which came to rest against trees and a post impact fire ensued. The main wreckage was the last major piece of debris; it included the cabin, right inboard wing and right engine, and the empennage. The main wreckage exhibited extensive thermal damage from a postimpact fire. The pilot reported that he positioned the airplane just left of the centerline and held the brakes for a short-field takeoff. After adding full power, he released the brakes and directed the airplane toward the center of the runway. Once the airplane was centered, he attempted to realign the nose of the airplane with the runway; however, the airplane kept turning left. At the same time, the airplane reached 80 knots and lifted off the runway. The pilot attempted to add right rudder, but it did not move because his left shoe was stuck between the rudder pedals. The airplane continued to turn left, so he reduced power on the right engine in attempt to straighten the airplane. He freed his foot from the rudder pedal, but the airplane was headed directly toward a large tree along the left side of the runway. He pulled back on the yoke and attempted to climb, but the airplane struck several trees and a postimpact fire ensued. The pilot reported there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. 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).

  • Environmental issues-Physical environment-Object/animal/substance-Tree(s)-Contributed to outcome
  • Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot
  • Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Yaw control-Not attained/maintained

Verbatim from NTSB's published report. Source file NTSB_2020_WPR20LA111.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 (maintenance). 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 ↗