FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA09CA401 · Robinson Helicopter R22 BETA

13 Jul 2009 · Bedford, MA, United States

East Coast Aero Club Robinson Helicopter R22 BETA · Accident: loss of control in flight while maneuvering

From Laurence G Hanscom Field (BED) to Laurence G Hanscom Field (BED)

Report a problem

Event

NTSB case
ERA09CA401
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 R22 BETA

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
N211SH
Onboard fatalities
Unknown
Route
From Laurence G Hanscom Field (BED), Bedford, MATo Laurence G Hanscom Field (BED), Bedford, MA
Aircraft age
Not recorded
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 · hover
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
Loss of control in flight
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 as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

According to the certificated flight instructor, he was performing hover practice with the student pilot in a grassy area beside a taxiway. During the practice, the helicopter climbed to approximately 20 feet above ground level, and then the instructor advised the student to position the helicopter at a lower altitude. The instructor stated that the helicopter began “a high rate of descent which [he] was unable to arrest prior to ground contact.” He also said that the helicopter developed a “dynamic rolling moment that full down collective was unable to stop.” The helicopter rolled and came to rest on its left side, substantially damaging the tail boom, skids, and main rotor. The winds reported at the airport about the time of the accident were from 250 degrees at 13 knots gusting to 17 knots. The pilot did not report any mechanical anomalies with the helicopter.

Probable cause

The flight instructor's inadequate remedial action while conducting hover practice with a student pilot, which resulted in the helicopter rolling over when it contacted the ground.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA09CA401
Event ID
20090713X62731
Case number
ERA09CA401
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: 4d8b7258aeef0a227683ea3ad850df15c324265cb73122576e29be4354f17e72; retrieved 2026-09-15T11:50:10.172Z.