FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA09FA068 · Beech 95-B55 (T4

24 Nov 2008 · Whites Creek, TN, United States

Beech 95-B55 (T4 · Accident: loss of control in flight on approach

From Memorial Field Airport (HOT) to Nashville International Airport (BNA)

Report a problem

Event

NTSB case
ERA09FA068
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
3 · 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
Instrument Meteorological Cond

Beech 95-B55 (T4

Aircraft type
Beechcraft 55
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
N412ES
Onboard fatalities
Unknown
Route
From Memorial Field Airport (HOT), Hot Springs, ARTo Nashville International Airport (BNA), Nashville, TN
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
Approach
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
Loss of control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

During flight in instrument meteorological conditions, the left engine experienced a total loss of power due to the separation of the flexible fuel supply hose between the left engine firewall fitting and the engine-driven fuel pump inlet fitting due to an inadequately torqued B-nut. The pilot informed air traffic control of a discrepancy, although he was not specific in the nature of the problem. A momentary change in heading to the left occurred consistent with the pilot’s failure to maintain directional control of the airplane following the loss of left engine power. Radar data indicated that the airplane was allowed to decelerate, followed by a loss of lateral and directional control and a subsequent flat spin to the left. The stall warning horn was recorded during the pilot's comment to the controller that he was in a spin. The airplane descended uncontrolled and crashed into a wooded area behind a home and was destroyed by impact and a postcrash fire. No preimpact mechanical failure or malfunction of the airplane or of either engine was noted.

Acoustic analysis of engine rpm signatures reflect a steadily decreasing rpm to 1,760, most likely from the left engine, which is below the normal operating range. The analysis indicated an rpm signature of 2,140, most likely from the right engine, which was in the normal operating range. The pilot neither feathered the left propeller nor secured the left engine following the total loss of power per the Pilot's Operating Handbook and Aircraft Flight Manual, and there were no mechanical discrepancies with the propeller or propeller governor that would have prevented him from doing so. Operational testing of the left engine with an exemplar flexible fuel hose that was finger-tight resulted in the separation of the line from the inlet fitting. The test runs determined that when finger-tight the B-nut loosened and tightened varying amounts with different power applications. Rebuilt engines were installed 9 months earlier and there was no entry indicating that the flexible fuel hoses were replaced at that time. There was no record that the left flexible fuel hose was ever replaced since the airplane was manufactured in 1978. Although the airplane manufacturer recommends that flexible fuel hoses be replaced when conditions warrant, at engine overhaul, or 5 years, whichever occurs first, there is no evidence to suggest that the age of the hose contributed to its separation from the engine-driven fuel pump inlet fitting.

Probable cause

The pilot's failure to feather the left propeller and secure the left engine following the total loss of left engine power, and his subsequent failure to maintain airspeed, lateral, and directional control of the airplane. Contributing to the accident was the failure of maintenance personnel to properly tighten the fuel supply hose at the engine-driven fuel pump.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA09FA068
Event ID
20081124X30428
Case number
ERA09FA068
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: 6898907952417132e48479ad8ed08b25a5b496c9b2635dc1ef28600c5f390e1b; retrieved 2026-09-13T19:49:54.133Z.