FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL82DA084 · Beech 58

25 Mar 1982 · Ridgeland, SC, United States

Gapway Groves Beech 58 · Accident: loss of control on ground/water during landing

From Winter Haven Regional Airport - Gilbert Field (GIF) to Yeager Airport (CRW)

Report a problem

Event

NTSB case
ATL82DA084
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 58

Aircraft type
Beechcraft 58
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
N3707N
Onboard fatalities
Unknown
Route
From Winter Haven Regional Airport - Gilbert Field (GIF), Winter Haven, FLTo Yeager Airport (CRW), Buckhannon, WV
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
Landing · landing roll
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 on ground/water
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

  • Fluid, hydraulic › Leak
  • Landing gear, emergency brake system › Inoperative
  • Landing gear, normal brake system › Failure, partial
  • Landing gear, normal brake system › Inoperative

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE PILOT STATED THAT DURING LANDING, THE LEFT BRAKE WAS INOPERATIVE. WHEN HE REALIZED THE PROBLEM, THERE WAS INSUFFICIENT RUNWAY REMAINING TO STOP OR GO-AROUND. AT THE END OF THE RUNWAY WAS A DEEP DROP-OFF. THEREFORE THE PILOT USED THE RIGHT BRAKE, AND SUBSEQUENTLY, THE PLANE DEPARTED THE RIGHT SIDE OF THE RUNWAY. THE RIGHT GEAR SEPARATED IN SOFT TERRAIN AS THE PLANE ENTERED A DEPRESSION BESIDE THE RUNWAY. AN EXAMINATION REVEALED THE LEFT BRAKE MASTER CYLINDER WAS WET WITH HYDRAULIC FLUID. THE CYLINDER, PARAMOUNT MODEL VI-15-750-3, WAS DISASSEMBLED. AN INSPECTION OF THE MASTER CYLINDER PISTON SHAFT REVEALED SEVERAL COMPRESSION INDENTATIONS. THE INDENTATIONS WERE LOCATED IN SUCH A MANNER AS TO PERMIT FLUID LEAKAGE AND INTRODUCTION OF AIR INTO THE CYLINDER. THE CAUSE OF THE INDENTATIONS WAS NOT DETERMINED.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record ATL82DA084
Event ID
20020917X01690
Case number
ATL82DA084
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: 4a1d3da1feb6af1a2363f85056f2ba77a57bf20745dfcce242eb86d4c2627d46; retrieved 2026-09-22T03:08:43.912Z.