FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

BFO95LA094 · Cessna 310K

29 Aug 1995 · Columbiana, OH, United States

Cessna 310K · Accident: airframe, component or system failure during landing

From Youngstown Warren Regional Airport (YNG) to 02G

Report a problem

Event

NTSB case
BFO95LA094
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

Cessna 310K

Aircraft type
Cessna 310
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
N6921L
Operator
Unknown
Onboard fatalities
Unknown
Route
From Youngstown Warren Regional Airport (YNG), Youngstown, OHTo 02G
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
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
Destroyed

Cause areas

  • Company maintenance personnel › Maintenance, installation, improper
  • Landing gear, main gear strut scissors › Disconnected

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

NTSB narrative

THE PILOT REPORTED THAT DURING THE LANDING ROLL HE 'FELT SOMETHING DRAG ON THE LEFT SIDE.... CAUSING THE AIRCRAFT TO VEER VIOLENTLY TO THE LEFT.' THE AIRCRAFT DEPARTED THE LEFT SIDE OF THE RUNWAY AND STRUCK TREES LOCATED APPROXIMATELY 150 FEET TO THE LEFT OF THE LANDING SURFACE. POSTACCIDENT EXAMINATION REVEALED THAT THE WASHER UNDER THE LEFT LANDING GEAR TORQUE LINK ATTACHMENT BOLT HEAD WAS NOT INSTALLED, AND THE TORQUE LINKS HAD SEPARATED. THE PILOT STATED THAT THE AIRPLANE HAD JUST RECEIVED MAINTENANCE TO REPAIR A PREVIOUSLY FAILED TORQUE LINK.

Probable cause

The improper maintenance installation and the subsequent separation of the torque links on the left main landing gear during the landing roll.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record BFO95LA094
Event ID
20001207X04177
Case number
BFO95LA094
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: 6130bbe0946933d497755a5bc7ce8bddb07ac3a8797fc5b7511aa12afc5b0b15; retrieved 2026-09-21T22:06:03.257Z.