Skip to content

Atlas / NTSB / GAA18CA228

NTSB CAROL · Event

Event GAA18CA228

2018-04-17 Ashland, Virginia, United States Airport · OFP None 1 aircraft Status: Completed

Aircraft involved

Probable cause & findings

The student pilot’s improper landing flare and the flight instructor’s delayed remedial action, which resulted in a hard landing.

Factual narrative

The flight instructor reported that, while the airplane was in the landing flare for a touch and go landing, the student pilot allowed the airspeed to become too low and he instructed the student to perform a go around. The student applied full power and retracted the flaps, but the airplane continued to descend, so the instructor "got on the controls with him". During the go-around the airplane touched down on the runway hard, bounced, and the instructor reported hearing a "ping" and observed that the right main landing gear was no longer attached. The instructor continued the go-around and entered the traffic pattern and during the approach observed the right main landing gear laying on the right side of the runway. He landed and the airplane veered to the right off of the runway. The airplane sustained substantial damage to the fuselage. The flight instructor reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The automated weather observation station located on the airport reported that, about 36 minutes before the accident, the wind was from 250° at 9 knots. The airplane landed on runway 34. The flight instructor reported that, while the airplane was in the landing flare for a touch-and-go landing, the student pilot allowed the airspeed to become too low, and he instructed the student to perform a go around. The student applied full power and retracted the flaps, but the airplane continued to descend, so the instructor "got on the controls with him." During the go-around, the airplane touched down on the runway hard, bounced, and the instructor reported hearing a "ping" and observed that the right main landing gear was no longer attached. The instructor continued the go-around and entered the traffic pattern; during the approach, he observed the right main landing gear laying on the right side of the runway. He landed the airplane and it veered to the right off of the runway. The airplane sustained substantial damage to the fuselage. The flight instructor reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The automated weather observation station located on the airport reported that, about 36 minutes before the accident, the wind was from 250° at 9 knots. The airplane landed on runway 34. 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-Landing flare-Not attained/maintained - C
  • C Personnel issues-Task performance-Use of equip/info-Aircraft control-Student/instructed pilot - C
  • C Personnel issues-Task performance-Use of equip/info-Aircraft control-Instructor/check pilot - C
  • C Personnel issues-Action/decision-Action-Delayed action-Instructor/check pilot - C
  • Environmental issues-Conditions/weather/phenomena-Wind-Crosswind-Effect on operation

Verbatim from NTSB's published report. Source file NTSB_2018_GAA18CA228.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 (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 ↗