FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX00TA318 · Bell 206L-1

29 Aug 2000 · Los Angeles, CA, United States

Bell 206L-1 · Accident: airframe, component or system failure during initial climb

From an unrecorded airport to Long Beach International Airport (LGB)

Report a problem

Event

NTSB case
LAX00TA318
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

Bell 206L-1

Aircraft type
Bell 206
Category
Helicopter
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
N5758H
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo Long Beach International Airport (LGB), Long Beach, CA
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
Initial climb
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

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Estimated position: the centre of Los Angeles, CA, the place the record names. Not the accident site.

NTSB narrative

During takeoff from a heliport atop a 10-story parking structure, the pilot heard a 'loud pop or snapping sound' as the helicopter transitioned to forward flight and then sensed a main rotor imbalance and vibration. The pilot returned to the heliport and landed on the skids, however, the helicopter subsequently rolled over and came to rest on its left side. Subsequent examination of the helicopter showed the skid cross tubes were displaced approximately 2 inches to the right in their fuselage attachment bushings and the main rotor transmission was inclined approximately 20 degrees to the right and 10 degrees forward. Examination and testing of the hydraulic pump, three flight control servos and two hydraulic filters revealed no anomalies. The tip of one main rotor blade and part of one pitch change link were not located after the accident. The mating end of the pitch change link exhibited bending along its length and crippling at the separation point consistent with overload failure.

Probable cause

The probable loss of the main rotor tip weight on the red blade for undetermined reasons resulting in main rotor vibration and oscillation. Sideward movement during the ensuing emergency landing resulted in a dynamic rollover.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX00TA318
Event ID
20001212X21792
Case number
LAX00TA318
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: a3b5ab23e4455b2e3b982c21f9833cae462441c1f6c628a7ed9cbbde8522f511; retrieved 2026-09-21T20:05:59.771Z.