ERA09CA007

NTSB accident investigation · Cirrus Design SR20 · Chester, CT · October 7, 2008

Accident · No injuriesData collectionFinal report
Date
October 7, 2008, 19:40 local (23:40 UTC)
Place
Chester, CT
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N889LDCirrus Design SR20
Defining event
Landing-flare/touchdown: Landing area undershoot
Weather
Visual (VMC) · Night/dark
Status
Completed · report December 3, 2008
Report
Approved by Office Director
NTSB office
Eastern Region Aviation
Parties
FAA/FSDO
FAA report
20081007850249A
Case key
69238

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

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 · 4

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Performance/control parameters: descent/approach/glide pathAircraft › Aircraft oper/perf/capability · Not attained/maintainedCirrus Design SR20: 6 casesAll aircraft: 809 casesProbable cause
Experience/qualificationsPersonnel issues › Experience/knowledge · PilotCirrus Design SR20: 1 caseAll aircraft: 18 casesProbable cause
Light condition: darkEnvironmental issues › Conditions/weather/phenomena · Effect on personnelCirrus Design SR20: 5 casesAll aircraft: 448 casesProbable cause
Airport facilities/design: runway lightingEnvironmental issues › Operating environment · Not specifiedCirrus Design SR20: 1 caseAll aircraft: 18 casesProbable cause

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

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
Reported as
Cirrus Design SR20
Category
Airplane
Serial number
1434
Airframe hours
949
Engine
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

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
57
Injuries
None
Certificate
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.