FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR26LA083 · Robinson R44 II

19 Jan 2026 · Parkman, WY, United States

Native Range Capture Services Robinson R44 II and Native Range Capture Services Robinson R44 II · Accident: midair collision en route

Report a problem

Event

NTSB case
WPR26LA083
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
Event fatalities
Unknown
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

Aircraft 1 · 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
N996NR
Onboard fatalities
Unknown
Route
From Sheridan County Airport (SHR), Sheridan, WYTo Parkman, WY
Aircraft age
About 20 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 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
En route · cruise
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
Midair collision
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Aircraft 2 · 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
N74730
Onboard fatalities
Unknown
Route
From Sheridan County Airport (SHR), Sheridan, WYTo not recorded
Aircraft age
About 21 years (built 2005)
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
En route · cruise
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
Midair collision
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 systems
  • Environmental issues › Physical environment
  • Environmental issues › Task environment
  • Personnel issues › Psychological
  • 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

Two helicopters were conducting low-altitude wildlife capture operations in mountainous terrain when they collided mid-air. Both helicopters were substantially damaged; the pilots and passenger were uninjured. The pilots and passengers briefed their operational plan prior to departing. The first helicopter (N74730) was assigned to a northern sector and would perform operations starting on the north edge of that sector, working south. The second helicopter (N996NR) was assigned a sector bordering the southern boundary of the north sector and would begin its operations at the southernmost portion of its assigned sector, working north. The pilots each planned to meet at a fuel truck located near the common border of the two sectors. The operational area was in remote terrain that included hills, canyons, and ridges. The mission required the helicopters to operate close to/at ground level and included periodic landings. Approximately one hour after operations began, both helicopters arrived in the same area near the sector boundary, where they continued to independently conduct the low-altitude operations. The pilot of the second helicopter had just dropped off his passenger to complete a wildlife capture and had become airborne again. Both pilots reported they were airborne and descending slightly, when the pilot of the first helicopter saw the other helicopter converging head-on. The pilot of the first helicopter quickly applied full up collective control to attempt to climb above the flight path of the converging helicopter, and as they passed the helicopters collided. The collision resulted in substantial damage to the tail section of the first helicopter. The pilots stated they believed the accident could have been avoided with better radio communication. Additionally, the pilots reported that the terrain’s effect on radio transmissions and the operational workload prevented continuous and unreliable communication between the helicopters; therefore, they relied on see-and-avoid techniques to ensure safe separation. The pilots of both helicopters reported no mechanical malfunctions or anomalies that would have precluded normal operations.

Probable cause

The pilots’ failure to maintain separation while conducting air work in a common operational area. Contributing to the accident was the pilots’ divided attention associated with the mission activity and unreliable radio communications.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR26LA083
Event ID
20260120202315
Case number
WPR26LA083
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, cause areas. 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: f5d7deee76070e7f73c8696777abea5566238efe53ff30465d32f4f798aca472; retrieved 2026-09-13T18:51:45.914Z.