CHI02FA237 · Beech 95-A55
Beech 95-A55 · Accident: loss of control in flight on approach
From FES · Festus, MO to an unrecorded destination
Event
- NTSB case
- CHI02FA237
- 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
- 1 · 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 95-A55
- Aircraft type
- Beechcraft 55
- 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
- N13MS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From FES · Festus, MOTo not recorded
- 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
- 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
- Loss of control in flight
- 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
- Destroyed
Cause areas
- Pilot in command › Lack of recent experience
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane was destroyed when it impacted terrain after a loss of control during landing approach. The airplane was in a left hand traffic pattern. According to witnesses, the airplane was on a base leg for landing when the pilot reported that he was too close to land and he would make a right turn and enter the final approach for the runway. The witnesses reported that, during the right turn, the bank angle appeared to be 90 degrees. The airplane subsequently impacted the ground. No preexisting airframe or engine defects were found during the postaccident examination. The pilot's flight instructor stated that the pilot did not fly the airplane enough to stay proficient and that he had a tendency to make steep turns in the traffic pattern. According to logbook records, the pilot had flown 2 hours in the preceding 90 days and had only flown once in the preceding 8 months.
Probable cause
The pilot's lack of recent experience and his failure to maintain adequate airspeed which resulted in a stall and collision with the ground. The pilot's failure to execute a go-around was a factor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI02FA237
- Event ID
- 20020813X01378
- Case number
- CHI02FA237
- 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, coordinates. 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: c58e27097fbfc81a5d764bbba1ae743cebb3a83e227ef998081ac633e61cd787; retrieved 2026-09-20T19:55:25.745Z.