N789EP accident

NTSB ERA10CA305 · 2010-06-04 · Baltimore, MD · near MTN

Docket — crew, injuries and powerplant

Summary

According to the pilot, he was cleared to land on runway 33 and advised of approaching weather. During the approach, the airplane encountered heavy rain, moderate turbulence, strong crosswinds, and a “sudden downdraft and crosswind” that resulted in a “very hard” landing. The airplane became “unstable,” and began to bounce down the runway. The pilot aborted the landing and returned to land on runway 15. The airplane landed hard once again, and again bounced several times down the runway. During a turn on the runway, the pilot noted a flat nose tire and requested assistance for a tow. A subsequent examination of the airplane revealed a propeller strike and substantial damage to the firewall, as well as wrinkling of the lower fuselage. An aviation routine weather report for the airport, about the time of the accident, included winds from 150 degrees true at 7 knots, and thunderstorms in the vicinity. The director of operations where the airplane was based on the airport, and one of the line service personnel who towed the airplane after the accident, confirmed that there had been a passing thunderstorm at the time of the accident. The pilot was not sure which of the hard landings resulted in the damage to the airplane.

Full narrative

According to the pilot, he was cleared to land on runway 33 and advised of approaching weather. During the approach, the airplane encountered heavy rain, moderate turbulence, strong crosswinds, and a “sudden downdraft and crosswind” that resulted in a “very hard” landing. The airplane became “unstable,” and began to bounce down the runway. The pilot aborted the landing and returned to land on runway 15. The airplane landed hard once again, and again bounced several times down the runway. During a turn on the runway, the pilot noted a flat nose tire and requested assistance for a tow. A subsequent examination of the airplane revealed a propeller strike and substantial damage to the firewall, as well as wrinkling of the lower fuselage. An aviation routine weather report for the airport, about the time of the accident, included winds from 150 degrees true at 7 knots, and thunderstorms in the vicinity. The director of operations where the airplane was based on the airport, and one of the line service personnel who towed the airplane after the accident, confirmed that there had been a passing thunderstorm at the time of the accident. The pilot was not sure which of the hard landings resulted in the damage to the airplane.

Probable cause

The pilot’s improper flare, which resulted in a hard landing. Contributing to the accident was the pilot’s improper decision to land during a thunderstorm. 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
Dusk
Sky condition
BKN
Ceiling (ft)
5500
Visibility (sm)
10
Wind direction
150
Wind speed (kt)
7
Temperature (F)
84
Nearest airport
Martin State Airport
Distance from field
0.0
Airport elevation
21

Aircraft

RegistrationMakeModelDamageFAR part
N789EP — — SUBS 091

Sequence of events

#OccurrencePhase
1 Landing-flare/touchdown Abnormal runway contact Cruise
2 Landing-flare/touchdown Hard landing defining Cruise
3 Landing-flare/touchdown Loss of control on ground Cruise

Findings

Finding
Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot cause
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Landing flare-Incorrect use/operation cause