Accident Details
Probable Cause and Findings
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.
Aircraft Information
Registered Owner (Historical)
Analysis
HISTORY OF FLIGHTOn October 17, 2015, at 1552 Pacific daylight time, a Piper PA28R-180, N4972J, impacted mountainous terrain near Morongo Valley, California. The private pilot and passenger sustained fatal injuries; the airplane was destroyed. The airplane was registered to and operated by the pilot under the provisions of 14 Code of Federal Regulations (CFR) Part 91. The cross-country personal flight departed Palm Springs International Airport (PSP), Palm Springs, California, at 1513, with a planned destination of Santa Barbara Municipal Airport, Santa Barbara, California. Visual meteorological conditions prevailed at the departure airport, and no flight plan had been filed.
Earlier on the day of the accident, the pilot and passenger flew the airplane from their home base of Santa Barbara to Palm Springs in order to visit a museum. According to friends, the original planned departure time for the flight to Palm Springs was 0900; however, due to weather conditions, they departed just before noon and arrived about 1330. Radar data revealed that the route of the outbound flight was via Santa Paula, Valencia, and Acton, then across the east-west mountain range of the Angeles National Forest, across the Los Angeles Basin, and through the Banning Pass to Palm Springs.
For the return trip, the pilot requested visual flight rules (VFR) flight following from the clearance delivery controller at Palm Springs and reported that his route of flight back to Santa Barbara would be along a northern route via Palmdale. He initially requested an altitude of 7,500 ft mean sea level (msl) and then immediately corrected himself, requesting 5,500 ft msl. The controller responded, telling the pilot to squawk VFR and to expect a northbound departure with an unrestricted climb.
Radar and audio data provided by the Federal Aviation Administration (FAA) captured the entire flight sequence, beginning with the departure from runway 31R at PSP.
Following takeoff, the airplane began a climb to the north, and, about 6 minutes later, the pilot initiated radio contact with Southern California Terminal Radar Approach Control, stating that he was 6 miles northeast of Palm Springs. He requested VFR flight following to Santa Barbara and, during the exchange, stated, "It looks like we might have to get up to 9,000 ft with the clouds." The air traffic controller responded, providing the pilot with a squawk code, altimeter setting, and instructions to maintain VFR at an altitude at the pilot's discretion. The pilot confirmed the instructions, and, a short time later, the controller responded that he had obtained radar contact with the airplane. The airplane continued to climb, and, about 4 minutes later, after it reached an altitude of about 5,200 ft msl, the controller communicated, "just to be clear you do have the terrain in sight to your left, right?" The pilot responded in the affirmative and added that he was going to perform a 360° turn to gain altitude. The controller responded, "Ok, just wanted to make sure we are on the same page." The controller then transmitted, "Are you guessing you are going to wind up north of Big Bear or do you think you're going to be able to get up through the Banning Pass, is that what your intents are?" The pilot responded, "I'm going to try to go through San Bernardino and out to the desert then out by General Fox." The airplane then began a left 270° turn, rolling out on a northeast heading by which time it had reached an altitude of 7,000 ft msl.
Over the next 14 minutes, the airplane conducted a series of 6 climbing 360° turns, eventually rolling out on a west heading, at an altitude of 10,800 ft msl. By that time, the airplane was about 14 miles east of, and heading directly toward, the 11,500 ft peak of San Gorgonio Mountain. The pilot reported that he was now travelling west, and the controller transmitted, "So you're going to go north side of the peak then, there, correct?" The pilot reported, "Um, say again," and the controller responded, "N72J are you going to go north side of the peak there or south side there?" The pilot responded, "Umm, I show that we're heading right to San Bernardino." The controller retorted, "Ok, I show an eleven seven peak between you and San Bernardino." The pilot responded, "Um, I'm at um, one zero thousand six hundred." The controller responded, "Roger," and, after a brief pause, the pilot continued, "and I'm still climbing."
The airplane maintained the west heading and continued to climb at ground speeds varying between 60 and 70 knots, reaching 11,100 ft msl about 3 minutes later. It then conducted another 360° left turn but had not gained significant altitude once it rolled out about 2 minutes later. The westbound track continued at similar speeds toward the peak for the next 4 minutes, as the airplane climbed 200 ft to 11,300 ft. The next radar target appeared 15 seconds later, indicating the airplane had rapidly reversed course and descended to 9,700 ft msl. The airplane then began a spiraling descent, and the controller transmitted, "Piper 72J you are descending once again in an area of higher terrain just west of you, I have a peak that I show to be at eleven thousand seven hundred feet, just west of your position...72J you cut me out, verify you still have the terrain in sight." The pilot then transmitted, "Negative! Negative!," and in the background the passenger could be heard expressing significant alarm. The controller continued issuing instructions, "N72J remain calm, if you are able proceed eastbound, remain VFR proceed eastbound, hold your altitude if you are able I see you are descending - repeat, eastbound, VFR, hold your altitude if you are able you are in an area of higher terrain." The pilot did not respond, and, over the next 45 seconds, the airplane continued to perform two more spiraling turns, with radiuses of about 1,200 and 700 ft, respectively, to the last recorded radar position, at an altitude of 7,500 ft.
Over the next few minutes, the controller tried reestablishing communication with the pilot but did not receive a response. A Riverside County Sheriff's Department helicopter was flying in the vicinity, so the controller provided the helicopter's crew with vectors to the airplane's last radar location and asked if they could establish radio communication. They attempted to do so, but no response was received. They reported that the search area was mountainous and obscured by clouds, and, after multiple approach attempts, they located burning wreckage along a ridge, about 100 ft below the base of the clouds. The following three figures show the airplane's radar track.
Figure 1 - Route of Flight
Figure 2 - Excerpts of Pilot and Air Traffic Control Communications
Figure 3 - Radar Data Covering Final Two Minutes of Flight PERSONNEL INFORMATIONThe 71-year-old pilot held a third-class medical certificate limited by a requirement that he must wear corrective lenses for near and distant vision. He was issued a private pilot certificate on September 9, 2014, at which time he reported a total flight experience of 85 hours of which 15 hours were as pilot in command. All the reported flight experience was in a Cessna 172. The pilot did not hold an instrument rating.
The pilot was the general manager for a repair station at Santa Barbara Airport. The airplane was maintained at the repair station, and the passenger worked at the repair station.
No personal flight records were recovered; however, the repair station's chief inspector stated that the pilot had flown regularly in the airplane, taking multiple trips to Oregon and the Mojave area during the period between receiving his private certificate and the accident. He stated that the reason for the flight was to drop off memorabilia at the flight museum in Palm Springs, and he was not aware of any pressing reason for the pilot and passenger to return promptly that night. AIRCRAFT INFORMATIONThe single-engine, retractable-landing-gear airplane was manufactured in 1968 and powered by a fuel-injected Lycoming IO-360-B1E engine. An annual inspection was performed on May 27, 2015. At that time, the airframe had accrued 3,704.90 total flight hours, and the engine had accrued 1,308.0 hours since overhaul.
An avionics upgrade was performed following the May 2015 annual inspection and was completed on August 17, 2015. The upgrade included the installation of a Garmin GTN 650 touchscreen GPS/Nav/Comm and a Garmin GDL 88 ADS-B transceiver. In combination, the pairing provided the pilot with terrain mapping, graphical NEXRAD radar, and weather data on the GTN 650 screen. The chief inspector stated that the pilot was still gaining familiarity with the system and was not fully proficient with its use and features.
The chief inspector also reported that the pilot kept an iPad tablet computer onboard for weather and navigation and that the airplane was equipped with a portable oxygen system. Due to fire damage, neither of these systems could be positively identified in the debris; therefore, their operational status could not be determined. Photographs posted by the passenger on a social media website after the flight to Palm Springs indicated that the pilot had mounted the iPad on the control yoke. METEOROLOGICAL INFORMATIONThe pilot did not call Lockheed Martin Flight Service for a telephone weather briefing either the day before or the day of the accident, and there was no record of him downloading an official weather briefing from any DUAT vendor.
Satellite Data
Geostationary Operational Environmental Satellite number 15 (GOES-15) imagery taken at 1545 and 1600 indicated an area of low- to mid-level clouds over the accident site, with cloud tops near 11,000 ft (figure 4). During that period, an area of clouds was observed developing near Big Bear, California, 12 miles northwest of the accident site, along with rapidly developing enhanced clouds (tops near 33,000 ft) between the accident sit...
Data Source
Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# WPR16FA014