FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA10CA255 · Hughes 500 E

6 May 2010 · West Palm Beach, FL, United States

County of Gwinnett Georgia Hughes 500 E · Accident: hard landing during autorotation

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

Report a problem

Event

NTSB case
ERA10CA255
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

Hughes 500 E

Aircraft type
Hughes 500
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
N5189K
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
Autorotation
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
Hard landing
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 › Task performance

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

NTSB narrative

The certificated commercial helicopter pilot reported that he was practicing autorotations with a certificated flight instructor (CFI). The CFI stated that the first autorotation "went well," and ended with a "nice cushioned landing." During the second autorotation, the commercial pilot flared 100 feet above the ground and applied cyclic control to cushion the landing. The helicopter "settled abruptly," impacted the taxiway firmly, and bounced. A main rotor blade struck and partially severed the tail boom. No preaccident mechanical anomalies were noted with the helicopter.

Probable cause

The commercial pilot's improper flare during a simulated autorotation, which resulted in a hard landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA10CA255
Event ID
20100507X51119
Case number
ERA10CA255
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: ead2971e018af313ed388d9e3b9e18f14c7558db66a291cade9c78ebda5f26ea; retrieved 2026-09-15T14:01:04.730Z.