# Accident 20170106000039A: Cessna 172M, Hobart, IN, January 6, 2017

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: January 6, 2017, 13:05 local time
- Place: Hobart, IN
- Damage: Substantial damage
- Phase of flight: Landing: Approach
- Operating rules: General operating rules (Part 91)
- Location: 41.5517° N, 87.2639° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=41.5517&lon=-87.2639&mi=10
- Aircraft: N80374, a cancelled registration (https://openairdocs.org/deregistered/N80374-2017-12-14) (OpenAirDocs)
- Registry model: Cessna 172M (registry code 2072418, https://openairdocs.org/model/cessna-172m) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172M
- Reported engine: LYCOMING 0-320 SERIES
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 1
- Pilot certificates: Private pilot
- Pilot flight hours: 170 total, 150 in this make and model, 40 in the last 90 days
- NTSB investigation: [NTSB CEN17LA082](https://openairdocs.org/ntsb/CEN17LA082) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20170106000039A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

PILOT WAS LANDING ON RUNWAY 18 AT HOBART.  THE AIRPLANE RAN OFF THE END OF THE RUNWAY.

THE WIND AT THE GARY AIRPORT WAS 290 AT 12 KNOTS AT 12:45 P.M.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB CEN17LA082](https://openairdocs.org/ntsb/CEN17LA082), Jan 6, 2017: Cessna 172M (N80374), Hobart, IN, substantial damage. 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.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.