FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR11IA213 · Cessna 421B

2 May 2011 · Truckee, CA, United States

California Shock Trauma Air Rescue Cessna 421B · Incident: flight control system malfunction/failure on approach

From McClellan Airfield (MCC) to Truckee Tahoe Airport (TRK)

Report a problem

Event

NTSB case
WPR11IA213
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
Unknown
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
General aviation
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 421B

Aircraft type
Cessna 421
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
N270CS
Onboard fatalities
Unknown
Route
From McClellan Airfield (MCC), Sacramento, CATo Truckee Tahoe Airport (TRK), Truckee, CA
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 91: General Aviation
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
Approach · VFR pattern downwind
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
None

Cause areas

  • Aircraft › Aircraft systems

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

NTSB narrative

The airplane entered the downwind leg of the traffic pattern high, and, in an effort to descend, the pilot extended the landing gear and deployed full flaps. About the time the flaps reached their maximum extension, the right flap experienced an instantaneous retraction, and the airplane simultaneously rolled about 80 degrees to the right. The pilot countered with almost full left aileron control input for the remainder of the flight. He began troubleshooting steps, but was unable to extend the right flap or retract the left flap. He diverted to another airport and, for the remaining 35 minutes of flight, employed the assistance of a passenger to help with maintaining left aileron control deflection. The landing was made without further incident.

Postincident examination of the flap control system revealed that the right wing flap extend cable had failed in the area where it made contact with the inboard flap pulley, an area where the cable had experienced multiple bending cycles throughout its life. The failed cable strands exhibited fatigue signatures, and similar frays and failures were observed in the area of the outboard pulley. The corresponding left flap cable also exhibited similar strand failure features in the inboard and outboard pulley contact areas. The cables were installed when the airplane was manufactured, 36 years prior to the incident. Over this period, the airplane had accumulated 4,832.1 total flight hours.

The flap cable was not life limited, and the airplane manufacturer's maintenance manual did not require the removal of flight control cables during inspection. The mechanic who performed the most recent inspection reported that he examined the cables utilizing the methods prescribed in the manufacturer's service manual but did not detect any damage. He further stated that the damage was only obvious once the cables had been removed and subsequently flexed and looped by hand.

A review of Federal Aviation Administration Service Difficulty Reports for the airplane series revealed 33 instances of similar flap cable wear or failure on 25 separate airplanes. About half of the reports indicated flap cable failures occurring during flight; all were during the critical landing approach phase. The failures resulted in asymmetric flap deployment, and some resulted in a violent departure from controlled flight. In a few instances, the damage caused by the cable separation prevented the retraction of the remaining extended flap, and, therefore, the pilot had to maintain very high opposing aileron control inputs in order to control and land the airplane. A common finding noted in the reports was that the cable damage could not be readily observed unless the cables were removed.

A service bulletin is in development by the airplane manufacturer concerning the inspection procedures and replacement criteria for the flap cables in the airplane series.

Probable cause

Fatigue failure of the right flap extend cable during the landing approach.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR11IA213
Event ID
20110430X60514
Case number
WPR11IA213
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: 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: 4573605893610c017a5633ec5b7e90d5e9c5906c9df68f884518a28be92b9cf8; retrieved 2026-09-15T16:06:50.085Z.