# NTSB GAA16CA343: Cessna 172, N2473G, Frederick, MD, June 29, 2016 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: June 29, 2016, 08:45 local (12:45 UTC) - Place: Frederick, MD - Coordinates: 39.417499, -77.374443 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=39.4175&lon=-77.3744&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 December 5, 2016 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: FAA - NTSB case key (mKey): 93493 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA16CA343 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/93493/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=93493 - Page: https://openairdocs.org/ntsb/GAA16CA343 ## Probable cause The student pilot's failure to maintain pitch control during the touch down resulting in a bounced landing, subsequent hard 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 172R, 8 cases](https://openairdocs.org/ntsb-findings/01062022/cases.md?model=2072401), [All aircraft, 526 cases](https://openairdocs.org/ntsb-findings/01062022/cases.md) - [Performance/control parameters: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 172R, 37 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=2072401), [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/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 172R, 75 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072401), [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); cases with it: [Cessna 172R, 25 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=2072401), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md) - [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092) (defining event); cases with it: [Cessna 172R, 34 cases](https://openairdocs.org/ntsb-events/092/sequence.md?model=2072401), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md) ## Analysis The student pilot of the tricycle landing gear-equipped airplane reported that he executed a normal approach to the asphalt runway. He recalled that the airplane touched down on the main landing gear and bounced. He reported that when the airplane settled to the runway after it bounced, the nose gear struck the ground hard. The student pilot taxied the airplane to the ramp per the control tower's instruction and shut down. A post flight examination of the airplane by the flight school revealed substantial damage to the firewall. The student pilot reported that there were no mechanical malfunctions or anomalies with the airplane during the flight that would have prevented normal flight operations. ## Factual narrative The student pilot of the tricycle landing gear-equipped airplane reported that he executed a normal approach to the asphalt runway. He recalled that the airplane touched down on the main landing gear and bounced. He reported that when the airplane settled to the runway after it bounced, the nose gear struck the ground hard. The student pilot taxied the airplane to the ramp per the control tower's instruction and shut down. A post flight examination of the airplane by the flight school revealed substantial damage to the firewall. The student pilot reported that there were no mechanical malfunctions or anomalies with the airplane during the flight that would have prevented normal flight operations. ## Aircraft - Registration: [N2473G](https://openairdocs.org/aircraft/N2473G), registered now, S/N 17281019, built 2001 (OpenAirDocs) - Reported make and model: CESSNA 172 (R) - Registry model: [Cessna 172R](https://openairdocs.org/model/cessna-172r) (registry code 2072401) (OpenAirDocs) - Registry engine: [Lycoming IO-360-L2A](https://openairdocs.org/engine/lycoming-io-360-l2a) (registry code 41597, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17281019 - Year built: 2001 - Airframe hours: 9934.3 - Engines: LYCOMING IO-360-L2A 180 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: Frederick Flight Center - Registered owner: Rg Acquisitions LLC - Airworthiness certificate: Standard, Utility; Standard, Normal - Last inspection: 100 hour, June 1, 2016 - Departed: FDK, Frederick, MD - Destination: FDK, Frederick, MD - Airport: FDK, Frederick Muni, runway 30, 3,600 × 75 ft, asphalt - Equipment: None ## Flight crew As NTSB recorded them. NTSB leaves out names. - Student pilot; age 41; injuries: none; student; medical: class 3, without waivers/limitations; last flight review June 1, 2016; seat: left; restraint: 3-point; flight hours: 49 total, 32 in this make and model, 2 as pilot in command ## Weather - Conditions: Visual (VMC), Day - Wind: 320° at 7 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 73 °F, dew point 63 °F - Altimeter: 29.98 inHg - Observed at: KFDK ## 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 20160629010199A](https://openairdocs.org/incident/20160629010199A), Jun 29, 2016: Cessna 172R, Frederick, MD, Substantial damage. The pilot stated that at approximately 0845 on June 29, 2016 he was cleared for landing on runway 30 at Frederick Municipal Airport (kfdk) while on a solo… ## Docket (2 files) The files NTSB released with the investigation on November 3, 2016, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=93493. 7.7 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 7.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40446073&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Photo (Courtesy of FAA) (item 2, .PDF, 1 photo, 332 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40446074&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.