# NTSB GAA17CA111: Cessna 172, N907WA, Hollywood, FL, January 7, 2017 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: January 7, 2017, 09:00 local (14:00 UTC) - Place: Hollywood, FL - Coordinates: 26.002222, -80.239997 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=26.0022&lon=-80.2400&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing: Hard landing](https://openairdocs.org/ntsb-events/092) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report April 4, 2017 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: FAA - NTSB case key (mKey): 94596 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA17CA111 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/94596/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=94596 - Page: https://openairdocs.org/ntsb/GAA17CA111 ## Probable cause The student pilot’s improper landing flare in gusting crosswind conditions, which resulted in a hard landing. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [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 172N, 38 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=2072434), [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 172N, 150 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072434), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Wind: crosswind](https://openairdocs.org/ntsb-findings/03034040): Environmental issues › Conditions/weather/phenomena · Effect on operation; cases with it: [Cessna 172N, 19 cases](https://openairdocs.org/ntsb-findings/03034040/cases.md?model=2072434), [All aircraft, 1,008 cases](https://openairdocs.org/ntsb-findings/03034040/cases.md) - [Wind: gusts](https://openairdocs.org/ntsb-findings/03034045): Environmental issues › Conditions/weather/phenomena · Effect on operation; cases with it: [Cessna 172N, 28 cases](https://openairdocs.org/ntsb-findings/03034045/cases.md?model=2072434), [All aircraft, 1,199 cases](https://openairdocs.org/ntsb-findings/03034045/cases.md) - [Performance/control parameters: crosswind correction](https://openairdocs.org/ntsb-findings/01062030): Aircraft › Aircraft oper/perf/capability · Not attained/maintained; cases with it: [Cessna 172N, 2 cases](https://openairdocs.org/ntsb-findings/01062030/cases.md?model=2072434), [All aircraft, 184 cases](https://openairdocs.org/ntsb-findings/01062030/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing: Hard landing](https://openairdocs.org/ntsb-events/092) (defining event); cases with it: [Cessna 172N, 46 cases](https://openairdocs.org/ntsb-events/092/sequence.md?model=2072434), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md) - [Landing: Loss of control on ground](https://openairdocs.org/ntsb-events/230); cases with it: [Cessna 172N, 81 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=2072434), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Landing: Dragged wing/rotor/float/other](https://openairdocs.org/ntsb-events/093); cases with it: [Cessna 172N, 2 cases](https://openairdocs.org/ntsb-events/093/sequence.md?model=2072434), [All aircraft, 319 cases](https://openairdocs.org/ntsb-events/093/sequence.md) - [Landing: Landing gear collapse](https://openairdocs.org/ntsb-events/094); cases with it: [Cessna 172N, 10 cases](https://openairdocs.org/ntsb-events/094/sequence.md?model=2072434), [All aircraft, 1,787 cases](https://openairdocs.org/ntsb-events/094/sequence.md) - [Landing: Nose over/nose down](https://openairdocs.org/ntsb-events/096); cases with it: [Cessna 172N, 44 cases](https://openairdocs.org/ntsb-events/096/sequence.md?model=2072434), [All aircraft, 2,287 cases](https://openairdocs.org/ntsb-events/096/sequence.md) - [Landing: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Cessna 172N, 81 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2072434), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) ## Analysis The solo student pilot reported that, during his ninth landing of the day, the nose gear collapsed, and the left wing dipped down striking the runway. Subsequently, the airplane exited the runway to the right. The Federal Aviation Administration inspector who responded to the accident reported that the distance from the first point of impact to the final stopping point was about 320 ft. He added there were indications that the right aileron and wing tip contacted the runway first. There was also a sheared nose gear hub pin/bolt found 35 ft from the initial point of impact. There were multiple impact points along the debris path, and the second point of impact was the left wing tip, indicated by the blue-and-white paint markings from the wing tip on the runway. The third impact was the airplane's nosewheel assembly. The runway showed markings left by the tire on the surface for about 20 ft. The markings also indicated an extreme side load on the tire. The wheel/tire hub assembly was found at the end of the tire mark with one of the nose strut forks. Additionally, there were seven gouges in the runway surface from the propeller striking the ground. The airplane sustained substantial damage to both wings and the firewall. The student pilot reported that there were no preaccident mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation. The weather observation station at the accident airport reported that, about the time of the accident, the wind was 220° at 14 knots, gusting to 20 knots. The student pilot landed on runway 28L. ## Factual narrative The solo student pilot reported that during his 9th landing of the day, the nose gear collapsed, and the left wing dipped down striking the runway. Subsequently, the airplane exited the runway to the right. The Federal Aviation Administration (FAA) Inspector who responded to the accident reported that the distance from the first point of impact to the final stopping point was approximately 320 ft. He further reported there were indications that the right aileron and wing tip contacted the runway first. There was also a sheared nose gear hub pin/bolt found 35 ft. from the initial point of impact. There were multiple impact points along the debris path, and the second point of impact was the left-wing tip, indicated by the blue and white paint markings from the wing tip on the runway. The third impact was the airplane's nose wheel assembly. The runway showed markings left by the tire on the surface for about 20 ft. The markings also indicated an extreme side load on the tire. The wheel/tire hub assembly was found at the end of the tire mark with one of the nose strut forks. Additionally, there were 7 gouges in the runway surface from the propeller striking the ground. The airplane sustained substantial damage to both wings and the firewall. The student pilot reported there were no pre-accident mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation. The weather observation station at the accident airport, about the time of the accident, reported the wind at 220 degrees (true) at 14 knots, gusting to 20 knots. The student pilot landed runway 28L. ## Aircraft - Registration: [N907WA](https://openairdocs.org/aircraft/N907WA), registered now, S/N 17267907, built 1976 (OpenAirDocs) - Reported make and model: CESSNA 172 (N) - Registry model: [Cessna 172N](https://openairdocs.org/model/cessna-172n) (registry code 2072434) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17267907 - Year built: 1976 - Airframe hours: 16317 - Engines: LYCOMING O-320-D2J 160 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Airworthiness certificate: Standard, Utility; Standard, Normal - Last inspection: 100 hour, November 21, 2016 - Departed: HWO, Hollywood, FL - Destination: HWO, Hollywood, FL - Airport: HWO, North Perry, runway 28L, 3,255 × 100 ft, asphalt - Equipment: Stall warning system, ADS-B ## Flight crew As NTSB recorded them. NTSB leaves out names. - Student pilot; age 24; injuries: none; student; medical: class 1, without waivers/limitations; seat: left; flight hours: 50 total, 5 as pilot in command, 50 in the last 90 days, 50 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 220° at 14 knots, gusting 20 - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 79 °F, dew point 72 °F - Altimeter: 30.06 inHg - Observed at: KHWO ## 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 20170107000649A](https://openairdocs.org/incident/20170107000649A), Jan 7, 2017: Cessna 172N, Pembroke Pines, FL, Substantial damage. Aircraft Cessna C-172N, N907WA with a student pilot preforming touch and go?s at North Perry Airport (hwo) from runway 28L. Student completed 8 touch and go?s… ## Docket (3 files) The files NTSB released with the investigation on March 14, 2017, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=94596. 2.9 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 2.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40449927&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - FAA Inspector's Statement (item 2, .PDF, 17 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40449928&FileExtension=.PDF&FileName=FAA%20Inspector%27s%20Statement-Master.PDF - Accident Photo (Courtesy of FAA) (item 3, .PDF, 1 photo, 579 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40449929&FileExtension=.PDF&FileName=Accident%20Photo%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.