# NTSB WPR13CA104: Cirrus Design SR22, N5384W, Torrance, CA, January 15, 2013 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: January 14, 2013, 19:00 local (Jan 15, 2013, 03:00 UTC) - Place: Torrance, CA - Coordinates: 33.803333, -118.339447 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=33.8033&lon=-118.3394&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report April 25, 2013 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: FAA FSDO - NTSB case key (mKey): 86085 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR13CA104 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/86085/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=86085 - Page: https://openairdocs.org/ntsb/WPR13CA104 ## Probable cause The pilot’s improper landing flare, which resulted in a bounced 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: [Cirrus Design SR22, 9 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=2130001), [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md) - [Action: incorrect action performance](https://openairdocs.org/ntsb-findings/02041015): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cirrus Design SR22, 13 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md?model=2130001), [All aircraft, 1,386 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) (defining event); cases with it: [Cirrus Design SR22, 16 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=2130001), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md) ## Analysis The pilot reported that he intended to land on an asphalt runway in night visual conditions. As the airplane approached the runway, he added engine power because the flight controls felt “mushy.” The airspeed was about 85 knots with full flaps, and the airplane remained in ground effect longer than usual. When the airplane touched down, it bounced and the propeller struck the runway surface. The airplane porpoised but eventually came to a stop. The airplane sustained substantial damage to the engine mount structure and support assembly. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. ## Factual narrative The pilot reported that he intended to land on an asphalt runway in night visual conditions. As the airplane approached the runway, he added engine power because the flight controls felt mushy. The airspeed was approximately 85 knots with full flaps and the airplane remained in ground effect longer than usual. When the airplane touched down, it bounced and the propeller struck the runway surface. The airplane porpoised, but eventually came to a stop. The airplane sustained substantial damage to the engine mount structure and support assembly. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operations. ## Aircraft - Registration: [N5384W](https://openairdocs.org/aircraft/N5384W), registered now, S/N 0854, built 2004 (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: 0854 - Airframe hours: 958 - Engines: CONT MOTOR IO-550 SERIES 300 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Phillip Schoenwetter - Registered owner: Flitemax Inc - Airworthiness certificate: Standard, Normal - Last inspection: Annual, September 13, 2012 - Departed: KBUR, Burbank, CA - Destination: KTOA, Torrance, CA - Flight plan: Unknown - Airport: KTOA, Zamperini Field, runway 29R, 5,000 × 80 ft, concrete ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 63; injuries: none; private; airplane ratings: single-engine land; medical: class 2, with waivers/limitations; seat: left; flight hours: 608 total, 585 in this make and model, 397 as pilot in command, 12 in the last 90 days, 6 in the last 30 days ## Weather - Conditions: Visual (VMC), Night/dark - Wind: calm - Visibility: 20 statute miles - Lowest ceiling: none - Temperature: 41 °F ## 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 20130114000659A](https://openairdocs.org/incident/20130114000659A), Jan 14, 2013: Cirrus Design Corp SR22, Torrance, CA, Substantial damage. Upon landing at Torrance airport, during touchdown the propeller contacted the runway which damaged the propeller and the nose wheel. In the process of… ## Docket (1 files) The files NTSB released with the investigation on March 6, 2013, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=86085. 140 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 140 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40388353&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.