FTW97LA157 · Beech BE-95
Beech BE-95 · Accident: airframe, component or system failure on approach
From Aero Valley Airport (52F) to San Antonio International Airport (SAT)
Event
- NTSB case
- FTW97LA157
- 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 BE-95
- Aircraft type
- Beechcraft BE-95
- 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
- N2702Y
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Aero Valley Airport (52F), Fort Worth, TXTo San Antonio International Airport (SAT)
- 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 · VFR pattern final
- 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
- Company maintenance personnel › Maintenance, replacement, improper
- Landing gear, gear locking mechanism › Locked
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During the final approach for the runway, the right main landing gear did not extend. The pilot initiated a go-around and performed the emergency procedure for gear extension; however, the right main gear still did not extend. During the subsequent emergency landing roll, the left main gear and the nose gear collapsed and the airplane departed the runway. A maintenance record entry stated that the right main landing gear uplock cable assembly, P/N 35-815109, was installed, connected, lubed, and safety wired, in February 1997 (tachometer time 531.0 hours, total airframe time 5,431.3 hours). The aircraft was then jacked and the gear swung to verify correct operation of [the] uplock cable and aircraft step and 'all [was] found to be operating normally.' Following the accident, examination of the airplane revealed that the uplock assembly mechanism was jammed. The bolt which secures the release lanyard to the uplock mechanism had been installed in reverse. The nut on the bolt was on the aft side of the uplock attach point which caused interference between the nut and a metal guide shelf on the airframe. The interference was sufficient to jam the uplock in the locked position.
Probable cause
The failure of the right main gear due to improper repair by the company maintenance personnel.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW97LA157
- Event ID
- 20001208X07708
- Case number
- FTW97LA157
- 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: 2825bd7da936ff225f98326c7a69e20298b6665c0f5f93ff8b5471d960ff36e5; retrieved 2026-09-22T20:00:11.783Z.