The U.S. aircraft register, updated daily
Accidents · NTSB WPR11IA213 · Final report

Cessna 421B incident near Truckee, California, May 2, 2011

On May 2, 2011 at about 9:40 pm local time, a Cessna 421B, registered N270CS, was involved in an incident during approach (VFR pattern downwind) near Truckee, California (Truckee-Tahoe airport). It was a positioning flight under general aviation rules (Part 91). No one was hurt; 3 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
May 2, 2011 · about 9:40 pm local time
Place
Truckee, California · Truckee-Tahoe · map
Type
Incident
Injuries
No one was hurt; 3 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 421B · all 421Bs on the register
Registration
N270CS · no longer on the register · serial 421B0869
Damage
Not recorded
Flight
Positioning flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Flight control sys malf/fail during approach (VFR pattern downwind) defining event
  2. Inflight upset during approach (VFR pattern downwind)

The NTSB's findings

  • cause Aircraft › Aircraft systems › Flight control system › TE flap control system › Fatigue/wear/corrosion
  • cause Aircraft › Aircraft systems › Flight control system › TE flap control system › Failure

Pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
  • Flight time: 3,850 hours in all; 154 in this make and model; 61 in the last 90 days; 15 in the last 30 days; 3,675 as pilot in command; 1,132 on instruments
  • Last flight review: November 17, 2010
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 4,832 hours
  • Last inspection: 100-hour inspection, March 19, 2011; 10 hours since
  • Maximum gross weight: 7,579 lb
  • Seats: 4
  • Landing gear: retractable
  • Engine 1: Continental Motors GTSIO-520H (piston); 0 hours total
  • Engine 2: Continental Motors GTSIO-520H (piston); 0 hours total
  • Operator: California Shock Trauma Air Rescue

The flight

  • Departed from: MCC Sacramento CA at 9:12 pm
  • Destination: TRK Truckee CA
  • Flight plan: IFR
  • Runway 28, 7,000 ft by 100 ft

Weather at the time

  • Light: daylight
  • Wind: from 230° at 10 knots, gusting 18
  • Visibility: 10 statute miles
  • Sky: a few clouds at 6,000 ft
  • Temperature: 59°F (15°C), dew point 25°F (-4°C)
  • Altimeter: 30.32 inHg
  • Observation at 9:45 pm from TRK

Injuries

FatalSeriousMinorNone
Flight crew3

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.