# Accident 20160406008689A: Cessna 172S, Payson, AZ, April 6, 2016 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: April 6, 2016, 09:45 local time - Place: Payson, AZ - Damage: Substantial damage - Phase of flight: Landing: Touchdown - Operating rules: General operating rules (Part 91) - Location: 34.2569° N, 111.3392° W: From the FAA - Nearby events: https://openairdocs.org/map.md?lat=34.2569&lon=-111.3392&mi=10 - Aircraft: N5275S, registered now (https://openairdocs.org/aircraft/N5275S) (OpenAirDocs) - Registry model: Cessna 172S (registry code 2072439, https://openairdocs.org/model/cessna-172s) (OpenAirDocs) - Registry engine: Lycoming IO-360-L2A (registry code 41597, https://openairdocs.org/engine/lycoming-io-360-l2a) (OpenAirDocs) - Reported make and model: CESSNA 172S - Reported engine: LYCOMING IO-360-L2A - People aboard: 1 - Fatal injuries: 0 - Other injuries: 0 - Pilot certificates: Private pilot - Pilot flight hours: 65 total, 65 in this make and model, 32 in the last 90 days - NTSB investigation: [NTSB GAA16CA188](https://openairdocs.org/ntsb/GAA16CA188) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20160406008689A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. 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 THE STUDENT PILOT HAD A HARD LANDING THAT LEAD TO DAMAGE OF THE FAIRING LOCATED ON THE LOWER RUDDER, TAIL TIE DOWN HOOK, DAMAGE TO THE TAIL SKID AND FIREWALL. PILOT WITNESSES REPORTED THAT THE AIRCRAFT PERFORMED AN ABNORMALLY HIGH APPROACH LEADING TO A HIGH SPEED LANDING. THE WITNESSES ALSO REPORTED THE AIRCRAFT STARTED TO PORPOISE AND THAT THE AIRCRAFT ULTIMATELY LANDED ON THE NOSE WHEEL. WITNESSES STATED THAT THE AIRCRAFT TAXIED BACK TO PERFORM ANOTHER TAKEOFF. DURING THE TAKEOFF A PILOT IN ANOTHER AIRCRAFT RADIOED TO THE STUDENT THAT THE AIRCRAFT HAD A HARD LANDING AND THAT HE SHOULD HAVE THE AIRCRAFT LOOKED AT. THE STUDENT REJECTED THE TAKEOFF, CLEARED THE RUNWAY AND TAXIED TO THE FBO RAMP. MECHANICS AT THE AIRPORT DID AN INSPECTION OF THE AIRCRAFT OF BOTH THE TAIL SECTION AND INSPECTED THE FIREWALL BY OBSERVING THROUGH THE OIL ACCESS DOOR. THE MECHANIC STATED THAT THE STUDENT WAS INFORMED OF THE DAMAGE AND THAT HE SHOULD CONTACT THE SCHOOL. THE STUDENT CONTACTED THE INSTURCTOR WHO REQUESTED THAT THE STUDENT SEND PICTURES OF THE DAMAGE. THE STUDENT INITALY SENT A PICTURE OF THE NOSE WHEEL SECTION. THE INSTRUCTOR TEXT THE STUDENT THAT HE WAS NOT INTERESTED IN THE NOSE WHEEL SECTION AND THAT HE WANTED PICUTRES OF THE TAIL SECTION. THE INSTRUCTOR STATED THE STUDENT NEVER INDICATED TO HIM THAT THERE WAS DAMAGE TO THE FIREWALL. AFTER THE INSTRUCTOR REVIEWED THE PICTURES HE ASKED THE STUDENT TO BEND BACK THE TAIL SKID AND TO RETURN THE AIRCRAFT BACK TO DVT. THE STUDENT STATED HE WAS SHOOK UP AND THAT HE WAS CONCERNED ABOUT FLYING THE AIRCRAFT BACK. WITNESSES AT THE AIRPORT CLAIMED THE STUDENT APPEARED TO BE VISABLY DISTRAT. THE INSTRUCTOR ASSURED THE STUDENT THAT HE WOULD BE FINE FOR THE RETURN FLIGHT. THE STUDENT FLEW THE AIRCRAFT BACK TO DVT. THE MECHANIC AT PAN CONTACTED THE MAINTENANCE DEPARTMENT OF THE SCHOOL AND REPORTED THE DAMAGE TO THE TAIL SECTION AND THE FIREWALL. THE CHIEF INSTRUCTOR STATED THAT THE STUDENT DID NOT STATE THERE WAS ANY DAMAGE TO THE FIREWALL AND THEIR ONLY KNOWLEDGE OF THE DAMAGE WAS FROM THE PHONE CALL THEY RECEIVED FROM THE MECHANIC IN PAN. ## The NTSB's investigation of this event (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 GAA16CA188](https://openairdocs.org/ntsb/GAA16CA188), Apr 6, 2016: Cessna 172 (N5275S), Payson, AZ, substantial damage. 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. ## Other reports on N5275S (3) Matched to the same aircraft by N-number and date. - [Incident 20170726015289I](https://openairdocs.org/incident/20170726015289I), Jul 26, 2017: Cessna 172S (N5275S), Phoenix, AZ, Minor damage. Bird strike reported while doing pattern work for runway 25L, dvt. Large bird struck left wing 5 inches inboard causing significant dent in between ribs, no… - [Incident 20130615009559I](https://openairdocs.org/incident/20130615009559I), Jun 15, 2013: Cessna 172S (N5275S), Phoenix, AZ, No damage. N5275S landed runway 25L at Phoenix Deer Valley Airport (kdvt). Upon landing, the aircraft veered to the right side of the runway onto the gravel infield. The… - [Accident 20110908025169A](https://openairdocs.org/incident/20110908025169A), Sep 8, 2011: Cessna 172S (N5275S), Phoenix, AZ, Substantial damage. Private pilot lost control of aircraft during touchdown and landing rollout. This resulted in substantial damage to the aircraft. No mechanical issues were… From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record. --- 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.