ATL02LA044 · Hiller UH12E
Hiller UH12E · Accident: rotor failure/malfunction while maneuvering
From Miami, FL to an unrecorded destination
Event
- NTSB case
- ATL02LA044
- 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
- Unknown
- 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
- N103HA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Miami, FLTo 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
- Rotor failure/malfunction
- 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 hub › Fatigue
- Rotor system, main rotor hub › Fractured
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
A Hiller UH-12E collided with the ground during a forced landing. According to the pilot, while executing aerial applications at 15 to 20 feet AGL, he heard a bang and the helicopter began shaking and yawing. The pilot realized he was losing altitude and attempted to slow the descent by using the collective. The helicopter impacted the ground, and caught fire. The pilot exited the helicopter through a hole in the bubble. Examination of the main rotor hub pieces revealed that the fracture at the hub had progressed through the inboard pin hole for the torsion/tension plate set. Six fracture faces were noted in the examination corresponding with the pin hole. Two fracture faces showed discoloration with a distinctive banding pattern and smoothly curved crack arrest marks consistent with fatigue propagation. Examination of the remaining two fractures revealed no evidence of fatigue cracking, but did show some corrosion on the exposed portion of the pin.
Probable cause
Fatigue cracking in the main rotor hub that resulted in the separation of the main rotor system. A factor was corrosive deposits on the exposed portion of the plate set pin.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL02LA044
- Event ID
- 20020219X00228
- Case number
- ATL02LA044
- 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, coordinates. 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: d8e178ba060afc12fe3f88c940a6fd2a115f9e18182cce07a4a0f4ee03c5759e; retrieved 2026-09-21T19:46:53.928Z.