Summary
On September 30, 2011, a Cessna 172S (N11019) was involved in an incident near Westminster, MD. All 2 people aboard were uninjured. The aircraft sustained substantial damage.
The National Transportation Safety Board determined the probable cause of this incident to be: 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.
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.
This incident is documented in NTSB report ERA11CA516. AviatorDB cross-references NTSB investigation data with FAA registry records to provide comprehensive safety information for aircraft N11019.
Accident Details
Probable Cause and Findings
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.
Aircraft Information
Registered Owner (Current)
Analysis
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.
Data Source
Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# ERA11CA516