CHI94LA235 · Beech 17
Overturf Electric Motors Beech 17 · Accident: in flight collision with object during landing
From Columbus Municipal Airport (OLU) to NE (no airport)
Event
- NTSB case
- CHI94LA235
- 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
- 0
- 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
Beech 17
- Aircraft type
- Beechcraft 17
- 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
- N1184V
- Operator
- Overturf Electric Motors
- Onboard fatalities
- Unknown
- Route
- From Columbus Municipal Airport (OLU), Columbus, NETo NE (no airport)
- 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 · aborted
- 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
- In flight collision with object
- 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 › Clearance, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT EXTENDED THE AIRPLANE'S LANDING GEAR WHILE ON THE DOWNWIND LEG IN PREPARATION FOR LANDING. ALL INDICATIONS WERE NORMAL. WHEN HE FLARED THE AIRPLANE FOR TOUCHDOWN, THE PILOT REALIZED THAT THE AIRPLANE WAS SETTLING CLOSER TO THE GROUND THAN NORMAL. HE ELECTED TO GO AROUND AND ADDED FULL POWER. WHILE CLIMBING, THE AIRPLANE'S RIGHT WING STRUCK A ROAD SIGN LOCATED AT THE WEST END OF THE RUNWAY. THE AIRPLANE LANDED ON A FIELD APPROXIMATELY 100 FEET FROM THE RUNWAY WITH THE GEAR PARTIALLY EXTENDED. A POSTACCIDENT INSPECTION OF THE LANDING GEAR WAS PERFORMED. A COMPLETE RETRACTION CHECK COULD NOT BE PERFORMED DUE TO THE SEVERITY OF THE DAMAGE TO THE GEAR RETRACTION SYSTEM. DURING THE TEST, THE LANDING GEAR MOTOR STOPPED TWICE WITHOUT ANY EXTERNAL INFLUENCE.
Probable cause
the pilot's failure to maintain clearance with the road sign. Factors in the accident were the sign and the failure of the landing gear to extend into the full down and locked position.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI94LA235
- Event ID
- 20001206X01703
- Case number
- CHI94LA235
- 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. 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: c245da6a29539be34f30521d1fe00ced9652e3dfc330df45ac4cae3f4530429f; retrieved 2026-09-23T00:55:25.338Z.