# NTSB SEA95IA082: Fairchild SA-227, N385PH, Pasco, WA, April 16, 1995

- Type: NTSB incident investigation
- Classification: Incident · No injuries · Incident investigation · Final report
- Date: April 16, 1995, 08:05 local (15:05 UTC)
- Place: Pasco, WA
- Coordinates: 46.249294, -119.289657 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=46.2493&lon=-119.2897&mi=10
- Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 7 uninjured
- Status: Completed, report January 29, 1996
- Report: Approved by Office Director
- NTSB case key (mKey): 42071
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=SEA95IA082
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/42071/pdf
- Page: https://openairdocs.org/ntsb/SEA95IA082

## Probable cause

IMPROPER INSTALLATION OF THE RUDDER TRIM ACTUATOR ROD BY COMPANY MAINTENANCE PERSONNEL WHICH RESULTED IN BINDING AND FRACTURE OF THE ROD.

## Sequence of events

In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf).

- Airframe/component/system failure/malfunction, climb - to cruise
  - flt control syst,rudder trim/tab control - binding(mechanical) (cause)
  - maintenance,installation - improper, company maintenance personnel (cause)
  - flt control syst,rudder trim/tab control - fractured (cause)

## Analysis

DURING CLIMB OUT, THE CREW NOTICED AN UNUSUAL AIRFRAME VIBRATION, AND RETURNED TO THE DEPARTURE AIRPORT. FAA INSPECTORS DETERMINED THAT THE RUDDER TRIM ACTUATOR ROD HAD BEEN IMPROPERLY INSTALLED, ALLOWING IT TO BIND AND EVENTUALLY FRACTURE.

## Factual narrative

On April 16, 1995, approximately 0805 Pacific daylight time (PDT), a Fairchild SA-227, N385PH, experienced a failure of a rudder trim rod while climbing out from Tri-Cities Airport, Pasco, Washington. There were no injuries to the two crew members and their five passengers, and the aircraft sustained only minor damage. The FAR Part 135 revenue flight, which was en route to Portland International Airport, Portland, Oregon, was in visual meteorological conditions at the time of the incident. The scheduled passenger flight was on an IFR flight plan, and there was no ELT activation involved in this incident.

According to a representative of Horizon Airlines, the crew noticed an unusual airframe vibration after the departure from Pasco. They therefore elected to return to the Tri-Cities Airport, where they discovered that the rudder trim rod had failed.

FAA inspectors determined that the actuator rod had been improperly installed by company maintenance personnel, and it had been binding before it fractured and failed.

## Aircraft

- Registration: N385PH (not matched to a registry record)
- Reported make and model: FAIRCHILD SA-227
- Category: Airplane
- Serial number: AC-595
- Airframe hours: 23609
- Engines: GARRETT TPE331-11U-61 1000 horsepower turbo prop
- Damage: Minor damage
- Flight: Part 135
- Operator: Horizon Airlines
- Registered owner: First Security Bank Of Utah
- Airworthiness certificate: Standard, Normal
- Last inspection: Continuous airworthiness, March 26, 1995, 85 hours before
- Departed: PSC
- Destination: PDX, PORTLAND, OR
- Flight plan: IFR

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 34; airline transport; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 1, valid medical--w/ waivers/lim; seat: left; flight hours: 5,950 total, 567 in this make and model, 2,686 as pilot in command, 89 in the last 90 days, 23 in the last 30 days, 2 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Day

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Incident 19950416011329I](https://openairdocs.org/incident/19950416011329I), Apr 16, 1995: Swrngn SA227AC, Pasco, WA, Minor damage. Narrative: during takeoff phase of flight, crew experienced vibration through-out aircraft. Aircraft returned to point of departure without further incident.…

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.