ERA11LA454 · Diamond Aircraft IND Inc DA 40
Honaker Aviation Diamond Aircraft IND Inc DA 40 · Accident: collision during takeoff/landing during initial climb
From Hodgenville, KY to Cambridge Municipal Airport (CDI)
Event
- NTSB case
- ERA11LA454
- 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
Diamond Aircraft IND Inc DA 40
- Aircraft type
- Diamond DA-40
- 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
- N316MA
- Operator
- Honaker Aviation
- Onboard fatalities
- Unknown
- Route
- From Hodgenville, KYTo Cambridge Municipal Airport (CDI), Cambridge, 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
- Initial climb
- 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
- Collision during takeoff/landing
- 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 › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot initiated takeoff from an upsloping, 1,133-foot-long grass airstrip with two passengers onboard. The airplane struck 40-foot tall trees located 1,150 feet from the point where the takeoff ground roll was initiated. Subsequently, the airplane struck three power lines and impacted the ground. According to information from the closest airport with a weather recording system, the wind was most likely a headwind at the time of the accident. Calculations based on the performance data in the airplane’s flight manual indicated that a takeoff distance of about 1,570 feet was required to clear a 50-foot obstacle. A postaccident examination of the engine did not reveal any anomalies that would have precluded normal operation.
Probable cause
The pilot's inadequate takeoff performance planning, which resulted in collision with an obstacle during takeoff from a turf runway that was not long enough for the given conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA11LA454
- Event ID
- 20110816X90141
- Case number
- ERA11LA454
- 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: 6d54d02541862fc72f56657865b4ce35b2d5b0fdef50256ee975126768db5d04; retrieved 2026-09-15T16:37:23.404Z.