# NTSB WPR11FA407: Cirrus Design SR22, N675DH, Fall City, WA, August 21, 2011 - Type: NTSB accident investigation - Classification: Accident · No injuries · Field investigation · Final report - Date: August 21, 2011, 11:40 local (18:40 UTC) - Place: Fall City, WA - Coordinates: 47.559444, -121.863609 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=47.5594&lon=-121.8636&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report January 15, 2013 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: FAA FSDO - NTSB case key (mKey): 81586 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR11FA407 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/81586/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=81586 - Page: https://openairdocs.org/ntsb/WPR11FA407 ## Probable cause The pilot's inadequate approach planning and failure to achieve the proper touchdown point, which resulted in a runway overrun. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: descent/approach/glide path](https://openairdocs.org/ntsb-findings/01062040): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cirrus Design SR22, 14 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=2130001), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md) - [Aircraft capability: landing distance](https://openairdocs.org/ntsb-findings/01061030): Aircraft › Aircraft oper/perf/capability · Capability exceeded (probable cause); cases with it: [Cirrus Design SR22, 3 cases](https://openairdocs.org/ntsb-findings/01061030/cases.md?model=2130001), [All aircraft, 68 cases](https://openairdocs.org/ntsb-findings/01061030/cases.md) - [Planning/preparation](https://openairdocs.org/ntsb-findings/02061000): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cirrus Design SR22, 1 case](https://openairdocs.org/ntsb-findings/02061000/cases.md?model=2130001), [All aircraft, 113 cases](https://openairdocs.org/ntsb-findings/02061000/cases.md) - [Object/animal/substance: tree(s)](https://openairdocs.org/ntsb-findings/03022020): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Cirrus Design SR22, 11 cases](https://openairdocs.org/ntsb-findings/03022020/cases.md?model=2130001), [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 area overshoot](https://openairdocs.org/ntsb-events/380); cases with it: [Cirrus Design SR22, 4 cases](https://openairdocs.org/ntsb-events/380/sequence.md?model=2130001), [All aircraft, 400 cases](https://openairdocs.org/ntsb-events/380/sequence.md) - [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300) (defining event); cases with it: [Cirrus Design SR22, 40 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2130001), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) - [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cirrus Design SR22, 113 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2130001), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot reported that during the initial climb to cruise flight the airplane began to lose airspeed and the low engine oil light illuminated. The pilot diverted to a nearby airport and began an approach to the runway. The first approach to the runway terminated with a go-around due to high airspeed. The pilot reported that the airspeed for the second approach to the runway was “correct;” however, the airplane touched down near the midpoint of the 3,000-foot runway. The pilot was unable to stop the airplane in the remaining distance and the airplane overran the runway and collided with trees. The pilot reported no engine power anomalies during the go-around and ensuing approach. An operational test run of the engine and postaccident examination of the airplane, including data recovered from the multi-function display, indicated no mechanical malfunctions or failures that would have precluded normal operation; the engine performed to production test standards and no discrepancies were noted. ## Factual narrative HISTORY OF FLIGHT On August 21, 2011, at 1140 Pacific daylight time, a Cirrus Design SR22, N675DH, sustained substantial damage subsequent to a runway overrun at the Fall City Airport, Fall City, Washington. The private pilot and passenger were not injured. The airplane was registered to Daedelus Aviation LLC, and operated by the pilot under the provisions of 14 Code of Federal Regulations (CFR) Part 91. The cross-country flight departed Snohomish County Airport (PAE) Everett, Washington, about 1045, with a planned destination of Walla Walla, Washington. Visual meteorological conditions (VMC) prevailed and an instrument flight plan was filed. The pilot reported that during climb to cruise, about 7,500 feet, the airplane began to lose airspeed and the low engine oil light illuminated. The pilot diverted to Fall City and initiated an approach to the runway. He reported that the approach terminated with a go-around because his airspeed was too high. He reported that the airspeed for the second approach was “correct” however, he touched down near the mid-point of the 3,000 feet runway. The pilot was unable to stop the airplane in the remaining distance and overran the runway. The airplane subsequently collided with trees that bordered the departure end of the runway. The pilot reported no engine power anomalies during the go-around or ensuing approach. The airplane sustained structural damage to both wings during the accident sequence. PERSONNEL INFORMATION At the time of the accident the pilot, age 72, held a private pilot certificate with airplane single engine land and instrument privileges. The pilot’s most recent flight review was completed on June 24, 2011. The pilot reported that his total flight experience was 522 hours, 354 as pilot-in-command and 296 hours in make and model. His most recent Federal Aviation Administration third class medical was issued on October 18, 2010. AIRCRAFT INFORMATION The four-seat, low-wing, fixed-gear airplane was powered by a Continental IO-550 engine rated at 310-horse power and equipped with an adjustable pitch propeller. The pilot reported that the last annual inspection was completed September 10, 2010; the airframe, engine and propeller total time at inspection was approximately 950 hours. TESTS AND RESEARCH The engine was removed from the airframe and shipped to Continental Motors Inc. for further examination. The examination revealed that the engine was intact and no impact related damage was noted. The external surfaces of the engine were clean and undamaged. The engine accessories were in place and unremarkable. Combustion deposits were noted in the combustion chambers and on the piston heads. There was oil present on the cylinder bores. The cylinder head combustion chambers, intake and exhaust valve faces, piston heads and cylinder bores exhibit normal operating signatures. The top spark plugs were removed and no discrepancies were noted. The examination revealed no anomalies or damage. The engine wasplaced in an engine run test cell. The engine was started, and operated through a series of stabilized power settings, accelerations and decelerations. The engine performed to production test standards and no anomalies were noted. A post test run engine examination revealed no anomalies or discrepancies. An engine exam report, including test data results, is contained in the public docket. ## Aircraft - Registration: [N675DH](https://openairdocs.org/deregistered/N675DH-2013-02-15), registration cancelled 2013-02-15, S/N 0163, built 2002 (OpenAirDocs) - Reported make and model: CIRRUS DESIGN CORP SR22 - Registry model: [Cirrus Design SR22](https://openairdocs.org/model/cirrus-design-sr22) (registry code 2130001) (OpenAirDocs) - Registry engine: [Continental IO-550 series](https://openairdocs.org/engine/continental-io-550-series) (registry code 17042, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 0163 - Airframe hours: 986 - Engines: CONT MOTOR IO-550 SERIES 300 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Gerald Bernstein - Registered owner: Daedelus Aviation LLC - Airworthiness certificate: Standard, Normal - Last inspection: Annual, September 10, 2010 - Departed: KPAE, Snohomish, WA - Destination: 1WA6, Fall City, WA - Flight plan: IFR - Airport: 1WA6, Fall City, runway 09, 3,000 × 25 ft, grass/turf ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 72; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review May 24, 2011; seat: left; flight hours: 522 total, 296 in this make and model, 354 as pilot in command, 14 in the last 90 days, 3 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 73 °F, dew point 52 °F - Altimeter: 29.93 inHg ## 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 20110821018129A](https://openairdocs.org/incident/20110821018129A), Aug 21, 2011: Cirrus Design Corp SR22, Fall City, WA, Substantial damage. PIC, [privacy data omitted], and 1 passenger, reported the accident to NTSB on 8/21/11, Sunday, 1130 PDT, when his aircraft impacted trees at the east end of a… ## Docket (7 files) The files NTSB released with the investigation on November 9, 2012, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=81586. 4.2 MB in all. - Cockpit Display(s) - Recorded Flight Data - Specialist's Factual Report (item 1, .PDF, 219 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40362523&FileExtension=.PDF&FileName=Cockpit%20Display(s)%20-%20Recorded%20Flight%20Data%20-%20Specialist%27s%20Factual%20Report-Master.PDF - Cockpit Display(s) - Recorded Flight Data - Attachment 1 Tabular Data - (CSV Format) (item 2, .CSV, 61 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40362524&FileExtension=.csv&FileName=Cockpit%20Display(s)%20-%20Recorded%20Flight%20Data%20-%20Attachment%201%20Tabular%20Data%20-%20(CSV%20Format)-Master.csv - Cockpit Display(s) - Recorded Flight Data - Attachment 2 Tabular Data - (CSV Format) (item 3, .CSV, 49 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40362525&FileExtension=.csv&FileName=Cockpit%20Display(s)%20-%20Recorded%20Flight%20Data%20-%20Attachment%202%20Tabular%20Data%20-%20(CSV%20Format)-Master.csv - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 4, .PDF, 2.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40381475&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Engine Run and Exam Report (3 Embedded Photos) (item 5, .PDF, 3 photos, 506 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40377834&FileExtension=.PDF&FileName=Engine%20Run%20and%20Exam%20Report%20%20(3%20Embedded%20Photos)-Master.PDF - Statement of Party Representatives to NTSB Investigation (item 6, .PDF, 247 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40377835&FileExtension=.PDF&FileName=Statement%20of%20Party%20Representatives%20to%20NTSB%20Investigation-Redacted.PDF - Retention / Release of Wreckage Form / Evidence (item 7, .PDF, 224 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40378465&FileExtension=.PDF&FileName=Retention%20%2F%20Release%20of%20Wreckage%20Form%20%2F%20Evidence-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.