# NTSB IAD05LA050: Piper PA-31P-350, N134DE, Ridgefield, CT, April 2, 2005

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Limited investigation · Final report
- Date: April 2, 2005, 12:10 local (17:10 UTC)
- Place: Ridgefield, CT
- Coordinates: 41.36222, -73.526107
- Nearby events: https://openairdocs.org/map.md?lat=41.3622&lon=-73.5261&mi=10
- Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report October 27, 2005
- Report: Approved by Office Director
- Parties: FAA FSDO-03
- NTSB case key (mKey): 61391
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=IAD05LA050
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/61391/pdf
- Page: https://openairdocs.org/ntsb/IAD05LA050

## Probable cause

The pilot's improper IFR procedure by flying below the minimum descent altitude, which resulted in the airplane striking trees.

## Sequence of events

In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf).

- In flight collision with object, approach - faf/outer marker to threshold (ifr)
  - object - tree(s)
  - ifr procedure - not complied with, pilot in command (cause)
  - minimum descent altitude - not maintained, pilot in command (cause)

## Analysis

Prior to departing on the accident flight, a mechanic, who was to perform work on the airplane advised the owner/pilot that the weather was below landing minimums and he should not attempt the trip. During a localizer approach at the airport, the airplane impacted trees that were located west of the approach end of the runway.  After executing a missed approach  the pilot advised ATC that he had bird strikes on both wings and that it looked like the de-icing boots were damaged.  A local resident who witnessed the event stated that "the scraping sound of branches against metal was audible, and I saw the upper branches of the pine trees waving after contact with the plane."  The trees  were located at a terrain elevation of 599 feet above sea level.  The minimum descent altitude for the approach was published as 1,100 feet.

## Factual narrative

On April 2, 2005, about 1210 eastern standard time, a Piper PA-31P-350, N134DE, was substantially damaged when it struck trees in Ridgefield, Connecticut, while on an instrument approach to Danbury Municipal Airport (DXR), Danbury, Connecticut.  The certificated commercial pilot/owner was not injured.  Instrument meteorological conditions prevailed, and an instrument flight rules (IFR) flight plan was filed for the flight that departed East Hampton Airport (HTO), East Hampton, New York.  The personal flight was conducted under 14 CFR Part 91.

According to a mechanic, the purpose of the flight was to reposition the airplane to Danbury, Connecticut to replace a propeller de-icing boot. Prior to departing East Hampton, the mechanic advised the pilot that the weather was below landing minimums, and he should not attempt the trip.

Radar plot data and air traffic control (ATC) transcripts obtained from the Federal Aviation Administration (FAA) revealed that the pilot departed East Hampton, New York, on an IFR flight plan, destined for Danbury, Connecticut. After departure, the pilot initially climbed to 4,000 feet msl and proceeded direct to Bridgeport, Connecticut. A while later, the pilot was given radar vectors to the Localizer Runway 8 approach at Danbury. He crossed the final approach fix at approximately 2,200 feet msl and initiated his descent on the localizer where the last radar return during the descent was recorded at 1,200 feet msl. The altitude readout was then lost by ATC and later reacquired during the missed approach. He then climbed up to an altitude of 3,000 feet msl and advised ATC that he had bird strikes on both wings and that it looked like the de-icing boots were damaged.

The pilot then asked ATC about weather conditions at the Francis S. Gabreski Airport (FOK), Westhampton Beach, New York; however, the reported weather was below landing minimums. ATC then offered the pilot a choice of two other airports that might be suitable for an instrument approach and landing but he advised them that he would then have to "arrange alternate transportation."  He then proceeded to Long Island Mac Arthur Airport (ISP), Islip, New York and flew the instrument landing system (ILS) approach for runway 24. He was unable to land, executed another missed approach, and proceeded to Republic Airport (FRG) Farmingdale, New York where he was able to perform the ILS Runway 14 approach, and land.

A statement from a local resident revealed that an airplane had struck trees that were located west of the approach end of runway 08 at the Danbury Municipal Airport.  The witness stated that "the scraping sound of branches against metal was audible, and I saw the upper branches of the pine trees waving after contact with the plane."

Topographical data for the local area showed that the trees mentioned in the witness's statement were located at a terrain elevation of 599 feet above sea level.  The minimum descent altitude for the Localizer Runway 8 approach was published as 1,100 feet, and the Danbury Municipal Airport was located at a field elevation of 458 feet.

According to a witness statement, on April 4, 2005, the airplane was flown without a special flight permit from Farmingdale, New York, to Danbury, Connecticut. An airframe and powerplant mechanic advised the pilot that he was unable to repair the airplane in a reasonable amount of time, as the wing skins would require replacement. He suggested that the repair work could be accomplished at two other locations, one of which was in Hagerstown, Maryland.

On April 9,2005 the airplane was flown to Hagerstown, Maryland.

According to an FAA inspector, on April 21, 2005, while inspecting other airplanes located at the Hagerstown Regional Airport (HGR), Hagerstown, Maryland, his attention was drawn to an airplane that appeared to be substantially damaged. Closer inspection by the inspector revealed the presence of wood imbedded in some of the screw heads, joint overlaps, and inspection plates. He was later informed by a mechanic that the airplane had been flown into the airport without a special flight permit.

On May 18, 2005, the airplane was inspected by the Safety Board in Hagerstown, Maryland. The inspection revealed that the airplane had sustained impact damage to both wings, the ailerons, horizontal stabilizers and elevators. The left and right side de-ice boots exhibited scrape marks and tears, the left wing gap fairing was cracked, the left engine exhaust shield exhibited crush marks and the left cowling was wrinkled. The navigation light for the right wing was broken, and numerous antennas were damaged.

The recorded weather at the Danbury Municipal Airport, at 1224, included: winds from 080 degrees at 9 knots; visibility 2 1/2 statute miles in light rain and mist; ceiling overcast at 200 feet; temperature 46 degrees Fahrenheit; dew point 46 degrees Fahrenheit; altimeter setting 29.64 inches of mercury.

## Aircraft

- Registration: N134DE (not matched to a registry record)
- Reported make and model: Piper PA-31P-350
- Category: Airplane
- Serial number: 31P-8414005
- Airframe hours: 2650
- Engines: Lycoming TIO-540-V2AD 350 horsepower reciprocating; Lycoming TIO-540-V2AD 350 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Airworthiness certificate: Standard, Normal
- Last inspection: Continuous airworthiness, February 1, 2005, 35 hours before
- Departed: HTO, East Hampton, NY
- Destination: DXR, Danbury, CT
- Flight plan: IFR
- Airport: DXR, Danbury Municipal Airport, runway 8, 4,422 × 150 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 46; injuries: none; commercial; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; last flight review January 1, 2004; seat: left; flight hours: 1,633 total, 695 in this make and model, 1,595 as pilot in command, 25 in the last 90 days, 16 in the last 30 days

## Weather

- Conditions: Instrument (IMC), Day
- Wind: 80° at 9 knots
- Visibility: 2.5 statute miles
- Lowest ceiling: 200 ft overcast
- Temperature: 46 °F, dew point 46 °F
- Altimeter: 29.63 inHg
- Observed at: DXR, 2 nm away

## 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 20050402007769A](https://openairdocs.org/incident/20050402007769A), Apr 2, 2005: Piper PA31P350, Danbury, CT, Substantial damage. (-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…

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.
