GAA16CA146 · Beech D17 S
Beech D17 S · Accident: loss of control in flight during takeoff
From Brighton Van-Aire Estates Airport (CO12) to Brighton Van-Aire Estates Airport (CO12)
Event
- NTSB case
- GAA16CA146
- 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 D17 S
- Aircraft type
- Beechcraft 17
- 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
- N9290H
- Operator
- Stephen E. Dyer · private individual
- Onboard fatalities
- Unknown
- Route
- From Brighton Van-Aire Estates Airport (CO12), Brighton, COTo Brighton Van-Aire Estates Airport (CO12), Brighton, CO
- Aircraft age
- About 72 years (built 1944)
- 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
- Takeoff
- 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
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot of a tailwheel-equipped biplane reported that shortly after the biplane lifted off the runway during takeoff, he diverted his attention and reached for the fuel selector which was located on the lower right wall of the cockpit. He further reported that the biplane drifted to the left of the runway and impacted a fence. The airplane sustained substantial damage to the upper and lower right wings, and the fuselage.
According to the pilot there were no preimpact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.
Probable cause
The pilot's failure to maintain the runway course during takeoff, resulting in the airplane drifting to the left and impacting a fence. A contributing factor to the accident was the pilot's diverted attention during the takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA16CA146
- Event ID
- 20160312X14654
- Case number
- GAA16CA146
- 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, coordinates. 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: a4ad58c9724db29386a5cacff315f42b15e00a2a6f109c71c2bb1d50d7f5c506; retrieved 2026-09-16T03:12:50.724Z.