- Date
- November 30, 1995, 07:28 local (14:28 UTC)
- Place
- Salt Lake City, UT
- Injuries
- 1 uninjured
- Damage
- No damage
- Phase of flight
- Enroute
- Aircraft
- N134PMBeech 99
- Weather
- Visual (VMC) · Day
- Status
- Completed · report October 4, 1996
- Report
- Approved by Office Director
- FAA report
- 19951130044179I
- Case key
- 29296
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the incident.
On this page
Probable cause
improper installation of the rudder control cable by company maintenance personnel, which resulted in chafing and/or fatigue and subsequent failure of the cable.
Sequence of events
NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.
Analysis
The pilot reported that shortly after takeoff, he felt a sharp jolt in the rudder pedals as the landing gear was retracting; after that, the aircraft would no longer respond to left rudder pedal input. The pilot declared an emergency and made an uneventful landing. Postflight examination of the aircraft revealed that the left rudder control cable had failed in proximity of a control pulley in the aft fuselage. Examination of the two cable retaining pins on the pulley braket showed cable scrape marks at their midpoints. The cable had been installed 3 months before the incident and had accumulated 183 hours in service. Metallurgical examination of the failed cable revealed evidence that at least a portion of the strands had failed from fatigue.
Factual narrative
On November 30, 1995, at 0728 hours mountain standard time, a Beech 99, N134PM, experienced a partial loss of directional control after takeoff from Salt Lake City, Utah. The 14 CFR Part 135 cargo flight was operated by Ameriflight, Inc., Burbank, California, and was destined for Boise, Idaho. The aircraft was not damaged and the pilot was not injured. Visual meteorological conditions prevailed and the flight was operating on an instrument flight rules flight plan.
The pilot reported that shortly after takeoff he felt a sharp jolt in the rudder pedals as the landing gear was retracting, after which the aircraft would no longer respond to left rudder pedal input. The pilot declared an emergency and returned to Salt Lake City where the aircraft landed uneventfully.
Postflight examination of the aircraft revealed that the left rudder control cable had separated in the control pulley radius at fuselage station 385.5. The cable (Beech Aircraft part number 115-524063) was installed 3 months prior to the incident and had accumulated 183 hours in service.
Ameriflight, Inc., notified the Southwest Region office of the NTSB of the incident on December 1, 1995. At that time, the aircraft had been repaired at the operator's Salt Lake City base and returned to service. The NTSB did not inspect the aircraft until a later date when it was routed through Burbank.
According to the operator, when replacing the cable, their personnel reported that the control pulley, cable retainer pins, and pulley bracket in the area of the failure showed evidence of wire brushing from the loose wire strands, but no evidence that the cable had been misrouted.
The aircraft was examined by the NTSB investigator on July 11, 1996. The control cable pulley at the location where the cable failed showed no abnormal wear or misalignment, and the interior faces of the adjacent bracket had many fine wire scrape marks. The two cable retaining pins at the cable tangent points on the pulley bracket showed scrape marks at their midpoints.
The failed cable sections were sent to the NTSB metallurgy laboratory in Washington, DC for examination. In his report the metallurgist segregated the failed cable ends into three groups. In the first two groups he stated consisted of failed cable ends had been 1) damaged, or 2) extensively damaged "to the extent that very little of the original fracture features remained." Of the third group, he stated "about 10 percent of the wire ends that were examined in detail contained lesser amounts of damage and at least some evidence of fatigue cracking in the form of longitudinal splits, flat fracture areas (generally with curved boundaries), or microfissures."
Aircraft
- Registration
- N134PM
- Reported as
- Beech 99
- Category
- Airplane
- Serial number
- U-34
- Airframe hours
- 34,246
- Engine
- P&W PT6A-28, 680 horsepower, turbo prop
- Damage
- No damage
- Flight
- Part 135
- Registered owner
- Ameriflight
- Airworthiness certificate
- Standard, Normal
- Last inspection
- AAIP · October 19, 1995 · 80 hours before
- Departed
- SLC
- Destination
- BOI · Boise, ID
- Flight plan
- IFR
- Airport
- SLC · Salt Lake City, runway 14, 5,295 × 150 ft, asphalt
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
- 38
- Certificate
- Airline transport
- Airplane ratings
- Multi-engine land, Single-engine land
- Instrument ratings
- Airplane
- Medical
- Class 1, Valid Medical--w/ waivers/lim
- Seat
- Left
- Flight hours
- 6,254 total · 2,882 in this make and model · 150 in the last 90 days · 60 in the last 30 days · 3 in the last 24 hours
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 120° at 17 knots
- Visibility
- 5 statute miles
- Lowest ceiling
- None
- Temperature
- 45 °F
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.