Eclipse Aviation CORP EA500 accident near Danbury, Connecticut, August 21, 2015
On August 21, 2015 at about 6:20 pm local time, a 2008 Eclipse Aviation CORP EA500, registered N120EA, was substantially damaged in an accident near Danbury, Connecticut (Danbury Muni airport). It was a personal flight under general aviation rules (Part 91). 3 people had minor injuries. The weather was visual conditions (good weather).
Preview. This page is not yet listed for search engines.
The NTSB's probable cause their words, unchanged
The pilot's failure to attain the proper touchdown point and exceedance of the target touchdown speed, which resulted in a runway overrun.
Source: NTSB aviation accident database, copy made September 29, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 21, 2015 · about 6:20 pm local time
- Place
- Danbury, Connecticut · Danbury Muni · map
- Type
- Accident
- Injuries
- 3 people had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Eclipse Aviation CORP EA500 NO SERIES, built 2008 · all EA500s on the register
- Registration
- N120EA · registry record · serial 000199
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
**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.
The NTSB's narratives can run to many pages; this is the opening. Read the full report at the NTSB.
About this page
Everything above comes from the NTSB's public accident database and is rewritten in plain English only where the NTSB used codes; the probable cause and narrative are the NTSB's own words. This site never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number ERA15LA322.
