# NTSB GAA16CA443: Cessna A185, N185SC, Klamath Falls, OR, August 19, 2016 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: August 19, 2016, 11:45 local (18:45 UTC) - Place: Klamath Falls, OR - Coordinates: 42.157775, -121.734443 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=42.1578&lon=-121.7344&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: 2 uninjured - Status: Completed, report January 18, 2017 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: FAA - NTSB case key (mKey): 93875 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA16CA443 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/93875/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=93875 - Page: https://openairdocs.org/ntsb/GAA16CA443 ## Probable cause The pilot's improper landing flare, which resulted in the airplane porpoising and the subsequent loss of directional control. ## 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 A185F, 56 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=2072821), [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 · Student/instructed pilot (probable cause); cases with it: [Cessna A185F, 71 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072821), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Performance/control parameters: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna A185F, 5 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=2072821), [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/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: [Cessna A185F, 15 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=2072821), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md) - [Landing: Loss of control on ground](https://openairdocs.org/ntsb-events/230); cases with it: [Cessna A185F, 75 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=2072821), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Landing: Landing gear collapse](https://openairdocs.org/ntsb-events/094); cases with it: [Cessna A185F, 12 cases](https://openairdocs.org/ntsb-events/094/sequence.md?model=2072821), [All aircraft, 1,787 cases](https://openairdocs.org/ntsb-events/094/sequence.md) - [Landing: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna A185F, 36 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2072821), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot receiving instruction in a high performance tailwheel-equipped airplane reported that during the initial touchdown the airplane porpoised, then settled onto the ground in a three point landing attitude. The pilot further reported that during the landing roll the airplane veered to the left. He "applied moderate right rudder to compensate", then he applied "heavy" right rudder, but he was unable to arrest the veer. The airplane ground looped to the left, the right main landing gear collapsed, and the right wing impacted the ground. The airplane sustained substantial damage to the right wing. The pilot reported no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. The Federal Aviation Administration has published the Airplane Flying Handbook FAA-H-8083-3A (2004). This handbook discusses porpoising and states in part: In a bounced landing that is improperly recovered, the airplane comes in nose first setting off a series of motions that imitate the jumps and dives of a porpoise—hence the name. The problem is improper airplane attitude at touchdown, sometimes caused by inattention, not knowing where the ground is, mistrimming or forcing the airplane onto the runway. Ground effect decreases elevator control effectiveness and increases the effort required to raise the nose. Not enough elevator or stabilator trim can result in a nose low contact with the runway and a porpoise develops. Porpoising can also be caused by improper airspeed control. Usually, if an approach is too fast, the airplane floats and the pilot tries to force it on the runway when the airplane still wants to fly. A gust of wind, a bump in the runway, or even a slight tug on the control wheel will send the air plane aloft again. The corrective action for a porpoise is the same as for a bounce and similarly depends on its severity. When it is very slight and there is no extreme change in the airplane's pitch attitude, a follow-up landing may be executed by applying sufficient power to cushion the subsequent touchdown, and smoothly adjusting the pitch to the proper touchdown attitude. ## Factual narrative The pilot receiving instruction in a high performance tailwheel-equipped airplane reported that during the initial touchdown the airplane porpoised, then settled onto the ground in a three point landing attitude. The pilot further reported that during the landing roll the airplane veered to the left. He "applied moderate right rudder to compensate", then he applied "heavy" right rudder, but he was unable to arrest the veer. The airplane ground looped to the left, the right main landing gear collapsed, and the right wing impacted the ground. The airplane sustained substantial damage to the right wing. The pilot reported no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. The Federal Aviation Administration has published the Airplane Flying Handbook FAA-H-8083-3A (2004). This handbook discusses porpoising and states in part: In a bounced landing that is improperly recovered, the airplane comes in nose first setting off a series of motions that imitate the jumps and dives of a porpoise—hence the name. The problem is improper airplane attitude at touchdown, sometimes caused by inattention, not knowing where the ground is, mistrimming or forcing the airplane onto the runway. Ground effect decreases elevator control effectiveness and increases the effort required to raise the nose. Not enough elevator or stabilator trim can result in a nose low contact with the runway and a porpoise develops. Porpoising can also be caused by improper airspeed control. Usually, if an approach is too fast, the airplane floats and the pilot tries to force it on the runway when the airplane still wants to fly. A gust of wind, a bump in the runway, or even a slight tug on the control wheel will send the air plane aloft again. The corrective action for a porpoise is the same as for a bounce and similarly depends on its severity. When it is very slight and there is no extreme change in the airplane's pitch attitude, a follow-up landing may be executed by applying sufficient power to cushion the subsequent touchdown, and smoothly adjusting the pitch to the proper touchdown attitude. ## Aircraft - Registration: [N185SC](https://openairdocs.org/aircraft/N185SC), registered now, S/N 18504301, built 1981 (OpenAirDocs) - Reported make and model: CESSNA A185 (F) - Registry model: [Cessna A185F](https://openairdocs.org/model/cessna-a185f) (registry code 2072821) (OpenAirDocs) - Registry engine: [Continental IO-520 series](https://openairdocs.org/engine/continental-io-520-series) (registry code 17032, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 18504301 - Year built: 1981 - Airframe hours: 10686 - Engines: Continental IO-520D 300 horsepower reciprocating - Damage: Substantial damage - Flight: Public aircraft - state, Public use - Operator: Oregon State Police - Registered owner: Oregon State Police - Airworthiness certificate: Certificate of authorization or waiver (COA) - Last inspection: 100 hour, December 3, 2015 - Departed: SLE, SALEM, OR - Destination: LMT, Klamath Falls, OR - Airport: LMT, Crater Lake-Klamath Rgnl, runway 32, 10,301 × 150 ft, concrete - Equipment: Stall warning system, Electronic flight bag or handheld device, Onboard weather, Satellite tracking device ## Flight crew As NTSB recorded them. NTSB leaves out names. - Student pilot; age 39; injuries: none; commercial; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; last flight review July 17, 2016; seat: left; restraint: 3-point; flight hours: 583 total, 1.2 in this make and model, 516 as pilot in command, 3 in the last 90 days, 3 in the last 30 days, 2 in the last 24 hours - Flight instructor; age 59; injuries: none; airline transport, flight instructor, commercial; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; seat: right; restraint: 3-point ## Weather - Conditions: Visual (VMC), Day - Wind: variable at 6 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 86 °F, dew point 43 °F - Altimeter: 30.11 inHg - Observed at: KLMT, 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 20160819013859A](https://openairdocs.org/incident/20160819013859A), Aug 19, 2016: Cessna A185F, Klamath Falls, OR, Substantial damage. A student pilot was training for flight controls of a tail wheel type aircraft. The flight was under the operational control of the listed pilot. During a… ## Docket (3 files) The files NTSB released with the investigation on November 23, 2016, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=93875. 1.2 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 1.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40446744&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Flight Instructor Statement (item 2, .PDF, 14 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40446745&FileExtension=.PDF&FileName=Flight%20Instructor%20Statement-Master.PDF - Accident Photo (item 3, .PDF, 111 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40446746&FileExtension=.PDF&FileName=Accident%20Photo-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.