ERA12FA563 · Aerospatiale AS 355F1
Analar Aerospatiale AS 355F1 · Accident: system/component malfunction/failure (non-power) en route
From Princeton Airport (39N) to Atlantic City International Airport (ACY)
Event
- NTSB case
- ERA12FA563
- 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
- 1 · 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
Aerospatiale AS 355F1
- Aircraft type
- Aerospatiale AS-355
- 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
- N58020
- Operator
- Analar
- Onboard fatalities
- Unknown
- Route
- From Princeton Airport (39N), Princeton, NJTo Atlantic City International Airport (ACY), Atlantic City, NJ
- 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 as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA12FA563
- Event ID
- 20120915X43730
- Case number
- ERA12FA563
- 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 local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 5813b32ff6892cacd40cf9616a2947e7522af782a8867b0f247bfefcd30b71c8; retrieved 2026-09-14T15:44:30.785Z.