FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

AAR Airlift Bell 214 ST accident

16 Jan 2012 · Camp Bastion, Afghanistan

Bell 214 ST · Accident: loss of control in flight en route

From Camp Bastion to an unrecorded destination

Report a problem

Event

NTSB case
DCA12FA024
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
3 · 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
Charter & commuter
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

Bell 214 ST

Aircraft type
Bell 214
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
N5748M
Operator
AAR Airlift
Onboard fatalities
Unknown
Route
From Camp BastionTo not recorded
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 135: Air Taxi & Commuter
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
En route · climb to cruise
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
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft propeller/rotor

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

NTSB narrative

Witness accounts from the flight crew of the helicopter flying behind the accident helicopter indicated that, after both helicopters had climbed to an altitude between about 800 to 1,000 feet, the accident helicopter rolled sharply to the right and entered a steep, nose-down pitch, at which time the aft tailboom separated from the helicopter. The helicopter's nose-down pitch attitude continued until ground impact.

There was no evidence of abnormal engine operation at the time of the accident or a failure of the tail rotor system or a major airframe structural component before the in-flight breakup. The damage observed on the right collective lever arm, idler link, and collective sleeve bearing support assemblies were consistent with an overtravel of the collective sleeve, which resulted in a severe and sudden reduction in main rotor collective pitch. Also, the damage to the left and right sides of the idler link showed that the left and right collective lever arms were in their installed position at the time of the collective sleeve overtravel.

Bell Helicopter Textron's math model simulation of the Bell 214 helicopter's response to a sudden and severe reduction of main rotor collective pitch (resulting from a failure of the collective flight control system) showed that the helicopter would respond with a severe right roll and a simultaneous nose-down pitch attitude. The math model simulation also showed that a sudden and severe reduction of main rotor collective pitch would cause the main rotor hub to exceed its flapping angle and the main rotor blade tips to deflect downward and possibly contact the tailboom due to the reduced amount of clearance.

The results of the math model simulation were closely aligned with the witness accounts from the flight crew of the helicopter behind the accident helicopter and the damage observed on the helicopter wreckage. For example, the nose-down pitch and right roll observed in the math model simulation was similar to the reported pitch and roll of the accident helicopter when the accident sequence began. Also, the main rotor mast showed damage consistent with mast bumping that resulted when the main rotor hub significantly exceeded its flapping angle. Thus, the evidence showed that, when the accident helicopter's main rotor hub exceeded its flapping angle, the resulting loss of clearance between the main rotor system blades and the tailboom caused the main rotor blades to contact the tailboom. This contact was severe enough to cause the aft tailboom section to completely separate from the rest of the tailboom, leading to a loss of pitch control.

Probable cause

the overtravel of the collective sleeve, which led to a severe and sudden reduction in main rotor blade collective pitch, resulting in a loss of control of the helicopter. The reason for the collective sleeve overtravel could not be determined since much of the collective control system was consumed in the post crash fire.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DCA12FA024
Event ID
20120116X72519
Case number
DCA12FA024
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 UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
  • API snapshot SHA-256: 5e44830257f994435e41dbfba3aa0039395257cee2cdc0c8785d9e59aa7cbc51; retrieved 2026-09-13T22:07:38.137Z.