# NTSB ERA10CA305: Cessna 172S, N789EP, Baltimore, MD, June 4, 2010 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: June 4, 2010, 18:15 local (22:15 UTC) - Place: Baltimore, MD - Coordinates: 39.325553, -76.413612 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=39.3256&lon=-76.4136&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report December 20, 2010 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 76262 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA10CA305 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/76262/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=76262 - Page: https://openairdocs.org/ntsb/ERA10CA305 ## 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. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna 172S, 206 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072439), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Performance/control parameters: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Incorrect use/operation (probable cause); cases with it: [Cessna 172S, 99 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=2072439), [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090); cases with it: [Cessna 172S, 77 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=2072439), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md) - [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092) (defining event); cases with it: [Cessna 172S, 102 cases](https://openairdocs.org/ntsb-events/092/sequence.md?model=2072439), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md) - [Landing-flare/touchdown: Loss of control on ground](https://openairdocs.org/ntsb-events/230); cases with it: [Cessna 172S, 77 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=2072439), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) ## 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. ## 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. ## Aircraft - Registration: [N789EP](https://openairdocs.org/aircraft/N789EP), registered now, S/N 172S8135, built 1999 (OpenAirDocs) - Reported make and model: CESSNA 172S - Registry model: [Cessna 172S](https://openairdocs.org/model/cessna-172s) (registry code 2072439) (OpenAirDocs) - Registry engine: [Lycoming I0360 SER A&C](https://openairdocs.org/engine/lycoming-i0360-ser-a-c) (registry code 41511, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 172S8135 - Airframe hours: 3462 - Engines: LYCOMING I0360-L2A 200 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Brett Aviation - Registered owner: Dream Flight LLC - Airworthiness certificate: Standard, Utility; Standard, Normal - Last inspection: 100 hour, May 6, 2010 - Departed: ESN, Easton/Newnam F, MD - Destination: MTN, Baltimore, MD - Airport: MTN, Martin State Airport, runway 15, 6,996 × 150 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 46; injuries: none; private; airplane ratings: single-engine land; medical: class 3, without waivers/limitations; last flight review January 10, 2010; seat: left; flight hours: 156 total, 45 in this make and model, 47 as pilot in command, 5 in the last 90 days, 1 in the last 30 days ## Weather - Conditions: Visual (VMC), Dusk - Wind: 150° at 7 knots - Visibility: 10 statute miles - Lowest ceiling: 5,500 ft broken - Temperature: 84 °F, dew point 70 °F - Altimeter: 29.80 inHg - Observed at: MTN ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20100604005539A](https://openairdocs.org/incident/20100604005539A), Jun 4, 2010: Cessna 172S, Middle River, MD, Substantial damage. Aircraft had hard landing at mtn. Substantial damage to aircraft:firewall wrinkled, prop strike, cowling shock mounts torn from brackets, wrinkles from main… ## Other investigations on N789EP (2) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB GAA18CA326](https://openairdocs.org/ntsb/GAA18CA326), May 26, 2018: Cessna 172 (N789EP), Westminster, MD, substantial damage. Probable cause: The pilot’s improper landing flare, which resulted in a hard landing. - [NTSB ERA11CA408](https://openairdocs.org/ntsb/ERA11CA408), Jul 1, 2011: Cessna 172S (N789EP), Cambridge, MD, substantial damage. Probable cause: The student pilot's improper recovery from a bounced landing. ## Docket (5 files) The files NTSB released with the investigation on July 14, 2010, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=76262. 980 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 701 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40332858&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Weather Reports and Records (item 2, .PDF, 192 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40331404&FileExtension=.PDF&FileName=Weather%20Reports%20and%20Records-Master.PDF - Other Pertinent Forms and Reports: Record of Conversation With Brett Aviation Director of Operations. (item 3, .PDF, 35 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40331405&FileExtension=.PDF&FileName=Other%20Pertinent%20Forms%20and%20Reports%3A%20Record%20of%20Conversation%20With%20Brett%20Aviation%20Director%20of%20Operations.-Master.PDF - Other Pertinent Forms and Reports: Record of Conversation With Line Services Technician who Towed the Accident Airplane. (item 4, .PDF, 31 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40331443&FileExtension=.PDF&FileName=Other%20Pertinent%20Forms%20and%20Reports%3A%20Record%20of%20Conversation%20With%20Line%20Services%20Technician%20who%20Towed%20the%20Accident%20Airplane.-Master.PDF - Other Pertinent Forms and Reports: Record of Conversation With the Pilot. (item 5, .PDF, 22 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40333113&FileExtension=.PDF&FileName=Other%20Pertinent%20Forms%20and%20Reports%3A%20Record%20of%20Conversation%20With%20the%20Pilot.-Redacted.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.