FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN13FA331 · Eurocopter AS 350 B3

7 Jun 2013 · Grand Prairie, TX, United States

CFS Air Eurocopter AS 350 B3 · Accident: loss of control in flight during landing

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

Report a problem

Event

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

Eurocopter AS 350 B3

Aircraft type
Eurocopter AS-350
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
N106LN
Operator
CFS Air
Onboard fatalities
Unknown
Route
From Grand Prairie Municipal Airport (GPM), Grand Prairie, TXTo Grand Prairie Municipal Airport (GPM), Grand Prairie, TX
Aircraft age
About 14 years (built 1999)
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
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
Loss of control in flight
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 › Action/decision
  • Personnel issues › Psychological
  • Personnel issues › Task performance

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

NTSB narrative

The instructor pilot reported that he and the pilot receiving instruction departed on a local night instructional flight to perform a simulated hydraulics failure maneuver in the helicopter. On shallow approach to the runway with hydraulic power off, the instructor told the pilot to fly the helicopter to a designated point on the airfield, at which point, the pilot was to perform a go-around. As the helicopter was "getting a little slow," the instructor again mentioned to the pilot that he needed to go around. As the pilot increased power, the helicopter's nose started rising, and the instructor told the pilot to get the nose down to increase the airspeed. The pilot remarked that it was hard to apply right pedal, so the instructor also manipulated the controls to assist him. At this point, the helicopter had started to turn left, and the instructor applied forward cyclic. The helicopter pitched nose down, and the instructor thought he might have overcompensated. The instructor felt the pilot applying aft cyclic, and the helicopter again pitched nose down, so he made an additional control input to level the helicopter. However, the helicopter started spinning left, developed extreme pitch attitude changes, and was not climbing. The instructor again attempted to level the helicopter, reduced the power to slow the rotation, and reapplied power to cushion the landing. The helicopter subsequently impacted terrain and rolled onto its right side.

Flight control continuity was established, and all observed separations were consistent with overload. No evidence of any preexisting failures of the helicopter's airframe or engine were found that would have precluded operational control of the helicopter. The recorded vehicle monitor data were consistent with impact and rollover occurrences, and no preimpact failures or overlimit events were recorded.

The flight manual notes that the hydraulic failure safety speed is from 40 to 60 knots and contains a caution to not attempt hover flight or any low-speed maneuver without hydraulic pressure assistance. The caution noted that the intensity and direction of the control feedback forces will change rapidly, which will result in excessive pilot workload, poor aircraft control, and possible loss of control. It is likely that the pilot receiving instruction failed to maintain adequate airspeed during the simulated hydraulics failure maneuver, which resulted in his loss of control of the helicopter and its subsequent impact with terrain.

Probable cause

The pilot receiving instruction's failure to maintain adequate airspeed during a simulated hydraulics failure training maneuver, which resulted in his loss of control of the helicopter and its subsequent impact with terrain, and the flight instructor's delayed and inadequate remedial action.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN13FA331
Event ID
20130610X20528
Case number
CEN13FA331
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2013-06-08.
  • API snapshot SHA-256: 9e5b7a70d03a2503b4ec9960a20630b7438a059b63b3c9eb183e892d41efee4d; retrieved 2026-09-15T21:48:33.671Z.