FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA10CA319 · Robinson Helicopter R22 BETA

19 Jun 2010 · West Palm Beach, FL, United States

Cloud 9 Helicopters Robinson Helicopter R22 BETA · Accident: dynamic rollover during landing

From North Palm Beach County General Aviation Airport (F45) to North Palm Beach County General Aviation Airport (F45)

Report a problem

Event

NTSB case
ERA10CA319
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
N7988H
Onboard fatalities
Unknown
Route
From North Palm Beach County General Aviation Airport (F45), West Palm Beach, FLTo North Palm Beach County General Aviation Airport (F45), West Palm Beach, FL
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
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
Dynamic rollover
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Personnel issues › Action/decision

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

NTSB narrative

The certificated flight instructor (CFI) stated that he was tasked with flying with the student the morning of the accident. He spoke with the student's regular CFI and was briefed on his progress and ability. The helicopter was taxied to a defined spot on the airport and he began teaching the student how to hover. Approximately 15 to 20 minutes into the flight, while still practicing hovering, the CFI felt the helicopter moving aft followed by a violent jolt. The helicopter rolled onto the left side and caught fire. A postaccident inspection of the helicopter revealed that the main rotor hub was fractured and the associated main rotor blade was in 2 pieces.

Probable cause

The CFI's failure to prevent ground contact during hover, which resulted in a dynamic rollover.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA10CA319
Event ID
20100621X51110
Case number
ERA10CA319
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: 0a9788bd0d126fff2ba7a194d75bd36f6678164e408bd12512dc6641d253cff7; retrieved 2026-09-15T14:28:46.109Z.