7 Jun 2013: CESSNA T210L

7 Jun 2013: CESSNA T210L (N732BS) — Unknown operator

No fatalities • Chiloquin, OR, United States

Probable cause

The pilot’s unstabilized approach and use of an excessive speed at touchdown, which resulted in a loss of directional control during the landing and a subsequent runway excursion.

— NTSB Determination

Accident narrative

On June 07, 2013, about 1015 Pacific daylight time, a Cessna T210L, N732BS, veered off the runway surface and came to rest inverted while landing at the Chiloquin State Airport, Chiloquin, Oregon. The airplane was registered to and operated by the pilot under the provisions of 14 Code of Federal Regulations (CFR) Part 91. The private pilot and passenger sustained minor injuries; the airplane sustained substantial damage. The personal cross-country flight departed from the Siskiyou County Airport, Montague, California about 0915 with a planned destination of Chiloquin. Visual meteorological conditions prevailed and no flight plan had been filed.A witness stated that he observed the airplane touchdown on runway 35. He noted that the airplane was landing at a higher-than-expected airspeed, which he estimated to be about 100 miles per hour. Following touchdown, the airplane veered into a gravel area adjacent to the runway and continued until encountering a culvert. The airplane flipped over inverted and came to rest at the edge of the airport's safety perimeter.

The pilot stated that as he entered the vicinity of the destination airport, he maneuvered the airplane on a higher-than-normal approach in an effort to avoid the tall trees located south of runway 35. During touchdown, the airplane's nose wheel failed and he continued down the runway at an excessive ground speed. The airplane began to veer left and in response the pilot applied right rudder. Despite his efforts to regain directional control, the airplane continued off the left of the edge of the runway. The pilot retarded the engine throttle to idle and realized that both wheel brakes had locked up. The airplane continued onto the dirt area adjacent to the runway, over a taxiway, and impacted a culvert; it subsequently nosed over and came to rest inverted.

In the section titled "RECOMMENDATION" in the NTSB Pilot/Operator Report, form 6120.1/2, the pilot stated that the accident could have been prevented if the trees located on the south end of the runway were shortened so it was not necessary to make such a fast, steep descent. He additionally stated that the culvert was too close to the taxiway and the airport environment contributed to the damage sustained.

A postaccident examination by a Federal Aviation Administration (FAA) certificated airframe and powerplant mechanic revealed no evidence of preimpact mechanical malfunctions or failures that would have precluded normal operation.

PERSONNEL INFORMATION

The pilot was certified to operate the accident airplane in accordance with existing Federal Aviation Regulations (FARs). A review of the Federal Aviation Administration (FAA) Airman and Medical Records database disclosed that the pilot held a private pilot certificate, with a rating for airplane single-engine land. The pilot's third-class medical certificate was issued in January 2013, with limitation that he must wear glasses for near vision.

The pilot's self-reported flight time indicated he had amassed 2,857 hours total flight experience, with 150 hours accumulated in Cessna 210 airplanes. The pilot reported that during the preceding 90 days, 30 days, and 24 hours, he had flown in the capacity of pilot-in-command approximately 44, 21, and 0.5 hours, respectively. The pilot stated that he had recorded making 128 landings at that airport.

AIRPORT INFORMATION

The Chiloquin State Airport was a FAR Part 139 certificated facility that had one hard-surfaced asphalt runway (runway 16/34). The runway was 3,749 feet long and 60 feet wide. According to the FAA Airport Facility Directory, there was a 66 foot tree, 1,058 from runway 35 requiring a 13:1 slope to clear it.

Contributing factors

  • cause Pilot
  • cause Directional control — Not attained/maintained
  • cause Incorrect use/operation

Conditions

Weather
VMC, wind 010/03kt, 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.