FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA19CA531 · Robinson R44 II

6 Sept 2019 · Nuiqsut, AK, United States Possible conflict

Pollux Aviation Robinson R44 II · Accident: propeller/jet/rotor blast or suction during landing

From Deadhorse Airport (PASC) to Deadhorse Airport (PASC)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
GAA19CA531
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

Robinson R44 II

Aircraft type
Robinson R44
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
N447PA
Onboard fatalities
Unknown
Route
From Deadhorse Airport (PASC), Deadhorse, AKTo Deadhorse Airport (PASC), Deadhorse, AK
Aircraft age
About 13 years (built 2006)
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 133: Rotorcraft Ext. Load
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
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
Propeller/jet/rotor blast or suction
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

  • Environmental issues › Physical environment
  • Personnel issues › Action/decision

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

NTSB narrative

The pilot reported that he landed the helicopter facing south and about 90 ft from where ground personnel were unhooking super sacks filled with gravel. When the skids touched down, the pilot reduced the collective and then saw an empty super sack about 15 ft away, which subsequently struck the main rotor toward the outboard portion of the blade. The super sack was ingested by the advancing side of the main rotor disk. The pilot rolled off the throttle and shut down the engine. The helicopter sustained substantial damage to the main rotor blades. The pilot reported that there were no preaccident mechanical failures or malfunctions with the helicopter that would have precluded normal operation.

Probable cause

The pilot's improper decision to land downwind from unsecured debris, which resulted in the helicopter’s main rotor disk ingesting foreign objects.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA19CA531
Event ID
20190909X84531
Case number
GAA19CA531
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. 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: baa0fd0cf8fc94276f2a83e3ba4b5c21410e905d647033ec988287b131ea2788; retrieved 2026-09-16T10:01:18.991Z.