ERA11CA365

NTSB accident investigation · Piper PA-32-300 · Bridgeport, CT · June 26, 2011

Accident · Serious injuriesData collectionFinal report
Date
June 25, 2011, 21:45 local (Jun 26, 2011, 01:45 UTC)
Place
Bridgeport, CT
Injuries
2 serious
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N600DKPiper PA-32-300
Defining event
Approach-VFR pattern final: Controlled flight into terr/obj (CFIT)
Weather
Visual (VMC) · Night
Status
Completed · report November 17, 2011
Report
Approved by Office Director
NTSB office
Eastern Region Aviation
Parties
FAA Windsor Locks FSDO
FAA report
20110625013849A
Case key
80906

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 maintain clearance from a blast fence on final approach to land.

Findings · 3

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.

Object/animal/substance: airport structureEnvironmental issues › Physical environment · Contributed to outcomePiper PA-32-300: 1 caseAll aircraft: 50 cases
Action: incorrect action performancePersonnel issues › Action/decision · PilotPiper PA-32-300: 5 casesAll aircraft: 1,386 casesProbable cause
Performance/control parameters: altitudeAircraft › Aircraft oper/perf/capability · Not attained/maintainedPiper PA-32-300: 10 casesAll aircraft: 1,310 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 purpose of the flight was for the pilot to regain night currency, which had lapsed two weeks prior. The pilot stated that he intended to fly three landing pattern approaches and perform three full stop landings. According to the pilot, the take off, and initial climbout to a left downwind were normal. The pilot reported that there was a slight haze in the vicinity of the airport. While turning to the base leg of the approach, the pilot trimmed the airplane for 90 mph and lowered the flaps to the "first notch." The pilot reported the he saw "two white lights" on the vertical approach slope indicator, which indicated that he was above the glideslope, so he adjusted the trim to maintain 80 mph and lowered the flaps to the "third notch." The airplane's left wing impacted a 12-foot-tall blast fence, which was located 20 feet from the end of the runway, resulting in the separation of the left wing from the fuselage. After the accident, the pilot stated that the blast fence was indistinguishable from the runway threshold markings. The blast fence was properly marked with red and white checker markings on the interior side and was not required to be lit by Federal Aviation Administration facility requirements. The pilot was familiar with the airport.

Factual narrative

The purpose of the flight was for the pilot to regain night currency which had lapsed two weeks prior. The pilot stated that he intended to fly three landing pattern approaches and perform three full stop landings. According to the pilot, the take off, and initial climb out to a left downwind were normal. The pilot also reported that there was a slight haze in the vicinity of the airport. While turning to the base leg of the approach, the pilot trimmed the aircraft for 90 miles per hour (mph) and lowered the flaps down to the "first notch." The pilot reported the he saw "two white lights" on the Vertical Approach Slope Indicator (VASI) which indicated that he was above glide-slope so he adjusted the trim to maintain 80 mph and lowered the flaps down to the "third notch." The airplane's left wing impacted a 12-foot-tall blast fence, which was located 20 feet from the end of the runway resulting in the separation of the left wing from the fuselage. The VASI was set for a 3 degrees glide-path and the threshold of the runway was displaced 319 feet. After the accident, the pilot stated that the blast fence was indistinguishable from the runway threshold markings. The blast fence was properly marked with red and white checker markings on the interior side and was not required to be lit by federal aviation administration facility requirements. The pilot was familiar with the airport.

Aircraft

Registration
N600DK
Reported as
Piper PA-32-300
Category
Airplane
Serial number
32-7340167
Airframe hours
4,297
Engine
Lycoming TIO-540 SER, 310 horsepower, reciprocating
Damage
Substantial damage
Fire
On-Ground
Flight
Personal · Part 91
Operator
Three Wing Flying Services
Registered owner
180 Brooklawn Avenue LLC
Airworthiness certificate
Standard, Normal
Last inspection
100 hour · May 5, 2011 · 35 hours before
Departed
KBDR · Bridgeport, CT
Destination
KBDR · Bridgeport, CT
Airport
KBDR · Igor Sikorsky Memorial Airport, runway 24, 4,677 × 150 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
59
Injuries
Serious
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, With waivers/limitations
Last flight review
March 5, 2011
Seat
Left
Flight hours
379 total · 90 in this make and model · 295 as pilot in command · 5 in the last 90 days · 4 in the last 30 days · 0 in the last 24 hours

Weather

Conditions
Visual (VMC) · Night
Wind
200° at 3 knots
Visibility
8 statute miles
Lowest ceiling
None
Temperature
70 °F, dew point 64 °F
Altimeter
29.86 inHg
Observed at
KBDR

Docket · 6

The files NTSB released with the investigation on September 27, 2011, on NTSB’s docket system: statements, records, photos and specialists’ reports. 2.5 MB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.