OpenAirDocs.org

20050402007769A

Accident · Substantial damage
Open the Markdown

FAA accident report · Piper PA31P350 · Danbury, CT · April 2, 2005

FAA Aviation Safety Information Portal

© OpenStreetMap
Date
April 2, 2005 · 12:00 local
Place
Danbury, CT
Airport
Danbury Municipal
Phase of flight
Final Approach-IFR
Operating rules
General operating rules (Part 91)
Damage
Substantial damage
Aircraft
N134DE
NTSB investigation
NTSBIAD05LA050
Reported as
Piper PA31P350
People aboard
1
Fatal injuries
0
Pilot’s flight hours
1,633 total24 in the last 90 days

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

(-23) The pilot privacy data omitted, PIC of N134DE was on the LOC 8 approach to Danbury, CT (dxr) when he descended below the approach minimums and hit trees. He was on an IFR flight plan in instrument meteorological conditions. The pilot privacy data omitted initiated a missed approach procedure at dxr, flew to islip, NY (isp), missed the approach, and then landed at farmingdale, NY (frg). There was substantial damage to the left and right wing leading edge. (-23 amendment) while on the LOC 8 approach to Danbury, CT (dxr), privacy data omitted PIC of N134DE, descended below minimums and hit trees before he went missed approach. He then proceeded to bridgeport, CT (bdr), conducted an instrument approach and went missed approach. From bdr he proceeded to islip, NY (isp), conducted an instrument approach and went missed approach. From isp he proceeded to farmingdale, NY (frg), conducted an instrument approach and landed. The pilot privacy data omitted was on an IFR flight plan in instrument meteorological conditions during the entire flight.

As the FAA filed it

(-23) THE PILOT ^PRIVACY DATA OMIT^, PIC OF N134DE WAS ON THE LOC 8 APPROACH TO DANBURY, CT (DXR) WHEN HE DESCENDED BELOW THE APPROACH MINIMUMS AND HIT TREES. HE WAS ON AN IFR FLIGHT PLAN IN INSTRUMENT METEOROLOGICAL CONDITIONS. THE PILOT ^PRIVACY DA^ INITIATED A MISSED APPROACH PROCEDURE AT DXR, FLEW TO ISLIP, NY (ISP), MISSED THE APPROACH, AND THEN LANDED AT FARMINGDALE, NY (FRG). THERE WAS SUBSTANTIAL DAMAGE TO THE LEFT AND RIGHT WING LEADING EDGE. (-23 AMENDMENT) WHILE ON THE LOC 8 APPROACH TO DANBURY, CT (DXR), ^PRIVACY DATA OMITTED^ PIC OF N134DE, DESCENDED BELOW MINIMUMS AND HIT TREES BEFORE HE WENT MISSED APPROACH. HE THEN PROCEEDED TO BRIDGEPORT, CT (BDR), CONDUCTED AN INSTRUMENT APPROACH AND WENT MISSED APPROACH. FROM BDR HE PROCEEDED TO ISLIP, NY (ISP), CONDUCTED AN INSTRUMENT APPROACH AND WENT MISSED APPROACH. FROM ISP HE PROCEEDED TO FARMINGDALE, NY (FRG), CONDUCTED AN INSTRUMENT APPROACH AND LANDED. THE PILOT ^PRIVACY DA^ WAS ON AN IFR FLIGHT PLAN IN INSTRUMENT METEOROLOGICAL CONDITIONS DURING THE ENTIRE FLIGHT.

NTSB investigation

The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.

NTSB IAD05LA050Accident · No injuriesLimited investigationFinal reportRidgefield, CTThe pilot's improper IFR procedure by flying below the minimum descent altitude, which resulted in the airplane striking trees.Apr 2, 2005 · Substantial damage