CEN19TA205 · Beech 23
Beech 23 · Accident: loss of control in flight on approach
From Winona–Montgomery County Airport (5A6) to Mitchells Airport (3MS5)
Event
- NTSB case
- CEN19TA205
- 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
- Unknown
- 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
- N7618R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Winona–Montgomery County Airport (5A6), Winona, MSTo Mitchells Airport (3MS5), Vaiden, MS
- Aircraft age
- About 50 years (built 1969)
- 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
- 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
- Loss of control in flight
- 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
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot had conducted a sightseeing flight with three passengers. He configured the airplane with flaps full down for the approach to land on the 2,500-ft turf runway with the airplane near its maximum gross weight. He reported that, due to excessive speed on the final approach, the airplane floated halfway down the runway, and he initiated a go-around. The wing flaps remained fully extended, and the pilot recognized the climb rate was not enough to clear trees at the end of the runway, so he pulled back on the flight control yoke. He then realized that the airplane was in an aerodynamic stall condition and decreased the pitch attitude. The airplane impacted rising terrain about 330 ft beyond the departure end of the runway, which resulted in substantial damage to the wings and fuselage. Examination of the airframe and engine revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. The pilot’s failure to retract the wing flaps during the go-around likely affected the airplane’s performance and ability to climb.
Probable cause
The pilot's unstable approach and failure to properly configure the flaps during the attempted go-around, which resulted in an aerodynamic stall and impact with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN19TA205
- Event ID
- 20190704X63244
- Case number
- CEN19TA205
- 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. 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: 8ec3b73f144ce7baae9ca0c3efb5aa1a4b4b017c01d5ed876aa5f250b9f2bd53; retrieved 2026-09-16T09:22:24.793Z.