ZLC Controller reported scheduled GPS Jamming in their sector resulted in loss of radar contact with aircraft resulting in one of them flying below the Minimum Vectoring Altitude.
Synopsis
ZLC Controller reported scheduled GPS Jamming in their sector resulted in loss of radar contact with aircraft resulting in one of them flying below the Minimum Vectoring Altitude.
Narrative
I was D-Side for sectors 30/31. BOV radar was out. There was GPS jamming causing multiple aircraft to be on vectors due to lost GPS capabilities. We had Aircraft X on a heading due to reported loss of GPS. He was south east of TWF and recently climbed to 120 for terrain. We lost radar on Aircraft X; we were unable to climb him due to overhead traffic at 130. We were unable to give instructions to join the V484 due to the MEA being 160. Aircraft X was last seen on a heading to avoid a 123 MIA (Minimum IFR Altitude) box; but we lost radar monitoring capabilities. Aircraft X was ADS-B equipped; but we weren't receiving several ADS-B targets due to the jamming. As soon as radar contact was lost I went to my OS (Operation Supervisor) and asked for stop buzzer due to the situation. Instead of calling for stop buzzer the OS came over to our position; stood behind us and tried to give us instructions on what to do; all of which we were unable due to reasons listed above. The OS finally went to call for stop buzzer; by which time we reacquired radar on Aircraft X.Recommendation: OS should have accepted controller request for stop buzzerGPS jamming mission sheet with anticipated affect should be placed at the position; this used to be done and was stopped for some reason.GPS jamming should have been cancelled after BOV radar outage.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.