23 Aug 2017: CESSNA 172 P

23 Aug 2017: CESSNA 172 P (N97116) — Unknown operator

No fatalities • Gulf Shores, AL, United States

Probable cause

The pilot's improper landing flare, which resulted in a hard landing.

— NTSB Determination

Accident narrative

On August 23, 2017, about 1630 central daylight time, a Cessna 172P, N97116, was substantially damaged during landing at the Jack Edwards Airport (JKA), Gulf Shores, Alabama. The commercial pilot was not injured. Visual meteorological conditions prevailed for the personal flight conducted under the provisions of 14 Code of Federal Regulations Part 91. No flight plan was filed for the flight that departed the Pensacola International Airport (PNS), Pensacola, Florida, about 1600.The pilot stated that before he departed PNS, he noted that the elevator trim was in the full nose-up position. He reset it to the "takeoff" position and completed his before-takeoff checklist and engine run-up procedures. He said that during takeoff, he needed more back pressure on the control yoke than he was used to, so he trimmed the elevator trim tab up to reduce pressure. The flight to JKA was uneventful and he made a normal approach to runway 17. The pilot said that he reduced engine power to idle and began the landing flare. However, when he pulled back on the control yoke, the nose of the airplane did not come up as expected. The pilot described the attitude of the airplane as, "...much more flat with only slight nose up." The airplane "fell through" the last few feet above the runway, landed hard, and bounced four or five times before he could stop the airplane. He said he tried to taxi off onto a taxiway, but he was unable to steer the airplane.

A Federal Aviation Administration (FAA) aviation maintenance inspector conducted a postaccident examination of the airplane. The examination revealed the firewall was wrinkled, the nose wheel was bent, and both propeller blades were damaged from contact with the ground. The control yoke had minimal movement due to the upper yoke control tubes at the chain sprocket binding against the aluminum channel brace due to the bent firewall. The inspector also noted that the elevator trim tab cable had slack and was not rigged correctly. When the trim tab wheel was moved, the cable's center travel block was catching on the aft tail cone bulkhead. An FAA airworthiness inspector performed a second examination of the airplane and determined that despite the rigging of the elevator trim cable, he could not find evidence of a preaccident elevator control problem. An FAA operations inspector spoke to the flight instructor of the pilot who flew the accident airplane prior to the accident flight. The student had not reported any issues with landing the airplane.

About a month after the accident, the pilot flew with an FAA designated pilot examiner (DPE). According to the DPE, the pilot's landings were "very flat and never set up with a nose high attitude." On one landing, the airplane bounced and then ballooned resulting in the DPE taking control of the airplane. The DPE later spoke with the pilot's flight instructor, who told him that the pilot had a tendency to land flat. He described the pilot's landings as "on and off."

The pilot held a commercial pilot certificate for rotorcraft with an instrument rating for rotorcraft-helicopter. He was enrolled in a Rotorcraft Transition Program, where he would earn his private pilot certificate for airplane single-engine land, then obtain a commercial pilot certificate for airplane multiengine land, and then attend a new-hire class for a commercial air carrier. His last FAA first class medical certificate was issued on June 30, 2017. The pilot reported he had accrued 29 hours of flight experience in single-engine airplanes.

Weather reported at JKA, about the time of the accident, included calm wind, visibility 10 miles and clear skies.

Contributing factors

  • cause Pilot
  • cause Incorrect use/operation
  • Pilot

Conditions

Weather
VMC, 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.