# NTSB WPR18CA072: Cessna 172P, N64204, Cloverdale, CA, January 20, 2018 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Data collection · Final report - Date: January 20, 2018, 13:00 local (21:00 UTC) - Place: Cloverdale, CA - Coordinates: 38.776111, -122.9925 - Nearby events: https://openairdocs.org/map.md?lat=38.7761&lon=-122.9925&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-VFR go-around: Loss of control in flight](https://openairdocs.org/ntsb-events/240) - Highest injury: Minor injuries - Injuries: 1 minor - Status: Completed, report June 14, 2018 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: FAA FSDO - NTSB case key (mKey): 96645 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR18CA072 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/96645/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=96645 - Page: https://openairdocs.org/ntsb/WPR18CA072 ## Probable cause The pilot's failure to maintain airplane control during the approach and his delayed decision to go around. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cessna 172P, 20 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=2072436), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/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 172P, 76 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072436), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Action: delayed action](https://openairdocs.org/ntsb-findings/02041025): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cessna 172P, 9 cases](https://openairdocs.org/ntsb-findings/02041025/cases.md?model=2072436), [All aircraft, 894 cases](https://openairdocs.org/ntsb-findings/02041025/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach-VFR go-around: Loss of control in flight](https://openairdocs.org/ntsb-events/240) (defining event); cases with it: [Cessna 172P, 16 cases](https://openairdocs.org/ntsb-events/240/sequence.md?model=2072436), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md) - [Approach-VFR go-around: Attempted remediation/recovery](https://openairdocs.org/ntsb-events/060); cases with it: [Cessna 172P, 13 cases](https://openairdocs.org/ntsb-events/060/sequence.md?model=2072436), [All aircraft, 1,422 cases](https://openairdocs.org/ntsb-events/060/sequence.md) ## Analysis The private pilot reported that he intended to make two full-stop landings before returning to his home base. The pilot entered the traffic pattern and announced his position as he maneuvered to final approach. The pilot stated that the approach was stable but appeared to be short. He added power and adjusted the pitch for the projected touchdown point beyond the displaced threshold. When the airplane was over the displaced threshold, the stability of the approach was lost. The pilot suspected a swirl of wind or updraft was encountered as the wing raised more than he expected from previous landings at this airport. The pilot tried to regain the runway centerline and level the wings; however, he was unsuccessful. The pilot then made a radio transmission that he was going around. He applied power and raised the flaps (he reported that his intention was to extend the flaps 20o; however, postaccident, the flap position was fully retracted). The airplane rolled to the left and contacted the ground, coming to rest inverted off the side of the runway. The forward fuselage, left wing and vertical stabilizer were substantially damaged. The pilot reported that there were no mechanical failures or malfunctions with the airplane or engine that would have precluded normal operation. ## Factual narrative The private pilot reported that he intended to make 2 full-stop landings before returning to his home base. The pilot entered the traffic pattern and announced his position as he maneuvered to final approach. The pilot stated that the approach was stable, but appeared to be short. He added power and adjusted the pitch for the projected touchdown point beyond the displaced threshold. When the airplane was over the displaced threshold, stability of the approach was lost. The pilot suspected a swirl of wind or updraft was encountered as the wing raised more than he expected from previous landings at this airport. The pilot tried to regain the runway centerline and level the wings, however he was unsuccessful. The pilot then made a radio transmission that he was going around. Power was applied and the flaps were raised (intention was 20o, however postaccident, the flap position was fully retracted). The airplane rolled to the left and contacted the ground; coming to rest inverted off the side of the runway. The airplane was substantially damaged. The pilot reported that there were no mechanical failures or malfunctions with the airplane or engine that would have precluded normal operation. ## Aircraft - Registration: [N64204](https://openairdocs.org/deregistered/N64204-2019-06-12), registration cancelled 2019-06-12, S/N 17275534, built 1981 (OpenAirDocs) - Reported make and model: CESSNA 172P (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: 17275534 - Year built: 1981 - Airframe hours: 17517 - Engines: LYCOMING O-320-D 160 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, December 28, 2017 - Departed: KSTS, Santa Rosa, CA - Destination: O60, Cloverdale, CA - Airport: O60, Cloverdale Municipal Airport, runway 32, 2,909 × 60 ft, asphalt - Equipment: Stall warning system, Electronic flight bag or handheld device ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 43; injuries: minor; private; airplane ratings: single-engine land; medical: class 2, without waivers/limitations; last flight review July 18, 2017; seat: left; restraint: 3-point; flight hours: 168.8 total, 28.2 in this make and model, 72.4 as pilot in command, 5.1 in the last 90 days, 0.6 in the last 30 days, 0.6 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 340° at 9 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 57 °F, dew point 37 °F - Altimeter: 30.14 inHg - Observed at: KSTS, 18 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 20180120001019A](https://openairdocs.org/incident/20180120001019A), Jan 20, 2018: Cessna 172P, Cloverdale, CA, Substantial damage. A Cessna 172P N64204 took off from santa rosa, CA. Airport and pilot was flying to Cloverdale airport for a solo training mission/full stop landings. With… ## Other investigations on N64204 (2) 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 WPR10CA392](https://openairdocs.org/ntsb/WPR10CA392), Aug 8, 2010: Cessna 172P (N64204), San Jose, CA, substantial damage. Probable cause: The pilot’s improper flare and inadequate recovery from a bounced landing. - [NTSB WPR09CA209](https://openairdocs.org/ntsb/WPR09CA209), Apr 20, 2009: Cessna 172P (N64204), Livermore, CA, substantial damage. Probable cause: The student pilot’s improper recovery from a bounced landing. ## Docket (3 files) The files NTSB released with the investigation on April 20, 2018, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=96645. 3.1 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 2.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40462157&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Record of Conversation - Volz (item 2, .PDF, 55 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40462158&FileExtension=.PDF&FileName=Record%20of%20Conversation%20-%20Volz-Master.PDF - Accident Photos (item 3, .PDF, 860 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40462159&FileExtension=.PDF&FileName=Accident%20Photos-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.