FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Conquest Airlines Flight 220

27 Feb 1995 · Austin, TX, United States

Fairchild SA227-AC · Incident: airframe, component or system failure during landing

From TYL · Tyler, TX to Austin Bergstrom International Airport (AUS)

Report a problem

Event

NTSB case
FTW95IA124
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
Instrument Meteorological Cond

Fairchild SA227-AC

Aircraft type
Fairchild SA227
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
N369AE
Onboard fatalities
Unknown
Route
From TYL · Tyler, TXTo Austin Bergstrom International Airport (AUS)
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
Landing · flare/touchdown
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
None

Cause areas

  • Company maintenance personnel › Maintenance, compliance with ad, improper
  • Flt control syst, rudder control cable/rod › Failure, total
  • Flt control syst, rudder control cable/rod › Misrouted

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

NTSB narrative

WHILE FLARING TO LAND, THE RUDDER CABLE FOR THE LEFT RUDDER SEVERED DUE TO IMPROPER ROUTING DURING THE SCHEDULED REPLACEMENT OF THE CONTROL CABLES IN COMPLIANCE WITH AN AIRWORTHINESS DIRECTIVE. THE FLIGHT CREW REPORTED HEARING A POPPING SOUND FOLLOWED BY THE RUDDER PEDAL DEFLECTING TO THE STOP. CONTROL WAS MAINTAINED AND A NORMAL LANDING COMPLETED.

Probable cause

THE FAILURE OF THE MISROUTED RUDDER CONTROL CABLE DUE TO IMPROPER INSTALLATION DURING SCHEDULED REPLACEMENT TO COMPLY WITH AN AIRWORTHINESS DIRECTIVE.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW95IA124
Event ID
20001207X02957
Case number
FTW95IA124
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, damage. 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: e66b2cb1039b540695cded486b4649f4cbb7c564f397d96e2d47d6f6a39ed37d; retrieved 2026-09-18T18:03:21.172Z.