7 Oct 2008: CIRRUS DESIGN CORP SR20

7 Oct 2008: CIRRUS DESIGN CORP SR20 — Unknown operator

No fatalities • Chester, CT, United States

Probable cause

The pilot’s failure to obtain the proper touchdown point while landing. Contributing to the accident were the pilot’s inexperience landing at the airport, night conditions, and non-standard runway lighting.

— NTSB Determination

Accident narrative

The pilot of the Cirrus SR20 stated that he was on an instrument flight rules (IFR) flight plan to an airport, which he had been to before. The airport was privately owned, publicly used, and equipped with non-standard lighting. The pilot was concerned with the runway length at the destination airport, which was significantly shorter than what he was accustomed to. An additional concern was the steep drop-off at the end of the runways. When the pilot was about 6 miles from the airport, he observed the airport lighting and continued on a visual approach to runway 35,a 2,566-foot long, 50-foot wide, asphalt runway. The airport’s runway lighting was illuminated, but somewhat dim and not controllable from the cockpit. In addition, runway 35 was not equipped with a visual slope indicator. The pilot noted that the night seemed to be especially dark with an absence of any visual cues. The landing was hard. The pilot "chopped" the power completely and applied the brakes. About 1,500 feet down the runway, braking effectiveness and directional control of the airplane was lost. The airplane veered to the left, went through a fiberglass fence, down an embankment, and came to rest into pine trees. The responding Federal Aviation Administration (FAA) inspector stated that the airplane impacted up-sloping terrain 6 feet before the runway’s pavement began. The airplane traveled about three-quarters of the runway before exiting off the left side. The airplane’s propeller, fuselage underside, and all three landing gears incurred damage. Both main landing gear brake fluid supply fittings were broken off.

Contributing factors

  • cause Descent/approach/glide path — Not attained/maintained
  • factor Pilot
  • factor Effect on personnel
  • factor Runway lighting

Conditions

Weather
VMC, wind 320/04kt, 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.