WPR16FA131 · Cessna A185F F
Cessna A185F F · Accident: controlled flight into terrain/object (CFIT) while maneuvering
From Felts Field (SFF) to an unrecorded destination
Event
- NTSB case
- WPR16FA131
- 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
- 1 · 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
- General aviation
- 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 A185F 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
- N4585F
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Felts Field (SFF), Spokane, WATo not recorded
- Aircraft age
- About 50 years (built 1966)
- 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
- Part 91: General Aviation
- 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
- Maneuvering
- 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
- Controlled flight into terrain/object (CFIT)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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 › Action/decision
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The private pilot was on a local personal flight in the airplane. According to witnesses, the pilot appeared to fly a series of practice approaches at a remote private airstrip and then flew northeast up a nearby canyon towards rising mountainous terrain. The airplane impacted trees on the canyon hillside about 1 mile from the airstrip on a southwest heading, indicating that the pilot had reversed course. It is likely that the pilot realized that the canyon narrowed ahead and that he was surrounded by rising terrain. He likely attempted to turn the airplane around, and while maneuvering in the turn, he was unable to maintain clearance with the trees on the canyon hillside.
No significant weather or turbulence was reported or forecast in the area, however wind at the time of the accident may have created some light turbulence, though it is unlikely to have affected the flight.
Postaccident examination of the airframe and engine revealed no evidence of pre-impact mechanical malfunctions or failures that would have precluded normal operation. The engine was subsequently test run in a test cell at various power settings with no anomalies noted.
It is unlikely that the pilot's elevated blood pressure, insomnia, or medications used to treat these conditions impaired him or contributed to the accident. Additionally, it is unlikely that the pilot's antidepressant medications contributed to the accident. The pilot had used the potentially-impairing medication tramadol before the accident. However, because of variations in patient tolerance to opioid medications and possible postmortem changes in drug concentrations, the investigation was unable to determine if the pilot was impaired by tramadol at the time of the crash.
Probable cause
The pilot's failure to maintain clearance from trees while maneuvering at low altitude in mountainous terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR16FA131
- Event ID
- 20160625X01739
- Case number
- WPR16FA131
- 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. 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: 39c68a749292a01efffb14c6e21281a4bfb5b6992b8469ee1acb528c53710ce6; retrieved 2026-09-14T21:52:00.935Z.