FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Horizon Air Fairchild SA-227-AC incident

23 Jan 1989 · Seattle, WA, United States

Fairchild SA-227-AC · Incident: airframe, component or system failure during takeoff

From an unrecorded airport to Portland International Airport (PDX)

Report a problem

Event

NTSB case
SEA89IA042
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
Incident
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
0
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

Fairchild SA-227-AC

Aircraft type
Fairchild SA-227
Category
Airplane
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
N386PH
Operator
Horizon Air
Onboard fatalities
Unknown
Route
From not recordedTo Portland International Airport (PDX), Portland, OR
Aircraft age
Not recorded
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
Takeoff · roll/run
First occurrenceThe 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
Airframe, component or system failure
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

  • Company maintenance personnel › Maintenance, installation, improper
  • Directional control › Not possible
  • Landing gear, steering system › Inoperative

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

WHILE ON TAKEOFF ROLL, THE CPT TURNED THE ELECTRIC NOSE WHEEL STEERING OFF. THE FIRST OFFICER, FLYING THE ACFT, ANNOUNCED AN UNCOMMANDED RIGHT YAW. THE CPT TOOK THE CONTROLS BUT WAS NOT ABLE TO BRING THE ACFT TO A HALT BEFORE DEPARTING THE SIDE OF THE RUNWAY. POST MISHAP TESTS REVEALED A MALFUNCTION OF THE NOSE WHEEL STEERING DUE TO IMPROPER REPLACEMENT OF VALVES IN THE HYDRAULIC STEERING ACTUATOR UNIT.

Probable cause

INOPERATIVE NOSEWHEEL STEERING DUE TO IMPROPER MAINTENANCE. CONTRIBUTING TO THE INCIDENT WAS THE LACK OF ADEQUATE MAINTENANCE INFORMATION AVAILABLE IN THE AIRCRAFT MANUALS.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA89IA042
Event ID
20001213X27664
Case number
SEA89IA042
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: e856d2af24d37e75dd755e836b700f5e89f6e387907d11c9a0662f6089d18a70; retrieved 2026-09-18T19:14:31.107Z.