FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW04IA078 · Beech C90

19 Feb 2004 · Oklahoma City, OK, United States

National Flight Oversight Office/FAA Beech C90 · Incident: airframe, component or system failure during takeoff

From Wichita Dwight D. Eisenhower National Airport (ICT) to OKC Will Rogers World Airport (OKC)

Report a problem

Event

NTSB case
FTW04IA078
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
Incident
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
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 C90

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
N21
Onboard fatalities
Unknown
Route
From Wichita Dwight D. Eisenhower National Airport (ICT), Wichita, KSTo OKC Will Rogers World Airport (OKC), Oklahoma City, OK
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
Takeoff
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
Minor

Cause areas

  • Landing gear, normal retraction/extension assembly › Disengaged
  • Other maintenance personnel › Maintenance, installation, improper

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

NTSB narrative

The crew reported the landing gear would not completely retract after take off, and only the right main came up while the gear motor continued to run. The left main and nose gear did not retract. The landing gear handle was cycled to the down position and the gear motor stopped running, but the right main landing gear failed to extend. The landing gear handle was cycled again, and the right main still would not extend. The crew used the emergency checklist, but the emergency gear extension handle was very hard to move, then it seemed to not catch anything at all. The crew made an emergency landing with the right main gear retracted. During the recovery process, a bolt, which attached the clutch shaft and nose gear drive sprocket, was found laying in the belly of the airplane. Examination of aircraft and maintenance records revealed the airplane underwent a phase inspection about a month prior to the event that included the replacement of the landing gear retraction gear box and clutch. The records indicated that this item was removed and an overhauled unit was reinstalled in accordance with the manufacturer's maintenance manual. According to the maintenance technician that performed the work, he used the manufacturer's maintenance manual as a step-by-step guide, and "all parts, nuts, bolts, cotter pin, etc, were intact when the final inspection was completed. New cotter pins were used to safety these items." After installation, the assembly and operational checks were inspected by his lead mechanic and an inspector. The gear was cycled approximately 12-15 times, and the "cavity" was vacuumed before the final inspection and the floor panels reinstalled. At the time of the incident, the airplane had flown a total of 21.9 hours, which included a total of 35 landings, after the phase inspection was completed. Nine days prior to the emergency landing, another flight crew reported that they were unable to retract all three landing gear while executing a go-around procedure. An examination revealed that a mechanic had removed the center and right floor boards and visually inspected the landing gear limit switches and engagement of the emergency extension disconnect assembly. Inspection of the limit switches consisted of visually inspecting the mount bracket and security of the switches and wiring. The mechanic also made a visual inspection of the wiring to the gear motor and engagement of the emergency extension disconnect, and engaged and disengaged "J" hook several times and found it operated normally. The visible portion of the nose gear chain was also examined for general condition. The floorboard panels were reinstalled, and the gear were cycled three times in five minutes, followed by four more cycles. All functional tests were normal and the airplane was returned to service. At the time of this inspection, the airplane had flown 11 hours since the phase 4 inspection, which included 17 landings.

Probable cause

The failure of the right main landing gear to extend due to an improperly installed attachment bolt by other maintenance personnel.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW04IA078
Event ID
20040601X00704
Case number
FTW04IA078
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: 0da1bd35fa3083885713f12a439f3a421c82e5b6a37248494b79abedba383839; retrieved 2026-09-22T07:56:08.579Z.