FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Dominion Aviation Services Beech C90A accident

20 Nov 2012 · Roanoke, VA, United States

Beech C90A · Accident: system/component malfunction/failure (non-power) on approach

From Richmond Executive-Chesterfield County Airport (FCI) to Virginia Tech Montgomery Executive Airport (BCB)

Report a problem

Event

NTSB case
ERA13LA065
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
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
Charter & commuter
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 C90A

Aircraft type
Beechcraft 90
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
N702DK
Onboard fatalities
Unknown
Route
From Richmond Executive-Chesterfield County Airport (FCI), Richmond, VATo Virginia Tech Montgomery Executive Airport (BCB), Blacksburg, VA
Aircraft age
About 22 years (built 1990)
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 135: Air Taxi & Commuter
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
Defining eventThe 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
System/component malfunction/failure (non-power)
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

  • Aircraft › Aircraft systems

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

NTSB narrative

During the downwind leg of the traffic pattern at the destination airport, the pilots lowered the landing gear. The pilot then noticed that the right main landing gear (MLG) was not down and locked in position for landing. The flight crew made multiple attempts to get a down-and-locked indication without success, so the pilot decided to abort the landing and divert to another airport with longer runways. After executing the manual gear extension checklist, the flight crew made a low pass at the diversion airport, and the air traffic controller in the control tower advised that the landing gear appeared to be in the down position. During the landing, the touchdown was normal, and the airplane slowed normally; however, as the airplane exited the runway, the right MLG collapsed. Examination of the wreckage revealed that the right wing, right nacelle, and right wheel well had received substantial damage and that the right MLG, after collapsing, had punctured the right nacelle fuel tank.

The right MLG bearing actuator support bracket was made of aluminum. Examination of the right MLG revealed that the right MLG bearing actuator support bracket was broken and had separated from its mounting position. Multiple cracks in the bracket were visible, and, at the microscopic level, the cracks had shiny surfaces indicative of abrasion, and overload regions with a cloudy appearance. Essentially, with each cycle, whether it was with extension of the landing gear, retraction of the landing gear, or landing itself, the cracks were subjected to loading which caused them to continue to propagate until the entire assembly reached a point at which structural integrity was no longer present to hold the landing gear actuator.

In December 2003, the airplane manufacturer issued a mandatory service bulletin to replace the right and left aluminum MLG bearing actuator support brackets with steel brackets and specified that the replacement of the brackets be accomplished "as soon as possible," but "no later than the next scheduled inspection, the next 200 flight hours or 24 months." The airplane manufacturer also requested that the Federal Aviation Administration (FAA) issue an Airworthiness Directive (AD) based on the service bulletin. However, the FAA did not find an "unsafe condition" and did not issue an AD, which would have made compliance with the service bulleting mandatory.

Review of the airplane's maintenance records confirmed that the airplane owner and the operator had not had the new steel brackets installed. Further, the FAA has not issued an AD for the MLG bearing actuator support brackets.

Probable cause

The failure of the right main landing gear bearing actuator support brackets. Contributing to the accident was the owner's and operator's failure to comply with the airplane manufacturer's mandatory service bulletin and the Federal Aviation Administration's failure to issue an airworthiness directive.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA13LA065
Event ID
20121121X33535
Case number
ERA13LA065
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 121b4c17a8ca03c5b33f8ae7c0c70ea2df256936e4410ec171b7737e0aec1b32; retrieved 2026-09-15T20:28:17.123Z.