ERA12FA458 · Beech A23
Beachcraft Aviation Club Beech A23 · Accident: loss of control in flight during initial climb
From Davis Airstrip (W50) to Davis Airstrip (W50)
Event
- NTSB case
- ERA12FA458
- 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 A23
- Aircraft type
- Beechcraft 23
- 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
- N8771M
- Operator
- Beachcraft Aviation Club
- Onboard fatalities
- Unknown
- Route
- From Davis Airstrip (W50), Laytonsville, MDTo Davis Airstrip (W50), Laytonsville, MD
- 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 systems
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot performed a preflight inspection and fueled the airplane with no anomalies noted. He performed two takeoffs and landings without incident. Before the third takeoff, the pilot verified that the flaps were retracted for takeoff and that the left fuel tank was selected. The pilot applied power to take off and released the brakes. As the airplane rolled down the runway, it lifted off the ground, and then settled back onto the runway. The pilot stated that he continued to apply full power but that the airplane was not performing as well as on the previous takeoffs. The airplane eventually became airborne. The pilot stated that he initiated a turn to the right in order to avoid striking trees off the end of the runway; the flight instructor subsequently took the flight controls as the right turn became steeper and the airplane began to descend. According to a witness, the airplane appeared like it would not clear the trees, banked right, and then entered a spin before impacting the ground.
Postaccident examination of the fuel selector revealed it was in a mid-range position, with neither the left or right tank selected. When the fuel selector was placed to the center position, similar to where it was found after the accident, fuel would not flow through the fuel selector. Thus, it is likely that the pilot did not turn the fuel selector completely so that it was not locked in the detent, which restricted fuel flow and resulted in a loss of engine power. In addition, the main fuel line and the return fuel line were removed and there was no fuel present.
A postaccident engine teardown was performed and the fuel manifold was disassembled; dry rot was noted on the manifold diaphragm and it was leaking. The leak might have reduced fuel consumption, but not a significant amount. It is likely that, because of the loss of engine power, the airplane would not have been able to adequately climb above the trees off the end of the runway. Therefore, the pilot attempted to avoid the trees and initiated a turn during the initial climb, which resulted in an aerodynamic stall and subsequent spin.
Although postaccident testing indicated that the flight had adult-onset diabetes, it could not be determined if the flight instructor experienced symptoms from the condition or side effects from the medication that treated the diabetes, which could have hindered his ability to operate the airplane. Furthermore, the flight instructor did not report the diabetic condition or medications on his most recent application for an Aviation Medical Certificate.
Probable cause
The pilot’s failure to ensure that the fuel selector handle was correctly positioned, which resulted in an interruption of fuel to the engine and a loss of engine power during the takeoff, which necessitated a turn away from the trees at the end of the runway and the subsequent stall.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA12FA458
- Event ID
- 20120716X04538
- Case number
- ERA12FA458
- 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: effac8e8658e4cde5a8835b833defae25ac66249b99eeaa87cc8b1c44664c1d8; retrieved 2026-09-13T22:29:29.176Z.