FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX99FA272 · Beech BH 125-600A BH 125-600

17 Aug 1999 · Las Vegas, NV, United States

Beech BH 125-600A BH 125-600 · Accident: airframe, component or system failure during takeoff

From Salina Municipal Airport (SLN) to Harry Reid International Airport (LAS)

Report a problem

Event

NTSB case
LAX99FA272
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 BH 125-600A BH 125-600

Aircraft type
Beechcraft BH-125
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
N454DP
Operator
Unknown
Onboard fatalities
Unknown
Route
From Salina Municipal Airport (SLN), Salina, KSTo Harry Reid International Airport (LAS)
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
Substantial

Cause areas

  • Hydraulic system, seal › Burst
  • Landing gear, emergency extension assembly › Disabled
  • Landing gear, normal retraction/extension assembly › Disabled
  • Landing gear, tire › Burst
  • Miscellaneous, bolt/nut/fastener/clamp/spring › Fractured

Approximate · Estimated position: the centre of Las Vegas, NV, the place the record names. Not the accident site.

NTSB narrative

The pilot landed with the landing gear in the retracted position, when both the main and auxiliary hydraulic systems failed to extend the gear. The airplane caught fire as it skidded down the runway. The left inboard main tire had blown on takeoff and a 30-inch section of tread was loose. Black marks were along the length of the landing gear strut and up into the wheel well directly above the left inboard wheel. The normal and emergency hydraulic systems both connect to a common valve body on the landing gear actuator. This valve body also had black marks on it. A gap of 0.035 inch was measured between the valve body and actuator. When either the normal or auxiliary hydraulic system was pressurized, red fluid leaked from this gap. Examination revealed that one of two bolts holding the hydraulic control valve in place had fractured and separated. The fractured bolt experienced a shear load that was oriented along the longitudinal axis of the actuator in a plane consistent with impact forces from the flapping tire tread section.. Separation of only one bolt allowed the control valve to twist about the remaining bolt in response to the load along the actuator's longitudinal axis. This led to a loss of clamping force on that side of the actuator. Hydraulic line pressure lifted the control valve, which resulted in rupture of an o-ring that sealed the hydraulic fluid passage. 14 CFR 25.739 describes the requirement for protection of equipment in wheel wheels from the effects of tire debris. The revision of this regulation in effect at the time the airplane's type design was approved by the FAA requires that equipment and systems essential to safe operation of the airplane that is located in wheel wells must be protected by shields or other means from the damaging effects of a loose tire tread, unless it is shown that a loose tire tread cannot cause damage. Examination of the airplane and the FAA approved production drawings disclosed that no shields were installed to protect the hydraulic system components in the wheel well.

Probable cause

the complete failure of all hydraulic systems due to the effects of a main gear tire disintegration on takeoff. Also causal was the manufacturer's inadequate design of the wheel wells, which did not comply with applicable certification regulations, and the FAA's failure to ensure that the airplane's design complied with standards mandated in certification regulations.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX99FA272
Event ID
20001212X19549
Case number
LAX99FA272
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. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1999-08-18.
  • API snapshot SHA-256: f54c1ded2047dc6f76a76f7309bd7fc5b4b585cd567b53bbded75b9abe1b4394; retrieved 2026-09-22T14:16:29.512Z.