Skip to content

LAX06CA193

2006-06-03 · Gualala, California, United States · None · 1 aircraft · Status: Completed

Airport E55

Current FAA registration · N4174Z

Make / Model
PIPER PA-32R-301T
Year of manufacture
2000 · 6 years old at event
Engine
LYCOMING TI0-540 SER (310 hp)
Seats / Engines
7 seats · 1 engine
Last airworthiness date
20000926
ADS-B equipped
Yes — Mode-S A4F11D

Source: FAA Aircraft Registry (releasable master file).

Aircraft involved

Probable cause & findings

the pilot's misjudged distance and speed, which resulted in a runway overrun. A contributing factor was the hump in the runway.

Factual narrative

On June 3, 2006, at 1215 Pacific daylight time, a Piper PA32R-301T, N4174Z, ran off the end of the runway and the landing gear collapsed at Ocean Ridge Airport, Gualala, California. The pilot was operating the airplane under the provisions of 14 CFR Part 91. The private pilot and two passengers were not injured. Visual meteorological conditions prevailed and no flight plan had been filed for the personal flight. The pilot departed from San Rafael Airport, San Rafael, California, at 1130, and was landing at his destination when the accident occurred. The pilot stated that the while landing on the 2,500-foot runway, the airplane ran off the end. As it slid across the grass-covered terrain, the landing gear collapsed, which resulted in rib damage to the outboard left wing and right wheel well area. There were no mechanical failures or malfunctions during the flight. The pilot noted that the runway had a hump in its middle that decreased his visibility during landing. When he realized that he needed to perform a go-around, there was not enough runway available to safety do so. The Airport/Facility Directory Southwest notes in the remarks section for Ocean Ridge Airport, in part, "Acft not visible from opposite ends of rwy." The airplane overran the departure end of the 2,500-foot runway on landing and the landing gear collapsed. The runway had a hump in its middle that decreased the landing visibility. The pilot said that when he realized that he needed to perform a go-around, he did not have the runway available to safety execute the procedure. The pilot said that there were no mechanical failures or malfunctions during the flight. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12

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

Related research

Matched on aircraft type or causal vocabulary (go-around). All research papers