CEN23LA194 · Beech 35-C33A
Beech 35-C33A · Accident: fire/smoke (non-impact) during initial climb
From Indianola Municipal Airport (IDL) to George M Bryan Airport (STF)
Event
- NTSB case
- CEN23LA194
- 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 35-C33A
- Aircraft type
- Beechcraft 35
- 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
- N63B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Indianola Municipal Airport (IDL), Indianola, MSTo George M Bryan Airport (STF), Starkville, MS
- Aircraft age
- About 57 years (built 1966)
- 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
- Initial climb
- Defining eventThe 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/smoke (non-impact)
- 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
- Aircraft › Aircraft systems
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot stated that before the flight he completed an engine runup with no anomalies noted. After departure, when the airplane was about 800 to 1,000 ft above ground level, he smelled “burning plastic” and observed smoke from the engine compartment. He turned back toward the airport and was on the base leg of the traffic pattern when he observed flames coming through the firewall under the battery box area. He tried to kick out the flame, but the fire seemed to be coming from the engine side of the firewall. He turned off the electrical system and adjusted the mixture control to cut off the fuel. He performed a gear-up landing on the runway as the cabin filled with smoke. After the airplane came to rest and the pilot egressed, the fire consumed a majority of the fuselage before it was extinguished. The pilot recorded a video of the airplane that showed dark smoke in the cabin and heat discoloration below the front right windscreen, near the battery box. The postaccident examination was unable to determine the source of the fire due to the extensive fire damage.
Probable cause
An in-flight fire for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN23LA194
- Event ID
- 20230522192214
- Case number
- CEN23LA194
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates, cause areas. 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: db8a7bb903b99966531fc970732225c79a8b45ca07a4a2d1509f67c292144dea; retrieved 2026-09-16T17:37:38.155Z.