FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN05LA056 · Hughes 369HS

3 Feb 2005 · Provo, UT, United States

Hughes 369HS · Accident: in flight collision with terrain/water during landing

From Park City, UT to Provo, UT

Report a problem

Event

NTSB case
DEN05LA056
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
Charter & commuter
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

Hughes 369HS

Aircraft type
Hughes 369
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
N9118F
Operator
Unknown
Onboard fatalities
Unknown
Route
From Park City, UTTo Provo, UT
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 135: Air Taxi & Commuter
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
Landing · flare/touchdown
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
In flight collision with terrain/water
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 › Altitude/clearance, not maintained
  • Pilot in command › In-flight planning/decision, improper

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

According to the pilot, while approximately 4 feet above the ground, he applied power for the landing and felt an "unusual" vibration in both tail rotor pedals and the helicopter's airframe. He stated that he increased the power and brought the helicopter up to a 10-foot hover to reposition approximately 20 feet away. While repositioning, the vibrations and noise became worse. As he attempted the second landing, he heard a "clanking" sound. He immediately lost all tail rotor authority. He decreased the power and executed an autorotation. The helicopter spun to the right approximately 200 degrees as it settled upright into a 1foot deep layer of snow. One of the passengers stated that they were landing on a down slope. As they approached the landing zone, he noticed the nose of the helicopter "elevate slightly" and then he felt something in the rear of the helicopter "hit" the snow. He said that the pilot lifted the helicopter up about 10 to 15 feet as it began to spin and then they touched down facing to the west. He stated that he noticed a mark in the snow where the pilot first attempted to land. The mark was approximately 30 feet away and was about 10 feet in length. He stated that he watched the pilot walk away from the helicopter, in the direction of the mark, and he watched him walk directly through the mark in the snow. A visual examination revealed a 3 inch by 4 inch tear on the aft right side of the fuselage, and that the tail rotor shaft was fractured. No tail rotor blade damage was noted. According to the Boeing representative, the tail rotor drive shaft had a "rotational/torsion fracture" near fuselage station 170.0, and exhibited a degree of "shaft wind-up" normally associated with a "sudden stoppage to the tail rotor system." According to a metallurgist who examined the fractured tail rotor drive shaft, the fractured surfaces exhibited "extensive torsional deformation on both sides of the aft fracture." The indicated direction of torsion, as viewed looking aft, was "as if the forward portion of the shaft rotated clockwise," relative to the aft portion of the shaft. This fracture was largely circumferential and was at a location where the exterior surface of the shaft contained mechanical rubbing and rotational contact damage. Several other areas of rotational damage were noted on the shaft surface between the forward and aft fractures. A detailed examination of the fracture surfaces in the shaft revealed clean fractures on a 45-degree slant plane, "typical of recent overstress fracture under tension or tearing loads." No evidence of preexisting fracture such as fatigue cracking was noted.

Probable cause

the pilot's improper in-flight planning and decision making, his failure to maintain terrain clearance, and the total failure of the tail rotor drive shaft as a result of the tail rotor strike.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN05LA056
Event ID
20050228X00238
Case number
DEN05LA056
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: c790fdfd66ff153c8e7985f82e4c27a614473c515148554a1b4f38db93f7ab53; retrieved 2026-09-18T15:06:55.806Z.