Narrative:

I obtained from the sdp AWOS the current WX conditions, and at about xa:58Z I reported on CTAF (frequency 122.3) that I was 12 mi to the south of sdp inbound for runway 13. Cold bay FSS then announced on the frequency that there was inbound traffic, but his position was unknown at that time. He stated the pilot had extended his flight plan by an extra 10 mins. I then informed FSS I was planning a right downwind for runway 13, then asked the other part 135 operator if he was up on the frequency 122.3. There was no reply. On communication #2, I brought up the sdp AWOS again and determined that at that time, with the direction of the wind, that runway 31 would be less of a crosswind. I made a radio call informing sdp traffic I was 8 1/2 mi out, but was now planning a straight in approach to runway 31. About 30 seconds later, I clicked the microphone 7 times for the pilot controled runway lights and REIL's to be turned on. 1 min later (XA57:04Z) I then made a call to sdp traffic of a 5 mi straight in final for runway 31. A few seconds later (XA57:20Z) the other flight contacted cdb FSS on 122.3 and informed him that he had 'arrived at sand point' and wanted his VFR flight plan closed. FSS then said 'copy on the ground' and flight plan closed. The pilot never corrected FSS, he just gave a PIREP of the WX conditions. About 1 1/2 mins later (XA59:00Z), while on short final to runway 31, I saw another aircraft coming from my left turning a left final for runway 31. At this time the king air was about 100-200 ft below and 300-500 ft in front of me. I called out to the pilot and made a statement about not making any radio call, with no reply from the pilot. Full power was applied and a climbing left turn was made. I informed FSS I was going around (XA59:06Z) and asked if I had heard the other flight say he was on the ground. FSS stated (XA59:18Z) 'affirmative I copied him on the ground and canceled about 2 mins ago.' after landing (XB02:44Z), I walked over to where the king air was parked and talked to the pilot. He said he was making all the proper radio callouts and he even talked to cdb FSS. Then I asked which frequency he was making his calls. He stated he was on the CTAF 122.8, however, he did talk to FSS on 122.3. When I informed him that 122.8 was no longer the correct CTAF, he stated that all the approach plates and charts he had stated the frequency was 122.8. After getting back into the company's aircraft, I checked my current approach plates, all having the frequency of 122.3 for unicom/CTAF and pilot controled lighting. However, the cold bay sectional aeronautical chart (36TH edition feb/03 and becoming obsolete for us in navigation feb/xa/04) does have the CTAF as 122.8. No reported injuries.

Google
 

Original NASA ASRS Text

Title: ON NIGHTTIME ARR TO SDP, PLT OF PA31 HAD NMAC WITH BE10. EACH ACFT MAKING TA'S ON DIFFERENT CTAF FREQS.

Narrative: I OBTAINED FROM THE SDP AWOS THE CURRENT WX CONDITIONS, AND AT ABOUT XA:58Z I RPTED ON CTAF (FREQ 122.3) THAT I WAS 12 MI TO THE S OF SDP INBOUND FOR RWY 13. COLD BAY FSS THEN ANNOUNCED ON THE FREQ THAT THERE WAS INBOUND TFC, BUT HIS POS WAS UNKNOWN AT THAT TIME. HE STATED THE PLT HAD EXTENDED HIS FLT PLAN BY AN EXTRA 10 MINS. I THEN INFORMED FSS I WAS PLANNING A R DOWNWIND FOR RWY 13, THEN ASKED THE OTHER PART 135 OPERATOR IF HE WAS UP ON THE FREQ 122.3. THERE WAS NO REPLY. ON COM #2, I BROUGHT UP THE SDP AWOS AGAIN AND DETERMINED THAT AT THAT TIME, WITH THE DIRECTION OF THE WIND, THAT RWY 31 WOULD BE LESS OF A XWIND. I MADE A RADIO CALL INFORMING SDP TFC I WAS 8 1/2 MI OUT, BUT WAS NOW PLANNING A STRAIGHT IN APCH TO RWY 31. ABOUT 30 SECONDS LATER, I CLICKED THE MIKE 7 TIMES FOR THE PLT CTLED RWY LIGHTS AND REIL'S TO BE TURNED ON. 1 MIN LATER (XA57:04Z) I THEN MADE A CALL TO SDP TFC OF A 5 MI STRAIGHT IN FINAL FOR RWY 31. A FEW SECONDS LATER (XA57:20Z) THE OTHER FLT CONTACTED CDB FSS ON 122.3 AND INFORMED HIM THAT HE HAD 'ARRIVED AT SAND POINT' AND WANTED HIS VFR FLT PLAN CLOSED. FSS THEN SAID 'COPY ON THE GND' AND FLT PLAN CLOSED. THE PLT NEVER CORRECTED FSS, HE JUST GAVE A PIREP OF THE WX CONDITIONS. ABOUT 1 1/2 MINS LATER (XA59:00Z), WHILE ON SHORT FINAL TO RWY 31, I SAW ANOTHER ACFT COMING FROM MY L TURNING A L FINAL FOR RWY 31. AT THIS TIME THE KING AIR WAS ABOUT 100-200 FT BELOW AND 300-500 FT IN FRONT OF ME. I CALLED OUT TO THE PLT AND MADE A STATEMENT ABOUT NOT MAKING ANY RADIO CALL, WITH NO REPLY FROM THE PLT. FULL PWR WAS APPLIED AND A CLBING L TURN WAS MADE. I INFORMED FSS I WAS GOING AROUND (XA59:06Z) AND ASKED IF I HAD HEARD THE OTHER FLT SAY HE WAS ON THE GND. FSS STATED (XA59:18Z) 'AFFIRMATIVE I COPIED HIM ON THE GND AND CANCELED ABOUT 2 MINS AGO.' AFTER LNDG (XB02:44Z), I WALKED OVER TO WHERE THE KING AIR WAS PARKED AND TALKED TO THE PLT. HE SAID HE WAS MAKING ALL THE PROPER RADIO CALLOUTS AND HE EVEN TALKED TO CDB FSS. THEN I ASKED WHICH FREQ HE WAS MAKING HIS CALLS. HE STATED HE WAS ON THE CTAF 122.8, HOWEVER, HE DID TALK TO FSS ON 122.3. WHEN I INFORMED HIM THAT 122.8 WAS NO LONGER THE CORRECT CTAF, HE STATED THAT ALL THE APCH PLATES AND CHARTS HE HAD STATED THE FREQ WAS 122.8. AFTER GETTING BACK INTO THE COMPANY'S ACFT, I CHKED MY CURRENT APCH PLATES, ALL HAVING THE FREQ OF 122.3 FOR UNICOM/CTAF AND PLT CTLED LIGHTING. HOWEVER, THE COLD BAY SECTIONAL AERO CHART (36TH EDITION FEB/03 AND BECOMING OBSOLETE FOR US IN NAV FEB/XA/04) DOES HAVE THE CTAF AS 122.8. NO RPTED INJURIES.

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.