ERA12FA526 · Beech B24R
Beech B24R · Accident: loss of engine power (total) en route
From Wilmington International Airport (ILM) to AGH · West Mifflin, PA
Event
- NTSB case
- ERA12FA526
- 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
- Instrument Meteorological Cond
Beech B24R
- Aircraft type
- Beechcraft 24
- 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
- N9200S
- Operator
- Hall Brian F
- Onboard fatalities
- Unknown
- Route
- From Wilmington International Airport (ILM), Wilmington, NCTo AGH · West Mifflin, PA
- 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
- 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 (total)
- 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 › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Before departing on the accident flight, the noninstrument-rated pilot obtained a weather briefing and was advised several times that visual flight rules (VFR) flight was not recommended due to existing and forecast instrument meteorological conditions (IMC) along his intended route of flight. The pilot then departed on a VFR flight without filing a flight plan. More than 2 hours after departure, the pilot contacted air traffic control (ATC) and advised that he was climbing the airplane from 9,000 to 10,500 feet. Two minutes later, the pilot declared an emergency and advised ATC that he had "lost" the engine. The controller provided vectors to nearby airports, attempting to orient the pilot to the airplane's position relative to the airports so that he could acquire the airports visually. However, the pilot advised that he was "still in the soup and can't see much of anything at this point." About 5 minutes later, the pilot stated that the airplane was unable to clear a ridgeline in its flightpath, and shortly thereafter, radar and voice communication with the airplane was lost. The airplane collided with trees and terrain before reaching a suitable landing site.
Examination of the wreckage and engine revealed no preimpact mechanical malfunctions or failures that would have precluded normal operation. The fuel tanks were intact, and about 1 pint of fuel was drained from the left tank and 10 gallons were drained from the right. The fuel selector was found positioned to the right tank. Continuity of the entire fuel system was confirmed. Disassembly of the gascolator found that it contained no fuel, was completely dry, and was absent of debris. At the time of departure, each fuel tank contained 26.1 gallons of usable fuel. According to the manufacturer's pilot operating handbook, the airplane would consume 10.2 gallons per hour at 75 percent maximum continuous power. Given the fuel capacity of each tank, continuity of the fuel system, dry fuel system components, and published fuel consumption rates, it is likely the pilot exhausted the fuel supply in the left tank. It is likely that the engine lost power due to fuel starvation, and the pilot switched the fuel selector to the right tank but was unable to restore engine power before encountering a ridgeline in IMC. Toxicological testing and a review of the pilot's medical records revealed the contraindicated use of anti-depressant medication, which was not declared on his most recent medical certificate application.
Probable cause
The pilot's improper fuel management, which resulted in fuel starvation and a total loss of engine power. Contributing to the accident was the noninstrument-rated pilot's decision to attempt a visual flight rules flight in instrument meteorological conditions over mountainous terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA12FA526
- Event ID
- 20120826X33639
- Case number
- ERA12FA526
- 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: 290f18aa2c93f15d0f5263f9d81f268cafe338a2b01dac515479c287d3ae8061; retrieved 2026-09-13T22:34:57.170Z.