# NTSB WPR16LA061: Cessna 210, N7316E, Lodi, CA, January 26, 2016

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Limited investigation · Final report
- Date: January 25, 2016, 19:30 local (Jan 26, 2016, 03:30 UTC)
- Place: Lodi, CA
- Coordinates: 38.202777, -121.263336
- Nearby events: https://openairdocs.org/map.md?lat=38.2028&lon=-121.2633&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300)
- Highest injury: No injuries
- Injuries: 2 uninjured
- Status: Completed, report August 16, 2016
- Report: Approved by Office Director
- NTSB office: Western Pacific Region
- Parties: Federal Aviation Administration
- NTSB case key (mKey): 92667
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR16LA061
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/92667/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=92667
- Page: https://openairdocs.org/ntsb/WPR16LA061

## Probable cause

The pilot's failure to attain a proper touchdown point, which led to a runway excursion.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Use of equip/info: use of equip/system](https://openairdocs.org/ntsb-findings/02063015): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna 210, 2 cases](https://openairdocs.org/ntsb-findings/02063015/cases.md?model=2073402), [All aircraft, 1,391 cases](https://openairdocs.org/ntsb-findings/02063015/cases.md)
- [Aircraft capability: landing distance](https://openairdocs.org/ntsb-findings/01061030): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 210, 1 case](https://openairdocs.org/ntsb-findings/01061030/cases.md?model=2073402), [All aircraft, 68 cases](https://openairdocs.org/ntsb-findings/01061030/cases.md)
- [Runway/land/takeoff/taxi surface: wet surface](https://openairdocs.org/ntsb-findings/03023010): Environmental issues › Physical environment · Effect on operation; cases with it: [Cessna 210, 1 case](https://openairdocs.org/ntsb-findings/03023010/cases.md?model=2073402), [All aircraft, 141 cases](https://openairdocs.org/ntsb-findings/03023010/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 210, 9 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2073402), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md)
- [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300) (defining event); cases with it: [Cessna 210, 1 case](https://openairdocs.org/ntsb-events/300/sequence.md?model=2073402), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md)

## Analysis

The private pilot reported that, following an uneventful local personal flight, he entered the airport traffic pattern, and he then landed the airplane slightly beyond the runway numbers at 75 mph. He let the airplane "coast" down the remainder of the runway, and as it crossed the runway threshold, he applied brakes with the airplane about 15 to 20 mph to prepare to initiate a right turn. Shortly after, the airplane broke traction and skidded in a straight line. Despite the pilot's attempts to stop the airplane, it impacted an airport perimeter fence about 495 ft beyond the runway threshold, traveled across a ditch and adjacent frontage road, impacted a second fence, and then came to rest upright. The pilot stated that the asphalt was damp with scattered puddles. A pilot-rated witness, who was located at the airport adjacent to the runway reported that he observed the airplane on downwind and that, as the airplane neared the approach end of the runway, it made a steep right turn toward the runway. The witness said that the airplane appeared to be traveling too fast over the runway and that it touched down around the area where the two runways intersected. The witness further stated that the airplane seemed to be under braking immediately after touchdown but that it continued off the runway. Postaccident examination of the airplane revealed no evidence of any preexisting mechanical malfunctions or failures that would have precluded normal operation. Examination of the runway revealed skid marks extending from the departure end of the runway threshold to the airport perimeter fence. Both the left and right tires exhibited signatures consistent with skidding.

## Factual narrative

On January 25, 2016, about 1930 Pacific standard time, a Cessna 210F, N7316E, was substantially damaged during a runway overrun at the Lodi Airport (1O3), Lodi, California. The airplane was registered to a private individual, and operated by the pilot under the provisions of Title 14 Code of Federal Regulations Part 91. The private pilot and passenger were not injured. Night visual meteorological conditions prevailed, and no flight plan was filed for the local personal flight, which originated from 1O3 about 1900.In a written statement to the National Transportation Safety Board (NTSB) investigator-in-charge (IIC), the pilot reported that after performing a local flight, which included a touch-and-go landing at a nearby airport, he returned to 1O3. He entered the airport traffic pattern on a right downwind for runway 8. The pilot stated that the airplane touched down just east of the numbers at 75 miles per hour, and that he let the airplane "coast" down the remainder of the runway. During the landing roll, he retracted the flaps, and as the airplane crossed the departure end of the runway threshold and entered the area of the displaced threshold, he applied the brakes at an estimated ground speed of 15 to 20 miles per hour in order to start a turn toward the fuel pumps. The pilot stated that the asphalt was damp with scattered puddles, and shortly after applying the brakes, the airplane broke traction and skidded in a straight line. Despite the pilot's attempts to stop the airplane, it impacted an airport perimeter fence about 495 feet beyond the runway threshold, and traveled across a ditch and adjacent frontage road before impacting a second fence as it came to rest upright. A pilot rated witness, who was located at his hangar east of the runway 8 and runway 12 intersection, reported that he observed an airplane fly south of runway 8, traveling in a westerly direction at an altitude of about 500 feet above ground level. He stated that as the airplane neared the approach end of runway 8, it made a steep right turn towards the runway. The witness said that he continued to watch the airplane, which seemed to be traveling too fast over the runway, and observed it touch down around the area of the runway 8 and runway 12 intersection. The witness further stated that the airplane seemed to be under braking immediately after touch down and that it continued off the runway, through an airport perimeter fence, across a ditch, a frontage road, and then struck a second fence before it came to a stop. Examination of the airplane by a Federal Aviation Administration inspector revealed that the left horizontal stabilizer was structurally damaged. The inspector reported that skid marks were observed extending from the departure end of the runway 8 threshold to the airport perimeter fence. 1O3 features two runways, runway 8/26, a 3,735 foot-long and 42-foot wide asphalt runway, and runway 12/30, a 2,073-foot long and 26-foot wide asphalt runway. Runway 8 hasa displaced threshold of about 555 feet, and the runway 26 threshold is displaced about 495 feet, which equates to about 2,685 feet of runway between both thresholds. Both displaced thresholds are composed of asphalt. The intersection for both runways is located about 1,415 feet from the runway 8 threshold to the runway 12 centerline. Examination of the airplane by the NTSB IIC on February 16, 2016, revealed that both the left and right brakes were intact and undamaged. When actuated, both brakes functioned normally. The right main landing gear tire exhibited an area that was smooth in appearance, flat, with no visible areas of tread present. The left main landing gear exhibited an area of wear that had a significantly lower tread depth. No evidence of any preexisting mechanical malfunction that would have precluded normal operation was observed.

## Aircraft

- Registration: [N7316E](https://openairdocs.org/deregistered/N7316E-2016-07-07), registration cancelled 2016-07-07, S/N 57016, built 1959 (OpenAirDocs)
- Reported make and model: CESSNA 210 (F)
- Registry model: [Cessna 210](https://openairdocs.org/model/cessna-210) (registry code 2073402) (OpenAirDocs)
- Registry engine: [Continental I0-470 series](https://openairdocs.org/engine/continental-i0-470-series) (registry code 17027, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 57016
- Year built: 1959
- Engines: Continental Motors IO-470-F reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, November 17, 2015, 37 hours before
- Departed: 1O3, Lodi, CA
- Destination: 1O3, Lodi, CA
- Airport: 1O3, Lodi, runway 08, 3,735 × 42 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 62; injuries: none; private; airplane ratings: single-engine sea; medical: class 3, with waivers/limitations; last flight review December 7, 2014; seat: left; flight hours: 311 total, 10 in this make and model, 247 as pilot in command

## Weather

- Conditions: Visual (VMC), Night
- Wind: 290° at 5 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 50 °F, dew point 46 °F
- Altimeter: 30.27 inHg
- Observed at: KSCK, 19 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 20160125001439A](https://openairdocs.org/incident/20160125001439A), Jan 25, 2016: Cessna 210, Lodi, CA, Substantial damage. Aircraft was landing at Lodi, CA. (1O3) runway 8, touch downed long, skidded past runway 26 threshold and continue to roll out while skidding through airport…

## Other investigations on N7316E (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 FTW67D0165](https://openairdocs.org/ntsb/FTW67D0165), Jul 13, 1966: Cessna 210 (N7316E), Zacatecas, Mexico, substantial damage

## Docket (4 files)

The files NTSB released with the investigation on May 31, 2016, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=92667. 2.2 MB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 920 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40440584&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF
- Record of Conversation - Witnesses (item 2, .PDF, 66 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40440585&FileExtension=.PDF&FileName=Record%20of%20Conversation%20-%20Witnesses-Master.PDF
- FAA Runway Examination of Skid Marks (item 3, .PDF, 12 photos, 1.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40440586&FileExtension=.PDF&FileName=FAA%20Runway%20Examination%20of%20Skid%20Marks-Master.PDF
- NTSB Wreckage Examination Memo (item 4, .PDF, 54 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40440587&FileExtension=.PDF&FileName=NTSB%20Wreckage%20Examination%20Memo-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.
