Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

June 26, 2011 · Piper PA-32-300 · N600DK

Bridgeport, CT

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
June 26, 2011
Injury Outcomes
2 injuries (2 serious injuries)
Location
Bridgeport, CT
Aircraft
Piper PA-32-300
Tail Number
N600DK
Operator
Three Wing Flying Services
Injuries
Serious
Aircraft Damage
Substantial
NTSB Number
ERA11CA365

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

NTSB Probable Cause

Environmental issues-Physical environment-Object/animal/substance-Airport structure-Contributed to outcome

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

Flight

Event TypeAccident
Event Time21:45 EDT
Nearest AirportIgor Sikorsky Memorial Airport (0nm)
Runway24
Runway Length4677 ft
Runway Width150 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireGrd
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-32-300
Tail NumberN600DK
Aircraft CategoryAir
DamageSubstantial
OperatorThree Wing Flying Services
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · TIO-540 SER · Reciprocating · 310
Seats6

People & Injuries

Injury Summary2 injuries (2 serious injuries)
Fatal0
Serious2
Minor0
Uninjured0
Total2
Crew 1Age 59 · Third Class · Serious

Conditions

ConditionsVMC
LightNight
Wind200° @ 3 kt
Visibility8 sm
CeilingNone
Temperature / Dew Point70 F / 64 F
Altimeter29.86 inHg
Observation Time01:52
Weather SourceWFAC

Appendix: Source Data