Narrative:

A UH60 IFR at 4;000 ft en route to ijd for RNAV runway 27 practice approach. I switched the UH60 to frequency 123.67 (the main frequency for that sector when decombined) 10 NM prior to entering that controller's airspace. Shortly after the UH60 came back saying that couldn't reach anyone. The other controller never heard any check in from the UH60. I then coordinated to use 133.8; the frequency for the overlying sector which was combined at the time. Again the UH60 came back saying he could not reach them. The other controller tried reaching out as well; but neither heard each other. I then coordinated a point out and I would keep the UH60 for the approach despite it being at 15 NM into the other sector. The frequency I had the UH60 on in my sector would not work well that far north so I changed him to my frequency of 127.9 which is used sometimes in that area. Twenty miles from the final fix; I issued him the missed approach instructions which Y90 requested; ijd is in their airspace but we run the approach. I attempted to clear him 12 NM from the procedure turn fix but got no response. I repeated this 5 or 6 more times with no response on main or standby. I changed an aircraft that was at a high altitude in that area to frequency 127.9 to try a relay; but he could not reach him either. A few miles later I was able to get a response; cleared the UH60 and told him that I would probably lose him on radio again and to change to the advisory frequency once established on final if no further instructions are received. I tried to call him as he made his procedure turn inbound with no response. If I had anything more than moderate traffic all these communications and coordination's would have been extremely burdensome and distracting for what essentially was a practice approach. The frequency coverage in our airspace is extremely poor. It is possible that the radio on the UH60 was also very poor; but it worked fine as he transitioned the heart of my airspace. Procedurally; I would handle this situation exactly the same in the future. I knew the frequency might become problematic so I tried to accomplish all instructions as soon as possible once the aircraft was unable to establish communication with the other sector. It seems that the only real solution to prevent this situation from occurring again; unless due to an aircraft equipment issue; is to fix the ongoing inadequacy in our frequency coverage. It is unacceptable that we are unable to communicate with aircraft with any frequency within the confines of our airspace. This has been a long documented issue; yet so far no working solution has been enacted.

Google
 

Original NASA ASRS Text

Title: PVD Controller described a lost communications event noting this type of radio coverage limitation has been problematic for some time.

Narrative: A UH60 IFR at 4;000 FT en route to IJD for RNAV Runway 27 practice approach. I switched the UH60 to frequency 123.67 (the main frequency for that sector when decombined) 10 NM prior to entering that Controller's airspace. Shortly after the UH60 came back saying that couldn't reach anyone. The other Controller never heard any check in from the UH60. I then coordinated to use 133.8; the frequency for the overlying sector which was combined at the time. Again the UH60 came back saying he could not reach them. The other Controller tried reaching out as well; but neither heard each other. I then coordinated a point out and I would keep the UH60 for the approach despite it being at 15 NM into the other sector. The frequency I had the UH60 on in my sector would not work well that far north so I changed him to my frequency of 127.9 which is used sometimes in that area. Twenty miles from the final fix; I issued him the missed approach instructions which Y90 requested; IJD is in their airspace but we run the approach. I attempted to clear him 12 NM from the procedure turn fix but got no response. I repeated this 5 or 6 more times with no response on main or standby. I changed an aircraft that was at a high altitude in that area to frequency 127.9 to try a relay; but he could not reach him either. A few miles later I was able to get a response; cleared the UH60 and told him that I would probably lose him on radio again and to change to the advisory frequency once established on final if no further instructions are received. I tried to call him as he made his procedure turn inbound with no response. If I had anything more than moderate traffic all these communications and coordination's would have been extremely burdensome and distracting for what essentially was a practice approach. The frequency coverage in our airspace is extremely poor. It is possible that the radio on the UH60 was also very poor; but it worked fine as he transitioned the heart of my airspace. Procedurally; I would handle this situation exactly the same in the future. I knew the frequency might become problematic so I tried to accomplish all instructions as soon as possible once the aircraft was unable to establish communication with the other sector. It seems that the only real solution to prevent this situation from occurring again; unless due to an aircraft equipment issue; is to fix the ongoing inadequacy in our frequency coverage. It is unacceptable that we are unable to communicate with aircraft with any frequency within the confines of our airspace. This has been a long documented issue; yet so far no working solution has been enacted.

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