ASN Wikibase Occurrence # 187331
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: | Sunday 15 May 2016 |
| Time: | 08:29 |
| Type: |  Cessna R182 Skylane RG |
| Owner/operator: | Private |
| Registration: | N133BW |
| MSN: | R18200450 |
| Year of manufacture: | 1978 |
| Total airframe hrs: | 8912 hours |
| Engine model: | Lycoming O-540-J3C5D |
| Fatalities: | Fatalities: 1 / Occupants: 1 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | Near Brown Mountain, Angeles National Forest, CA -
 United States of America
|
| Phase: | En route |
| Nature: | Private |
| Departure airport: | San Diego, CA |
| Santa Monica, CA | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The instrument-rated private pilot departed in the airplane on a cross-country flight under daytime instrument meteorological conditions (IMC). Throughout the first portion of the flight, the pilot was in contact with air traffic control (ATC) controllers. As the flight neared its destination, the pilot was instructed to turn the airplane to a heading of 030° and maintain an altitude of 4,000 ft mean sea level (msl). The pilot complied with the instructions and was told to change frequencies to another ATC sector. The new controller provided the pilot with an altimeter setting and approach information, which the pilot acknowledged receiving. A short time later, the controller issued the pilot directions to turn left to a heading of 290° and descend to 3,000 ft msl for a radar vector to the final approach course. Despite 10 attempts by the controller to reach the pilot, no response was received. About 3 minutes after the controller issued the initial heading and altitude change, the pilot transmitted that he was still on the 030° heading. The controller immediately responded to the pilot and provided him instructions to turn left and climb to 6,000 ft msl. The pilot did not respond, and the airplane continued on the 030° heading toward mountainous terrain with elevations above the airplane's 4,000-ft altitude. The controller made 17 additional attempts to communicate with the pilot over a period of about 5 minutes. There was no response before radar contact with the airplane was lost. The airplane impacted mountainous terrain near the last recorded radar target at an elevation of about 4,000 ft.
Weather data indicated that the flight would likely have been in IMC between 2,800 and 5,000 ft msl; therefore, the terrain would not have been visible to the pilot. However, avionics equipment installed in the airplane could have displayed a moving map showing the airplane's current position in relation to airports, and navigational aids.
The wreckage was severely fragmented and mostly consumed by a postimpact fire. The damage to the airplane was consistent with controlled flight into terrain. Although no evidence of preimpact mechanical malfunctions was found, the severity of the damage to the airplane precluded testing of the airplane's avionics equipment. It could not be determined why the pilot was unable to communicate with ATC or why he failed to maintain situational awareness and clearance from rising mountainous terrain.
The pilot's autopsy results revealed severe coronary artery disease, which placed the pilot at significantly increased risk of acute impairment or incapacitation by a cardiac event such as ischemia, a heart attack, or an arrhythmia, which could include symptoms ranging from chest pain, shortness of breath, or palpitations all the way to loss of consciousness. However, during the pilot's last transmission, he did not mention any such symptoms, and he did not seem to be in distress. Therefore, it is unlikely that an acute cardiac event caused or contributed to this accident. Toxicology testing identified the pilot's use of a potentially impairing drug, hydrocodone. However, there was no blood available for testing, and there is no method for calculating blood levels from liver or urine results. While the impairing effects of hydrocodone and its metabolite dihydrocodeine could have decreased the pilot's attentiveness or increased his susceptibility to a distraction, whether this occurred could not be determined.
Probable Cause: The pilot's failure to maintain clearance from rising mountainous terrain while flying in instrument meteorological conditions. Contributing to the accident was the loss of radio communications for a reason that could not be determined because of the extensive impact and thermal damage to the airplane.
Accident investigation:
 |
|
Sources:
NTSB
https://flightaware.com/live/flight/N133BW/history/20160515/1424Z/KMYF/KSMO
FAA register: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=133BW
https://flightaware.com/photos/view/563408-c0b6aedd903f740d6206ae68011aa2b4604e7d7f/aircraft/N133BW
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 15-May-2016 19:52 | Geno | Added |
| 15-May-2016 19:57 | Geno | Updated [Departure airport, Narrative] |
| 16-May-2016 05:13 | Geno | Updated [Time, Total fatalities, Total occupants, Other fatalities, Location, Source, Damage, Narrative] |
| 16-May-2016 06:28 | Anon. | Updated [Operator] |
| 16-May-2016 06:39 | Anon. | Updated [Operator, Narrative] |
| 17-May-2016 19:04 | bovine | Updated [Source] |
| 21-Dec-2016 19:30 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 28-Dec-2016 08:36 | Anon. | Updated [Source] |
| 11-Feb-2018 10:59 | Anon. | Updated [Source] |
| 22-Apr-2018 19:29 | ASN Update Bot | Updated [Operator, Nature, Departure airport, Destination airport, Source, Narrative] |
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