EMB-505 / Phenom 300
Flight Crew Air Transport Pilot (ATP)
Confusion; Distraction; Troubleshooting; Workload
Inflight Event / Encounter Other / Unknown
Flight Crew FLC complied w / Automation / Advisory; Flight Crew Overcame Equipment Problem; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Took Evasive Action
Aircraft; Environment - Non Weather Related
Descending out of cruise onto the STAR into SLC we encountered what turned out to be GPS jamming operations which seriously degraded the Phenom's ability to navigate via RNAV. We advised ATC; requested vectors and ran the AHARs (Altitude and Heading Reference System) 1 & 2 fail checklists. We were vectored for 34R and advised a regional jet was visual for 35 but was unable to make visual contact with that traffic and advised ATC. We were cleared for the visual approach and while on approach had multiple TCAS RAs commanding 'descend' we complied and advised ATC. After the 3rd RA we were below 1200 AGL and requested a break off to the left and was offered a go-around but the TCAS still showed the traffic above us (400 ft). We were able to maneuver for a stable approach and landing after the traffic diverged and we had a 'clear of conflict' call out. I called tower after landing and was told they had no evidence of a conflict and that we were compliant with all ATC instructions.I do not know if the GPS jamming affected the TCAS. This was a difficult situation with traffic depicted above us; responding to the mandatory RA requirements to descend; and the only offer from ATC was a go-around. Obviously things worked out in this instance. I offer this report in the hope that it may create better options for response and to warn other crews of this possibility.
Phenom 300 Captain reported a serious degradation of his ability to navigate due to suspected GPS jamming while descending into SLC. Captain received radar vectors from ATC to the airport; however; they experienced several RAs from an undetermined source during the approach.