ERA24LA215 · Hughes 369 D
Vertol Systems Hughes 369 D · Accident: hard landing during autorotation
Event
- NTSB case
- ERA24LA215
- 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
- 0
- 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 369 D
- Aircraft type
- Hughes 369
- 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
- N969VS
- Operator
- Vertol Systems
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 44 years (built 1980)
- 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
On the day of the accident, the pilot had been practicing autorotations. The first was a power-on autorotation to the ground, followed by two hovering autorotations, all of which were uneventful. The pilot then briefed and set up for a power off autorotation to the ground. The entry began at 600 ft above ground level (agl) and the glide was normal. He set up a 70-knot glide speed and added collective to keep the rotor at 480 rpm. The helicopter was heavy with fuel and the added pilot-rated passenger, so the decent was faster than anticipated. The pilot reported that at 40 ft agl, he accomplished an “auto-rotative flare attitude” and that the “flare was not aggressive enough for the weight,” and as a result, he held the flare longer than usual. The ground speed bled off, but the leveling of the helicopter was not accomplished in a timely manner. The tail skid contacted the ground hard and the main rotor blades flexed down resulting in contact with the tail boom and the fuselage behind the rotor head. The helicopter’s tailboom and main rotor blades were substantially damaged. The pilot reported that there were no pre-accident mechanic malfunctions or failures with the helicopter that would have precluded normal operation.
Probable cause
The pilot’s improper flare, which resulted in a hard landing and the main rotor blades contacting the tail boom.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA24LA215
- Event ID
- 20240510194239
- Case number
- ERA24LA215
- 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, cause areas. 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: 5ad31f5d73a4eb73ec8de87a8632816139ff0cf05316111689a30a2aa0be2794; retrieved 2026-09-16T18:45:16.543Z.