Schuman Carriage Hughes 369 D accident
Hughes 369 D · Accident: flight control system malfunction/failure en route
From Daniel K. Inouye International Airport (HNL) to Daniel K. Inouye International Airport (HNL)
Event
- NTSB case
- WPR18LA221
- 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
- Charter & commuter
- 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
Hughes 369 D
- Aircraft type
- Hughes 369
- 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
- N369MH
- Operator
- Schuman Carriage
- Onboard fatalities
- Unknown
- Route
- From Daniel K. Inouye International Airport (HNL), Honolulu, HITo Daniel K. Inouye International Airport (HNL), Honolulu, HI
- Aircraft age
- About 40 years (built 1978)
- 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 135: Air Taxi & Commuter
- 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
- Flight control system malfunction/failure
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot of the helicopter commercial air tour flight stated that the helicopter was in cruise flight at an altitude of about 1,800 ft when, about 11 minutes after takeoff, he felt "severe" vibrations and then heard a "loud bang," after which the helicopter began to shake "violently." The pilot entered a power-on autorotation and stated that the severity of the vibration caused the transponder to shake free of its mount in the instrument panel. He also stated that even small tail rotor pedal inputs significantly worsened the vibrations. The pilot conducted a partial run-on landing in a field. Examination revealed that multiple tail rotor blade and gearbox components had failed in flight, rendering the helicopter substantially damaged.
The helicopter tail rotor (TR) transmission was mounted on the aft end of the tail boom, and the four-blade TR assembly mounted onto a four-arm fork that mounted on the output shaft of the TR transmission. The TR blade assembly comprised a pair of two-blade rotor assemblies that attached to the fork. A teeter bearing mounted in each fork arm, and each two-blade rotor assembly was secured in its fork arm pair by a teeter bolt that suspended it between, and was suspended by, the two teeter bearings.
At least two different tail boom versions were available for the accident model helicopter. One was the original McDonnell-Douglas Helicopters, Inc (MDHI) version, and the other was an aftermarket version produced by a company called Aerometals. The accident helicopter was equipped with the Aerometals tail boom. The primary difference between the two tail boom versions was the attachment method of the TR transmission to the tail boom. The MDHI version used studs and locking nuts, whereas the Aerometals version used bolts and locking nut plates. Both versions used a total of four attach fasteners.
Postaccident examination revealed that the two bolts that attached the left side of the TR transmission to the tail boom had fractured and partially pulled through their nut plates. The two right side attach bolts were damaged, but had not failed; instead, their respective mounting lugs on the TR transmission had failed. The failure of all four attachments meant that the TR assembly was retained on the helicopter by only the TR drive shaft and the pitch control linkage. Neither of those components was designed to retain the TR transmission, and the pitch control system incurred damage during the event. The TR assembly was on the verge of imminent failure. Based on the observed damage, it is likely that with continued operation, the TR would have very shortly separated from the helicopter, rendering control difficult or impossible.
All four TR blades remained attached to the fork, but the outer (furthest from the transmission) blade pair remained only partially attached to the fork. The outer teeter bolt was fractured and only a portion of it was recovered. Of the two teeter bearings that were normally mounted in the outer pair of fork arms, one was absent and presumed lost in flight. The remaining outer teeter bearing had debonded from its fork arm, and both it and its fork arm seat exhibited fretting damage on their mating surfaces. The fretting indicated that there was relative motion between the bearing and its seat, caused by helicopter operation with a debonded bearing.
Detailed laboratory examinations revealed that the fractured teeter bolt and the two fractured attach bolts had all failed in fatigue. The examinations also revealed several discrepancies with the repair and installation of some of the TR components, as well as some discrepancies within the applicable maintenance and inspection guidance.
The teeter bearings had been improperly installed in the fork during overhaul or during maintenance by the operator. Contrary to MDHI overhaul guidance, none of the four teeter bearing installations, including the two debonded ones for the outer blade pair, displayed any evidence of the presence of either primer or scrim cloth. "Scrim cloth" was a single-ply layer of glass fabric that should have been installed at the bearing-fork mating juncture to ensure proper bonding of the adhesive that secured the bearing in its fork seat.
An overhauled fork includes installed teeter bearings, and the maintenance records indicated that the accident fork was overhauled by an outside vendor. Information provided by the operator indicated that it had not replaced or reinstalled any of the bearings, and the available records did not specify the serial numbers of the bearings installed during the overhaul. However, contrary to the operator-provided information, research revealed that the operator had independently purchased at least five bearings subsequent to the installation of the overhauled fork, and that at least two of those bearings, including one that had disbonded from the fork, were installed on the helicopter at the time of the accident. The operator was unable to provide any explanation for the improper repair or why their installation of new teeter bearings was absent from the maintenance records. Subsequent to these findings, an FAA search of the operator's premises did not locate any additional overhauled TR assemblies.
Contrary to the MDHI TR transmission installation guidance, paint was observed on the faying surfaces of the transmission-tail boom mounting pads. The operator had partially cleaned these surfaces during postaccident removal of the transmission before the investigative examination took place; therefore, the thickness or condition of that paint, or a reliable estimate of its effect on the joint clamp-up, could not be determined. Reduction in joint clamp up, due to compression or breakdown of the paint in the joint, particularly over time, has the potential to result in shear failure of the attachment hardware threads and/or fatigue and failure of the attach hardware, by allowing relative motion between the TR transmission and the tail boom. This condition can be aggravated by increased vibrations due to multiple sources, including but not limited to TR imbalance, disbonded or deteriorated elastomeric bearings, and improper torque of the TR transmission attach hardware. When asked, the operator was unable to provide any explanation for the improper paint application.
The available evidence indicates that the failure sequence began with the disbonding of one or both of the improperly installed outer teeter bearings from their respective fork seats. This permitted increased vibration of the TR, which then caused the outer teeter bolt to rapidly fatigue and fracture. The fracture failure of the outer teeter bolt resulted in the in-flight liberation of one outer teeter bearing and a segment of the outer teeter bolt. This further increased the vibration level, which caused the failure of all four structural attach points that secured the TR transmission (including the TR) to the tail boom and resulted in the TR being retained on the helicopter only by the TR drive shaft and the pitch control linkage. Neither of those components was designed to retain the TR transmission, and likely would have failed rapidly with continued operation, resulting in loss of the TR. The pilot's decision to land as quickly as possible likely prevented the loss of the TR and subsequent loss of control of the helicopter.
Probable cause
The operator's improper installation of the tail rotor (TR) teeter bearings, which resulted in cascading in-flight failures of the TR components and attach hardware.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR18LA221
- Event ID
- 20180810X81812
- Case number
- WPR18LA221
- 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: 023c25ca48ac71638d15296bf6c2a8f24e874faddaaad9d81fb919e8c4011374; retrieved 2026-09-16T08:04:46.324Z.