FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR11GA115 · McDonnell Douglas Heli Co 369FF

31 Jan 2011 · Marana, AZ, United States

Pima County Sheriff's Department McDonnell Douglas Heli Co 369FF · Accident: dragged wing/rotor/float/other during landing

From Tucson International Airport (TUS) to Marana, AZ

Report a problem

Event

NTSB case
WPR11GA115
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
Government
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

McDonnell Douglas Heli Co 369FF

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
N530RL
Onboard fatalities
Unknown
Route
From Tucson International Airport (TUS), Tucson, AZTo Marana, AZ
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
Public Aircraft
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
Dragged wing/rotor/float/other
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 propeller/rotor
  • 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 four-place, turbine-powered helicopter was being operated by the county sheriff's department in support of a county emergency communications system development and construction project. The accident flight was intended to enable technical personnel to conduct a site survey for the planned installation of a communications repeater tower near the top of a mountain. The sheriff's department pilot had satisfactorily completed training for and had demonstrated confined area, slope, and pinnacle landings. None of the three passengers were helicopter pilots, and no anti-torque pedals were installed at the front passenger's station. The mountain's remote location and its topography prevented postaccident availability of specific meteorological conditions at the time of the accident, but analysis of available data indicated that mostly overcast skies, intermittent rain, and a generally westerly wind at 10 to 15 knots were present. Those conditions were within the helicopter's and pilot's performance capabilities. The helicopter orbited the peak for general reconnoitering before the pilot attempted a landing. The pilot's selected landing zone was on a relatively level area of a pinnacle on the northeast side of the mountain, and the approach was from the southeast. The passengers reported that during the landing attempt, they felt a bump, and the helicopter rose a few feet, then the nose pitched down, and the helicopter began to spin to the right. The main rotor blades struck a rock outcrop, and the helicopter tumbled and slid about 120 feet down a shallow canyon on the northeast face of the peak before it was halted by rocks and scrub vegetation.

The wreckage was examined in situ, recovered, and examined in detail. All components were accounted for. All damage patterns were consistent with the helicopter's low-speed impact with terrain in the horizontal and vertical planes, and its subsequent tumble down the canyon. The engine successfully met specification power settings during an operational run in a test fixture. No evidence of any preexisting mechanical defect or malfunction was noted during the examination or testing of the airframe and engine. Main and tail rotor damage patterns and debris distribution were consistent with rotor strikes under power. The witness and passenger descriptions of the helicopter's motions are consistent with a tail rotor ground strike and a subsequent loss of directional control. Although no reliable ground scars indicative of a tail rotor strike were found, that was likely precluded by the rocky, hard surface of the landing zone.

Probable cause

An inadvertent tail rotor strike during an attempted pinnacle landing, which resulted in the pilot's loss of control of the helicopter. Inhospitable terrain/topography contributed to the severity of the accident.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR11GA115
Event ID
20110131X92536
Case number
WPR11GA115
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: edb5087acd398d906c9a8ca02b7c2b377978851a97fdb591a446dc9c4cb935ba; retrieved 2026-09-13T21:13:27.946Z.