The U.S. aircraft register, updated daily
Accidents · NTSB ERA15LA322 · Final report

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 during landing (landing roll) 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).

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 November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
August 21, 2015 · about 6:20 pm local time · cases in 2015
Place
Danbury, Connecticut · Danbury Muni · cases near this airport · 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 complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Landing area overshoot during landing (flare/touchdown)
  2. Runway excursion during landing (landing roll) defining event
  3. Collision with terrain or object (not controlled flight into terrain) during landing

The NTSB's findings

  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Not attained/maintained
  • Environmental issues › Physical environment › Object/animal/substance › (general) › Contributed to outcome

Pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; single-engine land; single-engine sea; instrument: airplane
  • Flight time: 7,846 hours in all; 1,111 in this make and model; 43 in the last 90 days; 6 in the last 30 days; 7,846 as pilot in command
  • Last flight review: March 27, 2015
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: minor injuries

The aircraft

  • Airframe total time: 858.1 hours
  • Last inspection: annual inspection, May 26, 2015
  • Maximum gross weight: 5,995 lb
  • Seats: 6
  • Landing gear: retractable
  • Engine 1: P&W Canada PW610F-A (turbofan); 858 hours total
  • Engine 2: P&W Canada PW610F-A (turbofan); 858 hours total
  • Operator: Uf Equipment LLC

The flight

  • Departed from: OSH Oshkosh WI at 4:20 pm
  • Destination: DXR Danbury CT
  • Flight plan: IFR
  • Runway 26, 4,422 ft by 150 ft

Weather at the time

  • Light: daylight
  • Wind: from 350° at 6 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 82°F (28°C), dew point 61°F (16°C)
  • Altimeter: 30.04 inHg
  • Observation at 6:25 pm from DXR

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers2

Documents from the investigation the NTSB's docket: the evidence folder behind the report

16 documents, released by the NTSB on January 8, 2018. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/ERA15LA322.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.