Skip to content

ERA10CA305

2010-06-04 · Baltimore, Maryland, United States · None · 1 aircraft · Status: Completed

Airport MTN

Current FAA registration · N789EP

Make / Model
CESSNA 172S
Year of manufacture
1999 · 11 years old at event
Engine
LYCOMING I0360 SER A&C (200 hp)
Seats / Engines
4 seats · 1 engine
Last airworthiness date
19990407
ADS-B equipped
Yes — Mode-S AAB267

Source: FAA Aircraft Registry (releasable master file).

Aircraft involved

Probable cause & findings

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.

Factual 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. 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. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12

NTSB Findings

FAA avdata. C = Cause, F = Factor.

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

Verbatim from NTSB's published report. Source file NTSB_2010_ERA10CA305.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.

Related research

Matched on aircraft type or causal vocabulary (turbulence, thunderstorm). All research papers