FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Grant Aviation Cessna 207 A accident

27 Jul 2022 · Dillingham, AK, United States

Cessna 207 A · Accident: flight control system malfunction/failure en route

From ANW · New Stuyahok, AK to an unrecorded destination

Report a problem

Event

NTSB case
ERA22LA358
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
Accident
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

Cessna 207 A

Aircraft type
Cessna 207
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
N6908M
Onboard fatalities
Unknown
Route
From ANW · New Stuyahok, AKTo not recorded
Aircraft age
About 42 years (built 1980)
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
En route
Defining eventThe 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
Flight control system malfunction/failure
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft systems
  • Personnel issues › Task performance

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

NTSB narrative

The pilot reported that, during approach to landing, he became aware that the left rudder pedal was not responsive. He declared an emergency and landed uneventfully. Examination revealed that the left rudder cable fractured due to corrosion and severe cable wear at the left pulley location. Nearly all wires on the cable were worn to a chisel-like point, leaving a small number of wires in the core strand to fracture in ductile overstress during final separation. The cable corrosion and wear were likely accelerated due to sliding contact with the left pulley.

Issues with the rudder control system installation were evident on both pulleys. Rubbing damage on the face of the left pulley indicated that the pulley was contacting adjacent structure at the outer diameter. This contact likely interfered with pulley rotation, leading to the accelerated corrosion and wear of the control cable from sliding contact within the pulley groove. Although no rubbing damage was observed on the right pulley, the cable contact pattern was offset from the groove centerline, indicating an alignment problem in the rudder control system at the right pulley. Review of the maintenance logs revealed that the last inspection of the flight controls was completed about 8 months before the accident, and an entry about 3 months later noted a stuck pulley and corrosion of the left rudder cable. The maintenance response to the entry stated, “upon further inspection, determined cable not corroded. . . No defects.” Given the findings of the postaccident examination, it is likely that the accident would have been prevented had maintenance personnel taken more proactive action at that time.

Probable cause

Maintenance personnel’s failure to detect and correct improper rudder control system alignment, the resulting interference with the pulley’s rotation, and the accelerated corrosion and wear of the control cable, which ultimately led to its failure in flight.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA22LA358
Event ID
20220805105670
Case number
ERA22LA358
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: local date, investigation status, cause areas. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2022-07-28.
  • API snapshot SHA-256: ae3d2fefc9bb984004358354f1411cd750890931a8aa92709308c36648ecdee4; retrieved 2026-09-16T15:34:06.587Z.