FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN23LA389 · McDonnell Douglas Heli Co 530FF

31 Aug 2023 · Liberty Hill, TX, United States

McDonnell Douglas Heli Co 530FF · Accident: hard landing during autorotation

From Georgetown Executive Airport at Johnny Gantt Field (KGTU) to an unrecorded destination

Report a problem

Event

NTSB case
CEN23LA389
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
Event fatalities
Unknown
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

McDonnell Douglas Heli Co 530FF

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
N530JR
Operator
Unknown
Onboard fatalities
Unknown
Route
From Georgetown Executive Airport at Johnny Gantt Field (KGTU), Georgetown, TXTo not recorded
Aircraft age
About 11 years (built 2012)
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

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

NTSB narrative

During an instructional flight, the instructor reported that they were practicing simulated engine failures and power recovery autorotations. During the fourth practice autorotation, the pilot receiving instruction attempted to terminate the maneuver with power to a 5 ft above ground level hover. The pilot did not move the twistgrip throttle from idle power back to full open and began raising the collective. The helicopter “fell through” and experienced a hard landing onto a field. The helicopter bounced, touched down hard again and spun about 150° resulting in substantial damage to the tail boom and empennage. The instructor reported that there were no mechanical malfunctions or failures that contributed to the accident.

Probable cause

The pilot’s improper recovery from a practice autorotation resulting in a hard landing. Contributing to the accident was the instructor’s inadequate supervision of the pilot receiving instruction.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN23LA389
Event ID
20230831192972
Case number
CEN23LA389
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: 3634d122156dfd557b1fc351ac5b324ae2fdf6bbd1950b7a79b51ed32af76a71; retrieved 2026-09-16T18:04:06.224Z.