27 Jul 2017: CESSNA 170 A

27 Jul 2017: CESSNA 170 A — Unknown operator

No fatalities • San Andreas, CA, United States

Probable cause

The pilot’s improper landing flare during an aborted go-around in gusting wind conditions, which resulted in a hard landing.

— NTSB Determination

Accident narrative

The pilot of the tailwheel-equipped airplane reported that, he landed on the main wheels, and while waiting for the tailwheel to drop, the "tailwheel jammed." He added, that when the tailwheel touched down, the airplane was difficult to control, and veered to the left. He corrected for the veer, but the airplane veered to the right. He then did a go-around, however, once airborne the airplane "did not appear to be producing proper power." He then aborted the go-around, and opted to land on the remaining runway. About 25 ft. above the runway, he set the airplane up for a wheel landing and descended. When the airplane was about 5-10 ft. above the runway, the airplane "abruptly" sank, landed hard and collapsed the main landing gear. Subsequently, the airplane came to rest nose down on the runway.

The airplane sustained substantial damage to the fuselage.

During a telephone interview, the pilot reported that he believed the tailwheel had jammed prior to touchdown, and that he had previously re-designed and altered the tailwheel. Further, the airplane produced insufficient power during the go-around. He reported that, the tailwheel was mechanically "okay" when inspected after the accident.

Additionally, an airframe and powerplant mechanic reported that he inspected the tailwheel assembly after the accident, and found no defects and no binding.

The pilot reported the weather at the accident airport, about the time of the accident to be, wind from 320° at 10 knots, gusting to 12 knots. The pilot landed on runway 31.

Photographs taken at the accident site showed torsional twisting of the propeller, consistent with the engine producing power at the time of impact. The National Transportation Safety Board did not examine the engine.

Contributing factors

  • cause Landing flare — Not attained/maintained
  • cause Pilot
  • Nose/tail landing gear
  • Effect on operation

Conditions

Weather
VMC, wind 300/06kt, 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.