Crash of an Eclipse EA500 in Danbury

Date & Time: Aug 21, 2015 at 1420 LT
Type of aircraft:
Operator:
Registration:
N120EA
Flight Type:
Survivors:
Yes
Schedule:
Oshkosh – Danbury
MSN:
199
YOM:
2008
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7846
Captain / Total hours on type:
1111.00
Aircraft flight hours:
858
Circumstances:
**This report was modified on April 2, 2020. Please see the public docket for this accident to view the original report.**
After the airplane touched down on the 4,422-ft-long runway, the airline transport pilot applied the brakes to decelerate; however, he did not think that the brakes were operating. He continued "pumping the brakes" and considered conducting a go-around; however, there was insufficient remaining runway to do so. The airplane subsequently continued off the end of the runway, impacted a berm, and came to rest upright, which resulted in substantial damage to the right wing. During postaccident examination of the airplane, brake pressure was obtained on both sets of brake pedals when they were depressed, and there was no bleed down or reduction in pedal firmness when the brakes were pumped several times. Examination revealed no evidence off any preimpact anomalies with the brake system that would have precluded normal operation. In addition, the pilot indicated that he was not aware of and was not trained on the use of the ALL INTERRUPT button, which is listed as a step in the Emergency Procedures section of the airplane flight manual and is used to disable the anti-skid brake system functions and restore normal braking when the brakes are ineffective; thus, the pilot did not follow proper checklist procedures. According to data downloaded from the airplane's diagnostic storage unit (DSU), the airplane touched down 1,280 ft beyond the runway threshold, which resulted in 2,408 ft of runway remaining (the runway had a displaced threshold of 734 ft) and that it traveled 2,600 ft before coming to rest about 200 ft past the runway. The airplane's touchdown speed was about 91 knots. Comparing DSU data from previous downloaded flights revealed that the airplane's calculated deceleration rate during the accident landing was indicative of braking performance as well as or better than the previous landings. Estimated landing distance calculations revealed that the airplane required about 3,063 ft when crossing the threshold at 50 ft above ground level. The target touchdown speed was 76 knots. However, the airplane touched down with only 2,408 ft of remaining runway faster than the target touchdown speed, which resulted in the runway overrun.
Probable cause:
The pilot's failure to attain the proper touchdown point and exceedance of the target touchdown speed, which resulted in a runway overrun.
Final Report:

Crash of a Piper PA-61 Aerostar (Ted Smith 601) near Penn Yan

Date & Time: Oct 28, 2007 at 1330 LT
Operator:
Registration:
N717SB
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Rochester – Danbury
MSN:
61-0808-8063418
YOM:
1980
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2413
Captain / Total hours on type:
1683.00
Aircraft flight hours:
2619
Circumstances:
The private pilot was continuing a cross-country flight after having stopped for fuel. About 20 minutes into the flight, the pilot said both engines started running rough, and he turned the airplane toward the nearest airport and descended. The pilot reported that he did not think the airplane would make it to the airport, and that due to the rugged terrain, he felt it was better to ditch the airplane in a large lake he was flying over. The pilot reported there were no mechanical anomalies prior to the loss of engine power. He said he felt that fuel contamination was the cause of the engine problem, and that not fueling during heavy rain might have prevented the problem. Fuel samples were taken from the fuel supply where he added fuel, and the equipment used to fuel the airplane. No other instances of fuel contamination were reported, and according to the FAA inspector the fuel samples were tested, and found to be clean. The airplane was not recovered from the lake, and has not been examined by the NTSB.
Probable cause:
The loss of engine power during cruise flight for an undetermined reason.
Final Report:

Crash of a Piper PA-60P Aerostar (Ted Smith 602P) in Danbury: 1 killed

Date & Time: Apr 12, 1995 at 1327 LT
Registration:
N602PC
Flight Type:
Survivors:
Yes
Schedule:
Washington DC – Danbury
MSN:
62-0861-8165002
YOM:
1981
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
1486
Captain / Total hours on type:
481.00
Aircraft flight hours:
3253
Circumstances:
After making a localizer runway 08 approach, the pilot landed over halfway down the 4,422 feet wet runway. He then decided to abort the landing, added power, and when airborne, retracted the landing gear. He said he asked the right front seat (non-rated) passenger to reset the flaps (to 20°). The pilot saw trees ahead, and realized the airplane was not going to clear the obstacles, though full power was applied. Just before impact, he pulled back on the elevator control to soften the impact, rather than hitting the trees nose first. After the accident, the wing flaps were found in the retracted position. A passenger was killed and three other occupants were seriously injured.
Probable cause:
The pilot's delay in initiating a go-around (aborted landing) and failure to assure that the flaps were properly reset for the go-around. Factors relating to the accident were: the pilot's failure to achieve the proper touchdown point for landing, the wet runway condition, and the proximity of tree(s) to the runway.
Final Report:

Crash of a Piper PA-60 Aerostar (Ted Smith 601P) in North Salem: 2 killed

Date & Time: Dec 30, 1991 at 0748 LT
Registration:
N36362
Flight Type:
Survivors:
No
Schedule:
Clarksville – Danbury
MSN:
60-0787-8063400
YOM:
1980
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
2700
Aircraft flight hours:
1624
Circumstances:
The pilot was on a personal trip that he had flown many times. On the day of the accident, additional fuel was not available at the departure airport. As he neared his destination, the pilot left one of his engines in a fuel crossfeed configuration causing a partial power loss. The airplane has the capability to climb at more than 500 feet per minute using only one engine. After declaring his emergency to the control tower, radio contact was lost. The aircraft was observed flying 90° to the ILS final approach course at very low altitude banking side to side. The airplane crashed in a 70° nose down position. Heavy snow had started falling just before the accident. A post crash fire destroyed much of the airplane. Both occupants were killed.
Probable cause:
A loss of control due to a distraction caused by a partial loss of power. Contributing to the accident was adverse weather near the destination airport.
Final Report: