FTW96LA026 · Beech 23
Beech 23 · Accident: partial loss of engine power (non-mechanical) en route
From Parkland Airport (7CO0) to F-28 · El Reno, OK
Event
- NTSB case
- FTW96LA026
- 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 23
- Aircraft type
- Beechcraft 23
- 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
- N5070T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Parkland Airport (7CO0), Erie, COTo F-28 · El Reno, 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
- En route · 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
- Partial loss of engine power (non-mechanical)
- 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
- Fuel system, carburetor › Ice
- Pilot in command › Carburetor heat, delayed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WHILE IN CRUISE FLIGHT, THE ENGINE LOST 25-35 RPM AND BEGAN TO RUN ROUGH. THE PILOT CHECKED THE MAGNETOS, WHICH WERE FOUND TO BE OPERATING NORMALLY, AND THEN APPLIED CARBURETOR HEAT. THE ENGINE DECELERATED TO IDLE AND WOULD NOT ACCELERATE BACK TO NORMAL POWER. AN EMERGENCY LANDING WAS MADE TO A FIELD WHICH WAS SOFT AND MUDDY. DURING TOUCHDOWN, THE AIRCRAFT STRUCK A FENCE AND DURING LANDING ROLL THE LANDING GEAR SHEARED OFF WHEN IT SUNK INTO THE SOFT TERRAIN. EXAMINATION OF THE AIRCRAFT AND ENGINE PROVIDED NO EVIDENCE OF PREIMPACT FAILURE OR MALFUNCTION. TEMPERATURE/DEW POINT SPREAD AT THE TIME OF THE OCCURRENCE WAS 14 DEGREES FAHRENHEIT.
Probable cause
THE PILOT'S DELAYED APPLICATION OF CARBURETOR HEAT. A FACTOR WAS THE UNSUITABLE TERRAIN.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW96LA026
- Event ID
- 20001207X04705
- Case number
- FTW96LA026
- 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: b0f8672e3df834fcc5a822a19febdbb2b2cedab3469719d284a62279cac9603d; retrieved 2026-09-22T23:06:36.938Z.