MIA00FA166 · Beech 95-A55
Beech 95-A55 · Accident: in flight collision with object en route
From Key Field / Meridian Regional Airport (MEI) to Walker County Airport Bevill Field (JFX)
Event
- NTSB case
- MIA00FA166
- 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
- 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 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
- N711MS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Key Field / Meridian Regional Airport (MEI), Meridian, MSTo Walker County Airport Bevill Field (JFX), Jasper, AL
- 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 · descent
- 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
- In flight collision with object
- 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
- Tree(s)
- 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
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot complained of a headache before the flight departed and asked for an obtained Tylenol. The flight departed and while in contact with an air traffic control facility, he advised the controller, "...I'm having a little problem---not the airplane...." He asked for vectors to the nearest airport and was provided direction and distance then advised the controller, ""I can't move my---can't move my left arm...." Radio communications were lost. The airplane impacted trees then terrain located on private property in a nose and left wing low attitude. The nose section including the cockpit and both wings were fragmented; aircraft debris were found along the wreckage path. Examination of the engines/propellers, and flight controls revealed no evidence of preimpact failure or malfunction. The autopsy report indicates that the cause of death was multiple blunt trauma with a contributory cause as atherosclerotic cardiovascular disease. Review of the pilot's civilian and Air National Guard medical files revealed that he had elevated blood pressure, blood sugar, and weight during periodic physical examinations. The high blood pressure was not being treated according to the Air National Guard medical records.
Probable cause
The in-flight collision with trees then terrain while descending for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA00FA166
- Event ID
- 20001212X21057
- Case number
- MIA00FA166
- 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: 6d5871e7ae449fde77d02f9513387d4eabdb2933f637998946ca5d12b891783a; retrieved 2026-09-20T21:12:49.371Z.