FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA15LA293 · Beech C90B

1 Aug 2015 · Georgetown, KY, United States

Beech C90B · Accident: loss of engine power (partial) en route

From James M. Cox Dayton International Airport (DAY) to Lake Cumberland Regional Airport (SME)

Report a problem

Event

NTSB case
ERA15LA293
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 C90B

Aircraft type
Beechcraft 90
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
N257CQ
Operator
Unknown
Onboard fatalities
Unknown
Route
From James M. Cox Dayton International Airport (DAY), Dayton, OHTo Lake Cumberland Regional Airport (SME), Somerset, KY
Aircraft age
About 20 years (built 1995)
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
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 engine power (partial)
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

  • Not determined › Not determined

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

NTSB narrative

The airplane was fueled with 140 gallons of fuel before the second of three flight segments. The pilot reported that, while en route on the third segment, a fuel crossfeed light illuminated. He reset the indicator and decided to land the airplane to troubleshoot. He requested to divert to the nearest airport, which was directly beneath the airplane. Subsequently, the right engine lost power, and the autofeather system feathered the right engine propeller. He reduced power on the left engine, lowered the nose, and extended the landing gear while entering the traffic pattern. The pilot indicated that, after the landing gear was extended, the electrical system "failed," and shortly after, the left engine would not respond to power lever inputs. As the flight was on a base leg approach, the airplane was below the intended flightpath to reach the runway. The pilot stated that he pulled "gently on the control wheel"; however, the airplane impacted an embankment and came to rest on airport property, which resulted in substantial damage to both wings and the fuselage.

Postaccident examination of the engines and airframe revealed no evidence of mechanical malfunctions or abnormalities that would have precluded normal operation. Signatures on the left propeller indicated that the engine was likely producing power at the time of impact; however, actual power settings could not be conclusively determined. Signatures on the right propeller indicated that little or no power was being produced. The quantity of fuel in the airplane's fuel system, as well as the configuration of the fuel system at the time of the accident, could not be determined based on the available evidence.

Although the position of the master switch (which includes the battery, generator 1, and generator 2) was found in the OFF position, the airplane had been operating for about 30 minutes when the electrical power was lost; thus, it is likely that the airplane had been operating on battery power throughout the flight. This could have been the result of the pilot's failure to activate, or his inadvertent deactivation of, the generator 1 and 2 switch. If the flight were operating on battery power, it would explain what the pilot described as an electrical system failure after the landing gear extension due to the exhaustion of the airplane's battery.

The postaccident examination of the left engine and propeller revealed that the engine was likely producing some power at the time of impact, and an explanation for why the engine reportedly did not respond to the pilot's throttle movements could not be determined. Additionally, given the available evidence, the reason for the loss of power to the right engine could not be determined.

Probable cause

Undetermined based on the available evidence.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA15LA293
Event ID
20150803X51616
Case number
ERA15LA293
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2015-08-02.
  • API snapshot SHA-256: 591b5371ec95bd50842bf2473489353e92e8b69ba23d399c7b71e61fb71dcf7d; retrieved 2026-09-16T02:37:01.400Z.