ECLIPSE AVIATION CORP EA500 near Danbury, CT — 2015-08-21
- Date
- 2015-08-21
- Location
- Danbury, CT, USA
- Airport
- DXR
- Aircraft
- ECLIPSE AVIATION CORP EA500
- Registration
- N120EA
- Category
- Airplane
- Highest injury
- Minor
- Fatalities
- 0
- Phase of flight
- Landing
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.
NTSB narrative
**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.
Analysis
- Primary failure mode
- Mechanical failure
- First missed decision gate
- Pilot could have initiated a go-around earlier when brakes felt ineffective.
NTSB coding
Evidence available
- FDR / data
- Photos
- 16 docket documents
Docket documents16
- Air Traffic Controller Statementatc
- Evidence Control Formform
- Performance Studyform
- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1form
- FAA Inspector Statementinterview
- Pilot Statementinterview
- Statement of Party Representatives to NTSB Investigationinterview
- Aircraft Data Recorder - Attachment 1 - Tabular Data (CSV)other
- Airplane Flight Manual Excerpt - Description of ABSother
- Brake Examinationother
- Brake Inoperative Emergency Procedureother
- Eclipse Modification Bulletinother
- Landing Distance Summaryother
- Memorandum for Record - Conversation with Pilotother
- Photo Array (Courtesy of Insurance Adjuster)photos
- Aircraft Data Recorder - Specialist's Factual Reportreport
Related mishaps
- JEREMY PRICE SMITH SUPER CUB
2026-07-19 · Allisonia, VA
- CESSNA 172S
2026-06-17 · DEATH VALLEY, CA
- PIPER PA 31P 350
2026-04-17 · Ardmore, OK
- CESSNA 180K
2026-03-27 · Beloit, KS
- CESSNA T210
2026-03-11 · Upland, CA
- FRANKEWICH WALTER S-21 OUTBOUND
2026-01-19 · Madisonville, TN