FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW02FA062 · Beech 95-B55

5 Jan 2002 · Oak Grove, LA, United States

Beech 95-B55 · Accident: loss of control in flight while maneuvering

From Avon, MS (no airport) to Monroe Regional Airport (MLU)

Report a problem

Event

NTSB case
FTW02FA062
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
Instrument Meteorological Cond

Beech 95-B55

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
N77RY
Operator
Unknown
Onboard fatalities
Unknown
Route
From Avon, MS (no airport)To Monroe Regional Airport (MLU), Monroe, LA
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
Maneuvering
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/spin
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 › Airspeed, not maintained
  • Pilot in command › Stall/spin, inadvertent

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

A witness stated that he heard the airplane over fly the private airport at what sounded like a "low altitude." The witness went outside and observed the airplane approximately 1/4 of a mile southeast, at 300 feet above the ground, in a steep left bank. The airplane entered a spin, rotated 1-1.5 times, and impacted the ground. The witness reported that the cloud base was approximately 500 feet agl. On the day prior to the accident date, the instrument-rated pilot flew the airplane to a private ranch. Concerned with the deteriorating weather conditions, the pilot elected to depart the ranch one day earlier than he had planned, then return to the ranch via his vehicle. Prior to departure, the pilot obtained a weather briefing and visual flight rules (VFR) was not recommended for his route of flight. The pilot purchased the airplane in August 1994, and reported on an insurance form, dated May 14, 2001, that he accumulated 1,081 flight hours in the accident airplane make and model. Examination of the airplane and engines revealed no evidence of any pre-impact discrepances.

Probable cause

the pilot's failure to maintain control of the airplane while maneuvering resulting in an inadvertent stall/spin.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW02FA062
Event ID
20020108X00047
Case number
FTW02FA062
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: 5bbd363e968c5c089db1658072576171d08aaec4d70680c5b9fe6eddd51b336d; retrieved 2026-09-20T20:14:59.977Z.