FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR13LA025 · Robinson Helicopter Company R22 MARINER

27 Oct 2012 · Lake Havasu, AZ, United States

N2627M Robinson Helicopter Company R22 MARINER · Accident: settling with power/vortex ring state while maneuvering

From Lake Havasu City Airport (HII) to Lake Havasu City Airport (HII)

Report a problem

Event

NTSB case
WPR13LA025
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 Helicopter Company R22 MARINER

Aircraft type
Robinson R22
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
N2627M
Operator
N2627M
Onboard fatalities
Unknown
Route
From Lake Havasu City Airport (HII), Lake Havasu, AZTo Lake Havasu City Airport (HII), Lake Havasu, AZ
Aircraft age
About 24 years (built 1988)
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 · low-altitude flying
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
Settling with power/vortex ring state
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
  • Personnel issues › Task performance

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

NTSB narrative

Both the pilot and copilot of the helicopter were employed by and operating for a company that photographed boats in motion. The typical procedure was to fly low and slow on a path parallel to, and in the same direction as, the target boat; pass the boat; make a climbing 180-degree course reversal turn around the bow of the boat; and then descend and proceed to the next boat. During their second flight of the day, while nearing the completion of the course reversal turn to the right after a photo pass, the pilot initiated the descent for the next photo pass. The pilot added power and collective pitch to arrest the descent; however, he was unable to do so before the helicopter impacted the water. Although the tail boom was not recovered, no evidence of any preimpact failures with the helicopter was observed in the recovered wreckage.

The course reversal turn was made from north to south, and the wind at an airport 17 miles to the northwest was out of the north at 15 knots. The pilot reported that the wind was about 12 knots gusting to 17 knots and that "clear air turbulence" was present. Although the exact wind conditions at the accident site were not known, evidence indicated that the helicopter experienced an overall wind change from a 12- to 15-knot headwind to a similar magnitude tailwind during the course reversal turn. Given the low speed of the photo pass, it is likely that the pilot did not correctly compensate for the wind speed and direction change during the course reversal and that the helicopter entered a vortex ring state (settling with power) due to the combination of low forward speed and the tailwind. The pilot's perception of, or attention to, the airspeed could have been adversely affected by his extra-cockpit focus on locating and tracking target boats.

The pilot's attempt to arrest the descent by adding power and collective pitch was not the proper technique for recovery from the vortex ring state, but no evidence suggests that the pilot even recognized the onset of that condition. However, even if he did recognize its onset, the helicopter's altitude was likely too low to safely exit the vortex ring state because proper recovery from that state requires increasing the airspeed and/or lowering the collective pitch, which respectively either requires or results in a temporarily increased descent. Further, it is likely that the pilot was operating in a region of the height-velocity chart such that an autorotation would not have been successful.

Probable cause

The pilot’s unintentional and unrecognized entry into a vortex ring state as a result of conducting a course reversal turn into a tailwind while at a low altitude and airspeed, which resulted in an uncontrolled descent into water.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR13LA025
Event ID
20121027X02310
Case number
WPR13LA025
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: bdc41b7d141c7993e21567fabedcdb1f4a83aa83ea0b18799f22f86bc1610db9; retrieved 2026-09-15T20:17:39.965Z.