FTW00LA251 · Beech BE58
Beech BE58 · Accident: fire while taxiing
From OKC Will Rogers World Airport (OKC) to Wiley Post Airport (PWA)
Event
- NTSB case
- FTW00LA251
- 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
- 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 BE58
- Aircraft type
- Beechcraft 58
- 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
- N84DE
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From OKC Will Rogers World Airport (OKC), Oklahoma City, OKTo Wiley Post Airport (PWA), OK
- 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
- Taxi · from runway
- 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
- Substantial
Cause areas
- Engine compartment › Fire
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The commercial pilot made an uneventful landing and was taxiing the twin-engine airplane off of the runway when the right engine lost power. The pilot restarted the engine; however, the engine soon lost power again. The pilot was attempting a third start when the passenger noticed a fire near the right wing engine compartment. The pilot stated that he pulled the right engine mixture to idle cut-off and continued cranking the engine in an attempt to suck the fire into the intake manifold. The fire continued to burn, and the pilot and passenger exited the aircraft and attempted to find help. The fire extinguished on its own accord. According to the FAA inspector, who responded to the accident site, and a mechanic, who examined the aircraft after the event, there was no evidence of ruptured fuel lines or loose fittings.
Probable cause
the fire, which ignited in the engine compartment for undetermined reasons while taxiing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW00LA251
- Event ID
- 20001212X21972
- Case number
- FTW00LA251
- 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: 8d8f1343251ba5d0a6802a7df6d815685508476ba9d7c91aa126c3f31cf58687; retrieved 2026-09-22T12:28:51.023Z.