FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX00LA024 · Bell 206-L4

23 Oct 1999 · Santa Clarita, CA, United States

Bell 206-L4 · Accident: hard landing

From Van Nuys Airport (VNY) to an unrecorded destination

Report a problem

Event

NTSB case
LAX00LA024
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 206-L4

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
N36R
Operator
Unknown
Onboard fatalities
Unknown
Route
From Van Nuys Airport (VNY), Van Nuys, 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
Hard landing
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

  • Dual student › Throttle/power control, delayed
  • Pilot in command(cfi) › Supervision, inadequate

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

NTSB narrative

The pilot was practicing autorotations to a power-on recovery. When he attempted to recover the power, the engine did not respond as quickly as anticipated and the helicopter landed hard, hitting on the rear heels of both skids. The flight instructor said that when he saw the pilot was late adding power, he attempted to correct the situation but was unsuccessful. The surface of the dry riverbed was mostly soft sand. The left skid heel contacted a log that was embedded in the sand and the helicopter pitched forward onto the skid toes and rolled over onto its left side. Both the flight instructor and pilot reported that there were no problems with the engine during prior autorotations, and, it was running after the helicopter came to rest. The engine was run in a test cell and met all of the manufacturer's perimeters. No discrepancies were found with the control or fuel systems.

Probable cause

The pilot's delay in adding power during a power-on recovery from an autorotation, which resulted in a hard landing and rollover. The flight instructor's inadequate supervision of the flight was also causal.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX00LA024
Event ID
20001212X19997
Case number
LAX00LA024
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: a24110e661d217f980bea44c91217de196d6eab27a19502a5587518ce8535d70; retrieved 2026-09-22T13:49:01.688Z.