Atherton Aviation Robinson R44 - II accident
Robinson R44 - II · Accident: collision during takeoff/landing
From Scottsdale Airport (SDL) to Flagstaff, AZ
Event
- NTSB case
- WPR13CA424
- 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
- Charter & commuter
- 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
- N190SH
- Operator
- Atherton Aviation
- Onboard fatalities
- Unknown
- Route
- From Scottsdale Airport (SDL), Scottsdale, AZTo Flagstaff, AZ
- Aircraft age
- About 6 years (built 2007)
- 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 135: Air Taxi & Commuter
- 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
- Collision during takeoff/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
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
The pilot reported that he was landing the helicopter in a bowl-shaped meadow surrounded by mountains and trees. While circling the landing zone to determine the surface wind and descending, about 20 feet above ground level, the helicopter encountered a wind gust. The low rotor horn sounded and the pilot regained rpm, but another wind gust from behind again resulted in a loss of rotor rpm. The pilot said he was too low to recover, so he performed a run-on landing. The helicopter struck an earthen berm and rolled onto its left side, which resulted in substantial damage to the fuselage and tail boom. The elevation at the accident site was 8,411 feet; the density altitude was calculated to have been 10,059 feet. The pilot reported no preimpact mechanical malfunctions or failures with the helicopter that would have precluded normal operation.
Probable cause
The pilot's failure to maintain rotor rpm while landing in a gusty wind at a high density altitude.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR13CA424
- Event ID
- 20130925X93321
- Case number
- WPR13CA424
- 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: 11c4e15f2b1b1d421eb53e52dc0b3e8e3d53ff6bb30de3db8edb2d601242c08b; retrieved 2026-09-15T22:54:36.483Z.