Skip to content

Atlas / NTSB / GAA19CA582

NTSB CAROL · Event

Event GAA19CA582

2019-09-27 Mesa, Arizona, United States Airport · FFZ None 1 aircraft Status: Completed

Aircraft involved

Probable cause & findings

The pilot's decision to abort a go-around with insufficient runway remaining to safely stop the airplane, which resulted in a loss of control, runway excursion and impact with a concrete barrier.

Factual narrative

The pilot reported that, he intended to do touch-and-goes in the local traffic pattern. While on the downwind leg, the air traffic controller cleared him to land. During the landing roll, past the halfway point on the runway, he increased the engine power to full to takeoff and told the controller that he was doing a "go-around". The controller immediately instructed him to exit the runway on to the last taxiway so the pilot "cut the entire power", applied brakes and full right rudder, but the airplane skidded, exited the runway and impacted a concrete barrier. The airplane sustained substantial damage to the forward, lower fuselage. The flight safety officer reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The pilot added that he wanted to do touch and goes but did not accurately communicate his intentions to the air traffic controller. The pilot reported that, he intended to do touch-and-goes in the local traffic pattern.  While on the downwind leg, the air traffic controller cleared him to land.  During the landing roll, past the halfway point on the runway, he increased the engine power to full to takeoff and told the controller that he was doing a "go-around".  The controller immediately instructed him to exit the runway on to the last taxiway so the pilot "cut the entire power", applied brakes and full right rudder, but the airplane skidded, exited the runway and impacted a concrete barrier.    The airplane sustained substantial damage to the forward, lower fuselage.  The flight safety officer reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The pilot added that he wanted to do touch and goes but did not accurately communicate his intentions to the air traffic controller.  Source: NTSB Aviation Accident Database Retrieved: 2026-02-12

NTSB Findings

Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).

  • C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained - C
  • C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
  • C Personnel issues-Action/decision-Info processing/decision-Decision making/judgment-Pilot - C
  • Personnel issues-Task performance-Communication (personnel)-Accuracy of communication-Pilot

Verbatim from NTSB's published report. Source file NTSB_2019_GAA19CA582.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.

Related research

What the literature says.

Academic papers and agency reports matching this event's aircraft type or causal vocabulary (loss of control, runway excursion, go-around). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.

Browse the full corpus — academia portal ↗