N3RB

HISTORY OF FLIGHTOn January 9, 2021, at 1337 Pacific standard time, a Cessna 560, N3RB, was destroyed when it was involved in an accident near Warm Springs, Oregon. The pilot, who was the sole occupant, was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 flight.

The pilot filed an instrument flight rules (IFR) flight plan to Boise Air Terminal/Gowen Field, Boise, Idaho. The reason for the flight could not be determined; however, family members and acquaintances stated that the pilot usually travelled with his dog, and because on this occasion he did not, he was likely planning to return that day. A friend also stated that Boise was a typical lunch destination for the pilot, and it would not be unusual for him to make a return trip in one day.

Security video footage from a fixed base operator at the departure airport in Troutdale, Oregon, revealed that the pilot boarded the airplane and closed the cabin door at 1244. Federal Aviation Administration (FAA) air traffic control audio recordings indicated that, about five minutes later, he initiated radio contact with the clearance controller and requested to open his IFR clearance. The controller provided the clearance, the pilot read it back correctly, and about nine minutes later, the pilot stated that he was ready to taxi and that he had information Foxtrot. The controller stated that information Golf was current and provided instructions to taxi to runway 07. The pilot replied, but only stated the altimeter setting, “3025”, and the ground controller asked him to respond with the full taxi instructions. The pilot responded, and about 1300 the airplane began to taxi to the runway hold short line.

The airplane arrived at the runway hold short line about 1304, and the ground controller asked if the pilot was ready for departure, to which the pilot replied, “just a minute.” About two minutes later, a partial transmission of the pilot’s voice could be heard, and the local controller asked twice if it was N3RB. The pilot stated that it was him, and the controller issued a takeoff clearance. The pilot responded, and at 1307, the airplane had taken off.

The pilot subsequently contacted the Portland Approach controller and was provided instructions to climb and maintain 15,000 ft mean sea level (msl). The pilot responded with, “up to 15,” following which the controller confirmed radar contact and instructed the pilot to turn left to a heading of 310°. The pilot did not respond, airplane did not turn, and over the next minute, both the Portland Approach and Troutdale Tower controllers made multiple attempts to contact the pilot. On the fifth attempt by the approach controller, the pilot responded and was again instructed to turn left. Automatic Dependent Surveillance – Broadcast (ADS-B) data indicated that the airplane then began to turn left; after one minute, the controller issued a heading of 180° and told the pilot to expect vectors for the TIMEE intersection after reaching 10,000 ft. The pilot did not respond until the controller issued the instructions a second time.

About one minute later, the airplane had reached 10,000 ft msl and was on a southbound heading. The controller then issued a clearance direct to the TIMEE intersection.

The pilot responded, and the airplane began to turn left; however, its heading was about 15° left of that required to reach the TIMEE intersection.

By 1315:30, the airplane had reached an altitude of 12,000 ft msl, and the controller asked the pilot to verify he was direct TIMEE. The pilot responded that he was; however, the airplane’s track had not changed, and the airplane was flying directly toward Mount Hood, about 27 miles to the east-southeast.

After the airplane had reached an altitude of 13,000 ft, the controller issued a right turn to 130°, and the pilot repeated the instructions correctly, but the airplane turned left. The controller asked of the pilot was flying direct TIMEE, to which the pilot replied, “I was.”

The controller explained that the pilot was in fact flying northeast and provided another right turn to a heading of 130°. The pilot responded, and the airplane began a right turn, eventually rolling out on a 130° track, after which the controller issued a frequency change to Seattle Center. The pilot responded with the correct frequency, but about one minute later, he called back with a confirmation of the Seattle center frequency.

By this time, the airplane had reached an altitude of 14,000 ft, and after the pilot made contact with the Seattle Center controller, the controller immediately issued a low altitude alert warning, stating that the airplane was just above the minimum IFR altitude for that sector (at this time, the airplane was flying just south of the peak of Mount Hood). The controller then issued him a clearance to 23,000 ft msl.

