FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN11CA004 · Cessna 172N

1 Oct 2010 · Wabash, IN, United States

Cessna 172N · Accident: landing area overshoot

From Wabash Municipal Airport (IWH) to Wabash Municipal Airport (IWH)

Report a problem

Event

NTSB case
CEN11CA004
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 172N

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
N2140E
Operator
Unknown
Onboard fatalities
Unknown
Route
From Wabash Municipal Airport (IWH), Wabash, INTo Wabash Municipal Airport (IWH), Wabash, IN
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
Defining eventThe 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
Landing area overshoot
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The certificated flight instructor (CFI) and student had been practicing touch-and-go landings and were planning a full-stop landing. The airplane touched down on the grass airstrip slightly faster than normal and approximately 100 feet beyond the approach end of the runway. The CFI took authority of the airplane's controls and applied brakes. As the airplane approached the end of the runway, the CFI applied left rudder to avoid a ditch in front of the airplane. Subsequently, the right main landing gear went into the ditch and the airplane flipped over. Postaccident examination of the airplane revealed that the vertical stabilizer and rudder were bent. The CFI reported that there were no preimpact mechanical anomalies with the airplane. He further stated that they should have landed on the adjacent asphalt runway or performed a go-around after overshooting the final approach leg during the landing.

Probable cause

The student pilot's failure to maintain proper airspeed during the landing and certificated flight instructor's failure to execute a go-around.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN11CA004
Event ID
20101005X94649
Case number
CEN11CA004
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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. 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: ab67b46d9a651c7c56d8908c9df95bd6dd44d9373eb7cb6376489b7d06704112; retrieved 2026-09-15T15:27:18.308Z.