CHI06CA182 · Cessna 172L
Cessna 172L · Accident: overrun during landing
From Waterford, OH (private airstrip) to Waterford, OH
Event
- NTSB case
- CHI06CA182
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna 172L
- Aircraft type
- Cessna 172
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N7805G
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Waterford, OH (private airstrip)To Waterford, OH
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Overrun
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Unsuitable terrain or takeoff/landing/taxi area, selected
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane was damaged when it went off the end of a grass runway during landing. The pilot reported that he touched down about 1/3 of the way down the 2,200 foot-long grass strip, applied the brakes and felt that the airplane was sliding. He attempted to stop by pumping the brakes. When he realized that he would not be able to stop the airplane before the end of the runway, he locked the left brake in an attempt to skid the airplane sideways to a stop. The airplane went off the end of the runway, down an embankment, and struck a fence. He stated that he was aware that the runway was wet prior to the flight and that the runway has a downhill slope in the direction used for the landing attempt. The pilot reported no mechanical problems with the airplane.
Probable cause
The pilot's selection of unsuitable terrain for landing. The runway's downhill slope, the wet grass, the fence, and the embankment were factors.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI06CA182
- Event ID
- 20060814X01160
- Case number
- CHI06CA182
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: cbef1ddd712bcb1aa485fe04b151d071e513303684b2c3113258df3ee8398136; retrieved 2026-09-22T04:41:25.223Z.