LAX86FVM05 · Hiller UH12E
Hiller UH12E · Accident: airframe, component or system failure en route
From Castroville, CA to Salinas, CA
Event
- NTSB case
- LAX86FVM05
- 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 UH12E
- Aircraft type
- Hiller UH12
- 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
- N5374V
- Operator
- Douglas E. Walker · private individual
- Onboard fatalities
- Unknown
- Route
- From Castroville, CATo Salinas, 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 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
- 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
- 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
- Destroyed
Cause areas
- Landing gear, main gear strut › Failure, total
- Rotor system, tail rotor blade › Failure, total
- Rotor system, tail rotor blade › Overload
- Rotor system, tail rotor blade › Separation
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT LANDED HARD AND ROLLED OVER AFTER THE LNDG SKID FAILED IN A FORCED LNDG. THE PLT SAID HE WAS CRUSING AT 500 FT AGL OVER AN OPEN FIELD WHEN HE HEARD A LOUD BANG. THE HELICOPTER BEGAN TO VIBRATE SEVERELY AND SPIRAL TO THE RIGHT. THE PLT LOST GROUND REFERENCE IN THE PRE-DAWN DARKNESS WHEN HE TURNED ON THE LIGHTS. NOT WANTING TO LAND TOO HARD HE ELECTED TO LEAVE THE ENG RUNNING AND NOT AUTO-ROTATE. INVESTIGATION INDICATED THAT ONE TAIL ROTOR BLADE HAD SEPARATED AT THE TENSION TORSION STRAP ATTACH BOLT HOLE. THIS IS THE TRANSITION AREA WHERE THE BLADE ROOT CASTING AND SHEET METAL BLADE SKIN ARE JOINED. THE FRACTURE SURFACE OF THE CASTING APPEARED TO BE OVERLOADED WITH NO APPARENT INDICATION OF FATIGUE. THE OUTBOARD BLADE SECTION SHOWED NO INDICATION OF FOREIGN OBJECT CONTACT. ALL COMPONENTS OF THE HELICOPTER WERE LOCATED IN THE IMPACT AREA EXCEPT ONE TAIL ROTOR BLADE.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX86FVM05
- Event ID
- 20001213X33299
- Case number
- LAX86FVM05
- 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: 47c02f77720a300ef22f8384d9ca5f539634692d9093573ba1c044d27e7fd066; retrieved 2026-09-22T01:28:09.909Z.