GAA16CA188
2016-04-06 · Payson, Arizona, United States · None · 1 aircraft · Status: Completed
Airport PAN
Current FAA registration · N5275S
- Make / Model
- CESSNA 172S
- Year of manufacture
- 2002 · 14 years old at event
- Engine
- LYCOMING IO-360-L2A (180 hp)
- Seats / Engines
- 4 seats · 1 engine
- Last airworthiness date
- 20021031
- ADS-B equipped
- Yes — Mode-S A6A607
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The student pilot's failure to maintain pitch control during the landing flare, resulting in the subsequent porpoise during landing and substantial damage to the firewall.
Factual narrative
According to the student pilot, during landing on his solo flight the airplane porpoised. He reported that after landing he repositioned the airplane, but prior to takeoff, a fellow pilot, who witnessed the porpoise, contacted him on the VHF radio, and informed him that he should have the airplane checked out before attempting to takeoff. The student pilot taxied to the parking area and the airport manager and airframe and powerplant mechanic inspected the airplane. The student pilot called his flight instructor and conveyed the situation and the level of damage. However, according to the flight instructor, the student pilot only conveyed the damage to the tail skid. The flight instructor reported that he told the student to confer with the mechanic and determine if the airplane was airworthy. The student pilot departed and proceeded to the airport where his flight school was based. Shortly after the departure, the airport manager that looked the airplane over for the student pilot, called the flight school and conveyed the gravity of the situation and informed the school that the airplane actually sustained damage to the firewall, tail skid and rudder fairing. The flight instructor did not confer with anyone other than the student pilot to ensure the airplane was airworthy. The airplane sustained substantial damage to the fire wall. The student pilot reported that there were no mechanical failures or anomalies with the airplane prior to or during the flight that would have prevented normal flight operation. According to the student pilot, during landing on his solo flight the airplane porpoised. He reported that after landing he repositioned the airplane, but prior to takeoff, a fellow pilot, who witnessed the porpoise, contacted him on the VHF radio, and informed him that he should have the airplane checked out before attempting to takeoff. The student pilot taxied to the parking area and the airport manager and airframe and powerplant mechanic inspected the airplane. The student pilot called his flight instructor and conveyed the situation and the level of damage. However, according to the flight instructor, the student pilot only conveyed the damage to the tail skid. The flight instructor reported that he told the student to confer with the mechanic and determine if the airplane was airworthy. The student pilot departed and proceeded to the airport where his flight school was based. Shortly after the departure, the airport manager that looked the airplane over for the student pilot, called the flight school and conveyed the gravity of the situation and informed the school that the airplane actually sustained damage to the firewall, tail skid and rudder fairing. The flight instructor did not confer with anyone other than the student pilot to ensure the airplane was airworthy. The airplane sustained substantial damage to the fire wall. The student pilot reported that there were no mechanical failures or anomalies with the airplane prior to or during the flight that would have prevented normal flight operation. 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-Pitch control-Not attained/maintained - C
- C Personnel issues-Task performance-Use of equip/info-Aircraft control-Student/instructed pilot - C
Verbatim from NTSB's published report. Source file
NTSB_2016_GAA16CA188.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. All research papers
- NASA NTRS 2023 · Reprint (Version printed in journal) Finite Element Simulation of Three Full-Scale Crash Tests for Cessna 172 Aircraft
The NASA Emergency Locator Transmitter Survivability and Reliability project was initiated in 2013 to assess the crash performance standards for the next generation of emergency locator transmitter (E…
- 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.
- Embry-Riddle Scholarly Commons 2023 · Conference paper Validation of Training Satisfaction Survey
The Training Satisfaction Survey (TSS) was developed as part of a larger project to examine the features of Virtual Reality software and supporting devices as a training program on visual illusions an…
- Semantic Scholar 2021 · Article (Data in Brief) Cockpit voice recorder transcript data: Capturing safety voice and safety listening during historic aviation accidents
Cockpit Voice Recorder (CVR) transcripts capture audio data within cockpit environments. This aids the investigation of causal factors contributing to aviation accidents by revealing communication and…
- Semantic Scholar 2021 · Article (Safety Science) Safety voice and safety listening during aviation accidents: Cockpit voice recordings reveal that speaking-up to power is not enough
Abstract Safety voice is theorised as an important factor for mitigating accidents, but behavioural research during actual hazards has been scant.