Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

November 30, 1995 · Beech 99 · N134PM

Salt Lake City, UT

Overview

Report Status
Final with probable cause
Event Type
Incident
Date
November 30, 1995
Injury Outcomes
No injuries (1 uninjured)
Location
Salt Lake City, UT
Aircraft
Beech 99
Tail Number
N134PM
Injuries
None
NTSB Number
LAX96IA065

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.

NTSB 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.

Full 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."

Flight

Event TypeIncident
Event Time07:28 MST
Nearest AirportSalt Lake City (0nm)
Runway14
Runway Length5295 ft
Runway Width150 ft
Flight Plan FiledIFR
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftBeech 99
Tail NumberN134PM
Aircraft CategoryAir
Operating RulePart 135
Engines2
Engine TypeTurboprop
Engine DetailsP&W · PT6A-28 · Turboprop · 680
Seats2

People & Injuries

Injury SummaryNo injuries (1 uninjured)
Fatal0
Serious0
Minor0
Uninjured1
Total1
Crew 1Age 38 · First Class

Conditions

ConditionsVMC
LightDaylight
Wind120° @ 17 kt
Visibility5 sm
CeilingNone
Temperature / Dew Point45 C / 0 C
Altimeter0
Weather SourcePILO

Appendix: Source Data