# NTSB ERA11CA365: Piper PA-32-300, N600DK, Bridgeport, CT, June 26, 2011

- Type: NTSB accident investigation
- Classification: Accident · Serious injuries · Data collection · Final report
- Date: June 25, 2011, 21:45 local (Jun 26, 2011, 01:45 UTC)
- Place: Bridgeport, CT
- Coordinates: 41.158054, -73.122222 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=41.1581&lon=-73.1222&mi=10
- Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping)
- Defining event: [Approach-VFR pattern final: Controlled flight into terr/obj (CFIT)](https://openairdocs.org/ntsb-events/120)
- Highest injury: Serious injuries
- Injuries: 2 serious
- Status: Completed, report November 17, 2011
- Report: Approved by Office Director
- NTSB office: Eastern Region Aviation
- Parties: FAA Windsor Locks FSDO
- NTSB case key (mKey): 80906
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA11CA365
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/80906/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=80906
- Page: https://openairdocs.org/ntsb/ERA11CA365

## Probable cause

The pilot's failure to maintain clearance from a blast fence on final approach to land.

## Findings

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

- [Object/animal/substance: airport structure](https://openairdocs.org/ntsb-findings/03022042): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Piper PA-32-300, 1 case](https://openairdocs.org/ntsb-findings/03022042/cases.md?model=7103212), [All aircraft, 50 cases](https://openairdocs.org/ntsb-findings/03022042/cases.md)
- [Action: incorrect action performance](https://openairdocs.org/ntsb-findings/02041015): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Piper PA-32-300, 5 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md?model=7103212), [All aircraft, 1,386 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md)
- [Performance/control parameters: altitude](https://openairdocs.org/ntsb-findings/01062012): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Piper PA-32-300, 10 cases](https://openairdocs.org/ntsb-findings/01062012/cases.md?model=7103212), [All aircraft, 1,310 cases](https://openairdocs.org/ntsb-findings/01062012/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Approach-VFR pattern final: Altitude deviation](https://openairdocs.org/ntsb-events/282); cases with it: [Piper PA-32-300, 1 case](https://openairdocs.org/ntsb-events/282/sequence.md?model=7103212), [All aircraft, 104 cases](https://openairdocs.org/ntsb-events/282/sequence.md)
- [Approach-VFR pattern final: Controlled flight into terr/obj (CFIT)](https://openairdocs.org/ntsb-events/120) (defining event); cases with it: [Piper PA-32-300, 8 cases](https://openairdocs.org/ntsb-events/120/sequence.md?model=7103212), [All aircraft, 1,074 cases](https://openairdocs.org/ntsb-events/120/sequence.md)
- [Uncontrolled descent: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper PA-32-300, 43 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7103212), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md)

## 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](https://openairdocs.org/deregistered/N600DK-2013-09-16), registration cancelled 2013-09-16, S/N 32-7340167, built 1973 (OpenAirDocs)
- Reported make and model: PIPER PA-32-300
- Registry model: [Piper PA-32-300](https://openairdocs.org/model/piper-pa-32-300) (registry code 7103212) (OpenAirDocs)
- Registry engine: [Lycoming TI0-540 series](https://openairdocs.org/engine/lycoming-ti0-540-series) (registry code 41533, turbo-prop) (OpenAirDocs)
- Category: Airplane
- Serial number: 32-7340167
- Airframe hours: 4297
- Engines: 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

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 59; injuries: serious; 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

## 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 20110625013849A](https://openairdocs.org/incident/20110625013849A), Jun 25, 2011: Piper PA-32-300, Bridgeport, CT, Destroyed. On 6/25/11 at 2145 EDT N600DK a PA32-300 piloted by [privacy data omitted] a private pilot holding certificate number [privacy data omitted] struck the blast…

## Docket (6 files)

The files NTSB released with the investigation on September 27, 2011, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=80906. 2.5 MB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 597 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40350606&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF
- Pilot Interview Summary (item 2, .PDF, 103 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40351038&FileExtension=.PDF&FileName=Pilot%20Interview%20Summary-Master.PDF
- Correspondance with Operator (item 3, .PDF, 62 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40351040&FileExtension=.PDF&FileName=Correspondance%20with%20Operator-Redacted.PDF
- Bridgeport (BDR) Meteorological Observations (item 4, .PDF, 58 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40350608&FileExtension=.PDF&FileName=Bridgeport%20(BDR)%20Meteorological%20Observations%20-Master.PDF
- Photo 1 - Wreckage Overview (item 5, .PDF, 1.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40350630&FileExtension=.PDF&FileName=Photo%201%20-%20Wreckage%20Overview-Master.PDF
- Photo 2 - View of Blast Fence (item 6, .PDF, 250 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40350631&FileExtension=.PDF&FileName=Photo%202%20-%20View%20of%20Blast%20Fence-Master.PDF

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.