Robinson Helicopter R22 accident near Long Beach, California, September 20, 2017
On September 20, 2017 at about 8:09 pm local time, a 2002 Robinson Helicopter R22, registered N7514S, was substantially damaged in an accident during landing (flare/touchdown) near Long Beach, California (Long Beach /Daugherty Field/). It was an instructional flight under general aviation rules (Part 91). 1 person was seriously injured. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The student pilot's failure to maintain rotor rpm during the crosswind landing approach and his subsequent improper decision to initiate an autorotation instead of applying corrective control inputs after the helicopter experienced normal airframe vibration. Also causal was his failure to raise the collective during the landing flare, which resulted in a hard landing.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- September 20, 2017 · about 8:09 pm local time
- Place
- Long Beach, California · Long Beach /Daugherty Field/ · map
- Type
- Accident
- Injuries
- 1 person was seriously injured.
- Weather
- visual conditions (good weather)
- Aircraft
- Robinson Helicopter R22 BETA, built 2002 · all R22s on the register
- Registration
- N7514S · no longer on the register · serial 3333
- Damage
- Substantial damage
- Flight
- Instructional flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
During the final phase of a crosswind landing approach, the solo student pilot felt the helicopter shudder and heard the low rotor rpm horn sound. Instead of applying corrective control inputs, he immediately initiated an autorotation. He did not raise the collective control during the flare, as required, and the helicopter then landed hard and rolled over. Postaccident examination did not reveal any preimpact anomalies with the airframe or engine that would have precluded normal operation, and the engine appeared to be operating at the time of ground impact. Airframe vibration during the final phase of a landing approach is not an unusual phenomenon, and a low rotor rpm warning under high-load conditions (such as when landing with a crosswind) can also occur if rotor speed and engine power are not properly managed. The pilot improperly decided to initiate an autorotation instead of applying corrective control inputs to address the vibrations and improperly performed the landing flare.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Miscellaneous/other during landing (flare/touchdown)
- Autorotation Attempted remediation/recovery
- Autorotation Hard landing defining event
- Roll over during landing (landing roll)
The NTSB's findings
- cause Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot
- cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
- cause Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Prop/rotor parameters › Not attained/maintained
- Environmental issues › Conditions/weather/phenomena › Wind › Crosswind › Effect on operation
Dual student
- Certificate: student
- Ratings: instrument: helicopter
- Flight time: 45 hours in all; 45 in this make and model; 43 as pilot in command
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: rgt
- Injury: serious injuries
The aircraft
- Airframe total time: 1,390.7 hours
- Last inspection: condition inspection, August 25, 2017; 20 hours since
- Maximum gross weight: 1,369 lb
- Landing gear: fixed
- Engine: Lycoming O-360 J2A (piston); 1,370 hours total
- Operator: Revolution Aviation
The flight
- Departed from: LGB Long Beach CA at 8:05 pm
- Destination: LGB Long Beach CA
- Flight plan: none
- Runway H3, 300 ft by 35 ft
Weather at the time
- Light: daylight
- Wind: from 170° at 9 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 73°F (23°C), dew point 63°F (17°C)
- Altimeter: 29.88 inHg
- Observation at 8:19 pm from KLGB, 1 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
9 documents, released by the NTSB on October 22, 2018. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Interview Summary - Student Pilot | PDF, 1 page | View Download |
| 2 | Statement - Flight Instructor | PDF, 2 pages | View Download |
| 3 | Airframe and Engine Examination Report | PDF, 9 pages | View Download |
| 4 | Governor Examination Report | PDF, 3 pages | View Download |
| 5 | Maintenance Records Excerpts | PDF, 3 pages | View Download |
| 6 | Pilot's Operating Handbook Excerpts | PDF, 4 pages | View Download |
| 7 | Statement of Party Representatives to NTSB Investigation | PDF, 1 page | View Download |
| 8 | Release of Aircraft Wreckage, NTSB Form 6120.15 | PDF, 1 page | View Download |
| 9 | Evidence Control Form | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.