# NTSB WPR20CA219: Cessna 172, N9559D, Concord, CA, July 12, 2020 - Type: NTSB accident investigation - Classification: Accident · No injuries · Class 4 · Data collection · Final report - Date: July 12, 2020, 12:00 local (19:00 UTC) - Place: Concord, CA - Coordinates: 37.989723, -122.056945 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=37.9897&lon=-122.0569&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing: Loss of control in flight](https://openairdocs.org/ntsb-events/240) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed - Report: Approved by Office Director - Investigation class: Class 4 - Basic report with no Prelim publish - NTSB office: Western Pacific Region - Parties: FAA - NTSB case key (mKey): 101589 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR20CA219 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/101589/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=101589 - Page: https://openairdocs.org/ntsb/WPR20CA219 ## Probable cause The student pilot's failure to maintain airplane control when the airplane drifted off of runway centerline and subsequently collided with a taxiway sign during a go-around. ## 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 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) - [Object/animal/substance: sign/marker](https://openairdocs.org/ntsb-findings/03022015): Environmental issues › Physical environment · Effect on equipment (probable cause); cases with it: [Cessna 172R, 7 cases](https://openairdocs.org/ntsb-findings/03022015/cases.md?model=2072401), [All aircraft, 214 cases](https://openairdocs.org/ntsb-findings/03022015/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing: Loss of control in flight](https://openairdocs.org/ntsb-events/240) (defining event); cases with it: [Cessna 172R, 19 cases](https://openairdocs.org/ntsb-events/240/sequence.md?model=2072401), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md) - [Landing: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 172R, 46 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2072401), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The solo student pilot reported that, during landing, the airplane floated and drifted left of runway centerline. The pilot did not feel that he could make a safe landing and decided to go-around. Full power was added and shortly there after, the airplane struck a taxiway sign. The pilot continued the climb and maneuvered the airplane in the airport traffic pattern and landed without further incident. The left horizontal stabilizer was substantially damaged. The student pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. ## Factual narrative The solo student pilot reported that, during landing, the airplane floated and drifted left of runway centerline. The pilot did not feel that he could make a safe landing and decided to go-around. Full power was added and shortly there after, the airplane struck a taxiway sign. The pilot continued the climb and maneuvered the airplane in the airport traffic pattern and landed without further incident. The left horizontal stabilizer was substantially damaged. The student pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. ## Aircraft - Registration: [N9559D](https://openairdocs.org/aircraft/N9559D), registered now, S/N 17280488, built 1999 (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 I0360 series](https://openairdocs.org/engine/lycoming-i0360-series) (registry code 41515, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17280488 - Year built: 1999 - Airframe hours: 9199.8 - Engines: Lycoming IO-360-L2A 160 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: Pacific States Aviation, Inc - Registered owner: Christiansen Aviation Inc - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, March 17, 2020, 79 hours before - Departed: CCR, Concord, CA - Destination: CCR, Concord, CA - Airport: CCR, Buchanan Field, runway 01R, 2,770 × 75 ft, asphalt - Equipment: ADS-B, Stall warning system, Auto-pilot ## Flight crew As NTSB recorded them. NTSB leaves out names. - Student pilot; age 27; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 1, with waivers/limitations; last flight review December 30, 2019; seat: left; restraint: 3-point; flight hours: 247 total, 247 in this make and model, 128 as pilot in command, 1 in the last 90 days, 1 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 330° at 10 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 88 °F, dew point 54 °F - Altimeter: 29.88 inHg - Observed at: KCCR, 1 nm away ## 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 20200712012189A](https://openairdocs.org/incident/20200712012189A), Jul 12, 2020: Cessna 172R, Concord, CA, Substantial damage. A Cessna 172R [privacy data omitted] took off from Concord, CA. Airport for cross country flight and upon returning to this airport, pilot was performing touch… ## Docket (2 files) The files NTSB released with the investigation on October 9, 2020, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=101589. 1.2 MB in all. - Pilot/operator aircraft accident report, NTSB form 6120.1 (item 1, PDF, 9 pages, 685 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9984106&FileExtension=pdf&FileName=6120%20219_Redacted-Rel.pdf - Accident photo (item 2, PDF, 2 pages, 477 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9984200&FileExtension=pdf&FileName=Accident%20Photos%20219-Rel.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.