WPR13LA178 · MD Helicopter 369A
MD Helicopter 369A · Accident: hard landing
From Darby, MT (no airport) to Darby, MT (no airport)
Event
- NTSB case
- WPR13LA178
- 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
MD Helicopter 369A
- Aircraft type
- MD Helicopters 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
- N369HW
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Darby, MT (no airport)To Darby, MT (no airport)
- Aircraft age
- About 43 years (built 1970)
- 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 91: General Aviation
- 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
- 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
- Hard landing
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
- Personnel issues › Task performance
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 reported that he purchased the turbine-powered helicopter about 5 weeks before the accident and departed from his private airstrip for a brief local personal flight. During the approach for landing, when the helicopter was about 200 to 300 ft above ground level (agl), he added some power, and the engine responded normally. Shortly thereafter, he conducted a height-velocity check with satisfactory results. The pilot then slowed the helicopter to a descending hover with the engine running at an unspecified speed above flight idle. The pilot stated that, when the helicopter was about 10 ft agl, he increased the throttle setting, but the engine did not respond. He added collective to slow the descent, but the helicopter landed hard.
Postaccident on-scene examination and system testing did not reveal evidence of any mechanical anomalies that would have resulted in a loss of engine power. The engine was tested in its as-removed condition and satisfactorily met all operational test and power calibration criteria with no anomalies or deficiencies noted. Review of the helicopter manufacturer's operating manual revealed that, during all phases of normal flight, the throttle should be in the full open (normal) position and should not be moved by the pilot. With the throttle in the full open position, a governor automatically increases and decreases engine power to maintain rotor rpm as the pilot raises and lowers the collective. According to the manufacturer, when the throttle is not in the full open position, the governor will not maintain rotor rpm, and full power will not be available. The pilot's statement that he increased the throttle setting about 10 feet agl indicates that he was manipulating the throttle contrary to the operating manual procedures, and this is likely the reason he was unsuccessful in stopping the helicopter's descent.
Probable cause
The pilot's failure to arrest the landing descent due to his incorrect use of the throttle, which resulted in a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR13LA178
- Event ID
- 20130403X95057
- Case number
- WPR13LA178
- 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: 14bb5cc902d4e6ffddc76e8ecaac34efe1d9519b2745ae43b125c85625f2aaca; retrieved 2026-09-15T21:12:37.217Z.