ASN logo
ASN Wikibase Occurrence # 149159
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Type:Silhouette image of generic AS55 model; specific model in this crash may look slightly different
Aérospatiale AS 355F1 Ecureuil II
Owner/operator:Analar Corporation
Registration: N58020
MSN: 5227
Fatalities:Fatalities: 1 / Occupants: 1
Aircraft damage: Substantial
Location:Quakerbridge Mall, West Windsor, NJ -   United States of America
Phase: En route
Departure airport:Princeton, NJ (39N)
Destination airport:Atlantic City, NJ (ACY)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
During cruise flight, witnesses on the ground reported hearing a grinding or popping noise, which was followed by the separation of the yellow main rotor blade. Examination of the fore/aft servo revealed that the internal threads of the upper rod end fitting on the servo were severely worn. The lower threaded portion of the upper rod end was not found secured into the servo's upper end fitting and was not recovered. Additionally, the upper end fitting was packed with soil as the lower threaded portion of the upper rod end had separated from it prior to ground impact. A 100-hour maintenance inspection of the accident helicopter had been completed on the morning of the accident and a 600-hour inspection of the accident helicopter was completed about 3 months prior to the accident. Neither inspection detected the worn threads on the fore/aft servo upper end fitting. The fore/aft servo had been overhauled about 4 years prior to the accident. Additionally, the fore/aft servo was repaired 10 months prior to the accident and no anomalies were observed with the threads at that time.

The operator used Mastinox, a corrosion inhibiting compound, during installation of the upper rod ends to the right-roll, left-roll, and fore/aft servos. The helicopter manufacturer's maintenance manual listed only G.355 grease and did not prescribe for the use of Mastinox. However, the standard practices manual stated that a torque correction factor of 0.4 is used for G.355 grease, but not for Mastinox, since the latter is not a lubricant. The torque value listed in the manual for the rod ends already took a torque correction factor into account. A higher torque value would theoretically have been necessary when Mastinox was used in place of G.355 grease. The operator stated an adjusted torque value was not used during installation of the upper rod ends using Mastinox. Evidence of sealant at the junction of the upper rod end and nut, which was required to be applied during servo installation per the maintenance procedures, was not found on either the right-roll or left-roll servos. While the lack of sealant may not result in a catastrophic event, its breakage or absence (and/or radial play of a servo end bearing) noted during a maintenance inspection could be indicative of a loss of torque.

Review of the helicopter manufacturer's checklists and maintenance manuals revealed some guidance for servo inspections. The daily operating check (after the last flight of the day) included an instruction to check the main rotor servos for security and absence of leaks. The 600-hour inspection called for checking the radial play of the end bearings; however, there were no instructions to specifically check the threads of the servo end fitting or the torque of the rod end nut.
Probable Cause: Disconnection of the upper rod end from the fore/aft servo due to severely worn threads, which resulted in a loss of control and separation of a main rotor blade during cruise flight. Contributing to the accident were incorrect maintenance procedures and inadequate maintenance inspections performed by the operator, and insufficient inspection criteria provided by the helicopter manufacturer.


Accident investigation:
Investigating agency: NTSB
Status: Investigation completed
Download report: Final report


Revision history:

15-Sep-2012 14:16 Alpine Flight Added
15-Sep-2012 15:12 RobertMB Updated [Aircraft type]
16-Sep-2012 00:12 bob375 Updated [Narrative]
16-Sep-2012 21:59 gwog Updated [Operator, Location, Departure airport, Destination airport, Narrative]
17-Sep-2012 08:03 RobertMB Updated [Aircraft type, Registration, Cn, Operator, Location, Source]
17-Sep-2012 11:18 mhab Updated [Aircraft type]
21-Sep-2012 07:14 harro Updated [Aircraft type, Registration, Cn, Operator, Source, Narrative]
23-May-2016 19:31 Aerossurance Updated [Aircraft type, Operator, Location, Nature, Departure airport, Destination airport, Source, Narrative]
23-May-2016 19:31 Aerossurance Updated [Aircraft type]
22-Sep-2016 16:43 Aerossurance Updated [Source]
21-Dec-2016 19:28 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
28-Nov-2017 13:23 ASN Update Bot Updated [Other fatalities, Nature, Departure airport, Destination airport, Source, Narrative]
15-Sep-2021 07:40 Aerossurance Updated [Nature, Source, Embed code]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2022 Flight Safety Foundation

701 N. Fairfax St., Ste. 250
Alexandria, Virginia 22314