GAA16CA443 · Cessna A185 F
Oregon State Police Cessna A185 F · Accident: abnormal runway contact during landing
From Salem-Willamette Valley Airport/McNary Field (SLE) to Crater Lake-Klamath Regional Airport (LMT)
Event
- NTSB case
- GAA16CA443
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- Government
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna A185 F
- Aircraft type
- Cessna 185
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N185SC
- Operator
- Oregon State Police
- Onboard fatalities
- Unknown
- Route
- From Salem-Willamette Valley Airport/McNary Field (SLE), Salem, ORTo Crater Lake-Klamath Regional Airport (LMT), Klamath Falls, OR
- Aircraft age
- About 35 years (built 1981)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Public Aircraft
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · flare/touchdown
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Abnormal runway contact
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB 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.
Probable cause
The pilot's improper landing flare, which resulted in the airplane porpoising and the subsequent loss of directional control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA16CA443
- Event ID
- 20160823X22819
- Case number
- GAA16CA443
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 50cb046de196c56fb47dc6a0861906c9ba290d67031bd8babccdcc21d7d789c9; retrieved 2026-09-16T04:11:10.552Z.