# NTSB ERA09CA007: Cirrus Design SR20, N889LD, Chester, CT, October 7, 2008

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: October 7, 2008, 19:40 local (23:40 UTC)
- Place: Chester, CT
- Coordinates: 41.384166, -72.505836 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=41.3842&lon=-72.5058&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing-flare/touchdown: Landing area undershoot](https://openairdocs.org/ntsb-events/370)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report December 3, 2008
- Report: Approved by Office Director
- NTSB office: Eastern Region Aviation
- Parties: FAA/FSDO
- NTSB case key (mKey): 69238
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA09CA007
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/69238/pdf
- Page: https://openairdocs.org/ntsb/ERA09CA007

## 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.

## Findings

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

- [Performance/control parameters: descent/approach/glide path](https://openairdocs.org/ntsb-findings/01062040): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cirrus Design SR20, 6 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=2130000), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md)
- [Experience/qualifications](https://openairdocs.org/ntsb-findings/02031000): Personnel issues › Experience/knowledge · Pilot (probable cause); cases with it: [Cirrus Design SR20, 1 case](https://openairdocs.org/ntsb-findings/02031000/cases.md?model=2130000), [All aircraft, 18 cases](https://openairdocs.org/ntsb-findings/02031000/cases.md)
- [Light condition: dark](https://openairdocs.org/ntsb-findings/03036020): Environmental issues › Conditions/weather/phenomena · Effect on personnel (probable cause); cases with it: [Cirrus Design SR20, 5 cases](https://openairdocs.org/ntsb-findings/03036020/cases.md?model=2130000), [All aircraft, 448 cases](https://openairdocs.org/ntsb-findings/03036020/cases.md)
- [Airport facilities/design: runway lighting](https://openairdocs.org/ntsb-findings/03017015): Environmental issues › Operating environment · Not specified (probable cause); cases with it: [Cirrus Design SR20, 1 case](https://openairdocs.org/ntsb-findings/03017015/cases.md?model=2130000), [All aircraft, 18 cases](https://openairdocs.org/ntsb-findings/03017015/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 area undershoot](https://openairdocs.org/ntsb-events/370) (defining event); cases with it: [Cirrus Design SR20, 1 case](https://openairdocs.org/ntsb-events/370/sequence.md?model=2130000), [All aircraft, 201 cases](https://openairdocs.org/ntsb-events/370/sequence.md)
- [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Cirrus Design SR20, 22 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2130000), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md)

## Analysis

The accident flight was the first time the pilot was landing at the privately owned, publicly used airport, with non-standard runway lighting. The pilot was concerned with the runway length and steep drop-off at the end of the runways. The landing runway was 2,566 feet long, 50 feet wide, and was not equipped with a visual slope indicator. Upon his approach to the destination airport, the pilot noted that the runway lights were dim. The night was especially dark for the pilot, limiting his visual cues. The pilot landed hard, on up-sloping terrain, 6 feet short of where the runway’s pavement began. Both main landing gear brake system were damaged in the process. The pilot was not able to brake or steer the airplane. The airplane veered off to the left, went through a fiberglass fence, and down an embankment before coming to a stop into several pine trees.

## Factual 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.

## Aircraft

- Registration: [N889LD](https://openairdocs.org/aircraft/N889LD), registered now, S/N 1434, built 2004 (OpenAirDocs)
- Reported make and model: CIRRUS DESIGN CORP SR20
- Registry model: [Cirrus Design SR20](https://openairdocs.org/model/cirrus-design-sr20) (registry code 2130000) (OpenAirDocs)
- Registry engine: [Continental IO-360 series](https://openairdocs.org/engine/continental-io-360-series) (registry code 17025, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 1434
- Airframe hours: 949
- Engines: CONT MOTOR IO-360 SER 210 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, March 13, 2008, 53 hours before
- Departed: CPK, Chesapeake, VA
- Destination: SNC, Chester, CT
- Flight plan: IFR
- Airport: SNC, Chester Airport, runway 35, 2,566 × 50 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 57; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review July 31, 2007; seat: left; flight hours: 576 total, 234 in this make and model, 455 as pilot in command, 9 in the last 90 days, 4 in the last 30 days

## Weather

- Conditions: Visual (VMC), Night/dark
- Wind: 320° at 4 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 50 °F, dew point 37 °F
- Altimeter: 30.21 inHg
- Observed at: SNC

## 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 20081007850249A](https://openairdocs.org/incident/20081007850249A), Oct 7, 2008: Cirrus SR20, Chester, CT, Substantial damage. (-23) The pilot landed short of runway 35 non-standard displaced threshold and impacted the ground six feet before runway pavement begins. Pilot then applied…

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.
