# NTSB GAA16CA064: Cessna 172, N52632, Gaithersburg, MD, November 24, 2015 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: November 24, 2015, 10:00 local (15:00 UTC) - Place: Gaithersburg, MD - Coordinates: 39.170833, -77.169441 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=39.1708&lon=-77.1694&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 March 14, 2016 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: Federal Aviation Administration - NTSB case key (mKey): 92378 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA16CA064 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/92378/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=92378 - Page: https://openairdocs.org/ntsb/GAA16CA064 ## Probable cause The student pilot's improper flare during landing, which resulted in a bounced landing, and a runway excursion. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [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 172P, 76 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072436), [All aircraft, 9,308 cases](https://openairdocs.org/ntsb-findings/02063040/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 172P, 38 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=2072436), [All aircraft, 1,287 cases](https://openairdocs.org/ntsb-findings/01062041/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 172P, 39 cases](https://openairdocs.org/ntsb-events/092/sequence.md?model=2072436), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md) - [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090); cases with it: [Cessna 172P, 17 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=2072436), [All aircraft, 1,514 cases](https://openairdocs.org/ntsb-events/090/sequence.md) - [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Cessna 172P, 29 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2072436), [All aircraft, 3,656 cases](https://openairdocs.org/ntsb-events/300/sequence.md) ## Analysis The student pilot reported that during the second landing of his second solo flight, he flared too high above the runway. He reported that the airplane touched down, bounced twice, exited the runway to the left, bounced once in the grass and came to rest in the safety area between the runway and taxiway. The airplane sustained substantial damage to both wings and the fuselage. The pilot reported that there were no mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation. ## Factual narrative The student pilot reported that during the second landing of his second solo flight, he flared too high above the runway. He reported that the airplane touched down, bounced twice, exited the runway to the left, bounced once in the grass and came to rest in the safety area between the runway and taxiway. The airplane sustained substantial damage to both wings and the fuselage. The pilot reported that there were no mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation. ## Aircraft - Registration: [N52632](https://openairdocs.org/deregistered/N52632-2018-03-15), registration cancelled 2018-03-15, S/N 17274571, built 1981 (OpenAirDocs) - Reported make and model: CESSNA 172 (P) - Registry model: [Cessna 172P](https://openairdocs.org/model/cessna-172p) (registry code 2072436) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17274571 - Year built: 1981 - Airframe hours: 26755 - Engines: LYCOMING O-320 160 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: W I F A (Washington Intl Flight Academy) - Registered owner: W I F A (Washington Intl Flight Academy) - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, October 15, 2015 - Departed: GAI, Gaithersburg, MD - Destination: GAI, Gaithersburg, MD - Flight plan: VFR - Airport: GAI, Montgomery County Airpark, runway 14, 4,202 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Student pilot; age 22; injuries: none; student; medical: class 2, without waivers/limitations; seat: left; restraint: lap only; flight hours: 30 total, 30 in this make and model, 30 in the last 90 days, 30 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 270° at 7 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 43 °F, dew point 21 °F - Altimeter: 30.39 inHg - Observed at: KGAI ## 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 20151124022629A](https://openairdocs.org/incident/20151124022629A), Nov 24, 2015: Cessna 172P, Gaithersburg, MD, Substantial damage. CFI authorized solo flight for student pilot. Student pilot made a hard landing lost control of aircraft and the aircraft came to a stop when it entered sand… ## Other investigations on N52632 (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 NYC08CA220](https://openairdocs.org/ntsb/NYC08CA220), Jun 19, 2008: Cessna 172P (N52632), Lancaster, PA, substantial damage. Probable cause: The student pilot's failure to maintain directional control during the landing rollout. ## Docket (2 files) The files NTSB released with the investigation on February 8, 2016, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=92378. 3.2 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 2.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40436475&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Photos (Courtesy of Owner) (item 2, .PDF, 3 photos, 374 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40436476&FileExtension=.PDF&FileName=Photos%20(Courtesy%20of%20Owner)-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.