IAD99FA038 · Beech BE-95A
Beech BE-95A · Accident: loss of control in flight en route
From Roanoke–Blacksburg Regional Airport (ROA) to Claxton Evans County Airport (CWV)
Event
- NTSB case
- IAD99FA038
- 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
- 4 · 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 BE-95A
- Aircraft type
- Beechcraft BE-95
- 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
- N3113K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Roanoke–Blacksburg Regional Airport (ROA), Roanoke, VATo Claxton Evans County Airport (CWV), Claxton, GA
- 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 · climb to cruise
- 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
- Loss of control in flight
- 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
- Tree(s)
- 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
- Pilot in command › Aircraft control, not maintained
- Pilot in command › Flight into known adverse weather, intentional
- Pilot in command › Preflight planning/preparation, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was briefed on two occasions by a flight service briefer and was advised of a SIGMET for moderate to severe turbulence for the departure airport area and along the airplane's proposed route of flight. The pilot acknowledged receipt of a Hazardous In-flight Alert System (HIWAS) alert for moderate to occasional severe turbulence just prior to takeoff. After departure, the tower controller stopped the airplane's climb at 6,000 feet for traffic, then told the pilot to continue the climb to 8,000 feet. The controller had received Pilot Reports (PIREPs) about turbulence and asked the pilot what he was experiencing. The controller did not receive a response, and the airplane disappeared from the radarscope after reaching an altitude of 6,700 feet. Post accident interviews with other pilots revealed they experienced severe turbulence during the same time frame in the vicinity of the accident. Computer analysis of weather data indicated a 100% probability of severe turbulence at 6,000 feet, and at 7,000 feet, vertical motions of 3,153 feet per minute indicated a severe mountain wave. A PIREP placed the base of the cloud layer at 5,400 feet and the tops at 9,500 feet. The airplane's published maximum gross weight was 4,200 pounds, with a center-of-gravity (CG) range of 80.5 inches to 86 inches aft of datum. The airplane's calculated weight at the time of the accident was 4,566 pounds, with the center of gravity calculated at 90.68 inches aft of datum.
Probable cause
the pilot's inadequate preflight planning which resulted in intentional flight into known severe turbulence and the subsequent loss of control. Factors in the accident were the turbulence in instrument meteorological conditions and an airplane loaded over the maximum allowable gross weight and outside the allowable center-of-gravity range.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD99FA038
- Event ID
- 20001205X00479
- Case number
- IAD99FA038
- 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: 90b91ac466e3269c44dec89dfb04766c082ff4372dca714b451ea269be38c06d; retrieved 2026-09-20T22:09:59.616Z.