Narrative:

I was flying into port angeles; wa; on a pleasure flight; AWOS said calm winds; but I noticed smoke blowing with a west wind; so I decided to land to the west. I noticed a skyhawk following the coastline just ahead and below me about 5 mi out; so I announced myself on 123.0; what my current AFD said was the CTAF. I heard nothing back; so I assumed he wasn't listening and continued my approach. He passed the airport and I called a long straight-in; traffic permitting. On my short final; I noticed he was coming in on a long final opposite me. I announced again several times; but no answer. Finally I turned my landing lights on (it was dusk); and he went around. I was near a taxiway and could have easily left the runway if needed. On his go around; he called up and asked if I was listening to 123.0. I replied yes; and he chewed me out since the CTAF had been changed to unicom (122.975) 'in july.' I replied I had a current AFD a couple cycles later than that; and it still said 123.0. I didn't want to argue in the air; so I left the area. The next day I called the airport manager; who said the paperwork was sent in july and the change was notamed. I called FSS; who initially agreed the CTAF was 123.0; but then found a NOTAM that said the change was not active until mid-october. I hadn't originally planned to land at port angeles; so I didn't get a briefing. It was spur of the moment; and although I had current charts and AFD onboard; I still could have called flight service in air for any updates. At the same time; there was a lot of confusion about when the change actually took place. I wonder if some pilots had been announcing on 122.975 all summer long. I suggest that such non-time-critical changes be made at the AFD or chart roll-over time. Frequency changes could also be announced on ASOS/AWOS for a period of time (an AFD cycle?) to let people adjust.

Google
 

Original NASA ASRS Text

Title: C150 PILOT ON FINAL FOR RUNWAY 26 AT CLM HAS CONFLICT WITH ANOTHER AIRCRAFT ON FINAL FOR RUNWAY 08. DISCOVERS CTAF FREQUENCY HAD BEEN CHANGED VIA NOTAM BUT WAS NOT SHOWN IN HER CURRENT AF/D.

Narrative: I WAS FLYING INTO PORT ANGELES; WA; ON A PLEASURE FLT; AWOS SAID CALM WINDS; BUT I NOTICED SMOKE BLOWING WITH A WEST WIND; SO I DECIDED TO LAND TO THE W. I NOTICED A SKYHAWK FOLLOWING THE COASTLINE JUST AHEAD AND BELOW ME ABOUT 5 MI OUT; SO I ANNOUNCED MYSELF ON 123.0; WHAT MY CURRENT AFD SAID WAS THE CTAF. I HEARD NOTHING BACK; SO I ASSUMED HE WASN'T LISTENING AND CONTINUED MY APCH. HE PASSED THE ARPT AND I CALLED A LONG STRAIGHT-IN; TFC PERMITTING. ON MY SHORT FINAL; I NOTICED HE WAS COMING IN ON A LONG FINAL OPPOSITE ME. I ANNOUNCED AGAIN SEVERAL TIMES; BUT NO ANSWER. FINALLY I TURNED MY LNDG LIGHTS ON (IT WAS DUSK); AND HE WENT AROUND. I WAS NEAR A TXWY AND COULD HAVE EASILY LEFT THE RWY IF NEEDED. ON HIS GAR; HE CALLED UP AND ASKED IF I WAS LISTENING TO 123.0. I REPLIED YES; AND HE CHEWED ME OUT SINCE THE CTAF HAD BEEN CHANGED TO UNICOM (122.975) 'IN JULY.' I REPLIED I HAD A CURRENT AFD A COUPLE CYCLES LATER THAN THAT; AND IT STILL SAID 123.0. I DIDN'T WANT TO ARGUE IN THE AIR; SO I LEFT THE AREA. THE NEXT DAY I CALLED THE ARPT MGR; WHO SAID THE PAPERWORK WAS SENT IN JULY AND THE CHANGE WAS NOTAMED. I CALLED FSS; WHO INITIALLY AGREED THE CTAF WAS 123.0; BUT THEN FOUND A NOTAM THAT SAID THE CHANGE WAS NOT ACTIVE UNTIL MID-OCTOBER. I HADN'T ORIGINALLY PLANNED TO LAND AT PORT ANGELES; SO I DIDN'T GET A BRIEFING. IT WAS SPUR OF THE MOMENT; AND ALTHOUGH I HAD CURRENT CHARTS AND AFD ONBOARD; I STILL COULD HAVE CALLED FLT SVC IN AIR FOR ANY UPDATES. AT THE SAME TIME; THERE WAS A LOT OF CONFUSION ABOUT WHEN THE CHANGE ACTUALLY TOOK PLACE. I WONDER IF SOME PLTS HAD BEEN ANNOUNCING ON 122.975 ALL SUMMER LONG. I SUGGEST THAT SUCH NON-TIME-CRITICAL CHANGES BE MADE AT THE AFD OR CHART ROLL-OVER TIME. FREQ CHANGES COULD ALSO BE ANNOUNCED ON ASOS/AWOS FOR A PERIOD OF TIME (AN AFD CYCLE?) TO LET PEOPLE ADJUST.

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