FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN09CA317 · Cessna 182E

22 May 2009 · Martinsville, IN, United States

Cessna 182E · Accident: landing area overshoot

From Mc Daniel's Field (90IN) to Mc Daniel's Field (90IN)

Report a problem

Event

NTSB case
CEN09CA317
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 182E

Aircraft type
Cessna 182
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
N3229Y
Operator
Unknown
Onboard fatalities
Unknown
Route
From Mc Daniel's Field (90IN), Martinsville, INTo Mc Daniel's Field (90IN), Martinsville, 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 · flare/touchdown
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
  • Personnel issues › Task performance

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

NTSB narrative

During the landing at a private airport, the pilot "landed long to avoid [a] dip in the field..." With the flaps positioned at 30 degrees, the airplane landed on the grass runway (2,000 feet long by 90 feet wide). The pilot felt that the airspeed was too fast to stop and he aborted the landing and attempted to execute a go-around. He retracted the flaps and applied full engine power. He "jumped the airplane off the grass" and tried to get the airplane to clear power lines. The airplane stalled and the left wing impacted another set of power lines. The airplane impacted several vehicles in a used car parking lot and came to rest on top of three vehicles. The pilot sustained serious injuries; the passenger and a person on the ground sustained minor injuries. The pilot indicated that he should have touched down sooner "or make [the] go-around decision if that is not possible on short fields like this one..."

Probable cause

The pilot's failure to attain the proper touchdown point during landing and his delay in initiating a successful go-around, which resulted in a loss of airspeed and an aerodynamic stall.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN09CA317
Event ID
20090526X61640
Case number
CEN09CA317
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: 62c20a1f9a6df4cfef0c19ee133dca5957140275965c28bb4928e1423653737e; retrieved 2026-09-15T11:12:04.765Z.