N4823B accident

NTSB ERA10CA369 · 2010-07-20 · Indian Head, MD · near 2W5

Docket — crew, injuries and powerplant

Summary

According to the pilot, he received a weather briefing that stated there was a convective SIGMET (significant meteorological information) over the airport and the storm would be arriving in about one hour. After receiving the briefing, the pilot performed a preflight check on the airplane, and proceeded to take off on a local solo flight. The pilot stated that during different phases of each traffic pattern, he had difficulty due to the gusty wind conditions. After initiating a go-around on the original departure runway, the pilot elected to set up for a long approach to a different runway. While on final approach, the airplane encountered gusty conditions and the pilot attempted to compensate for a crosswind. During touchdown, the airplane bounced several times, overran the end of the runway, and collided with a small ditch resulting in damage to the firewall. The pilot reported that there were no mechanical failures or malfunctions with the airplane. The recorded wind conditions about the time of the accident at an airport 8 miles away indicated a velocity of 10 knots, gusting to 18 knots.

Full narrative

According to the pilot, he received a weather briefing that stated there was a convective SIGMET (significant meteorological information) over the airport and the storm would be arriving in about one hour. After receiving the briefing, the pilot preflighted the airplane, and proceeded to take off of runway 18 on a local solo flight. The pilot stated that during different phases of each traffic pattern, he had a difficult time due to the gusty wind conditions. On final approach to runway 18, he realized that the airspeed and altitude of the airplane were too high and he initiated a go-around. The pilot stated that he recognized "the difficultly landing in gusty conditions" and requested assistance over the UNICOM frequency. A pilot, who was required to monitor the solo flight, advised the student pilot to fly away from the airport and set up for a long final approach to runway 36. On final approach, the pilot of the accident airplane stated that he "continued to encounter gusty conditions" and was advised to lower the left wing of the airplane to compensate for the crosswind. The pilot stated when the airplane first touched down, it was a "rough landing," and "the airplane bounced a few times." The airplane overran the end of the runway and hit a small ditch damaging the firewall. The pilot did not report any mechanical failures or malfunctions of the airplane. Winds, recorded at an airport 8 miles to the northwest about the time of the accident, were from 260 degrees at 10 knots, gusting to 18 knots.

Probable cause

The pilot's loss of control while landing in gusting crosswind 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)
9000
Visibility (sm)
10
Wind direction
260
Wind speed (kt)
10
Temperature (F)
84
Nearest airport
Maryland Airport
Distance from field
0.0
Airport elevation
170

Aircraft

RegistrationMakeModelDamageFAR part
N4823B — — SUBS 091

Sequence of events

#OccurrencePhase
1 Approach-VFR pattern final Other weather encounter Cruise
2 Landing-landing roll Runway excursion defining Cruise

Findings

Finding
Environmental issues-Conditions/weather/phenomena-Wind-Sudden wind shift-Contributed to outcome - F cause
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-Action/decision-Info processing/decision-Decision making/judgment-Student pilot cause
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Airspeed-Not attained/maintained cause