FTW00LA211 · Beech D35
Beech D35 · Accident: partial loss of engine power (non-mechanical) on approach
From Smith Field (SLG) to Crystal Lake Airport (5M5)
Event
- NTSB case
- FTW00LA211
- 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 D35
- 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
- N3424B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Smith Field (SLG), Siloam Springs, ARTo Crystal Lake Airport (5M5), AR
- 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
- Approach · VFR go-around
- 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)
- 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
- Stall
- 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
- Pilot in command › Stall, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that he made visual contact with the destination airport when he was 'several miles out.' He flew a left base for runway 31, close in, and hurried to get things set up for the turn to final. On short final, he noticed that the airplane was extremely fast, and as the airplane approached the runway, the pilot remarked to his passenger that 'something was not right.' He then noticed that the landing gear handle was in the retracted position and initiated a go-around. Simultaneously, he heard scraping as if the airplane had contacted the runway. The pilot stated that he believes 'the prop hit the runway.' During the go-around, the pilot noticed that the airplane would not maintain a positive rate of climb. The pilot initiated an approach to a field, but 'pulled the airplane up' to clear trees and, subsequently, the airplane stalled, impacted the ground, and came to rest upright.
Probable cause
The inadvertent stall while maneuvering to avoid obstructions during a forced landing. A factor was the pilot's failure to extend the landing gear, which resulted in a partial loss of engine power due to the propeller blades striking the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW00LA211
- Event ID
- 20001212X21466
- Case number
- FTW00LA211
- 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: 3d71bfd6dea83c6bfadd1e361be2e3d8684ac554be4ea2537bdd994d216bdceb; retrieved 2026-09-21T20:09:42.076Z.