FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR17FA044 · Cessna 182 P

29 Dec 2016 · Dabob, WA, United States

Cessna 182 P · Accident: loss of control in flight en route

From King County International Airport - Boeing Field (BFI) to William R Fairchild International Airport (CLM)

Report a problem

Event

NTSB case
WPR17FA044
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
4 · 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 182 P

Aircraft type
Cessna 182
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
N52388
Operator
Unknown
Onboard fatalities
Unknown
Route
From King County International Airport - Boeing Field (BFI), Seattle, WATo William R Fairchild International Airport (CLM), Port Angeles, WA
Aircraft age
About 43 years (built 1973)
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
En route · cruise
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
Loss of control in flight
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

  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision
  • Personnel issues › Psychological
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The non-instrument-rated private pilot departed at night on a visual flight rules (VFR) cross-country flight without obtaining an official weather briefing. If the pilot had received an official briefing, he would have been informed of instrument flight rules (IFR) conditions present on his route of flight. Radar data showed the airplane traveling on a heading towards its destination at varying altitudes. The pilot's communications with an air traffic controller indicated that he was trying to avoid restricted airspace, and then, when asked by the controller what his intentions were, the pilot stated that he was trying to stay out of the clouds. As the airplane made multiple 360° turns, the controller attempted to keep the airplane in controlled airspace before losing communications and radar contact with the airplane near the accident site.

Examination of the accident site indicated the airplane impacted terrain in a nose-down attitude at a high airspeed consistent with a loss of control. The attitude indicator was disassembled, and scoring was identified suggesting that the gyro rotor was spinning and, therefore, likely operational at the time of impact. There was no evidence found of mechanical malfunctions or failures that would have precluded normal operation of the airplane.

Based on upper air data, infrared satellite imagery, and surface observation data, the flight likely encountered precipitation, lowering ceilings, and IFR conditions around the time the airplane began to make the 360° turns. The IFR conditions encountered by the flight were conducive to spatial disorientation, and it is likely that the pilot experienced spatial disorientation and lost control of the airplane. The pilot had depression, anxiety, and insomnia, for which he was prescribed a number of potentially-impairing medications, most of which were identified during postaccident toxicology testing. However, whether these conditions or their treatment contributed to the pilot's poor decision-making in continuing a night VFR flight into IFR conditions or his susceptibility to spatial disorientation could not be determined from the available information.

Probable cause

The non-instrument-rated pilot's decision to continue a night visual flight rules into instrument flight rules conditions, which resulted in spatial disorientation and a loss of airplane control. Contributing to the accident was the pilot's failure to obtain an official weather briefing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR17FA044
Event ID
20161230X55950
Case number
WPR17FA044
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2016-12-30.
  • API snapshot SHA-256: ac492ebd5226d4893224d0243243ecfacc68420f256e4f45db1ee7ad689e874f; retrieved 2026-09-14T22:04:57.162Z.