LAX94LA054 · Hiller UH-12E
R&B Helicopters Hiller UH-12E · Accident: airframe, component or system failure while maneuvering
Event
- NTSB case
- LAX94LA054
- 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
Hiller UH-12E
- Aircraft type
- Hiller UH-12
- 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
- N161HA
- Operator
- R and B Helicopters
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 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 137: Agricultural
- 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
- Maneuvering · aerial application
- 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
- Rotor system, main rotor blade drag brace › Corroded
- Rotor system, main rotor blade drag brace › Fatigue
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING A SWATH RUN TO APPLY A MIXTURE OF PESTICIDES, THE PILOT HEARD A LOUD 'POP'. THE HELICOPTER'S COLLECTIVE CONTROL BEGAN TO OSCILLATE AND THE AIRCRAFT EXPERIENCED A SEVERE VIBRATION. THE HELICOPTER ALSO BEGAN TO OSCILLATE AND THE PILOT SLOWED TO ABOUT 15 KNOTS AND ATTEMPTED TO LAND. A SPRAY BOOM ATTACHED TO THE HELICOPTER CONTACTED THE GROUND AND THE HELICOPTER ROLLED ON ITS LEFT SIDE. EXAMINATION REVEALED THE PRESENCE OF FRETTING CORROSION AND A FATIGUE FAILURE OF THE TENSION-TORSION BAR PIN, INTO WHICH THE MAIN ROTOR BLADE DRAG BRACE IS ATTACHED. A SECOND TENSION-TORSION PIN FROM A SISTER HELICOPTER WAS DISCOVERED TO ALSO HAVE CORROSION AND A FATIGUE CRACK. PINS FAILED AT 369.5 HOURS AND 489.4 HOURS RESPECTIVELY. THE RETIREMENT LIFE OF THE PIN IS 643 HOURS.
Probable cause
a fatigue failure of the torsion-tension bar pin due to fretting corrosion. A factor in this accident was an inadequate quality of material utilized in the manufacture of the pin.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX94LA054
- Event ID
- 20001211X13762
- Case number
- LAX94LA054
- 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: 251c99e1be63f7bfb3e2409325a82ce2d869cb50eac1702c7cd61dafb13d991f; retrieved 2026-09-21T22:45:27.803Z.