NTSB CAROL · Event
Event WPR18LA044
Registry · N47536
FAA Aircraft Registry record.
Make / Model
PIPER PA-34-200T
Year of manufacture
1977 · 40 years old at event
Engine
CONT MOTOR TSIO-360 SER (225 hp)
Seats / Engines
7 seats · 2 engines
Last airworthiness date
19770926
ADS-B equipped
Yes — Mode-S A5D68D
Registrant of record
ANGEL AVIATION INC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot's failure to maintain directional control of the airplane during the landing roll. Contributing to the accident was the fatigue of the left main landing gear assembly.
Factual narrative
On December 5, 2017, about 1835 mountain standard time, a Piper PA-34-200T, N47536, was substantially damaged when it was involved in an accident near Glendale, Arizona. The flight instructor and the commercial pilot were not injured. The airplane was as a Title 14 Code of Federal Regulations Part 91 personal flight. The instructor reported that the commercial pilot receiving instruction, who was flying the airplane, successfully completed two simulated engine failure maneuvers in the traffic pattern. During the third traffic pattern, the instructor initiated a right engine failure. While on base, the pilot extended the landing gear and verbally confirmed that all three landing gear lights were green, which indicated the landing gear were down and locked. Upon touchdown, the left wing "dipped" and the airplane bounced back into the air. The instructor took the flight controls and, in an attempt to climb, applied full power to both engines; however, the nose of the airplane dropped, and the airplane started to drift toward the left side of the runway. The instructor determined that the airplane would not climb, and he retarded both throttle and mixture controls and attempted to maintain directional control while simultaneously applying brakes to stop. The airplane departed the left side of the runway and came to a complete stop in the adjacent dirt area. The instructor also reported that "the left landing gear malfunctioned" upon touchdown. Examination of the accident site revealed that the airplane landed with all three-landing gear extended; each tire's skid mark was visible on the runway surface to the left of the centerline. Additionally, the landing gear imprints were visible in the dirt where the airplane veered off the runway. The runway edge light and the 1,000-ft distance marker showed evidence of the left propeller/nose impacts. The left main landing gear collapsed after it impacted the distance marker, as evidenced by wide tire marks as the airplane started to roll on the sidewall of the left tire. Examination of the left main landing gear fracture surface revealed slant fractures consistent with an overstress failure. One small area of the fracture surface, coincident with the forging flash line, exhibited a flat fracture surface. A sample that contained the flat fracture area was further examined under the scanning electron microscope, which revealed striations consistent with a fatigue fracture. The flight instructor reported that, during touchdown, the left wing "dipped" and the instructor initiated an aborted landing. After determining that the airplane would not climb, the instructor reduced engine power and attempted to stop the airplane, which veered off the runway surface, impacted a sign, and came to rest in the dirt adjacent to the runway. The instructor later reported that the left main landing gear had "malfunctioned" upon touchdown. Examination of the accident site revealed that the airplane landed left of the runway centerline with all three landing gear extended; the first indication of the collapsed gear was visible in a dirt area on the left side of the runway behind a runway distance marker. Although examination of the left main landing gear revealed a small area of fatigue, the majority of the fracture surface exhibited signatures consistent with overstress failure; therefore, it is likely that the gear fractured due to overstress following the runway excursion and impact with a sign. 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).
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained - C
- C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
- — Aircraft-Aircraft systems-Landing gear system-Main landing gear-Fatigue/wear/corrosion
Verbatim from NTSB's published report. Source file
NTSB_2017_WPR18LA044.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 (engine failure, 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.
- arXiv 2022 · arXiv preprint
Multi-level Adaptation for Automatic Landing with Engine Failure under Turbulent Weather
This paper addresses efficient feasibility evaluation of possible emergency landing sites, online navigation, and path following for automatic landing under engine-out failure subject to turbulent wea…
- 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 2019 · Conference Paper
Simulation of Liquid Rocket Engine Failure Propagation Using Self-Evolving Scenarios
Traditional probabilistic risk assessment approaches often require failure scenarios to be explicitly defined through event sequences that are then quantified as part of the integrated analysis.
- NASA NTRS 2019 · Conference Paper
Rocket engine failure detection using system identification techiques
The theoretical foundation and application of two univariate failure detection algorithms to Space Shuttle Main Engine (SSME) test firing data is presented.
- NASA NTRS 2019 · Conference Paper
Rocket engine failure detection using system identification techniques
The theoretical foundation and application of two univariate failure detection algorithms to Space Shuttle Main Engine (SSME) test firing data is presented.
Browse the full corpus — academia portal ↗