FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA10LA118 · Eurocopter AS 350 B2

18 Jan 2010 · New York, NY, United States

Liberty Helicopters Eurocopter AS 350 B2 · Accident: system/component malfunction/failure (non-power) en route

From Downtown Skyport Heliport (JRB) to West 30th Street Heliport (JRA)

Report a problem

Event

NTSB case
ERA10LA118
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 B2

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
N696BH
Onboard fatalities
Unknown
Route
From Downtown Skyport Heliport (JRB), New York, NYTo West 30th Street Heliport (JRA), New York, NY
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 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
En route · 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
System/component malfunction/failure (non-power)
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 propeller/rotor

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

NTSB narrative

Shortly after takeoff, the pilot of the helicopter reported feeling a vibration through the airframe including the anti-torque pedals and cyclic. With positive control of the helicopter, he safely landed at a nearby heliport. After touchdown, while shutting down and applying the rotor brake, he noted that the vibration increased dramatically as the rotor speed decreased to a stop. Upon a cursory inspection of the helicopter after shutdown, the pilot noticed that one pitch change link of one tail rotor blade was separated from its respective attach point at the blade, and the blade was out of its normally installed position. Further inspection revealed a hole in the right side of the tailboom and the tailcone was damaged consistent with the tail rotor blade contacting the tailboom. The securing hardware (consisting of the bolt, castellated nut, and cotter pin) of the separated pitch change link were not found. The opposite tail rotor blade pitch change link was found properly connected at both ends, with both ends secured by cotter pins. Inspection of the tail rotor assembly by the Safety Board’s Materials Laboratory revealed no evidence indicating that the missing bolt had fractured or was properly installed and secured with a cotter pin.

Several days before the accident a mechanic had inspected the tail rotor pitch change links of the helicopter for end play and he was advised by the company's Director of Maintenance that the bearing of the tail rotor pitch change spider assembly needed to be replaced. The mechanic stopped his inspection and the work to the tail rotor pitch change spider assembly was completed the next morning at which point the tail rotor assembly was installed. There was no record of a post-maintenance inspection of the replaced pitch change link assembly at the tail rotor blade attach point. Additionally, the operator at the time did not have a Required Inspection Items (RII) program on their Federal Aviation Administration Approved Aircraft Inspection Program, and if they had, it is likely that a RII inspection by a trained mechanic would have detected the missing cotter pin upon completion of the replacement maintenance performed on the pitch change link assembly. Following the accident, the operator implemented a Lockout/Tagout procedure to ensure its aircraft are not returned to service before the RII program is completed.

Probable cause

The failure of maintenance personnel to properly secure one tail rotor pitch change link to its respective tail rotor blade resulting in an in-flight separation of the link from the blade. Contributing to the accident was the lack of an adequate post-maintenance inspection procedure.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA10LA118
Event ID
20100118X13843
Case number
ERA10LA118
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: c5ca2231cfe8c47433dc67de5aad191e8b26fec4348af6f268cc0ae454b10821; retrieved 2026-09-15T13:37:56.702Z.