FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW02LA172 · Beech BE-100-A100

4 Jun 2002 · Little Rock, AR, United States

Beech BE-100-A100 · Accident: airframe, component or system failure on approach

From Bill & Hillary Clinton National Airport/Adams Field (LIT) to Bill & Hillary Clinton National Airport/Adams Field (LIT)

Report a problem

Event

NTSB case
FTW02LA172
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
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 BE-100-A100

Aircraft type
Beechcraft BE-100
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
N799DD
Operator
Unknown
Onboard fatalities
Unknown
Route
From Bill & Hillary Clinton National Airport/Adams Field (LIT), Little Rock, ARTo Bill & Hillary Clinton National Airport/Adams Field (LIT), Little Rock, AR
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

  • Miscellaneous, bolt/nut/fastener/clamp/spring › Missing
  • Other maintenance personnel › Maintenance, 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 pilot was on a practice approach when he extended the landing gear. The cockpit gear indicators yielded "two" green indications. A go-around was performed and the gear cycled several times with no results, including an attempt to use the emergency extension system. Two confirmation passes were performed, and it was confirmed that the left main landing gear was retracted with the nose and right main landing gear extended. After touch down on the right side of the runway, the aircraft exited the left side of the runway. Examination of the aircraft revealed that left gear extension push/pull tube was found without the lock pin in its clevis. The pin was found in the belly of the aircraft but no nut and washer was found. The aircraft had recently come out of a maintenance facility where the landing gear was worked on.

Probable cause

The malfunction of the left main landing gear retraction/extension assembly due to a missing lock pin/washer/nut on the clevis of the push/pull gear extension tube that resulted from improper maintenance.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW02LA172
Event ID
20020607X00828
Case number
FTW02LA172
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2002-06-05.
  • API snapshot SHA-256: d7cd0b4af801d4ff093c0dc3d6b0cc4c19630c6482c9d80390d5b82845e31a05; retrieved 2026-09-22T10:52:41.934Z.