FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR16FA014 · Piper PA 28R-180

17 Oct 2015 · Morongo Valley, CA, United States

Piper PA 28R-180 · Accident: loss of visual reference en route

From Palm Springs International Airport (PSP) to Santa Barbara Municipal Airport (SBA)

Report a problem

Event

NTSB case
WPR16FA014
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
2 · 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

Piper PA 28R-180

Aircraft type
Piper PA-28
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
N4972J
Operator
Unknown
Onboard fatalities
Unknown
Route
From Palm Springs International Airport (PSP), Palm Springs, CATo Santa Barbara Municipal Airport (SBA), Santa Barbara, CA
Aircraft age
About 47 years (built 1968)
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 visual reference
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

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

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The non-instrument rated private pilot and his passenger completed a cross-country flight from their home base to another airport in the airplane earlier that day. They delayed their initial planned departure time for that flight due to weather concerns, ultimately arriving 3 hours later than planned. During that flight, they flew over a high mountain range and through a mountain pass.

For the return (accident) flight a few hours later, the weather had deteriorated, resulting in low ceilings along the original route (including in the pass), with high cloud tops and rapidly building cloud formations west and north of the departure airport in the intended direction of the return flight. However, there is no record that the pilot obtained weather information before departing on the return flight.

While on the ground, the pilot reported to air traffic control that he was planning to take a "northern route," which would have taken them around the north side of the east-west mountain range that they had crossed on the inbound leg. Shortly after takeoff, the pilot reported to air traffic control that, due to clouds, he would need to climb to an altitude of 9,000 ft mean sea level (msl), which was almost twice as high as originally requested. The request was most likely because, once airborne, the pilot could see the full extent of the building cloud formations to the north along his route, as well as the formations building just west of the departure airport.

As the flight proceeded, the air traffic controller began the first of what would become a series of warnings to the pilot about mountainous terrain. The pilot responded that he was aware of the terrain. He then began a series of six climbing 360° turns, rolling out on a west heading directly toward, and about 700 ft lower than, the mountain peak. The controller warned the pilot of the peak several times, and the pilot responded, sounding confused, stating that he was still climbing.

Now cruising at an altitude of about 11,000 ft msl, the airplane's climb capabilities had diminished. Furthermore, the pilot did not appear to be flying the airplane at a speed that would have resulted in optimal climb performance. The airplane continued heading west, now no longer climbing and most likely just above the cloud tops. With high and ominous-looking cloud formations now building to the left and right of the flight track, the pilot most likely opted to continue on his homeward westerly track, while attempting to climb over the terrain and clouds ahead.

The airplane then suddenly reversed course and rapidly descended. It then transitioned to a fast spiraling descent, and, when challenged by the controller as to whether he had the terrain in sight, the pilot exclaimed, "Negative! Negative!" The turn rate increased as the airplane descended to about 7,500 ft msl and then impacted mountainous terrain just below the cloud bases. Examination of the accident site indicated that the airplane struck the ground in a wings-level attitude at a high forward speed. Damage patterns indicated that the engine was producing power at impact.

It is likely that, unable to outclimb the terrain and the cloud tops, the airplane entered the clouds and thus instrument meteorological conditions during the final portion of the flight, and the pilot then experienced spatial disorientation and lost control of the airplane, which resulted in the rapid descent. Additionally, prior to the descent into clouds, he was flying almost directly towards the sun, which could have been a further distraction and additional source of stress.

Many of the 71-year-old pilot's medical conditions, including hypertension, low testosterone, Barrett's esophagus, chronic obstructive pulmonary disease, deafness, chronic neck pain, vitamin D deficiency, and prediabetes, were unlikely to cause acute symptoms or be chronically impairing. Similarly, his blood pressure medication, cholesterol medication, testosterone, and prostate medication would not have impaired judgement, decision-making, or flight skills.

However, several medications that the pilot was using would have impairing effects. Hydrocodone, which was detected in the toxicology testing, is an impairing opiate pain medication and carries warnings regarding hazards while driving or operating machinery; however, with regular use, a chronic user may appear to function normally, so the pilot may not have been impaired by his use of opiods. Quetiapine, also detected during toxicology testing, is an antipsychotic indicated for the treatment of schizophrenia and bipolar syndrome and carries warnings for an increased risk of seizures and somnolence. It can also impair judgment, thinking, or motor skills, and may have impaired the pilot's performance during the accident flight.

The pilot's medical records revealed that he had required years of ongoing psychotherapeutic support to manage the combined symptoms of PTSD and depression; at the time of the accident he had been experiencing an exacerbation of those symptoms for several months, and it did not appear that the symptoms had been completely resolved. Patients with PTSD experience marked cognitive, affective, and behavioral responses to stimuli. These symptoms are likely to occur in stressful situations and may have contributed to his confusion during the high workload period while attempting to ascend above mountain peaks. Further, depression is associated with cognitive degradation, particularly in executive functioning.

Therefore, under the stressful conditions of this flight, the combined effects of impairing medications, depression, and PTSD likely resulted in the pilot experiencing significant cognitive degradation.

Probable cause

The non-instrument rated pilot's improper inflight decision-making to attempt to outclimb clouds along his planned route rather than reverse course, which resulted in his inadvertent entry into instrument meteorological conditions, spatial disorientation, and a resultant loss of control. The pilot's preexisting medical conditions and his use of impairing medications contributed to his degraded performance.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR16FA014
Event ID
20151017X04139
Case number
WPR16FA014
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: 45388d9cf0d495d74ac4aa5e2dbd94071c1a0738917946945cb99f24d8976fe2; retrieved 2026-09-14T21:32:57.188Z.