26 Jan 2017: CESSNA 172 R — Tampa Bay Aviation

26 Jan 2017: CESSNA 172 R (N2382R) — Tampa Bay Aviation

No fatalities • Clearwater, FL, United States

Probable cause

The pilot's improper landing flare, which resulted in damage to the engine firewall.

— NTSB Determination

Accident narrative

On January 26, 2017, about 1230 eastern standard time, a Cessna 172R, N2382R, registered to Clearwater Helicopters, Inc., dba Tampa Bay Aviation, was substantially damaged during a hard landing at the Clearwater Air Park (CLW), Clearwater, Florida. The private pilot and one passenger were not injured. The airplane was operated under the provisions of 14 Code of Federal Regulations Part 91 as a local, personal flight. Visual meteorological conditions prevailed at the time and no flight plan was filed for the flight that originated about 30 minutes earlier from CLW.The pilot stated that he performed a preflight inspection of the rental airplane but elected to have it fueled because of the on-board fuel load. He finished his preflight inspection after fueling, which included an inspection of the undamaged propeller, but did note the passenger door was difficult to close, and he had an issue with his lap belt, but was able to secure it. After engine start, he taxied to runway 16, where he performed an engine run-up with no discrepancies noted.

After takeoff, he flew west towards the beach but elected to return after seeing adverse weather nearby. He entered the traffic pattern at CLW for runway 16, which was equipped with a visual approach slope indicator, but he did not turn it on. He turned the airplane onto the base leg of the traffic pattern and then onto final approach leg of the traffic pattern, where he maintained 65 mph with the flaps extended 30 degrees, and reported descending at the standard rate with no airspeed fluctuations. On his first landing attempt about at touchdown, the airplane encountered a strong wind gust which caused the airplane to climb "a little bit", or about 10 feet. He performed a go-around, and re-entered the traffic pattern for runway 16. The pilot conducted the second landing attempt with 10 degrees of flaps extended, maintaining 65 mph while on the final approach leg of the traffic pattern, and reported the, "touchdown was perfect soft" on the numbers. He did not experience a propeller strike on landing, and then taxied to the tie-down area where he secured the airplane. He then went inside the fixed-base operator and wrote up the discrepancies related to the lap belt, and for a fuel gauge which indicated 5 gallons after fueling.

According to the operator, their review of airport surveillance video revealed that later that same day, maintenance personnel of the operator went to the airplane, which had not been moved or damaged, and observed damage to the propeller. Additionally, review of aircraft operational records and the airplane's hour meter revealed that the airplane had not been operated since it was returned. During hand rotation of the propeller, maintenance personnel heard internal engine damage, and subsequently noted damage to the firewall. The oil pressure-activated hour meter reading when the mechanics inspected the airplane was the same as when the pilot returned the airplane. Subsequent testing of the hour meter with FAA oversight revealed it operated satisfactory with no discrepancies.

The operator reported that the airplane was flown the evening before on a training flight with a student and instructor, and at the conclusion of their uneventful flight, the airplane was secured. They also indicated that airport surveillance video depicted the accident pilot inspecting the propeller after securing the airplane at the conclusion of the flight.

Contributing factors

  • cause Pilot
  • cause Landing flare — Not attained/maintained

Conditions

Weather
VMC, wind 220/09kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.