Narrative:

I was working ZLC sector 4 without a d-side. I only had 8 to 10 airplanes, so no help was required. Aircraft X was eastbound on J84 about 60NM west of dta when I took the handoff on him. Aircraft Y was northbound mlf direct dta then J148 eastbound. Aircraft Y had been at FL290 which was not my airspace. The sector south of me climbed aircraft Y to FL330 and handed him off to me when he was about 40NM south of dta. Aircraft X checked on my frequency and was extremely broken. I asked him to identify and he did. Aircraft Y still had not checked on frequency when I felt it was time to turn him, so I called the sector south of me and they said they had already shipped him. I issued a turn to aircraft Y and received no response. I then turned aircraft X and got no response. I asked aircraft X to acknowledge his turn with an identify, which he did. I then issued another turn to aircraft Y and asked him to acknowledge with an identify. He idented and then told me that he had heard me all the time, but was on a company filed mountain wave deviation route and would not accept the turn. At this time the aircraft were about 20 NM apart and closing. I issued aircraft Y a 60 degree turn and told him we would discuss his pilot deviation later. Aircraft Y reported aircraft X in sight and said he was making the turn. Aircraft Y passed 7.5 NM behind aircraft X at the same altitude. I had traffic at FL350 and do not own FL310, so altitude was not an option for me. We have had trouble with the receivers on sector 4 for over two years. Several ucr's and other complaints have been filed, but management does not seem in a hurry to fix this problem. The site at fpk needs to be moved to filmore or some other location that provides coverage in the dta area. This is not an isolated incident and will happen until we get reliable receivers. Callback conversation with reporter revealed the following information: reporter advised that the francis peak (fpk) transmitter/receiver site was recabled 3 or 4 years ago, and has had receiver problems since. He advised that facility coordination had at one time been initiated to close the fpk site and move the frequency's to the filmore site, also in the vicinity of slc, ut, but for some reason, was not completed. A pilot deviation was addressed by a supervisor, but was denied because the mountain wave route aircraft Y was flying was a facility coordinated and approved routing. The reporter identified the poor communication area as: from 50 south of dta VORTAC to dta for aircraft deping from, or over flying the las, nv, area. The slc VORTAC 225 030 to the slc 225 030, and from 80 west of dta to 30 west of dta. Altitudes affected were FL330 through FL370, occasionally up to FL410.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZLC CTLR INVOLVED IN A CTL INCIDENT WHILE ATTEMPTING TO RESOLVE CROSSING CONFLICT IN AN AREA OF KNOWN POOR RADIO COVERAGE.

Narrative: I WAS WORKING ZLC SECTOR 4 WITHOUT A D-SIDE. I ONLY HAD 8 TO 10 AIRPLANES, SO NO HELP WAS REQUIRED. ACFT X WAS EBOUND ON J84 ABOUT 60NM W OF DTA WHEN I TOOK THE HANDOFF ON HIM. ACFT Y WAS NBOUND MLF DIRECT DTA THEN J148 EBOUND. ACFT Y HAD BEEN AT FL290 WHICH WAS NOT MY AIRSPACE. THE SECTOR S OF ME CLIMBED ACFT Y TO FL330 AND HANDED HIM OFF TO ME WHEN HE WAS ABOUT 40NM S OF DTA. ACFT X CHECKED ON MY FREQ AND WAS EXTREMELY BROKEN. I ASKED HIM TO IDENT AND HE DID. ACFT Y STILL HAD NOT CHECKED ON FREQ WHEN I FELT IT WAS TIME TO TURN HIM, SO I CALLED THE SECTOR S OF ME AND THEY SAID THEY HAD ALREADY SHIPPED HIM. I ISSUED A TURN TO ACFT Y AND RECEIVED NO RESPONSE. I THEN TURNED ACFT X AND GOT NO RESPONSE. I ASKED ACFT X TO ACKNOWLEDGE HIS TURN WITH AN IDENT, WHICH HE DID. I THEN ISSUED ANOTHER TURN TO ACFT Y AND ASKED HIM TO ACKNOWLEDGE WITH AN IDENT. HE IDENTED AND THEN TOLD ME THAT HE HAD HEARD ME ALL THE TIME, BUT WAS ON A COMPANY FILED MOUNTAIN WAVE DEV ROUTE AND WOULD NOT ACCEPT THE TURN. AT THIS TIME THE ACFT WERE ABOUT 20 NM APART AND CLOSING. I ISSUED ACFT Y A 60 DEG TURN AND TOLD HIM WE WOULD DISCUSS HIS PLT DEV LATER. ACFT Y RPTED ACFT X IN SIGHT AND SAID HE WAS MAKING THE TURN. ACFT Y PASSED 7.5 NM BEHIND ACFT X AT THE SAME ALT. I HAD TFC AT FL350 AND DO NOT OWN FL310, SO ALT WAS NOT AN OPTION FOR ME. WE HAVE HAD TROUBLE WITH THE RECEIVERS ON SECTOR 4 FOR OVER TWO YEARS. SEVERAL UCR'S AND OTHER COMPLAINTS HAVE BEEN FILED, BUT MANAGEMENT DOES NOT SEEM IN A HURRY TO FIX THIS PROB. THE SITE AT FPK NEEDS TO BE MOVED TO FILMORE OR SOME OTHER LOCATION THAT PROVIDES COVERAGE IN THE DTA AREA. THIS IS NOT AN ISOLATED INCIDENT AND WILL HAPPEN UNTIL WE GET RELIABLE RECEIVERS. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR ADVISED THAT THE FRANCIS PEAK (FPK) TRANSMITTER/RECEIVER SITE WAS RECABLED 3 OR 4 YEARS AGO, AND HAS HAD RECEIVER PROBS SINCE. HE ADVISED THAT FAC COORD HAD AT ONE TIME BEEN INITIATED TO CLOSE THE FPK SITE AND MOVE THE FREQ'S TO THE FILMORE SITE, ALSO IN THE VICINITY OF SLC, UT, BUT FOR SOME REASON, WAS NOT COMPLETED. A PLT DEV WAS ADDRESSED BY A SUPVR, BUT WAS DENIED BECAUSE THE MOUNTAIN WAVE ROUTE ACFT Y WAS FLYING WAS A FAC COORDINATED AND APPROVED ROUTING. THE RPTR IDENTIFIED THE POOR COM AREA AS: FROM 50 S OF DTA VORTAC TO DTA FOR ACFT DEPING FROM, OR OVER FLYING THE LAS, NV, AREA. THE SLC VORTAC 225 030 TO THE SLC 225 030, AND FROM 80 W OF DTA TO 30 W OF DTA. ALTS AFFECTED WERE FL330 THROUGH FL370, OCCASIONALLY UP TO FL410.

Data retrieved from NASA's ASRS site as of July 2007 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.