WPR13LA112

NTSB accident investigation · Cessna 305A · Camarillo, CA · February 2, 2013

Accident · No injuriesLimited investigationFinal report
Date
February 2, 2013, 14:00 local (22:00 UTC)
Place
Camarillo, CA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N342FSCessna 305A
Defining event
Landing-landing roll: Loss of control on ground
Weather
Visual (VMC) · Day
Status
Completed · report August 25, 2015
Report
Approved by Office Director
NTSB office
Western Pacific Region
Parties
FAA FSDO
FAA report
20130202001689A
Case key
86126

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

A tailwheel vibration upon touchdown and the subsequent loss of directional control for reasons that could not be determined because postaccident examination revealed no mechanical malfunctions or failures that would have precluded normal operation.

Findings · 2

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Not determinedNot determined › Not determined · Unknown/Not determinedCessna 305A: 2 casesAll aircraft: 2,247 casesProbable cause

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

The pilot reported that, following an uneventful flight, the three-point landing was normal in minimal wind. Immediately upon touchdown, the pilot felt an extreme tailwheel vibration, and the airplane abruptly made a sharp left turn. The airplane then veered off the runway, and the right main landing gear collapsed. Postaccident examination revealed that the right rudder control cables, which extend from the rudder pedals at both the front and rear seats to the rudder control horn, had separated from the rudder pedals. No evidence of preexisting defects, such as corrosion or fatigue, was found; the rudder cables likely fractured due to overstress during the accident sequence and did not cause the loss of directional control. Postaccident examination of the airplane revealed no mechanical malfunctions or failures that would have precluded normal operation. The reason for the tailwheel vibration on touchdown and the subsequent loss of control could not be determined.

Factual narrative

On February 2, 2013, about 1400 Pacific standard time, a Cessna 305A, N342FS, experienced a runway excursion at Camarillo Airport, Camarillo, California. The pilot/owner was operating the airplane under the provisions of 14 Code of Federal Regulations (CFR) Part 91. The commercial pilot and a pilot-rated passenger were not injured; the airplane sustained substantial damage. The local personal flight departed Camarillo at 1300. Visual meteorological (VMC) conditions prevailed, and no flight plan had been filed.The pilot reported that the preflight detected no anomalies with the airplane. The departure and local area flight had been uneventful. The three-point landing was normal in minimal wind. Immediately upon touchdown, the pilot felt an extreme tail wheel vibration, and the airplane abruptly made a sharp left turn. The airplane veered off the runway, and the right main landing gear collapsed. The right wing, right aileron, right landing gear box, horizontal stabilizer, and right elevator sustained substantial damage. The pilot noted that post flight inspection revealed that the right rudder cable had broken. Examination by a Federal Aviation Administration inspector revealed that the rudder control cables for the front and back seats, which extend from the rudder pedals to the rudder control horn, had separated about 14 inches from the rudder pedals. This was in the vicinity of the collapsed right main gear attachment point. No observations were made that could account for the tail wheel vibration on touchdown. The National Transportation Safety Board Materials Laboratory examined the rudder control cables. The specialist conducting the examination determined that both cable fractures were consistent with overstress; no evidence of preexisting defects, such as corrosion or fatigue, was found.

Aircraft

Registration
N342FS
Reported as
Cessna 305A
Category
Airplane
Serial number
21831
Airframe hours
15,442
Engine
Cont Motor O-470-11B, 213 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Operator
Stanley Shaw
Registered owner
Aircraft Financial Group LLC
Airworthiness certificate
Standard, Normal
Last inspection
Annual · September 12, 2012
Departed
CMA · Camarillo, CA
Destination
CMA · Camarillo, CA
Flight plan
Unknown
Airport
CMA · Camarillo, runway 26, 6,013 × 150 ft, concrete
Equipment
Stall warning system

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew · 2

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
77
Injuries
None
Certificates
Airline transport, Commercial
Airplane ratings
Single-engine sea, Single-engine land, Multi-engine land
Instrument ratings
Airplane
Medical
Class 2, With waivers/limitations
Last flight review
July 19, 2012
Seat
Front
Restraint
3-point
Flight hours
24,950 total · 3 in this make and model
Role
Pilot-rated passenger
Age
37
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, Without waivers/limitations
Last flight review
July 19, 2012
Seat
Rear
Restraint
3-point
Flight hours
618 total · 1 in this make and model · 565 as pilot in command · 21 in the last 90 days · 12 in the last 30 days

Weather

Conditions
Visual (VMC) · Day
Wind
150° at 3 knots
Visibility
10 statute miles
Lowest ceiling
12,000 ft broken
Temperature
70 °F, dew point 50 °F
Altimeter
30.12 inHg
Observed at
KCMA

Docket · 8

The files NTSB released with the investigation on July 15, 2015, on NTSB’s docket system: statements, records, photos and specialists’ reports. 10.1 MB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.