Skip to content

Atlas / NTSB / WPR18LA203

NTSB CAROL · Event

Event WPR18LA203

2018-07-25 Avalon, California, United States Airport · AVX Serious 1 aircraft Status: Completed

Aircraft involved

Probable cause & findings

The pilot's delayed decision to conduct a go-around following an unstable landing approach and long landing.

Factual narrative

On July 25, 2018, about 0930 Pacific daylight time, a Piper PA-32-300, N4747H, was substantially damaged when it was involved in an accident in Avalon, California. The private pilot sustained serious injuries and the two passengers sustained minor injuries. The airplane was operated by the pilot as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot reported that he did not remember the accident but did state there were no mechanical failures or malfunctions with the airplane prior to the accident. The airport manager reported that when the airplane was on downwind, he advised the pilot of the wind which was 330° at 4 knots. He stated that the pilot's first landing attempt was too high, and the airplane went around. On the second landing attempt the airplane was "still too high and came in too fast" but touched down past about midfield. As the airplane neared the end of the runway, he heard the engine "rev up" and observed the airplane depart the runway in a "very nose high" pitch attitude. The airplane subsequently collided with terrain about 1,000 ft beyond the departure end of the runway and about 75 to 100 ft below the runway surface elevation in a nose low attitude. A witness reported that the pilot's first landing attempt was too high, and the airplane went around. During the second landing attempt, the airplane was "still too high and came in too fast." The airplane touched down past the runway midpoint, and as the airplane neared the end of the runway, the witness heard the engine "rev up" and saw the airplane depart the runway in a "very nose high" pitch attitude. The airplane subsequently collided with terrain about 1,000 ft beyond the departure end of the runway and about 75 to 100 ft below the runway surface elevation. The pilot reported that he did not recall the events of the accident, but stated that there were no mechanical anomalies with the airplane. The accident is consistent with the pilot's delayed decision to conduct a go-around  following an unstable approach and long landing, which resulted in the airplane having insufficient airspeed to climb after the attempted go-around and impact with terrain. 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-Descent/approach/glide path-Not attained/maintained - C
  • C Personnel issues-Action/decision-Action-Delayed action-Pilot - C
  • C Personnel issues-Action/decision-Info processing/decision-Decision making/judgment-Pilot - C
  • Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot

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