FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW83LA289 · Beech 95-B55

20 Jun 1983 · Pineville, LA, United States

Beech 95-B55 · Accident: airframe, component or system failure on approach

From M76 · Monticello, AR to an unrecorded destination

Report a problem

Event

NTSB case
FTW83LA289
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 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
N7712R
Operator
Unknown
Onboard fatalities
Unknown
Route
From M76 · Monticello, ARTo 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
Airframe, component or system failure
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

  • Company/operator management › Maintenance, inspection, inadequate
  • Landing gear, normal retraction/extension assembly › Loose
  • Landing gear, normal retraction/extension assembly › Worn

Approximate · Estimated position: the centre of Pineville, LA, the place the record names. Not the accident site.

NTSB narrative

PRIOR TO LANDING, THE PLT MOVED THE GEAR SWITCH TO THE EXTEND POSITION & NOTED THAT THE GEAR INDICATED DOWN. HOWEVER, THE LEFT MAIN GEAR DID NOT EXTEND. WHILE LANDING WITH THE LEFT GEAR RETRACTED, THE ACFT SETTLED ON THE LEFT WING & PROP. THE ACFT SPUN 180 DEG TO THE LEFT & CAME TO REST IN A GRASSY AREA OFF THE RWY. AN EXAM REVEALED THE LEFT MAIN GEAR CABLE WAS LOOSE, THE RESPECTIVE UPLOCK WAS WORN & THE LEFT GEAR WAS STRUCK IN THE UP POSITION. THE LAST ANNUAL INSPECTION WAS PERFORMED ON 5/12/82. THE GEAR POSITION INDICATOR INDICATED THE LANDING GEAR ACTUATOR ARM POSITION RATHER THAN THE ACTUAL GEAR POSITION.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record FTW83LA289
Event ID
20001214X43352
Case number
FTW83LA289
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: 7afae955ee9931339c5b0cc7a08c3cbdfbfdfd0cfe256858480448099dda1880; retrieved 2026-09-23T21:57:27.407Z.