Summary
On August 01, 2010, a Cessna 172M (N13013) was involved in an accident near Newton, KS. The accident resulted in 1 minor injury, with 2 people uninjured out of 3 aboard. The aircraft sustained substantial damage.
The National Transportation Safety Board determined the probable cause of this accident to be: The pilot’s inadequate flare, which resulted in a hard landing.
Following a 25 nautical mile cross-country night flight the private pilot performed a full stop landing. The pilot then departed and stayed in the airport traffic pattern for a second landing. During touchdown the airplane impacted the runway hard and bounced back into the air before settling back on the runway. One of the two passengers reported hurting her back during the hard landing so the pilot taxied to and shut down the airplane at the airport’s fixed base of operations (FBO). After examining the airplane for damage and finding none, the pilot elected to depart with his passengers and successfully flew back to their originating airport. Approximately three months later during the airplane’s annual inspection, the engine firewall was found to be damaged.
This accident is documented in NTSB report CEN11CA018. AviatorDB cross-references NTSB investigation data with FAA registry records to provide comprehensive safety information for aircraft N13013.
Accident Details
Probable Cause and Findings
The pilot’s inadequate flare, which resulted in a hard landing.
Aircraft Information
Registered Owner (Historical)
Analysis
Following a 25 nautical mile cross-country night flight the private pilot performed a full stop landing. The pilot then departed and stayed in the airport traffic pattern for a second landing. During touchdown the airplane impacted the runway hard and bounced back into the air before settling back on the runway. One of the two passengers reported hurting her back during the hard landing so the pilot taxied to and shut down the airplane at the airport’s fixed base of operations (FBO). After examining the airplane for damage and finding none, the pilot elected to depart with his passengers and successfully flew back to their originating airport. Approximately three months later during the airplane’s annual inspection, the engine firewall was found to be damaged. The pilot later reported that there were no malfunctions or defects with the airplane’s flight controls that contributed to the hard landing.
Data Source
Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# CEN11CA018