FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR20LA224 · Hiller UH 12D

17 Jul 2020 · Mehama, OR, United States

Western Helicopter Service Hiller UH 12D · Accident: part(s) separation from aircraft while maneuvering

From Western Helicopter Services Airport (OR38) to an unrecorded destination

Report a problem

Event

NTSB case
WPR20LA224
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
1 · 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 UH 12D

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
N2297W
Onboard fatalities
Unknown
Route
From Western Helicopter Services Airport (OR38), Brooks, ORTo not recorded
Aircraft age
About 60 years (built 1960)
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
Defining eventThe 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
Part(s) separation from aircraft
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

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot was performing an aerial application flight. No radar information was available for the flight. The support truck operator reported that the helicopter departed from the truck and flew toward a field. Shortly after the helicopter departed, the truck operator heard the pilot report over the radio that he was “going down.” A witness reported that the engine noise changed pitch and became loud before impact. A postcrash fire ensued.

The helicopter struck several large trees and came to rest inverted at the base of a large tree. Postaccident examination of the engine revealed no anomalies that would have precluded normal operations. However, the tail rotor assembly was found fractured and separated from the tailboom with parts scattered in the initial part of the debris field. One tail rotor blade remained secured at the hub, and the other blade was fractured and separated.

The tension-torsion straps for that blade extended outward from the hub and were fractured and splayed. Metallurgical examination revealed that 10 of the 11 straps fractured from fatigue cracking followed by overstress. The fatigue cracking initiated at multiple locations along the bores in contact with the cylindrical plain bearing. Wear, in the form of smearing, gouging, spalling, and galling of the faying surfaces, led to the fatigue crack initiation. The fatigue cracks then propagated perpendicular to the area with the highest tensile stresses and at the thinnest locations along the bearing bore. No indications of corrosion were observed. Thus, the tail rotor blade separated during flight due to fatigue cracking and overstress.

According to the component replacement schedule, the tension-torsion strap bundles are to be replaced every 12,500 flight hours and were set to be removed in 1,383.3 flight hours from the time of the accident.

Probable cause

An in-flight separation of a tail rotor blade due to fatigue cracking and overstress, which resulted in a loss of directional control and subsequent ground impact.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR20LA224
Event ID
20200717X44819
Case number
WPR20LA224
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 42d4c36e3915af54388a52d636f5b5ba4e2455eab7cbe460515a8f3bd34391f5; retrieved 2026-09-15T07:17:18.463Z.