NTSB CAROL · Event
Event GAA16CA496
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 ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
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.
- NASA NTRS 2019 · Conference Paper
Crash Testing and Simulation of a Cessna 172 Aircraft: Pitch Down Impact Onto Soft Soil
During the summer of 2015, NASA Langley Research Center conducted three full-scale crash tests of Cessna 172 (C-172) aircraft at the NASA Langley Landing and Impact Research (LandIR) Facility.
- NASA NTRS 2019 · Technical Memorandum (TM)
Simulating the Impact Response of Three Full-Scale Crash Tests of Cessna 172 Aircraft
During the summer of 2015, a series of three full-scale crash tests were performed at the Landing and Impact Research Facility located at NASA Langley Research Center of Cessna 172 aircraft.
- NASA NTRS 2025 · Conference Paper
A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Flight Safety Foundation 2024 · FSF / AeroSafety World
Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
- Semantic Scholar 2022 · Article (Journal of Safety Research)
Go-around accidents and general aviation safety.
INTRODUCTION Changes in General Aviation (GA) accident rates, specifically in the go-around phase, are examined by comparing the number of accidents, the proportion of fatal accidents, and the proport…
- Semantic Scholar 2021 · Article (Aerospace)
Classification and Analysis of Go-Arounds in Commercial Aviation Using ADS-B Data
Go-arounds are a necessary aspect of commercial aviation and are conducted after a landing attempt has been aborted. It is necessary to conduct go-arounds in the safest possible manner, as go-arounds …
Browse the full corpus — academia portal ↗