ERA15LA202 · Beech D95 A
B G e Enterprises Beech D95 A · Accident: landing gear not configured
From Boone County Airport (HRO) to Jacksonville Executive at Craig Airport (CRG)
Event
- NTSB case
- ERA15LA202
- 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
Beech D95 A
- Aircraft type
- Beechcraft 95
- 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
- N8950U
- Operator
- B G e Enterprises
- Onboard fatalities
- Unknown
- Route
- From Boone County Airport (HRO), Harrison, ARTo Jacksonville Executive at Craig Airport (CRG), Jacksonville, FL
- Aircraft age
- About 50 years (built 1965)
- 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 gear not configured
- 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 systems
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The private pilot/owner reported that an air traffic controller vectored the airplane for the final approach for landing after the cross-country flight. The pilot noted that he performed the Before Landing checklist by rote and inadvertently positioned the flap handle believing that it was the landing gear handle. He added that he heard an electric motor actuate and that the airplane's speed and handling responded in a familiar fashion, so he continued the landing approach. The airplane subsequently landed with the landing gear retracted, which resulted in substantial damage to the airplane. The pilot reported that he did not confirm that the three green landing gear lights on the instrument panel had illuminated before landing but that the landing gear warning horn did not sound. The pilot also reported that there were no mechanical anomalies with the airplane that would have precluded normal operation.
After recovery, the airplane was placed on jacks, and the landing gear was extended and retracted with no anomalies noted. The airplane was then configured for landing, and the throttles were reduced to the idle-power position. Once configured, the landing gear warning horn did not sound as prescribed. Troubleshooting of the gear warning horn could not be performed; therefore, the cause of the horn malfunction could not be determined.
The pilot reported that he experienced lengthy delays earlier in his trip, which lengthened his duty day and resulted in fatigue. The pilot stated that fatigue, distractions, and complacency could have been mitigated by a "strict adherence to the checklist and visual verification of gear status."
Probable cause
The pilot's failure to properly configure the airplane for landing. Contributing to the accident were pilot fatigue, distraction, and complacency and the failure of the landing gear warning horn to sound for reasons that could not be determined based on the available information.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA15LA202
- Event ID
- 20150429X60027
- Case number
- ERA15LA202
- 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: dd0b8fcd0fe7a5cebcbac72d478d8e56e6f0233248abcba8b8a282464a6924b2; retrieved 2026-09-16T02:16:02.296Z.