# NTSB ERA11CA516: Cessna 172S, N11019, Westminster, MD, September 30, 2011 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: September 30, 2011, 08:00 local (12:00 UTC) - Place: Westminster, MD - Coordinates: 39.466945, -77.017219 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=39.4669&lon=-77.0172&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: 2 uninjured - Status: Completed, report February 16, 2012 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 82027 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA11CA516 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/82027/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=82027 - Page: https://openairdocs.org/ntsb/ERA11CA516 ## Probable cause The pilot's inadequate recovery from a bounced landing, which resulted in a loss of airplane control. Contributing to the accident was the pilot's improper approach airspeed for a short-field landing. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Action: incorrect action performance](https://openairdocs.org/ntsb-findings/02041015): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cessna 172S, 32 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md?model=2072439), [All aircraft, 1,386 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md) - [Performance/control parameters: airspeed](https://openairdocs.org/ntsb-findings/01062010): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 172S, 16 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md?model=2072439), [All aircraft, 1,681 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md) - [Performance/control parameters: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (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: 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) ## Analysis The pilot stated that, during approach for landing on the 1,840-foot-long runway, the airplane's airspeed was higher than recommended for a short-field landing. He stated that, after the first touchdown, the airplane bounced and floated, then it touched down on the runway a second time and bounced again. The third touchdown was "firm," the airplane became airborne, and the pilot elected to conduct a go-around. The pilot returned to his airport of origin, and postflight examinations revealed damage to one propeller blade and substantial damage to the engine firewall. The pilot reported that there were no preaccident mechanical malfunctions or anomalies with the airplane. ## Factual narrative The pilot stated that during approach for landing at the 1,840-foot-long runway, the airplane's airspeed was higher than recommended for a short field landing. He stated that after the first touchdown, the airplane bounced and floated, then touched down on the runway a second time and bounced again. The third touchdown was "firm," the airplane became airborne, and the pilot elected to conduct a go-around. The pilot returned to his airport of origin, and postflight inspection revealed damage to one propeller blade. Further inspection revealed substantial damage to the engine firewall. The pilot reported there were no mechanical malfunctions or anomalies with the airplane. ## Aircraft - Registration: [N11019](https://openairdocs.org/aircraft/N11019), registered now, S/N 172S10300, built 2006 (OpenAirDocs) - Reported make and model: CESSNA 172S - Registry model: [Cessna 172S](https://openairdocs.org/model/cessna-172s) (registry code 2072439) (OpenAirDocs) - Registry engine: [Lycoming IO-360-L2A](https://openairdocs.org/engine/lycoming-io-360-l2a) (registry code 41597, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 172S10300 - Airframe hours: 2124 - Engines: LYCOMING IO-360-L2A 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Frederick Flight Center, Inc - Registered owner: Morrow Airplane LLC - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, August 19, 2011 - Departed: FDK, Frederick, MD - Destination: FDK, Frederick, MD - Airport: 2W2, Clearview Airpark, runway 14, 1,840 × 30 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 43; injuries: none; private; airplane ratings: single-engine land, multi-engine land; medical: class 3, without waivers/limitations; last flight review July 15, 2011; seat: left; flight hours: 2,500 total, 5 in this make and model, 1,950 as pilot in command, 5 in the last 90 days, 2 in the last 30 days, 0 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 230° at 4 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 61 °F, dew point 55 °F - Altimeter: 29.73 inHg - Observed at: FDK, 16 nm away ## 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 20110930022239A](https://openairdocs.org/incident/20110930022239A), Sep 30, 2011: Cessna 172S, Frederick, MD, Substantial damage. Pilot left Frederick airport and flew to clearview airpark (2W2) pilot bounced twice and on the third bounce was followed by a hard landing. Pilot elected to… ## Docket (2 files) The files NTSB released with the investigation on December 31, 2011, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=82027. 4.2 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 3.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40356365&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Photo (Courtesy FAA) (item 2, .PDF, 728 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40356366&FileExtension=.PDF&FileName=Photo%20(Courtesy%20FAA)-Master.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.