26 Jan 2016: CESSNA 210 F

26 Jan 2016: CESSNA 210 F (N7316E) — Unknown operator

No fatalities • Lodi, CA, United States

Probable cause

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

— NTSB Determination

Accident 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 has a 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.

Contributing factors

  • cause Pilot
  • cause Landing distance — Not attained/maintained
  • Effect on operation

Conditions

Weather
VMC, wind 290/05kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.