# NTSB GAA16CA361: Cessna 172, N19820, Lancaster, OH, June 21, 2016 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: June 21, 2016, 13:30 local (17:30 UTC) - Place: Lancaster, OH - Coordinates: 39.755554, -82.657218 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=39.7556&lon=-82.6572&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 January 18, 2017 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: FAA - NTSB case key (mKey): 93542 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA16CA361 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/93542/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=93542 - Page: https://openairdocs.org/ntsb/GAA16CA361 ## Probable cause The pilot's improper landing flare in gusting wind conditions, which resulted in a hard 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 172M, 9 cases](https://openairdocs.org/ntsb-findings/01062022/cases.md?model=2072418), [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 172M, 37 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=2072418), [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 · Pilot (probable cause); cases with it: [Cessna 172M, 123 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072418), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Wind: gusts](https://openairdocs.org/ntsb-findings/03034045): Environmental issues › Conditions/weather/phenomena · Effect on equipment; cases with it: [Cessna 172M, 26 cases](https://openairdocs.org/ntsb-findings/03034045/cases.md?model=2072418), [All aircraft, 1,199 cases](https://openairdocs.org/ntsb-findings/03034045/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: Other weather encounter](https://openairdocs.org/ntsb-events/400); cases with it: [Cessna 172M, 20 cases](https://openairdocs.org/ntsb-events/400/sequence.md?model=2072418), [All aircraft, 1,127 cases](https://openairdocs.org/ntsb-events/400/sequence.md) - [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090); cases with it: [Cessna 172M, 30 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=2072418), [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 172M, 23 cases](https://openairdocs.org/ntsb-events/092/sequence.md?model=2072418), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md) ## Analysis The student pilot reported that the purpose of the flight was to practice flight maneuvers. He recalled that upon conclusion of the maneuver practice, he made a normal approach to runway 28. He reported that during the landing flare he encountered a crosswind gust, the airplane floated, and the airplane landed hard. He recalled that after the hard landing, he was unsatisfied with his landing performance. The student pilot reported that he decided to takeoff, stayed in the pattern, landed with full flaps and more airspeed, and accomplished "a controlled, more smooth touchdown." However, when he showed up for his next flight three days later, he was informed that the airplane sustained substantial damage to the firewall. The pilot reported that there were no mechanical failures or anomalies with the airplane during his flight that would have prevented normal flight operations. The meteorological aerodrome report at the accident airport about the time of the accident indicated the wind direction was out of 270 degrees true at 9 knots, gusting to 19 knots. ## Factual narrative The student pilot reported that the purpose of the flight was to practice flight maneuvers. He recalled that upon conclusion of the maneuver practice, he made a normal approach to runway 28. He reported that during the landing flare he encountered a crosswind gust, the airplane floated, and the airplane landed hard. He recalled that after the hard landing, he was unsatisfied with his landing performance. The student pilot reported that he decided to takeoff, stayed in the pattern, landed with full flaps and more airspeed, and accomplished "a controlled, more smooth touchdown." However, when he showed up for his next flight three days later, he was informed that the airplane sustained substantial damage to the firewall. The pilot reported that there were no mechanical failures or anomalies with the airplane during his flight that would have prevented normal flight operations. The meteorological aerodrome report at the accident airport about the time of the accident indicated the wind direction was out of 270 degrees true at 9 knots, gusting to 19 knots. ## Aircraft - Registration: [N19820](https://openairdocs.org/aircraft/N19820), registered now, S/N 17260783, built 1972 (OpenAirDocs) - Reported make and model: CESSNA 172 (M) - Registry model: [Cessna 172M](https://openairdocs.org/model/cessna-172m) (registry code 2072418) (OpenAirDocs) - Registry engine: [Lycoming O-320-E2D](https://openairdocs.org/engine/lycoming-o-320-e2d) (registry code 42123, 4 cycle) (OpenAirDocs) - Category: Airplane - Serial number: 17260783 - Year built: 1972 - Airframe hours: 5440 - Engines: LYCOMING O-320-E2D 150 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Sundowner Aviation LLC - Registered owner: Sundowner Aviation LLC - Airworthiness certificate: Standard, Utility; Standard, Normal - Last inspection: 100 hour, June 7, 2016 - Departed: LHQ, Lancaster, OH - Destination: LHQ, Lancaster, OH - Airport: LHQ, Fairfield County, runway 28, 5,004 × 75 ft, asphalt - Equipment: None ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 71; injuries: none; student; medical: class 3, with waivers/limitations; seat: left; restraint: 3-point; flight hours: 61 total, 39 in this make and model, 39 in the last 90 days, 7 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 270° at 9 knots, gusting 19 - Visibility: 10 statute miles - Lowest ceiling: 10,000 ft broken - Temperature: 82 °F, dew point 68 °F - Altimeter: 29.93 inHg - Observed at: KLHQ ## 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 20160621012379A](https://openairdocs.org/incident/20160621012379A), Jun 21, 2016: Cessna 172M, Carrol, OH, Substantial damage. Pilot was conducting solo flight, after the hard laning the pilot taxied back to the hanger with no post flight inspection ## Other investigations on N19820 (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 CHI75FEI15](https://openairdocs.org/ntsb/CHI75FEI15), Sep 11, 1974: Cessna 172M (N19820), N Jackson, OH, substantial damage ## Docket (3 files) The files NTSB released with the investigation on November 18, 2016, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=93542. 2.7 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 1.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40446634&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Pilot's Statement (item 2, .PDF, 369 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40446635&FileExtension=.PDF&FileName=Pilot%27s%20Statement-Master.PDF - Photos (item 3, .PDF, 476 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40446636&FileExtension=.PDF&FileName=Photos-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.