Skip to content

Atlas / NTSB / GAA16CA496

NTSB CAROL · Event

Event GAA16CA496

2016-08-30 Delta, Utah, United States Airport · DTA None 1 aircraft Status: Completed

Aircraft involved

Probable cause & findings

The student pilot’s improper landing flare, which resulted in a hard, porpoised landing.

Factual narrative

According to the student pilot, following the first leg of his solo cross-country flight, he entered the traffic pattern to land on runway 17; "because other traffic was using runway 17 even though winds were 050° at 3 knots". He reported that as the airplane approached the runway, the airspeed was too high, and the airplane landed hard on the nose wheel and porpoised. He conceded, "I knew it was a hard landing, but did not hear the prop strike occur." The student pilot departed the airport, and accomplished two approaches and a landing at a third airport, before returning to his home airport where he accomplished two approaches, a landing, and then taxied to parking. The student pilot reported that he could have prevented the accident by performing a go around when he realized that his approach speed was too high. The airplane sustained substantial damage to the firewall. The student pilot reported that there were no mechanical malfunctions or anomalies with the engine or airframe prior to the landing that would have prevented normal flight operation. According to the student pilot, following the first leg of his solo cross-country flight, he entered the traffic pattern to land on runway 17 "because other traffic was using runway 17 even though winds were 050° at 3 knots." He reported that, as the airplane approached the runway, the airspeed was too high, and the airplane landed hard on the nosewheel and porpoised. He conceded, "I knew it was a hard landing, but did not hear the prop strike occur." The student pilot departed the airport and accomplished two approaches and a landing at a third airport before returning to his home airport where he accomplished two approaches, a landing, and then taxied to parking. The student pilot reported that he could have prevented the accident by performing a go-around when he realized that his approach speed was too high. The airplane sustained substantial damage to the firewall. The student pilot reported that there were no mechanical malfunctions or anomalies with the engine or airframe that would have prevented normal operation. 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 Personnel issues-Task performance-Use of equip/info-Aircraft control-Student/instructed pilot - C
  • C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Landing flare-Not attained/maintained - C
  • Environmental issues-Conditions/weather/phenomena-Wind-Tailwind-Effect on equipment

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