Narrative:

I picked up my WX packet from operations for that days flying. I noticed that rdm or, had a NOTAM stating an amos had beem commissioned there but there was no frequency included in the NOTAM. Additionally, for some time there has been a class 3 NOTAM out stating cvo or, amos is 135.17. However, each time I passed by cvo and tried to monitor the amos I could not hear anything. I just thought the system was not yet fully functional and was therefore off the air. Later that day while flying between pdx and rdm I contacted rdm FSS 122.5 and asked for the frequency of the new rdm amos. They said it was 135.075, we were about 50 NM northwest at 13000'. I dialed it up and there it was but the voice was being covered by cvo amos. I then tried cvo amos on the published frequency of 135.17 and found nothing. I went back to 135.075 and both my first officer and myself could make out that both rdm and cvo amos are on the same frequency. The result was only a loud squeal that finally went away when we were within 20 NM of rdm. There we lost the cvo amos and could clearly hear rdm amos. Rdm FSS suggested that we contact pdx FSDO when we got back to pdx and inform them of the problem. Having only a short time at pdx I called FSDO, but because of meetings in progress, there was no one available to field my concerns. My next step was to contact sea FSDO. My call was directed to a mr X. I described the problem to him and he did not understand the different classes of NOTAMS and almost immediately said this is a pdx problem and you will have to contact pdx FSDO. I suggested that he might forward the information, but he then informed me that the offices do not talk to one another and I would need to contact pdx FSDO to get any action. Personally, I feel regardless of who's jurisdiction something is reported in these agencies have the responsibility to at least forward information. I do not believe it is my responsibility to accept the expense of long distance calls to report deficiencies on the system. I'm sure this problem has a simple solution.

Related reports:

Google
 

Original NASA ASRS Text

Title: NOTAM ON RDM, OR. AUTOMATIC METEOROLOGICAL OBSERVATION SYSTEM GIVES WRONG FREQ. CVO AMOS AND RDM AMOS OVERRIDE EACH OTHER PRODUCING A SQUEAL.

Narrative: I PICKED UP MY WX PACKET FROM OPS FOR THAT DAYS FLYING. I NOTICED THAT RDM OR, HAD A NOTAM STATING AN AMOS HAD BEEM COMMISSIONED THERE BUT THERE WAS NO FREQ INCLUDED IN THE NOTAM. ADDITIONALLY, FOR SOME TIME THERE HAS BEEN A CLASS 3 NOTAM OUT STATING CVO OR, AMOS IS 135.17. HOWEVER, EACH TIME I PASSED BY CVO AND TRIED TO MONITOR THE AMOS I COULD NOT HEAR ANYTHING. I JUST THOUGHT THE SYS WAS NOT YET FULLY FUNCTIONAL AND WAS THEREFORE OFF THE AIR. LATER THAT DAY WHILE FLYING BTWN PDX AND RDM I CONTACTED RDM FSS 122.5 AND ASKED FOR THE FREQ OF THE NEW RDM AMOS. THEY SAID IT WAS 135.075, WE WERE ABOUT 50 NM NW AT 13000'. I DIALED IT UP AND THERE IT WAS BUT THE VOICE WAS BEING COVERED BY CVO AMOS. I THEN TRIED CVO AMOS ON THE PUBLISHED FREQ OF 135.17 AND FOUND NOTHING. I WENT BACK TO 135.075 AND BOTH MY F/O AND MYSELF COULD MAKE OUT THAT BOTH RDM AND CVO AMOS ARE ON THE SAME FREQ. THE RESULT WAS ONLY A LOUD SQUEAL THAT FINALLY WENT AWAY WHEN WE WERE WITHIN 20 NM OF RDM. THERE WE LOST THE CVO AMOS AND COULD CLRLY HEAR RDM AMOS. RDM FSS SUGGESTED THAT WE CONTACT PDX FSDO WHEN WE GOT BACK TO PDX AND INFORM THEM OF THE PROB. HAVING ONLY A SHORT TIME AT PDX I CALLED FSDO, BUT BECAUSE OF MEETINGS IN PROGRESS, THERE WAS NO ONE AVAILABLE TO FIELD MY CONCERNS. MY NEXT STEP WAS TO CONTACT SEA FSDO. MY CALL WAS DIRECTED TO A MR X. I DESCRIBED THE PROB TO HIM AND HE DID NOT UNDERSTAND THE DIFFERENT CLASSES OF NOTAMS AND ALMOST IMMEDIATELY SAID THIS IS A PDX PROB AND YOU WILL HAVE TO CONTACT PDX FSDO. I SUGGESTED THAT HE MIGHT FORWARD THE INFO, BUT HE THEN INFORMED ME THAT THE OFFICES DO NOT TALK TO ONE ANOTHER AND I WOULD NEED TO CONTACT PDX FSDO TO GET ANY ACTION. PERSONALLY, I FEEL REGARDLESS OF WHO'S JURISDICTION SOMETHING IS RPTED IN THESE AGENCIES HAVE THE RESPONSIBILITY TO AT LEAST FORWARD INFO. I DO NOT BELIEVE IT IS MY RESPONSIBILITY TO ACCEPT THE EXPENSE OF LONG DISTANCE CALLS TO RPT DEFICIENCIES ON THE SYS. I'M SURE THIS PROB HAS A SIMPLE SOLUTION.

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.