N3167G accident

NTSB ERA17CA149 · 2017-04-08 · Culpepper, VA · near CJR

Docket — crew, injuries and powerplant

Summary

The pilot stated that, after a thorough preflight inspection and passenger briefing, he started the engine and noted that there was an 80° left crosswind at 5 knots, gusting to 15 knots. He performed an engine run-up, checked the flight controls, and then departed to fly around the local area for about 20 minutes. He then returned to the departure airport, and because the airplane was only equipped with a single radio and there was traffic congestion, he did not monitor the weather or ask for a wind check. He performed a "high break" at traffic pattern altitude, and while on final approach with the flaps fully extended, he maintained a left-wing-low attitude to correct for the left crosswind. He performed a wheel landing, but as the tailwheel was lowering, the left wing raised "dramatically," and the right wingtip contacted the runway. He added power to abort the landing, but because the right wing was contacting the runway, the airplane pivoted to the right. The airplane went off the right side of the runway and nosed over. The pilot reported that there were no preimpact mechanical failures or malfunctions of the airframe or engine that would have precluded normal operation. The reported wind conditions about 5 minutes before the accident included a variable crosswind between 80° and 170° left of the selected runway heading at 8 knots, gusting to 16 knots.

Full narrative

The pilot stated that after a thorough preflight inspection and passenger briefing, he started the engine and noted that there was an 80° left crosswind at 5 kts, with gusts to 15 kts. He performed an engine run-up and checked the flight controls, then departed to fly around the local area for about 20 minutes. He then returned to the departure airport, and because the airplane was only equipped with a single radio and traffic congestion, he did not monitor the weather or ask for a wind check. He performed a "high break" at traffic pattern altitude and while on final approach with the flaps fully extended, he maintained a left wing low attitude to correct for the left crosswind. He performed a wheel landing, but as the tailwheel was lowering, the left wing raised "dramatically" and the right wingtip contacted the runway. He added power to abort the landing, but because the right wing was contacting the runway, the airplane pivoted to the right. The airplane went off the right side of the runway and nosed over. The pilot indicated there were no preimpact mechanical failures or malfunctions of the airframe or engine that would have precluded normal operation. The reported wind conditions about 5 minutes before the accident included a crosswind that was variable between 80° and 170° left of the selected runway heading, at a velocity of 8 kts, with gusts to 16kts.

Probable cause

The pilot's failure to maintain airplane and directional control during the landing roll and subsequent go-around in gusting wind conditions. The National Transportation Safety Board determined the probable cause of this accident.

Circumstances

Event type
Accident
Highest injury
Serious
Weather conditions
Visual Meteorological Cond
Light condition
Day
Sky condition
NONE
Ceiling (ft)
0
Visibility (sm)
10
Wind direction
290
Wind speed (kt)
8
Temperature (F)
63
Nearest airport
Culpeper Regional Airport
Distance from field
0.0
Airport elevation
315

Aircraft

RegistrationMakeModelDamageFAR part
N3167G — — SUBS 091

Sequence of events

#OccurrencePhase
1 Landing-landing roll Loss of control on ground defining Cruise
2 Landing-aborted after touchdown Dragged wing/rotor/float/other Cruise
3 Landing-flare/touchdown Nose over/nose down Cruise

Findings

Finding
Environmental issues-Conditions/weather/phenomena-Wind-Gusts-Effect on operation cause
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained cause
Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot cause