CEN16CA317 · Ercoupe 415 CD
Ercoupe 415 CD · Accident: landing area undershoot
From Hendricks County Gordon Graham Field (2R2) to Patrum Field (II09)
Event
- NTSB case
- CEN16CA317
- 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
Ercoupe 415 CD
- Aircraft type
- Ercoupe 415
- 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
- N3884H
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Hendricks County Gordon Graham Field (2R2), Indianapolis, INTo Patrum Field (II09), Stilesville, IN
- Aircraft age
- About 60 years (built 1956)
- 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 undershoot
- 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
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The private rated pilot reported that he flew a normal traffic pattern to the grass strip airport. During the final landing approach, he was lined up with the runway but a little bit low for the approach. He stated that he knew he was low and for an unknown reason he did not advance the throttle to arrest the airplane's descent. This resulted in the airplane's landing gear contacting the bean field. When the gear contacted the beans, the airplane nosed down into the ground and was damaged. The airplane came to rest on the end of the grass runway. The airplane sustained substantial damage to the firewall and fuselage. The pilot was not injured. When asked if he experienced any mechanical difficulties with the airplane, he responded that there were none and that the airplane was operating perfectly. Based on this information the pilot failed to maintain a proper glide path during the landing approach and then failed to use available engine power to arrest the descent, resulting in an undershoot and collision with terrain.
Probable cause
The pilot's failure to maintain a proper glide path during the landing approach and his failure to use available engine power to arrest the descent, resulting in an undershoot and collision with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN16CA317
- Event ID
- 20160811X31136
- Case number
- CEN16CA317
- 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, 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: b3242d85bdf1771a83fcdb746857b3742c5ed047353d7e13db7f5878920eeab2; retrieved 2026-09-16T04:08:48.906Z.