C-GPJH accident

NTSB ERA16CA233 · 2016-06-28 · Farmington, PA · near PA88

Docket — crew, injuries and powerplant

Summary

The pilot reported that during his first attempt to land on the 3,950-foot-long asphalt runway, the airplane touched down too long and he performed a go-around. During the second attempt, the airplane touched down on the first one-third of the runway, when a gust of wind forced the airplane back into the air and it subsequently touched down further down the runway than during the first attempt. The pilot thought a go-around would be too dangerous at that point and applied brakes, but the airplane traveled off the end of the runway and struck and asphalt berm. The pilot further stated that the airplane landed with a headwind of 15 knots, gusting to 25 knots. A witness, who worked at the airport, stated that the airplane was still airborne as it flew over the runway numbers at the departure end of the runway. Examination of the accident site by a Federal Aviation Administration inspector did not reveal any skid marks on the runway; however, the inspector observed skid marks in the grass beyond the runway. The inspector did not observe any preimpact mechanical malfunctions with the airplane, nor did the pilot report any. The inspector added that during the impact, the airplane sustained damage to the firewall and lower fuselage.

Full narrative

The pilot reported that during his first attempt to land on the 3,950-foot-long asphalt runway, the airplane touched down too long and he performed a go-around. During the second attempt, the airplane touched down on the first one-third of the runway, when a gust of wind forced the airplane back into the air and it subsequently touched down further down the runway than during the first attempt. The pilot thought a go-around would be too dangerous at that point and applied brakes, but the airplane traveled off the end of the runway and struck and asphalt berm. The pilot further stated that the airplane landed with a headwind of 15 knots, gusting to 25 knots. A witness, who worked at the airport, stated that the airplane was still airborne as it flew over the runway numbers at the departure end of the runway. Examination of the accident site by a Federal Aviation Administration inspector did not reveal any skid marks on the runway; however, the inspector observed skid marks in the grass beyond the runway. The inspector did not observe any preimpact mechanical malfunctions with the airplane, nor did the pilot report any. The inspector added that during the impact, the airplane sustained damage to the firewall and lower fuselage.

Probable cause

The pilot's failure to obtain the proper touchdown point and failure to perform a go-around once a safe landing on the runway could not be accomplished. The National Transportation Safety Board determined the probable cause of this accident.

Circumstances

Event type
Accident
Highest injury
Minor
Weather conditions
Visual Meteorological Cond
Light condition
Day
Sky condition
BKN
Ceiling (ft)
3500
Visibility (sm)
10
Wind direction
240
Wind speed (kt)
7
Temperature (F)
73
Nearest airport
Nemacolin Airport
Distance from field
0.0
Airport elevation
2010

Aircraft

RegistrationMakeModelDamageFAR part
C-GPJH — — SUBS 091

Sequence of events

#OccurrencePhase
1 Landing Landing area overshoot defining Cruise
2 Landing Runway excursion Cruise
3 Landing Collision with terr/obj (non-CFIT) Cruise

Findings

Finding
Personnel issues-Action/decision-Action-Incorrect action performance-Pilot cause
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Descent/approach/glide path-Not attained/maintained cause
Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot cause