ASN Wikibase Occurrence # 192411
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Thursday 29 December 2016 |
| Time: | 18:44 |
| Type: |  Cessna 182P Skylane |
| Owner/operator: | Private |
| Registration: | N52388 |
| MSN: | 18262571 |
| Year of manufacture: | 1973 |
| Total airframe hrs: | 2554 hours |
| Engine model: | Continental O-470-R-25A |
| Fatalities: | Fatalities: 4 / Occupants: 4 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | near Dabob Bay, east of Quilcene, WA -
 United States of America
|
| Phase: | En route |
| Nature: | Private |
| Departure airport: | Seattle-Boeing Field International Airport, WA (BFI/KBFI) |
| Port Angeles-Fairchild International Airport, WA (CLM/KCLM) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
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.
Accident investigation:
 |
|
Sources:
NTSB
FAA register: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=N52388
https://flightaware.com/live/flight/N52388
Location
Images:
Photo: NTSB
Media:
NTSB on C182 N52388 (4F): The non-IR pilot continued under night VFR into IMC: spatial disorientation and LOC-l. Contributing was the pilot's failure to obtain an official weather briefing. #flightsafetyhttps://t.co/rBYiQoCPRI pic.twitter.com/ReIRo2URbF
— Aerossurance (@Aerossurance) February 28, 2019
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 30-Dec-2016 22:53 | Geno | Added |
| 30-Dec-2016 23:27 | Geno | Updated [Source] |
| 31-Dec-2016 00:38 | Geno | Updated [Aircraft type, Registration, Cn, Operator, Source] |
| 31-Dec-2016 00:40 | Geno | Updated [Aircraft type] |
| 31-Dec-2016 10:31 | Chieftain | Updated [Source] |
| 28-Feb-2019 04:28 | Aerossurance | Updated [Location, Nature, Embed code, Narrative] |
| 02-Mar-2019 14:46 | ASN Update Bot | Updated [Departure airport, Destination airport, Source, Embed code, Damage, Narrative, Accident report, ] |
| 03-Mar-2019 10:55 | harro | Updated [Source, Embed code, Narrative, Photo] |
| 03-Mar-2019 10:55 | harro | Updated [Departure airport, Destination airport] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation