FTW96FA030 · Beech 95-B95
Beech 95-B95 · Accident during takeoff
From Tulsa International Airport (TUL) to Aero Valley Airport (52F)
Event
- NTSB case
- FTW96FA030
- 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
- 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
- Visual Meteorological Cond
Beech 95-B95
- Aircraft type
- Beechcraft 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
- N9943R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Tulsa International Airport (TUL)To Aero Valley Airport (52F), Roanoke, TX
- 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
- Takeoff · roll/run
- 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
- Miscellaneous/other
- 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 › Aborted takeoff, not performed
- Pilot in command › Aircraft preflight, inadequate
- Pilot in command › Removal of control/gust lock(s), not performed
Approximate · Estimated position: the centre of Tulsa, OK, the place the record names. Not the accident site.
NTSB narrative
The pilot began an intersection takeoff with 5,450 feet of runway remaining. A controller in the tower noted that the airplane did not become airborne, while on the runway, although it was observed increasing in speed during the takeoff/ground roll. No evidence of an abort was found. Markings were found on the grass overrun that matched the distances between the airplane's landing gear. Beyond the overrun, the airplane (became airborne, but) descended, struck a tree, the terrain, and a railroad track before coming to rest. The cockpit control lock for the elevator and ailerons was found in place. Numerous parts of the airplane sustained fire damage; however, there was no physical evidence of an inflight fire, and no anomalies were found that would preclude engine operation. The right propeller piston position was in a low blade angle range; the blade angles for the left propeller could not be determined. The propeller blades, however, exhibited striations, nicks, gouges, bending and/or twisting.
Probable cause
Inadequate preflight by the pilot by failing to remove the flight control lock and failing to check the flight controls before takeoff, and the pilot's failure to abort the takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW96FA030
- Event ID
- 20001207X04684
- Case number
- FTW96FA030
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1995-10-28.
- API snapshot SHA-256: 6e57d4063f2e1cf45f5a7d1308ec7ea0b14df127f85ca2d167e920114a644491; retrieved 2026-09-20T23:32:44.385Z.