NTSB CAROL · Event
Event WPR20LA111
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 ↗.
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 (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.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- Semantic Scholar 2025 · Article (Applied Sciences)
Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
A New Trajectory in UAV Safety: Leveraging Reinforcement Learning for Distance Maintenance Under Wind Variations
In the field of aviation, safety is a critical cornerstone, and the operation of Unmanned Aerial Vehicle (UAV) systems is deeply connected with this principle.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Just Culture in Aviation: A Metaphorical Study on Aircraft Maintenance Students
Just Culture, a sub-dimension of safety culture, has been a prominent and debated topic in aviation safety in recent years.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Performance PRISM: A Comprehensive Framework For Performance Measurement In Aircraft Maintenance
Aircraft maintenance is governed by rigorous safety requirements and high operational complexity, demanding robust performance measurement frameworks to ensure optimal maintenance practices.
Browse the full corpus — academia portal ↗