FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA19CA110 · Robinson R44 II

3 Jan 2019 · Grace, ID, United States

Robinson R44 II · Accident: low altitude operation/event while maneuvering

From Grace, ID to Grace, ID

Report a problem

Event

NTSB case
GAA19CA110
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
N4246Z
Operator
Unknown
Onboard fatalities
Unknown
Route
From Grace, IDTo Grace, ID
Aircraft age
About 10 years (built 2009)
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
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
Low altitude operation/event
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Wire
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

  • Personnel issues › Psychological

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

NTSB narrative

The helicopter pilot reported that, shortly after liftoff to the north from his property, he saw coyote tracks and "wanted to inspect." To better observe the coyote, he maneuvered at a low altitude, which led him to cross over a power line. After crossing the power line for a third time, he spotted the coyote, turned left, diverted his attention from the power line, continued to turn left, and the main rotor blades struck the power line. He maintained control of the helicopter and landed without further incident.

The helicopter sustained substantial damage to the main rotor blades.

The pilot reported that there were no preimpact mechanical failures or malfunctions with the helicopter that would have precluded normal operation.

Probable cause

The pilot's failure to maintain clearance from the power lines.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA19CA110
Event ID
20190125X54539
Case number
GAA19CA110
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: e62b8864c306432218ded8ea3c205fd3517ecafa8e4f0777d4eba50ac590822e; retrieved 2026-09-16T08:33:38.213Z.