29 Apr 2016: PIPER PA28 200

29 Apr 2016: PIPER PA28 200 (N200KR) — Unknown operator

No fatalities • San Carlos, CA, United States

Probable cause

The failure of maintenance personnel to properly install and secure the input swivel boot on the swivel joint, which resulted in excessive vibration that led to fatigue cracks and failure of the throttle cable.

— NTSB Determination

Accident narrative

On April 29, 2016, about 1535 Pacific daylight time, a Piper PA-28-200, N200KR, completed a precautionary landing at the San Carlos Airport (SQL), San Carlos, California following a power control failure. The certified flight instructor (CFI) and the pilot receiving instruction were not injured, and the airplane was not damaged. Visual meteorological conditions prevailed for the instructional flight, which was being conducted in accordance with 14 Code of Federal Regulations Part 91, and a flight plan was not filed. According to the CFI, the intended destination was Byron, California.In a telephone interview with the National Transportation Safety Board (NTSB) investigator-in-charge, the CFI reported that he attempted to reduce power during the initial climb following departure from runway 30 at SQL, but he was only able to make a slight reduction in power. After he determined that no further power reduction was possible, the pilot then flew a right-hand traffic pattern back to runway 30, and on final approach over the runway threshold he fully retarded the mixture control to stop the engine. After landing, the airplane completed its landing roll with sufficient momentum to exit the runway at an intersecting taxiway. A subsequent inspection of the throttle control revealed that the cable had broken. The cable was subsequently recovered by a Federal Aviation Administration aviation safety inspector for further examination by the NTSB.

The throttle cable was sent to the National Transportation Safety Board's Materials Laboratory in Washington, D.C., for examination and analysis. Subsequent to the examination, a Senior NTSB Materials Engineer reported the following:

The cable was fractured near the input end. Damage to the conduit revealed two areas of wear contact. The smallest wear contact was located in the lower area and had a flat wear pattern, which corresponded to contact with a smooth surface. The larger of the two areas had a ridged pattern, which indicated that the area made contact with another cable. Individual cable wires were fractured at locations within approximately one-half of a lay length. Portions of the fracture surface on each of the outer wires had relatively smooth fracture features oriented perpendicular to the outer surface with curving boundaries, which are features consistent with fatigue. The fatigue origin for each individual wire was located at the same side relative to the overall cable, and the fatigue region extended across approximately half the diameter in each wire. The core wire fracture features appeared rubbed.

The wall of the sleeve was deformed into an oblong shape. Additionally, the overall features of the swivel joint were consistent with bending deformation. A curving deformation mark was observed on one side of the swivel tube, which corresponded to contact with the wall of the sleeve under bending loads on the joint. The axis of the conduit was angled (bent) relative to the axis of the sleeve. Adjacent to the sleeve, the blue outer sheath of the conduit was depressed inward at the outside of the bend. The depression in the outer sheath of the conduit was also visible in a radiograph of the part. Another radiograph of the conduit and sleeve revealed that the sleeve was crimped onto the conduit, and that the inner diameter of the coil and the spacing between coils varied along the length of the sleeve.

As assembled, an elastomeric boot covers the swivel joints at each end of the cable assembly. As received, the boot at the input end swivel joint was displaced onto the swivel tube. In comparison, the boot at the output end was received covering the joint, and a hose clamp was in place on the boot. No hose clamp was observed at the input end. During the examination, the hose clamp was removed from the boot at the output end swivel joint, and the boot was displaced onto the output swivel tube. The portion of the boot that covered the swivel joint was flared outward relative to the other end of the boot, and an impression was observed where the hose clamp had been installed. More than two months after the hose clamp was removed, the hose-clamp impression remained visible on the surface, and a slight flare was present at the end that had been covering the swivel joint. In comparison, the boot for the input swivel joint had a uniform outer diameter with no evidence of a flared end or hose clamp impression. Additionally, the input swivel tube had a date stamp 6 days after the accident, which revealed similar features for the boot with no evidence of a hose-clamp impression or flared end. According to the cable manufacturer, the swivel joint boot is an important component to prevent contamination and dampen vibration loads on the cable assembly.

Contributing factors

  • cause Not installed/available
  • cause Fatigue/wear/corrosion
  • cause Maintenance personnel

Conditions

Weather
VMC, wind 280/16kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.