FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA12FA262 · Beech 58

1 Apr 2012 · Calhoun, KY, United States

Beech 58 · Accident: loss of control in flight during initial climb

From Woosley Field Airport (96KY) to Madisonville Regional Airport (2I0)

Report a problem

Event

NTSB case
ERA12FA262
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
1 · 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 58

Aircraft type
Beechcraft 58
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
N9448Q
Operator
Daniel J. Woosley · private individual
Onboard fatalities
Unknown
Route
From Woosley Field Airport (96KY), Calhoun, KYTo Madisonville Regional Airport (2I0), Madisonville, KY
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
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
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability

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

NTSB narrative

The pilot was departing his home airport to fly to another airport to refuel the airplane. Witnesses reported that the airplane lifted off from the 1,800-foot-long grass runway; however, none of the witnesses observed the airplane crash shortly after takeoff. The airplane rolled left and impacted the ground inverted in a wooded area near the departure end of the runway; there was no postcrash fire.

Examination of the flight controls revealed no evidence of preimpact failure or malfunction. Damage to one of the right engine propeller blades was consistent with engine power at impact, whereas the left engine propeller blades showed no evidence of power at impact. Thus it is likely that the left engine experienced a total loss of power just after takeoff, which the pilot was unable to control. Both engines were removed, transported to the manufacturer’s facility, and test run with no mechanical discrepancies noted.

Rust-colored water was detected in various fuel system components from both engines. Further, the strainer drain lines and outer tank drains in both engines’ fuel systems were partially blocked by rust-colored debris. Postaccident examination revealed evidence of long-term water contamination of both engines’ fuel systems due to leakage past the fuel caps, which are normally replaced on an “on-condition” basis during maintenance. The engine failure was likely due to the water contamination in the fuel system, which was not detected by the pilot during the preflight inspection.

Further, the leaking fuel caps most likely existed, but went undetected, when the airplane’s most recent annual inspection was performed about 4 months earlier. A review of airplane maintenance records revealed that the only entry related to the fuel filler caps since the airplane was manufactured in 1972 was dated July 2010, at which time the left fuel filler cap was replaced and an outer o-ring of the incorrect dimension was installed. In April 2011, as a result of a 2008 investigation of a Canadian registered Beech 58 airplane that had water enter the fuel tank due to deteriorated fuel filler cap o-rings, the manufacturer revised the maintenance manual of Beech 55 and 58-series airplanes to require fuel cap overhaul. Maintenance manual guidance in effect when the accident airplane’s most recent annual inspection was performed excluded the accident airplane (by serial number) from this overhaul. Since this accident, the manufacturer has revised its Beech 55 and 58 maintenance manuals to include the fuel cap overhaul requirement for all potentially affected airplanes, including the accident airplane.

Probable cause

The failure of the pilot to maintain airplane control after experiencing a loss of power from the left engine due to water contamination of the fuel system. Contributing to the accident was the pilot’s inadequate preflight inspection of the airplane and maintenance personnel’s inadequate annual inspection, because both failed to detect the long-term water contamination of the fuel system and the deteriorated outer o-rings on both fuel caps. Also contributing to the water contamination of the fuel system was the inaccurate information and instructions in the airplane maintenance manual pertaining to overhaul requirements of the fuel filler caps.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA12FA262
Event ID
20120402X20342
Case number
ERA12FA262
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: 4ca300d03a5c6ecf8574bfb91443feeac1ed41dd70ffdaf7305ee15411e707ac; retrieved 2026-09-13T22:17:20.939Z.