# NTSB GAA17CA122: Cessna 172, N10897, Punta Gorda, FL, January 12, 2017 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: January 12, 2017, 12:30 local (17:30 UTC) - Place: Punta Gorda, FL - Coordinates: 26.918888, -81.990837 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=26.9189&lon=-81.9908&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report August 22, 2017 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: FAA - NTSB case key (mKey): 94648 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA17CA122 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/94648/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=94648 - Page: https://openairdocs.org/ntsb/GAA17CA122 ## Probable cause The student pilot’s failure to maintain proper pitch control, which resulted in a hard, bounced landing. ## 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: Hard landing](https://openairdocs.org/ntsb-events/092) (defining event); cases with it: [Cessna 172S, 102 cases](https://openairdocs.org/ntsb-events/092/sequence.md?model=2072439), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md) ## Analysis The student pilot reported that, during his solo cross-country flight, he performed touch-and-go landings and takeoffs. The student pilot reported that there was a notice to airman identifying that the precision approach path indicator (PAPI) lighting was not in service at the second of three airports on his itinerary. The student pilot was cleared for a touch-and-go at the airport with no PAPI, and he reported that his landing was flat. He recalled that the airplane bounced but that he completed the touch-and-go and departed the airport for the final leg of his itinerary. He reported that he landed and shut down the airplane at his home airport, and "it was then that I noticed the bent prop tips. I immediately notified management." Further examination of the airplane by the operator revealed substantial damage to the firewall. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. ## Factual narrative The student pilot reported that during his solo cross-country flight, he performed touch and go landings and takeoffs. The student pilot reported that there was a notice to airman identifying that the precision approach path indicator (PAPI) lighting was not in service at the second of three airports on his itinerary. The student pilot was cleared for a touch and go at the airport with no PAPI and he reported that his landing was flat. He recalled that the airplane bounced but he completed the touch and go, and departed the airport for the final leg of his itinerary. He landed and shut down the airplane at his home airport, and "it was then that I noticed the bent prop tips. I immediately notified management." Further inspection of the airplane by the operator revealed substantial damage to the firewall. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. ## Aircraft - Registration: [N10897](https://openairdocs.org/aircraft/N10897), registered now, S/N 172S10606, built 2007 (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: 172S10606 - Year built: 2007 - Airframe hours: 5147.5 - Engines: LYCOMING IO-360-L2A 180 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: Paragon Flight Training Co - Registered owner: Paragon Flight Training Co - Airworthiness certificate: Standard, Normal - Last inspection: Continuous airworthiness, January 10, 2017 - Departed: PGD, Punta Gorda, FL - Destination: FMY, Fort Myers, FL - Flight plan: VFR - Airport: PGD, Punta Gorda Airport, runway 04, 7,193 × 150 ft, asphalt - Equipment: Electronic multifunction display, Electronic primary flight display ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 52; injuries: none; student; medical: class 2, with waivers/limitations; seat: left; restraint: 3-point; flight hours: 56.5 total, 56.5 in this make and model, 4.6 as pilot in command, 14.6 in the last 90 days, 6.3 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 100° at 7 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 79 °F, dew point 54 °F - Altimeter: 30.34 inHg - Observed at: PGD ## 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 20170112000319A](https://openairdocs.org/incident/20170112000319A), Jan 12, 2017: Cessna 172S, Punta Gorda, FL, Substantial damage. Student pilot on first cross country solo flight experienced a hard landing at pdg during a touch and go on runway 04. Pilot elected to in-route back to fmy… ## Docket (2 files) The files NTSB released with the investigation on August 7, 2017, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=94648. 1.6 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 1.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40454908&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Photo (Courtesy of FAA) (item 2, .PDF, 1 photo, 172 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40454909&FileExtension=.PDF&FileName=Photo%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.