ATL06CA001 · Beech D-95A
Beech D-95A · Accident: loss of engine power en route
From Piedmont Triad International Airport (GSO) to Greensboro, NC
Event
- NTSB case
- ATL06CA001
- 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 D-95A
- Aircraft type
- Beechcraft D-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
- N5606S
- Operator
- Angus I Hines · private individual
- Onboard fatalities
- Unknown
- Route
- From Piedmont Triad International Airport (GSO), Greensboro, NCTo Greensboro, NC
- 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
- En route · cruise
- 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
- Loss of engine power
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Fuel starvation
- 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
- All engines
- Fluid, fuel › Starvation
- Passenger › Control interference, not approved
- Pilot in command › Fuel management, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
During cruise flight, the pilot experienced a loss of engine power of one engine. Using standard engine out procedures , the pilot experienced difficulty identifying which engine had lost power. However, without the knowledge of the pilot, the passenger attempted to assist the pilot in maintaining directional control after initial loss of engine power by applying right rudder. In an effort by the pilot to regain full engine power, the second engine lost power. The pilot selected a nearby landfill for an emergency landing. During the emergency landing, the main landing gear collapsed. After the pilot and passenger exited the airplane, the passenger told the pilot that he had applied right rudder after the initial loss of engine power. Post-accident examination of both engines failed to disclose any abnormalities and 35 gallons of fuel was recovered from the fuel system.
Probable cause
The pilot mistakenly shut down the operating engine when the passenger interfered with the rudder pedals as he attempted to identify the inoperative engine.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL06CA001
- Event ID
- 20051028X01747
- Case number
- ATL06CA001
- 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, 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: 23b139f01b3bd8f94bc14f491d684b476acb76521fc1b246d455b807181ceec7; retrieved 2026-09-21T18:53:17.633Z.