FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN14CA367 · American Eurocopter Corp AS350B3

15 Jul 2014 · Grand Praire, TX, United States

Airbus Helicopters American Eurocopter Corp AS350B3 · Accident: hard landing during autorotation

From Grand Prairie Municipal Airport (KGPM) to Grand Prairie Municipal Airport (KGPM)

Report a problem

Event

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

American Eurocopter Corp AS350B3

Aircraft type
Eurocopter AS350
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
N350GP
Onboard fatalities
Unknown
Route
From Grand Prairie Municipal Airport (KGPM), Grand Praire, TXTo Grand Prairie Municipal Airport (KGPM), Grand Praire, TX
Aircraft age
About 2 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

  • Personnel issues › Psychological

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The flight was scheduled as recurrent training in helicopters; the foreign rated pilot was accompanied by a flight instructor, and an interpreter and observer who were seated in the back seats. After a series of maneuvers, the foreign pilot conducted a hovering autorotation, following directions from the flight instructor which were translated by the interpreter. During the autorotation, the helicopter yawed slightly right and settled to the ground. The instructor and observer noted that the landing did not feel that hard, but more like a firm or rough landing. The training flight continued with several other autorotations. During a post flight inspection of the helicopter, several wrinkles were found in the tail boom of the helicopter. Further examination of the helicopter revealed that the tail boom had sustained substantial damage.

Probable cause

The flight instructor's inadequate supervision during a practice autorotation. Contributing to the accident was the pilot's hard landing during a practice autorotation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN14CA367
Event ID
20140716X61901
Case number
CEN14CA367
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, coordinates. 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: 7bf8d7ad7e28f93841e7d34ed99ec3fb0fb2089db0d5a00ee8eee01abe3db3ea; retrieved 2026-09-16T00:54:43.967Z.