Sikorsky S-58JT N126GW accident near Middletown, Delaware

Aug 1, 2012 · NTSB number ERA12LA493 · Final report

Probable cause

The pilot's failure to recognize that the helicopter was experiencing tail rotor dynamic instability and to take immediate corrective actions during an external load lift, which resulted in the failure of a tail rotor blade.

NTSB analysis

The pilot had flown two uneventful external load lifts to place 2,900-lb air conditioning units on a warehouse roof. The pilot reported that, during the third lift, he felt vibration in the pedals that became violent, and the helicopter then began to rotate about its vertical axis. The air conditioning unit touched down on the roof as the helicopter was spinning. The pilot could not stop the helicopter's rotation, so he released the cable attached to the air conditioning unit and then maneuvered the helicopter away from the warehouse. He then increased forward speed, turned right to line up with a street, and conducted a roll-on landing.

Examination of the helicopter revealed that the entire aft portion of one of the four tail rotor blades had separated just aft of the blade's spar where a bond line existed. Examination of the tail rotor blade revealed high-stress progressive crack growth features at the root end of the fracture, buckling deformation adjacent to the fracture, and bending deformation of the leading edge, all of which were consistent with the tail rotor blade fracturing due to dynamic instability in the tail rotor. The progressive crack growth features observed on the fracture surface were associated with relatively high stress and few cycles and likely occurred after the deformation associated with the buckling. In addition, all four tail rotor blades exhibited bending deformation, indicating that they all experienced loads that exceeded the allowable design loads, and the deformation pattern was consistent with an external input on the tail rotor assembly overloading all of the blades rather than a failure in the blade causing it to become unstable. The helicopter manufacturer confirmed that such damage can be caused by dynamic tail rotor instability and that such instability can be accompanied by tail rotor vibration, as was experienced during the accident flight.

Although dynamic tail rotor instability rarely occurs, it has been known to occur on the accident helicopter make and model. To improve tail rotor stability, the helicopter manufacturer had introduced two modifications to the tail rotor system, and both of these modifications had been installed on the accident helicopter. Even with the modifications, dynamic tail instability can occur, and high values of left pedal, improper tail rotor cable tension (too high or too low), bottoming of the tail rotor control system spring, higher rotor speed, or relative wind from the right forward quadrant could increase susceptibility. However, a review of the helicopter's maintenance records did not reveal that any of the mechanical factors that could contribute to tail rotor instability existed, and wind was calm at the time of the accident. Additionally, after the damaged components were replaced, the helicopter was returned to service. The helicopter's flight manual also contained guidance stressing that pilots should immediately decrease the tail rotor pitch after encountering pedal vibration. If the pilot had recognized that the pedal vibration was indicative of tail rotor instability and immediately taken the proper corrective actions in accordance with this guidance, the accident might have been prevented.

Text from the NTSB. Open the NTSB docket for ERA12LA493 for the full record.

Event

Date
Aug 1, 2012
Type
Accident
Place
Middletown, Delaware
Nearest airport
Parking Lot (None)
Highest injury
None
Weather
Visual (VMC)
Light
Day

Sikorsky S-58JT

N-number
N126GW
Category
Helicopter
Year built
1959
Damage
Substantial
Operating rule
Part 133 (external load)
Purpose of flight
External load

From the NTSB aviation accident database: N-registered aircraft, events since 2008, data through Oct 28, 2026. The file is published monthly, so the latest weeks are incomplete and recent records can change. The official source is the NTSB aviation investigation search. CheckAero is independent and not affiliated with the NTSB.