FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX96LA346 · Bell 206B

30 Sept 1996 · Fillmore, CA, United States

Bell 206B · Accident: roll over during landing

From Whiteman Airport (WHP) to an unrecorded destination

Report a problem

Event

NTSB case
LAX96LA346
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 206B

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
N59576
Operator
Unknown
Onboard fatalities
Unknown
Route
From Whiteman Airport (WHP), Los Angeles, CATo not recorded
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
Landing · flare/touchdown
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
Roll over
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

  • Pilot in command(cfi) › Dynamic rollover, inadvertent
  • Pilot in command(cfi) › Remedial action, delayed
  • Pilot in command(cfi) › Supervision, inadequate

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

According to the flight instructor (CFI), he and the student pilot were on an instructional flight, and the student was performing hovering autorotations to a clear, moist, sandy area of a river bed. The CFI reported that the student began an autorotation from a 3-foot hover when, about 1 foot above the ground, the helicopter began to drift to the left. The CFI took the controls and applied right cyclic as the rotor rpm continued to decay. His control input did not stop the helicopter's accelerating leftward movement. As the left skid touched down on sandy terrain, the helicopter experienced a dynamic rollover and rolled onto its left side. The wind at the accident site was estimated to be westerly at about 10 knots.

Probable cause

the flight instructor's inadequate supervision and delay in taking remedial action to stop the aircraft's lateral movement, which resulted in a dynamic rollover after touchdown.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX96LA346
Event ID
20001208X06782
Case number
LAX96LA346
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: d5fb5eef5e330500da70bf024079928e7ee7474b2ae585df0087a3dd338a19ca; retrieved 2026-09-22T21:01:55.901Z.