Robinson Helicopter R22 BETA accident near Palo Alto, California, March 15, 2012
On March 15, 2012 at about 11:45 pm local time, a Robinson Helicopter R22 BETA, registered N290SH, was substantially damaged in an accident during approach (VFR pattern downwind) near Palo Alto, California (Palo Alto Airport). It was an instructional flight under general aviation rules (Part 91). 1 person had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's improper use of the throttle grip, which resulted in the deactivation of the rpm governor and a loss of rotor rpm.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- March 15, 2012 · about 11:45 pm local time · cases in 2012
- Place
- Palo Alto, California · Palo Alto Airport · cases near this airport · map
- Type
- Accident
- Injuries
- 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Robinson Helicopter R22 BETA · all R22 BETAs on the register
- Registration
- N290SH · registry record · serial 4186
- Damage
- Substantial damage
- Flight
- Instructional flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
During a solo instructional flight, the pilot reported that while on the downwind leg of the traffic pattern, just before turning to the base leg, the helicopter sustained a loss of rotor rpm. The pilot reported that he entered an autorotation and that the throttle was unresponsive. After landing in a marsh area, the helicopter rolled over. A postaccident examination of the helicopter and a successful engine run revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. The pilot's flight instructor related that the pilot had a documented history of inadvertently gripping the throttle on the collective which, while manipulating the collective, would result in overriding the governor and a low rotor condition.
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
- Loss of control in flight during approach (VFR pattern downwind) defining event
- Autorotation Off-field or emergency landing
- Roll over during landing (flare/touchdown)
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Prop/rotor parameters › Not attained/maintained
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
Pilot
- Certificate: flight instructor, commercial pilot
- Ratings: single-engine land; instructor: airplane single-engine; instrument: airplane; rotorcraft: glider
- Flight time: 750 hours in all; 46 in this make and model; 24 in the last 90 days; 7 in the last 30 days; 631 as pilot in command; 42 on instruments
- Last flight review: January 12, 2012
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: rgt
- Injury: minor injuries
The aircraft
- Airframe total time: 2,051 hours
- Last inspection: 100-hour inspection, February 10, 2012; 63 hours since
- Maximum gross weight: 1,370 lb
- Seats: 2
- Landing gear: fixed
- Engine: Lycoming O-360-J2A (piston); 0 hours total
- Operator: Sirius Flying LLC
The flight
- Departed from: PAO Palo Alto CA at 11:40 pm
- Destination: PAO Palo Alto CA
- Flight plan: none
- Runway 31, 2,443 ft by 70 ft
Weather at the time
- Light: daylight
- Wind: from 270° at 10 knots
- Visibility: 13 statute miles
- Sky: broken clouds at 2,500 ft
- Temperature: 63°F (17°C), dew point 55°F (13°C)
- Altimeter: 30.10 inHg
- Observation at 11:47 pm from PAO
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
7 documents, released by the NTSB on November 7, 2013. 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 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1- Operator | PDF, 10 pages | View Download |
| 2 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1- Pilot | PDF, 11 pages | View Download |
| 3 | Statement of Cfi- Pyle | PDF, 1 page | View Download |
| 4 | Examination Report | PDF, 5 pages | View Download |
| 5 | FAA Interview of Pilot | PDF, 1 page | View Download |
| 6 | Statement of Party Representatives to NTSB Investigation | PDF, 14 pages | View Download |
| 7 | Release of Aircraft Wreckage, NTSB Form 6120.15 | 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.
Connections how this case links to the rest of the register
- N290SH on the register today · the tail number may have moved to another aircraft since
- Robinson R22 817 registered today · the model family and its accident history
- Engine: Lycoming O-360-J2A 254 aircraft carry this series today · as the NTSB recorded it
- Palo Alto Airport · nearest airport
- Accidents and incidents in California 9,080 since 1982 · 1,094 in the last ten years
- California 28,286 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/WPR12LA140.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
