FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW01FA015 · Beech BE-76

30 Oct 2000 · Tulsa, OK, United States

Beech BE-76 · Accident: fire while maneuvering

From Tulsa Riverside Airport (RVS) to an unrecorded destination

Report a problem

Event

NTSB case
FTW01FA015
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
2 · 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 BE-76

Aircraft type
Beechcraft BE-76
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
N23823
Operator
Unknown
Onboard fatalities
Unknown
Route
From Tulsa Riverside Airport (RVS)To not recorded
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
Fire
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(cfi) › Airspeed(vmc), not maintained

Approximate · Estimated position: the centre of Tulsa, OK, the place the record names. Not the accident site.

NTSB narrative

The instructor reported a right engine fire and requested a straight-in approach for a northbound runway. The wind at the time of the accident was from the south-southeast at 8 knots. At the time the pilot reported the engine fire to air traffic control, the aircraft was positioned approximately 4 miles north of another airport, and approximately 18 miles south of the pilot's intended landing airport. Numerous witnesses, located at the airport, stated that they observed the airplane flying fast on approach. The pilot reported to air traffic control that "the gear [was] not operating" and that he had to go-around. He added that "one of the lights [was] not coming on." The air traffic controller informed the pilot that the landing gear appeared to be down and cleared him to land on either runway at his discretion. The pilot stated that he was going to land on the opposite runway from his initial approach. The controllers and witnesses reported that the airplane initiated a climb, slowed, then started to roll over to the right and pitch nose down. The airplane impacted the ground and a fire erupted upon impact. Examination of the wreckage revealed that the right propeller was not feathered and the landing gear were extended; however, the right main landing gear indicator light filament was found separated. The cause of the engine fire was not determined. According to the aircraft Pilot Operating Handbook, in the case of an engine fire in-flight, the pilot is to feather the affected engine's propeller and "land immediately." In addition, the instructions for a single-engine go-around require that the pilot retract the landing gear.

Probable cause

the instructor pilot's failure to maintain the airplane's minimum controllable airspeed during a single-engine go-around, which resulted in his loss of control of the airplane. Contributory factors were the engine fire, the pilot's failure to follow the emergency checklist and feather the propeller, and the partial failure of the landing gear indicating system, which resulted in the instructor's diverted attention.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW01FA015
Event ID
20001212X22152
Case number
FTW01FA015
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 2000-10-31.
  • API snapshot SHA-256: 75cf21fcd61b18511e6afa7ccd3dd69fbff249d02737ff36af859229aa41b69e; retrieved 2026-09-20T20:47:55.664Z.