# NTSB WPR13LA238: Cessna 310R, N6096C, Bakersfield, CA, May 8, 2013 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: May 8, 2013, 14:55 local (21:55 UTC) - Place: Bakersfield, CA - Coordinates: 35.324722, -118.995834 - Nearby events: https://openairdocs.org/map.md?lat=35.3247&lon=-118.9958&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Flight control sys malf/fail](https://openairdocs.org/ntsb-events/333) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report November 13, 2014 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 86962 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR13LA238 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/86962/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=86962 - Page: https://openairdocs.org/ntsb/WPR13LA238 ## Probable cause The failure of the right main landing gear link assembly, which resulted in the right main landing gear collapsing during landing. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Landing gear system: main landing gear attach sec](https://openairdocs.org/ntsb-findings/01023211): Aircraft › Aircraft systems · Failure (probable cause); cases with it: [Cessna 310R, 2 cases](https://openairdocs.org/ntsb-findings/01023211/cases.md?model=2074245), [All aircraft, 66 cases](https://openairdocs.org/ntsb-findings/01023211/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-flare/touchdown: Landing gear collapse](https://openairdocs.org/ntsb-events/094); cases with it: [Cessna 310R, 8 cases](https://openairdocs.org/ntsb-events/094/sequence.md?model=2074245), [All aircraft, 1,787 cases](https://openairdocs.org/ntsb-events/094/sequence.md) - [Landing-flare/touchdown: Flight control sys malf/fail](https://openairdocs.org/ntsb-events/333) (defining event); cases with it: [Cessna 310R, 1 case](https://openairdocs.org/ntsb-events/333/sequence.md?model=2074245), [All aircraft, 410 cases](https://openairdocs.org/ntsb-events/333/sequence.md) ## Analysis The pilot reported that, upon touchdown, the airplane's right main landing gear began to wobble and then it folded under the fuselage. Despite his efforts to maintain directional control, the airplane veered off the runway surface and came to rest in an adjacent dirt area. The right wheel and lower strut had separated from the upper strut and were found lying on the runway. The right main landing gear torque links had separated at the center hinge point, and the damage indicated that a mechanical malfunction of the link assembly had occurred, which resulted in the right main landing gear collapsing during landing. ## Factual narrative On May 08, 2013, about 1455 Pacific daylight time, a Cessna 310R, N6096C, experienced a right main landing gear collapse during the landing roll at the Bakersfield Municipal Airport, Bakersfield, California. Barr Air Patrol LLC, was operating it under the provisions of 14 Code of Federal Regulations (CFR) Part 91. The commercial pilot and pilot-rated passenger were not injured; the airplane sustained substantial damage. The cross-country aerial observation flight departed from Concord, California about 1300 with a planned destination of Bakersfield. Visual meteorological conditions prevailed, and a company flight plan had been filed and activated.The pilot stated that the purpose of the flight was to perform pipeline patrol. The airplane touched down on runway 34 normally and immediately thereafter, the right main landing gear began to wobble and then it folded under the fuselage. Despite the pilot's efforts to maintain directional control by inputting left rudder and aileron, the airplane veered off the runway surface coming to rest in an adjacent dirt area. After egressing from the airplane, the pilot noted that the right wheel had departed from the landing gear and, as a result, the gear had collapsed. According to a Federal Aviation Administration (FAA) inspector, the airplane impacted a runway light as it departed the pavement. Skid marks on the runway were approximately 18 inches from the touchdown area and appeared consistent in orientation to the right main gear rotating approximately 90 degrees. The right wheel and lower strut had separated from the upper strut and were lying on the runway. The right main landing gear torque links had separated at the center hinge point, which he thought may have allowed the wheel to rotate 90 degrees to the direction of travel. A post accident examination of the airplane revealed that the landing gear had damaged the wheel well area including the ribs inboard and outboard of the gear attach point. The upper and lower torque links were intact. He opined that based on the damage there was a mechanical malfunction of the link assembly (part number 5141005-8) which would include the bushing, a sheered bolt, and/or the washer. The last annual inspection was completed on April 23, 2013, and 37 hours had been accumulated since the inspection. ## Aircraft - Registration: [N6096C](https://openairdocs.org/deregistered/N6096C-2015-05-15), registration cancelled 2015-05-15, S/N 310R1263, built 1977 (OpenAirDocs) - Reported make and model: CESSNA 310R - Registry model: [Cessna 310R](https://openairdocs.org/model/cessna-310r) (registry code 2074245) (OpenAirDocs) - Registry engine: [Continental IO-520 series](https://openairdocs.org/engine/continental-io-520-series) (registry code 17032, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 310R1263 - Airframe hours: 7952 - Engines: CONT MOTOR IO-520M 285 horsepower reciprocating; CONT MOTOR IO 520 SERIES 285 horsepower reciprocating - Damage: Substantial damage - Flight: Aerial observation, Part 91 - Operator: Barr Air Patrol LLC - Registered owner: Barr Air Patrol LLC - Airworthiness certificate: Standard, Normal - Last inspection: Annual, April 23, 2013, 37 hours before - Departed: CCR, Concord, CA - Destination: L45, Bakersfield, CA - Flight plan: Company VFR - Airport: L45, Bakersfield Municipal Airport, runway 34, 4,000 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 42; injuries: none; commercial; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 1, with waivers/limitations; seat: left; flight hours: 2,508 total, 800 in this make and model, 1,530 as pilot in command, 217 in the last 90 days, 76 in the last 30 days, 6 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 340° at 11 knots - Visibility: 10 statute miles - Lowest ceiling: 5,500 ft broken - Temperature: 75 °F, dew point 46 °F - Altimeter: 30.02 inHg - Observed at: BFL, 7 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20130508007499A](https://openairdocs.org/incident/20130508007499A), May 8, 2013: Cessna 310R, Bakersfield, CA, Substantial damage. On may 8, 2013, about 1505 PDT, a Cessna 310R, N6909C, was substantially damaged during landing at Bakersfield muni airport (L45), Bakersfield, CA on runway… ## Other investigations on N6096C (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB CHI87LA020](https://openairdocs.org/ntsb/CHI87LA020), Nov 8, 1986: Cessna 310R (N6096C), Belvidere, IL, substantial damage ## Docket (2 files) The files NTSB released with the investigation on October 7, 2014, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=86962. 2.0 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 1.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40417445&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - FAA Inspector Statement (item 2, .PDF, 54 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40417446&FileExtension=.PDF&FileName=FAA%20Inspector%20Statement-Master.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.