N6193B accident

NTSB GAA17CA325 · 2017-06-01 · Ellington, CT · near 7B9

Docket — crew, injuries and powerplant

Summary

According to the pilot, he landed the airplane on the 1,800-ft-long asphalt runway in the rain at 70 mph with full flaps. He reported that, on final, he had considered conducting a go-around due to wind and weather, but "we were low, slow, and 130 pounds below maximum gross weight with very dynamic wind conditions at the time and …apartment buildings about 400 yards beyond the end of runway 19." During the landing, he touched down with a right crosswind, about 600 ft beyond the runway threshold. He recalled that he retracted the flaps and pulled the control wheel all the way aft to put as much weight as possible on the main wheels, but he "felt our ground speed was fast and we must have a tailwind." He applied heavy braking, and as the end of the runway approached, he applied full left rudder to avoid a gully that was just beyond the end of the runway. The airplane exited the end of the runway and veered left. The airplane entered the gully and impacted vegetation. The airplane sustained substantial damage to the right-wing spar and aileron. The nearest METAR was 10 nautical miles east of the accident site, and it reported that the wind was from 270° at 13 knots, gusting to 20 knots. The visibility was 10 statute miles with light rain. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. Per the National Transportation Safety Board Pilot Aircraft Accident Report, the pilot noted that the accident could have been prevented by initiating a go-around after he realized that he could not land in the first third of the runway. He noted that the approaching rain and wind conditions added personal pressure to land before conditions deteriorated. Additionally, he reported that under normal, dry conditions, heavy braking was required to prevent an overrun.

Full narrative

According to the pilot, he landed the airplane on the 1,800-foot asphalt runway in the rain at 70 miles per hour with full flaps. He reported that on final, he had considered a go-around due to wind and weather, but "we were low, slow, and 130 pounds below maximum gross weight with very dynamic wind conditions at the time and there are apartment buildings about 400 yards beyond the end of runway 19."

During the landing, he touched down with a right crosswind, about 600 feet beyond the runway threshold.

He recalled that he, retracted the flaps, and pulled the control wheel all the way aft to put as much weight as possible on the main wheels, but he "felt our ground speed was fast and we must have a tailwind."

He applied heavy braking, and as the end of the runway approached, he applied full left rudder to avoid a gully that was just beyond the end of the runway.

The airplane exited the end of the runway and veered to the left. The airplane entered the gully and impacted vegetation.

The airplane sustained substantial damage to the right-wing spar and aileron.

The nearest METAR was 10 nautical miles east of the accident site, and reported that the wind was from 270° at 13 knots and gusting to 20 knots. The visibility was 10 statute miles with light rain.

The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Per the National Transportation Safety Board Pilot Aircraft Accident Report, the pilot noted that the accident could have been prevented by initiating a go-around after he realized that he could not land in the beginning of the first 1/3 of the runway. He noted that the approaching rain and wind condition added personal pressure to land before conditions deteriorated. Additionally, he reported that under normal, dry conditions, heavy braking was required to prevent an overrun.

Probable cause

The pilot’s unstabilized approach and failure to go around in rainy, gusting crosswind conditions, which resulted in a runway overrun. Contributing to the accident was the pilot’s self-induced pressure to land due to the deteriorating weather conditions. The National Transportation Safety Board determined the probable cause of this accident.

Circumstances

Event type
Accident
Highest injury
None
Weather conditions
Visual Meteorological Cond
Light condition
Day
Sky condition
BKN
Ceiling (ft)
7000
Visibility (sm)
10
Wind direction
270
Wind speed (kt)
13
Temperature (F)
70
Nearest airport
ELLINGTON
Distance from field
0.0
Airport elevation
253

Aircraft

RegistrationMakeModelDamageFAR part
N6193B — — SUBS 091

Sequence of events

#OccurrencePhase
1 Landing-landing roll Abnormal runway contact Cruise
2 Landing-landing roll Landing area overshoot defining Cruise
3 Landing-landing roll Loss of control on ground Cruise
4 Landing-landing roll Collision with terr/obj (non-CFIT) Cruise

Findings

Finding
Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot cause
Environmental issues-Conditions/weather/phenomena-Ceiling/visibility/precip-Rain-Effect on equipment cause
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Descent/approach/glide path-Not attained/maintained cause
Aircraft-Aircraft oper/perf/capability-Aircraft capability-Landing distance-Capability exceeded cause
Personnel issues-Psychological-Personality/attitude-Motivation/respond to pressure-Pilot - F cause
Environmental issues-Conditions/weather/phenomena-Wind-Crosswind-Effect on operation factor
Environmental issues-Conditions/weather/phenomena-Wind-Gusts-Effect on operation factor