The pilot responded, and the airplane continued to climb. The controller then asked the pilot if he was having problems with his radio, to which responded, “no, I think it’s cleared up now, radio loud and clear.” The controller subsequently issued the pilot with a clearance direct to BOI.

About 1323, as the airplane reached an altitude of 19,000 ft, the pilot was provided a new frequency for Seattle Center. He responded with an incorrect frequency and was corrected by the controller. The pilot then successfully made contact with the new controller, who issued a clearance to climb to 37,000 ft msl. The pilot responded, and the airplane continued to track in the general direction of BOI while continuing to climb.

At 1327, the airplane had reached an altitude of 27,000 ft when it began to deviate to the right while continuing to climb. The controller alerted the pilot that he was about 30° right of course, but the pilot did not respond. The airplane continued to climb until 1328:45, when it reached its highest altitude of 31,000 ft. The airplane began to descend and remained for the next eight minutes in a spiraling and descending 1-mile radius right turn. (see Figure 1.) The last ADS-B target was recorded at 1336:27, with the airplane on a northwest heading at an altitude of 3,800 ft.

Figure 1 – Flight track

The airplane impacted the ground in the Mutton Mountain Range, at an elevation of 3,600 ft msl about 450 ft north of the last ADS-B target.

Hikers in the vicinity of the accident took photos of the smoke rising from the debris field. One of the photos captured a single, circular contrail at high altitude above the accident site. Likewise, the pilot of a single-engine airplane flying in the area, was able to capture the circular contrail on a forward-mounted video camera. The images did not reveal any evidence of smoke trails. A commercial airline flight crew overflying the area saw the airplane just before impact and did not see any vapors or smoke trailing from it.

PERSONNEL INFORMATIONThe pilot held a private pilot certificate, and although he held type ratings for the Grumman G-111 Albatross and Learjet, FAA records did not indicate that he held a type rating for the Citation 560.

The pilot had taken Citation 560 training toward the end of 2020 at a facility in Arizona. The owner of that facility provided some of the flight training and stated that, when the pilot had initially approached him, his plan was to accomplish both his commercial pilot certificate, Citation type rating, and single-pilot exemption consecutively. They developed a custom syllabus to meet these goals; however, after the first few flights, it became apparent that, while the commercial and Citation ratings were possible, the single-pilot exemption would likely take significantly more time to accomplish. The decision was then made to abandon the single-pilot exemption and focus on a “crew method” of training.

As the training progressed, the pilot encountered significant difficulty mastering the operation of the autopilot and the Garmin 750 avionics suite, which had recently been installed. The owner of the training facility stated that the pilot struggled significantly in high-workload environments, such as while flying instrument approaches, where multiple configuration changes needed to be accomplished in a short amount of time, and that the presence of the Garmin 750 appeared to aggravate the situation. He stated that as his instructor/first officer, he was never able to transition from “instructor” into “first officer” mode. The pilot would typically make some progress on one flight, but during following flights, the results could be unpredictable, and the pilot could not make consistent, repeatable progress mastering the airplane. Additionally, although the pilot had a good general grasp of standard airwork, he was struggling in particular with steep turns.

After over a dozen flights over the course of 3 weeks, the training was not complete, and the pilot decided that he needed to leave to take care of some business at home and planned to return later to resume training. At that time, he had not performed to a level sufficient to be issued the type rating.

Since October 2020, the pilot had an arrangement with a contract pilot who flew the accident airplane, while he sat in the right seat. The contract pilot stated that he did not get a chance to see the pilot fly the airplane; however, during one of their flights, the pilot stated that he preferred to “hand fly” the airplane rather than use the autopilot, because he did not consider himself a professional pilot.

Review of historical flight data and statements provided by acquaintances and other pilots who flew with him indicated that the accident flight was likely the first time the pilot had flown the airplane solo.

AIRCRAFT INFORMATIONOwnership of the airplane was transferred to the pilot in July 2020. As part of the negotiations for sale, an avionics upgrade was performed in April 2020, which included the addition of a Garmin 650 Xi and 750Xi avionics suite, along with a G...