Cessna 172S N789EP accident near Baltimore, Maryland

Jun 4, 2010 · NTSB number ERA10CA305 · Final report

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.

NTSB analysis

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.

Text from the NTSB. Open the NTSB docket for ERA10CA305 for the full record.

Event

Date
Jun 4, 2010
Type
Accident
Place
Baltimore, Maryland
Nearest airport
Martin State Airport (MTN)
Highest injury
None
Weather
Visual (VMC)
Light
Dusk

Cessna 172S

N-number
N789EP
Category
Airplane
Damage
Substantial
Operating rule
Part 91 (general aviation)
Purpose of flight
Personal

Other records under this N-number

From the NTSB aviation accident database: N-registered aircraft, events since 2008, data through Oct 28, 2026. The file is published monthly, so the latest weeks are incomplete and recent records can change. The official source is the NTSB aviation investigation search. CheckAero is independent and not affiliated with the NTSB.