# NTSB WPR11CA037: Cessna 172S, N14511, Port Townsend, WA, November 4, 2010 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: November 4, 2010, 16:30 local (23:30 UTC) - Place: Port Townsend, WA - Coordinates: 48.054721, -122.810554 - Nearby events: https://openairdocs.org/map.md?lat=48.0547&lon=-122.8106&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report March 16, 2011 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Seattle FSDO - NTSB case key (mKey): 77740 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR11CA037 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/77740/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=77740 - Page: https://openairdocs.org/ntsb/WPR11CA037 ## Probable cause The pilot's improper flare/touchdown while landing, resulting in a loss of directional control and a runway excursion. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: directional control](https://openairdocs.org/ntsb-findings/01062020): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 172S, 66 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=2072439), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/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 172S, 206 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072439), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Object/animal/substance: tree(s)](https://openairdocs.org/ntsb-findings/03022020): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Cessna 172S, 11 cases](https://openairdocs.org/ntsb-findings/03022020/cases.md?model=2072439), [All aircraft, 933 cases](https://openairdocs.org/ntsb-findings/03022020/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [Cessna 172S, 77 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=2072439), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Cessna 172S, 76 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2072439), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) ## Analysis During a planned full-stop landing, the airplane bounced back into the air after the initial touchdown and then settled to the runway a second time. Almost immediately after the second touchdown the airplane veered sharply to the left and departed the runway surface. Before the pilot could get the airplane to come to a stop its left wing struck a tree, resulting in the airplane spinning. The pilot said that the airplane had no mechanical or directional control anomalies, and that he should have executed a go-around when the airplane first bounced back into the air. ## Factual narrative During a planned full-stop landing, the airplane bounced back into the air after the initial touchdown, and then settled to the runway a second time. Almost immediately after the second touchdown, the airplane veered sharply to the left and departed the runway surface. Before the pilot could get the airplane to come to a stop, its left wing struck a tree, resulting in the airplane spinning around and coming to a stop. The pilot said that the airplane had no mechanical or directional control anomalies, and that he should have executed a go-around when the airplane first bounced back into the air. ## Aircraft - Registration: [N14511](https://openairdocs.org/deregistered/N14511-2012-01-04), registration cancelled 2012-01-04, S/N 172S10582, built 2007 (OpenAirDocs) - Reported make and model: CESSNA 172S - Registry model: [Cessna 172S](https://openairdocs.org/model/cessna-172s) (registry code 2072439) (OpenAirDocs) - Registry engine: [Lycoming IO-360-L2A](https://openairdocs.org/engine/lycoming-io-360-l2a) (registry code 41597, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 172S10582 - Engines: LYCOMING IO-360-L2A 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Coastal Aviation Capital LLC - Registered owner: Coastal Aviation Capital LLC - Airworthiness certificate: Standard, Normal - Departed: KTIW, Tacoma, WA - Destination: 0S9, Port Townsend, WA - Airport: 0S9, Jefferson County International, runway 27, 3,000 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 53; injuries: none; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; last flight review February 26, 2009; flight hours: 290 total, 290 in this make and model, 3 in the last 90 days, 1 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 220° at 4 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 55 °F ## Docket (1 files) The files NTSB released with the investigation on November 22, 2010, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=77740. 693 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 693 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40339793&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.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.