LAX00LA013 · Bell 206B
Bell 206B · Accident: hard landing on approach
From Van Nuys Airport (VNY) to Los Angeles International Airport (LAX)
Event
- NTSB case
- LAX00LA013
- 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
- N16889
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Van Nuys Airport (VNY), Van Nuys, CATo Los Angeles International Airport (LAX)
- 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
- 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
- Pilot in command › Collective, improper use of
- Pilot in command › Rotor RPM, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
**This report was modified on 2/23/2016. Please refer to the public docket for this accident for additional information.**
The pilot turned right toward the helipad and descended at a rate of about 1,300 feet per minute until he intercepted a standard approach profile "sight picture." He reported that as he increased collective pitch, the rotor rpm immediately drooped to 90 percent. The low rotor rpm horn and light came on and the pilot stated that he fully lowered the collective. The company primary pilot, seated in the rear of the helicopter, stated that no engine out or warning horn was activated. The pilot estimated that his altitude at that time was between 100 to 150 feet agl and his airspeed was about 60 knots. He declared an emergency to the air traffic control tower and turned left toward an open area between terminals 5 and 6. The pilot realized he might not have sufficient altitude to clear the terminal buildings, so he pulled collective pitch, which further decayed the rotor rpm but provided additional lift. The primary pilot shouted to the pilot, several times, "Lower the collective." As he descended to his intended landing point, a twin-engine turboprop airplane turned into the ramp area and he veered to the right to avoid it. He stated that he fully lowered the collective and realized that he'd have to perform a run-on landing with little or no flare. He pulled all remaining collective pitch before impacting the ground. The helicopter contacted the ground in a tail-low attitude, slid forward approximately 60 feet, and made a 180-degree turn. The right front chin bubble shattered on impact. Both landing gear skids were forced upward through the cabin. The helicopter came to rest on its belly. The pilot attempted to shut the engine off by rolling the throttle past the idle cutoff position but was not able to manipulate the throttle. He turned off the fuel shutoff valve, generators, and battery. The pilot stated that he had not experienced any problems with the helicopter prior to the accident. The engine was removed and run in a test cell. Due to a breakdown of the test cell, the engine run could not be completed. Immediately before the test cell failed, an uncommanded decrease in rpm was observed. The fuel
control unit and power turbine governor were removed and bench tested. The static bench testing of the fuel control unit and power turbine governor indicated that both components were slightly out of calibration. According to Rolls Royce, the irregularities noted on the power turbine governor were consistent with a high-time governor and/or impact or vibration damage. The governor had 246.5 hours remaining before the next overhaul. The Rolls Royce investigator reported that the discrepancies noted might result in a 2 percent increase or decrease of N2 rpm with a corresponding reduction or increase of the collective lever. He stated that the fuel control discrepancies were insignificant deviations. The engine was then transported to Scottsdale, Arizona, where a complete and normal run was accomplished. During the test run, several aggressive accelerations/decelerations were conducted with no discrepancies noted. The test included: initial idle; seal run in to maximum power; five power point checks; governor droop; and a final idle setting. The engine performance met all required specifications. A copy of the performance data is appended to this file. The power turbine governor was bench tested again by Allied Signal.
Probable cause
**This report was modified on 2/23/2016. Please refer to the public docket for this accident for additional information.**
The pilot-in-command's excessive rate of descent and improper use of the collective control, which resulted in a low rotor rpm condition.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX00LA013
- Event ID
- 20001212X19988
- Case number
- LAX00LA013
- 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: 638c03d58096c77005ac8f4849f5e8f169b02b85fd32633b90ad4fff0708ca97; retrieved 2026-09-21T10:48:50.759Z.