ERA10CA305 · Cessna 172S
Brett Aviation Cessna 172S · Accident: hard landing
From Easton Airport / Newnam Field (ESN) to Martin State Airport (MTN)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ERA10CA305
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna 172S
- Aircraft type
- Cessna 172
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N789EP
- Operator
- Brett Aviation
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From Easton Airport / Newnam Field (ESN), Easton/Newnam F, MDTo Martin State Airport (MTN), Baltimore, MD
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · flare/touchdown
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Hard landing
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB 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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA10CA305
- Event ID
- 20100608X05715
- Case number
- ERA10CA305
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 2fb8604f6d922c49b5d8d33b5cef9d53c441b8d1cd82a996f5249563d4b586eb; retrieved 2026-09-15T14:23:55.761Z.