- Date
- September 11, 2019, 13:00 local (20:00 UTC)
- Place
- Azusa, CA
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Enroute
- Aircraft
- N1168USikorsky S58
- Defining event
- Enroute: Part(s) separation from AC
- Weather
- Visual (VMC) · Day
- Status
- Completed
- Report
- Approved by Office Director
- Investigation class
- Class 3
- NTSB office
- Western Pacific Region
- Parties
- RAL FSDO
- FAA report
- 20190911012989A
- Case key
- 100235
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
Probable cause
The in-flight separation of a section of the tail rotor blade due to a fatigue crack, which resulted in the pilot’s forced autorotation into a field.
Findings · 1
NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.
Sequence of events
The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.
Analysis
The pilot was conducting a ferry flight. During cruise flight while at an altitude of about 1,000 ft above ground level and at an airspeed of about 110 knots, one of the helicopter’s tail rotor blades separated, which resulted in a partial separation of the remaining tail rotor assembly and a forced autorotation. The remaining tail rotor assembly subsequently impacted the vertical stabilizer. The mechanic who performed the daily inspection of the helicopter before the accident flight did not observe any evidence of a crack on the tail rotor blades. The separated section of the tail rotor blade was not recovered. Postaccident fractographic examination of the tail rotor blade piece containing the root end revealed that most of the blade had cracked due to fatigue. No nicks, gouges, damage, or contamination were observed. Further examination revealed that the blade met the design specifications of the engineer drawings. Maintenance records revealed that the rotor blade was most recently repaired in April 2007, but details of the repair work were not available.
Factual narrative
A review of the maintenance records revealed that, on April 20, 2007, the blade that had separated from the tail rotor assembly was repaired. According to documents, details of the repairs were on file at the repair station that performed the work. The maintenance records also indicated that the paint on the blade was removed and that the blade was refinished and static balanced. After completion of the work, the blade was deemed to be in an airworthy condition. The company that performed the last repair stated that it retained no documents related to the work performed on the blade and could provide no additional information. The tail rotor blade was installed on the accident helicopter on May 13, 2013, when the helicopter had accumulated a total time of 18,897 hours. The blade had a total time of 885 hours and an “on condition” retirement life and was in compliance with all applicable airworthiness directives and service bulletins. According to the mechanic who performed the daily inspection of the helicopter on the morning of the accident flight, he wiped down the tail rotor blades and saw no working metal, cracks in the paint, or evidence of a crack. On September 11, 2019, about 1300 Pacific daylight time, a Sikorsky S-58ET helicopter, N1168U, was substantially damaged when it was involved in an accident near Azusa, California. The pilot was not injured. The helicopter was operated as a Title 14 Code of Federal Regulations Part 91 ferry flight. The pilot reported that he was ferrying the helicopter from Shafter Airport-Minter Field (MIT), Shafter, California, to Corona Municipal Airport (AJO), Corona, California. During cruise flight, when the helicopter was about 1,000 ft above ground level and at an airspeed of about 110 knots, the pilot “heard and felt a loud bang without the onset of noise or vibration.” Subsequently, the helicopter began to yaw to the right, and the pilot conducted an immediate autorotation and landed the helicopter in a baseball field. A postflight inspection revealed that one tail rotor blade had separated from the tail rotor assembly and that the remaining three tail rotor blades, which remained attached to the tail rotor assembly, exhibited dents and chordwise bends, The 90° gearbox had fractured, exposing the internal gears, and the vertical stabilizer was impact damaged. (See figure 1.) Figure 1. Left-side view of the tail rotor assembly, 90° degree gear box, and the vertical stabilizer (Source: Pilot). The separated section of the tail rotor blade was not recovered. The shank and the other three blades of the tail rotor assembly were shipped to the National Transportation Safety Board’s Materials Laboratory for examination. Fractographic examination of the shank revealed the blade had separated perpendicularly to the blade length along a chord plane located about 3 inches from the bottom of the blade. (See figure 2.) Figure 2. Side view of tail rotor blade shank. Examination of the tail rotor shank revealed athumbnail-shaped pattern emanating from one side of the blade that was consistent with fatigue that had propagated through about three-quarters of the blade. No nicks, gouges, damage, or contamination were observed at the fatigue origin. Further examination of the tail rotor blade shank and the other three tail rotor blades revealed that they met the design specifications identified in the engineering drawings.
Aircraft
- Registration
- N1168U
- Reported as
- Sikorsky S58 (ET)
- Category
- Helicopter
- Serial number
- 58-1070
- Built
- 1959
- Airframe hours
- 19,929
- Engines
- Pratt & Whitney PT6T-6, 970 horsepower, turbo shaftPratt & Whitney PT6T-6, 970 horsepower, turbo shaft
- Damage
- Substantial damage
- Flight
- Ferry · Part 91
- Airworthiness certificate
- Standard, Normal
- Last inspection
- Continuous airworthiness · August 1, 2019
- Departed
- MIT · Shafter, CA
- Destination
- AJO · Corona, CA
- Flight plan
- Company VFR
- Equipment
- Satellite tracking device, Handheld GPS
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 49
- Injuries
- None
- Certificate
- Commercial
- Airplane ratings
- Single-engine land, Multi-engine land
- Instrument ratings
- Airplane
- Medical
- Class 2, Without waivers/limitations
- Last flight review
- May 6, 2019
- Seat
- Right
- Restraint
- 4-point
- Flight hours
- 9,819 total · 1,022 in this make and model · 9,700 as pilot in command · 43 in the last 90 days · 22 in the last 30 days · 4 in the last 24 hours
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 260° at 5 knots
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 75 °F, dew point 55 °F
- Altimeter
- 30.00 inHg
- Observed at
- KPOC, 7 nm away
Docket · 7
The files NTSB released with the investigation on May 25, 2022, on NTSB’s docket system: statements, records, photos and specialists’ reports. 12.7 MB in all.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.
Other investigations on N1168U · 1
Matched to the same aircraft by N-number and date.