Narrative:

Due to the niagara main frequency 120.62 not working correctly; the sector frequency was on the standbys. As I was relieving the previous controller; the supervisor asked me to get checks on the mains. I proceeded to switch to the main frequency and continued to work the traffic. The traffic was a little complex with arrivals and departures. Also some additional traffic in the airspace. The frequencies appeared to be working fine except; the trainer who was training the d-side; told me that the area where the problem was earlier in the morning was south of all the aircraft that I had talked to. Lucky and unlucky for me; I had a syracuse arrival at FL410 entering the area that was having the frequency issues. Sure enough; the aircraft entered my airspace without checking on. So I called the aircraft 2 or 3 times to see if he was on the frequency and got no response. The d-side training team then called the previous sector to see if they switched comms to the aircraft; and they had switched him a while ago. Another aircraft in the area; going westbound at FL430; apparently was also attempting to call me; which I never heard. The syracuse arrival went back to the previous frequency at which time the controller from that sector called me and told me that aircraft had been attempting to call me but got no response; he then asked if I wanted to put the aircraft on [a different frequwncy]. I told the controller yes and then proceeded to switch back to the standby frequency on 120.62. And that's when things got a little hectic. Now I could hear the aircraft at FL410 and FL430 calling me; who was now stepping all over the several other aircraft that were checking on or looking for information. While I was trying to get the frequency congestion resolved. I noticed a departure; aircraft X had entered sector 77s airspace without a hand off. I immediately started a hand off to sector 77 and instructed the d-side training team; who had just finished dealing with another sector because of the frequency issues; to call sector 77 and do a manual handoff. Luckily there was no aircraft in that area and was not a loss of separation. I have one big and quite easy recommendation; fix the frequency.120.62 has had issues for as long as controllers that I have worked with in ZOB can remember. The problem isn't 100% all the time but I'd say 60-80% of the time there is a dead spot on the west side of the airspace. So bad some days that we have to go to back up emergency communications (buec) or use a different frequency. But all those are work arounds. The main problem is that the main transmitter and receiver on 120.62 are not working properly in the western area of the sector. And while we have been lucky not to have had any incidents; guess what; my luck ran out. I'm told another controller has submitted numerous [reports] about this problem and was told; in so many words; to stop filing them.the complaints go unheard; the papers go unread and nothing gets done or they are heard and they are read and the FAA chooses to do nothing. This is a serious problem. Not being able to talk to aircraft can cause chaos on the frequencies. Something needs to be done before there is a more serious incident.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZOB controller reported recurring radio coverage failures of Niagara sector.

Narrative: Due to the Niagara Main frequency 120.62 not working correctly; the sector frequency was on the standbys. As I was relieving the previous controller; the supervisor asked me to get checks on the Mains. I proceeded to switch to the main frequency and continued to work the traffic. The traffic was a little complex with arrivals and departures. Also some additional traffic in the airspace. The frequencies appeared to be working fine except; the trainer who was training the D-SIDE; told me that the area where the problem was earlier in the morning was south of all the aircraft that I had talked to. Lucky and unlucky for me; I had a Syracuse arrival at FL410 entering the area that was having the frequency issues. Sure enough; the aircraft entered my airspace without checking on. So I called the aircraft 2 or 3 times to see if he was on the frequency and got no response. The D-side training team then called the previous sector to see if they switched comms to the aircraft; and they had switched him a while ago. Another aircraft in the area; going westbound at FL430; apparently was also attempting to call me; which I never heard. The Syracuse arrival went back to the previous frequency at which time the controller from that sector called me and told me that aircraft had been attempting to call me but got no response; he then asked if I wanted to put the aircraft on [a different frequwncy]. I told the controller yes and then proceeded to switch back to the standby frequency on 120.62. And that's when things got a little hectic. Now I could hear the aircraft at FL410 and FL430 calling me; who was now stepping all over the several other aircraft that were checking on or looking for information. While I was trying to get the frequency congestion resolved. I noticed a departure; Aircraft X had entered Sector 77s airspace without a hand off. I immediately started a hand off to sector 77 and instructed the D-Side training team; who had just finished dealing with another sector because of the frequency issues; to call sector 77 and do a manual handoff. Luckily there was no aircraft in that area and was not a loss of separation. I have one big and quite easy Recommendation; fix the frequency.120.62 has had issues for as long as controllers that I have worked with in ZOB can remember. The problem isn't 100% all the time but I'd say 60-80% of the time there is a dead spot on the west side of the airspace. So bad some days that we have to go to Back Up Emergency Communications (BUEC) or use a different frequency. But all those are work arounds. The main problem is that the Main Transmitter and Receiver on 120.62 are not working properly in the western area of the sector. And while we have been lucky not to have had any incidents; guess what; MY luck ran out. I'm told another controller has submitted numerous [reports] about this problem and was told; in so many words; to stop filing them.The complaints go unheard; the papers go unread and nothing gets done or they are heard and they are read and the FAA chooses to do nothing. This is a serious problem. Not being able to talk to aircraft can cause chaos on the frequencies. Something needs to be done before there is a more serious incident.

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.