ERA15CA154
2015-03-04 · Monroe, North Carolina, United States · None · 1 aircraft · Status: Completed
Airport EQY
Aircraft involved
Probable cause & findings
The pilot's failure to maintain a proper glidepath and failure to perform a go-around once a safe landing could not accomplished, which resulted in a landing area overshoot and runway excursion.
Factual narrative
The pilot had initially intended to perform a GPS approach to runway 23, into the wind; however, the weather was below minimums for that approach and he then elected to perform an instrument landing system (ILS) approach in the opposite direction to runway 5. While about 100 feet above decision height for the ILS approach to runway 5, the pilot did not have the runway environment in sight and started to make the motions to go-around, but did not increase engine power. He then observed the runway centerline markings and due to excess speed and a tailwind, the airplane floated and landed long. When asked about the touchdown point location and speed at touchdown, the pilot estimated it was about 1,000 feet before the departure end of the 7,001-foot-long runway, at a speed of 85 knots. He applied the brakes, but the runway was wet and he did not feel deceleration. He left the flaps fully extended as the airplane traveled off the end of the runway, coming to rest upright in a grass area. The pilot added that there were no preimpact mechanical malfunctions with the airplane. The recorded weather at the airport, about the time of the accident, included an 11-knot tailwind. Examination of the wreckage by a Federal Aviation Administration inspector revealed damage to the landing gear and lower fuselage. The pilot had initially intended to perform a GPS approach to runway 23, into the wind; however, the weather was below minimums for that approach and he then elected to perform an instrument landing system (ILS) approach in the opposite direction to runway 5. While about 100 feet above decision height for the ILS approach to runway 5, the pilot did not have the runway environment in sight and started to make the motions to go-around, but did not increase engine power. He then observed the runway centerline markings and due to excess speed and a tailwind, the airplane floated and landed long. When asked about the touchdown point location and speed at touchdown, the pilot estimated it was about 1,000 feet before the departure end of the 7,001-foot-long runway, at a speed of 85 knots. He applied the brakes, but the runway was wet and he did not feel deceleration. He left the flaps fully extended as the airplane traveled off the end of the runway, coming to rest upright in a grass area. The pilot added that there were no preimpact mechanical malfunctions with the airplane. The recorded weather at the airport, about the time of the accident, included an 11-knot tailwind. Examination of the wreckage by a Federal Aviation Administration inspector revealed damage to the landing gear and lower fuselage. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
FAA avdata. C = Cause, F = Factor.
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Descent/approach/glide path-Not attained/maintained - C
- C Personnel issues-Action/decision-Action-Incorrect action selection-Pilot - C
Verbatim from NTSB's published report. Source file
NTSB_2015_ERA15CA154.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗
Related research
Matched on aircraft type or causal vocabulary (runway excursion, go-around). All research papers
- NASA NTRS 2011 · Conference Paper Joint thunderstorm operations using the NASA F-106B and FAATC/AFWAL Convair 580 airplanes
During the 1985 thunderstorm season, three joint thunderstorm research flights were conducted within 100 n.mi. of NASA Langley by the NASA Storm Hazards F-106B and the FAA/USAF CV-580 research airplan…
- NTSB Aircraft Accident Reports 2004 · Accident report In-Flight Separation of Vertical Stabilizer — American Airlines Flight 587
American Airlines 587 (A300-605R) Belle Harbor, NY, November 12, 2001 — 265 fatalities. Investigation of the post-takeoff in-flight breakup of American 587 over Belle Harbor.
- NASA NTRS 2024 · Presentation American Airlines Flight 587 Crash Investigation: NASA Langley Research Center Participation and Perspective
- NASA NTRS 2019 · Other Documentation for Three Wake Vortex Model Data Sets from Simulation of Flight 587 Wake Vortex Encounter Accident Case
This document contains a general description for data sets of a wake vortex system in a turbulent environment. The turbulence and thermal stratification of the environment are representative of the co…
- NASA NTRS 2016 · Conference Paper An overview of SAE ARP 1587: Aircraft gas turbine engine monitoring system guide
A systematic approach to developing an engine monitoring system (EMS) is outlined. An extensive shopping list of EMS capabilities and benefits are included.
- SKYbrary (Eurocontrol) 2024 · SKYbrary article Runway Excursion — SKYbrary Knowledge Base
SKYbrary runway excursion review — RE-OE (overruns) + RE-LO (lateral). Risk drivers: long landing, high approach speed, contaminated surface, tailwind, mis-set autobrakes.