Summary
On May 02, 2005, a Cessna 172SP (N66113) was involved in an incident near Clearwater, FL. 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 improper flare and recovery from a bounced landing.
On May 5, 2004, about 0900 eastern daylight time, a Cessna 172SP, N66113, registered to and operated by Clearwater Airpark Flight School Inc, as a Title 14 CFR Part 91 personal flight, incurred a hard landing in Clearwater, Florida. Visual meteorological conditions prevailed, and no flight plan was filed. The private-rated pilot and one passenger were not injured, and the airplane incurred substantial damage. The flight originated from the Clearwater Air Park, Clearwater, Florida, earlier that day at an unspecified time.
The pilot stated that he was flying traffic patterns and was practicing landings to a full stop. His first landing was satisfactory, just landing beyond the runway numbers. The second traffic pattern was again satisfactory until the he was on short final approach.
This incident is documented in NTSB report MIA05CA121. AviatorDB cross-references NTSB investigation data with FAA registry records to provide comprehensive safety information for aircraft N66113.
Accident Details
Probable Cause and Findings
The pilot's improper flare and recovery from a bounced landing.
Aircraft Information
Registered Owner (Historical)
Analysis
On May 5, 2004, about 0900 eastern daylight time, a Cessna 172SP, N66113, registered to and operated by Clearwater Airpark Flight School Inc, as a Title 14 CFR Part 91 personal flight, incurred a hard landing in Clearwater, Florida. Visual meteorological conditions prevailed, and no flight plan was filed. The private-rated pilot and one passenger were not injured, and the airplane incurred substantial damage. The flight originated from the Clearwater Air Park, Clearwater, Florida, earlier that day at an unspecified time.
The pilot stated that he was flying traffic patterns and was practicing landings to a full stop. His first landing was satisfactory, just landing beyond the runway numbers. The second traffic pattern was again satisfactory until the he was on short final approach. His airspeed was too high, and the airplane touched down just passed the runway numbers and bounced "high". He misjudged the severity of the bounced landing and failed to apply engine power to correct the situation. The airplane immediately started to porpoise, and became "uncontrollable". The pilot stated there were no mechanical failures or malfunction to the airplane or any of it's systems prior to the accident.
Data Source
Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# MIA05CA121