6 Jan 2017: CESSNA 172M M

6 Jan 2017: CESSNA 172M M (N80374) — Unknown operator

No fatalities • Hobart, IN, United States

Probable cause

The pilot's failure to abort the landing when he recognized the airplane was traveling too fast, which resulted in impact with trees off the end of the runway.

— NTSB Determination

Accident narrative

***This report was modified on July 20, 2020. Please see the docket for this accident to view the original report.***

On January 6, 2017, about 1305 central standard time, a Cessna 172M, N80374, was substantially damaged when it was involved in an accident at Hobart Sky Ranch Airport (3HO), Hobart, Indiana. The pilot received serious injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

The pilot told a law enforcement officer that he approached the runway to land from the north and when the landing gear contacted the runway the airplane "skipped" and overshot the runway. The airport owner saw the airplane approach the runway to land and noticed that the airplane was traveling at a high speed. As the airplane touched down it "skipped" off of the runway and then crashed into a wooded area off the departure end of the runway. The pilot could not recall what happened between the time the airplane "skipped" off the runway and when emergency personnel arrived.

According to the Federal Aviation Administration inspector who responded to the accident the pilot stated that the wind was from the west and he chose to land to the south. He stated that he noticed that his groundspeed "picked up" and he thought he had a tailwind. He elected to put the airplane on the runway and try to get it stopped.

The airplane came to rest about 150 ft beyond the departure end of the 3,125 ft. long runway in a thickly wooded area. Both wings, the engine, and the fuselage sustained substantial damage. The carburetor heat was "hot", the throttle and mixture were full forward, and the wing flaps were retracted. Chordwise scratches and leading-edge polishing were visible on one propeller blade. The condition of the second propeller blade was not documented. Scuff marks were present on each main landing gear. Tree limbs and brush were broken off about 3 ft above the ground along the path of travel from the runway to the wreckage.

Contributing factors

  • cause Pilot
  • cause Contributed to outcome

Conditions

Weather
VMC, wind 270/14kt, 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.