Narrative:

ATC gave us the DELTA4 since slc was landing south. We then were given a new slc ATC frequency and were told to do the JAMMN4 due to possible GPS outages/jamming in the area. Just as we were given that; a new ATIS had come out indicating that slc had changed landing runway direction to north. It seemed to have caught the controller off guard. She told us to standby for a new arrival. A few moments pass. Then we were given the QWENN4; once again and told to go direct frnzy intersection and cross it at 15;000. While we were entering the new arrival in the FMS; I was on heading in case the FMS went back to any earlier fixes. Once entered; for some reason; I never went direct to frnzy nor did I start my descent to 15;000. I think it was because my first officer and I were discussing how confusing all the changes were and how the GPS outage was going to affect our arrival. I realized my mistake a few minutes later and went direct to frnzy and started a steep descent to try and make the restriction. I believe I was approximately 10 miles from frnzy at 31;000 feet when I took action. Just after taking action; ATC came on and apologized for all the arrival confusion and said they would work with us to get down without any issues. I'm estimating that I crossed frnzy around the mid 20's and was at 15;000 ft approximately 10 miles north of frnzy. Slc center handed us over to slc approach control without any other problems. My first officer was on IOE after being off for approximately a year. He was doing a fine job entering things into the FMS; but I believe we both were caught up in being distracted by multiple changes and discussing them; as well as; a controller that gave us confusing and late changes. Mode confirmation and taking action once given instructions by ATC wasn't done in a timely manner.

Google
 

Original NASA ASRS Text

Title: C560XL Captain reported multiple routing changes and advisories of GPS outages distracted them resulting in several clearance deviations.

Narrative: ATC gave us the DELTA4 since SLC was landing south. We then were given a new SLC ATC frequency and were told to do the JAMMN4 due to possible GPS outages/jamming in the area. Just as we were given that; a new ATIS had come out indicating that SLC had changed landing runway direction to north. It seemed to have caught the controller off guard. She told us to standby for a new arrival. A few moments pass. Then we were given the QWENN4; once again and told to go direct FRNZY intersection and cross it at 15;000. While we were entering the new arrival in the FMS; I was on heading in case the FMS went back to any earlier fixes. Once entered; for some reason; I never went direct to FRNZY nor did I start my descent to 15;000. I think it was because my First Officer and I were discussing how confusing all the changes were and how the GPS outage was going to affect our arrival. I realized my mistake a few minutes later and went direct to FRNZY and started a steep descent to try and make the restriction. I believe I was approximately 10 miles from FRNZY at 31;000 feet when I took action. Just after taking action; ATC came on and apologized for all the arrival confusion and said they would work with us to get down without any issues. I'm estimating that I crossed FRNZY around the mid 20's and was at 15;000 ft approximately 10 miles north of FRNZY. SLC center handed us over to SLC approach control without any other problems. My first officer was on IOE after being off for approximately a year. He was doing a fine job entering things into the FMS; but I believe we both were caught up in being distracted by multiple changes and discussing them; as well as; a controller that gave us confusing and late changes. Mode confirmation and taking action once given instructions by ATC wasn't done in a timely manner.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.