DCA94GA010 · Beech 300/F
Federal Aviation Admin Beech 300/F · Accident: in flight encounter with weather while maneuvering
From W16 · Winchester, VA to Newport News Williamsburg International Airport (PHF)
Event
- NTSB case
- DCA94GA010
- 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
- 3 · all aircraft and ground
- Ground fatalities
- 0
- 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 300/F
- Aircraft type
- Beechcraft 300
- 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
- N82
- Operator
- Federal Aviation Admin
- Onboard fatalities
- Unknown
- Route
- From W16 · Winchester, VATo Newport News Williamsburg International Airport (PHF), Newport News, VA
- 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
- Maneuvering
- First occurrenceThe 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
- In flight encounter with weather
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Faa(organization) › Inadequate certification/approval
- Faa(organization) › Inadequate surveillance of operation
- Faa(organization) › Insufficient standards/requirements
- Pilot in command › VFR flight into imc, continued
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane was flying at 2,000 feet in the vicinity of high terrain when the airplane entered IMC conditions. The airplane struck the high terrain near the LINDEN VOR, while the PIC was awaiting an IFR clearance.
Probable cause
the failure of the pilot-in-command to ensure that the airplane remained in visual meteorological conditions over mountainous terrain, and the failure of the Federal Aviation Administration executives and managers responsible for the FAA flying program to: 1)establish effective and accountable leadership and oversight of flying operations; 2)establish minimum mission and operational performance standards; 3)recognize and address performance-related problems among the organization's pilots; and 4) remove from flight operations duty pilots who were not performing to standards.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA94GA010
- Event ID
- 20001211X13551
- Case number
- DCA94GA010
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 95cfe94b9b5157a8b3dfc31357a4177800a834f82d249af0af65729a3b6046d8; retrieved 2026-09-21T00:20:24.876Z.