# NTSB GAA16CA188: Cessna 172, N5275S, Payson, AZ, April 6, 2016 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: April 6, 2016, 08:45 local (15:45 UTC) - Place: Payson, AZ - Coordinates: 34.256942, -111.339164 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=34.2569&lon=-111.3392&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report July 14, 2016 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: FAA - NTSB case key (mKey): 92997 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA16CA188 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/92997/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=92997 - Page: https://openairdocs.org/ntsb/GAA16CA188 ## Probable cause 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. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: pitch control](https://openairdocs.org/ntsb-findings/01062022): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 172S, 26 cases](https://openairdocs.org/ntsb-findings/01062022/cases.md?model=2072439), [All aircraft, 526 cases](https://openairdocs.org/ntsb-findings/01062022/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Student/instructed pilot (probable cause); cases with it: [Cessna 172S, 206 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072439), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) (defining event); cases with it: [Cessna 172S, 77 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=2072439), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md) ## Analysis 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. ## 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. ## Aircraft - Registration: [N5275S](https://openairdocs.org/aircraft/N5275S), registered now, S/N 172S9203, built 2002 (OpenAirDocs) - Reported make and model: CESSNA 172 (S) - Registry model: [Cessna 172S](https://openairdocs.org/model/cessna-172s) (registry code 2072439) (OpenAirDocs) - Registry engine: [Lycoming IO-360-L2A](https://openairdocs.org/engine/lycoming-io-360-l2a) (registry code 41597, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 172S9203 - Year built: 2002 - Airframe hours: 9244 - Engines: LYCOMING IO-360-L2A 180 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: Westwind School of Aeronautics - Registered owner: Westwind Aero Group LLC - Airworthiness certificate: Standard, Normal; Standard, Utility - Last inspection: 100 hour, March 30, 2016 - Departed: DVT, PHOENIX, AZ - Destination: PAN, Payson, AZ - Airport: PAN, Payson, runway 06, 5,504 × 75 ft, asphalt - Equipment: Stall warning system ## Flight crew As NTSB recorded them. NTSB leaves out names. - Student pilot; age 30; injuries: none; student; medical: class 1, with waivers/limitations; seat: left; restraint: 3-point; flight hours: 75 total, 75 in this make and model, 4 as pilot in command, 35.2 in the last 90 days, 13.1 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 20° at 9 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 61 °F, dew point 9 °F - Altimeter: 30.37 inHg - Observed at: KPAN ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20160406008689A](https://openairdocs.org/incident/20160406008689A), Apr 6, 2016: Cessna 172S, Payson, AZ, Substantial damage. On March 6, 2016 the student pilot was on a solo cross country from deer valley airport (dvt) to pason airport (pan) with a return to dvt. During the landing… ## Other investigations on N5275S (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB WPR11CA440](https://openairdocs.org/ntsb/WPR11CA440), Sep 8, 2011: Cessna 172 (N5275S), Phoenix, AZ, substantial damage. Probable cause: The pilot's failure to maintain directional control during the landing roll. ## Docket (2 files) The files NTSB released with the investigation on June 14, 2016, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=92997. 1.3 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 1.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40441247&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Photos (Courtesy of FAA) (item 2, .PDF, 2 photos, 223 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40441248&FileExtension=.PDF&FileName=Photos%20(Courtesy%20of%20FAA)-Master.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.