LAX99LA047 · Bell 47G2
Bell 47G2 · Accident: loss of control in flight en route
From KRAMER'S JCT, CA to HELENDALE, CA
Event
- NTSB case
- LAX99LA047
- 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 47G2
- Aircraft type
- Bell 47
- 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
- N9021R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From KRAMER'S JCT, CATo HELENDALE, 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
- En route · cruise
- 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
- Loss of control in flight
- 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 › Procedures/directives, not followed
- Pilot in command › Retreating blade stall, encountered
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot encountered retreating blade stall while flying at 100 mph. He reported that the helicopter began to shake and it felt like an 'out of balance feeling, like when the washing machine gets unbalanced.' The rotor rpm began to decay. When he reduced power and stabilized the airspeed to about 60 to 65 mph, the shaking stopped. The pilot stated that he was not able to maintain lift, so he entered an autorotation over the hilly terrain. The tail rotor blades impacted an embankment and the main rotor blades severed the tail boom. The pilot's manual for the Bell 47G2 indicates that the 'never-exceed speed' (Vne) for the helicopter is 100 mph. According to the FAA's Basic Helicopter Handbook, the recovery procedure for retreating blade stall is to reduce the collective pitch, increase rotor rpm, reduce forward airspeed, and minimize maneuvering.
Probable cause
The pilot's failure to follow proper procedures to recover from main rotor blade aerodynamic retreating blade stall.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX99LA047
- Event ID
- 20001211X11580
- Case number
- LAX99LA047
- 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 1998-12-12.
- API snapshot SHA-256: a1a9eaf53f217b293cf5120ec20e29283093199aac830e3d8f4d4dfa36bb133c; retrieved 2026-09-22T16:09:47.463Z.