Narrative:

Upon arrival at guc, air carrier X operations did not respond to call. Visual approachs were being conducted to guc. ZDV cleared us for FMS arc to runway 6 per our request. Contacted unicom and received WX for guc and landed uneventfully. Prior to departure, contacted air carrier operations and asked about the WX. They told us that air carrier Y had the only WX person around and they could get us the WX. 15-20 mins later, we received a WX report from air carrier X operations which we believed was with an incorrect altimeter. We corrected this with other WX we received from ZDV. Although VFR conditions existed at the time, unicom is not an authority/authorized source of current WX, which we needed to be legal. I understand from dispatch, who I have talked to since this event and was informed that this is an ongoing problem with guc.

Related reports:

Google
 

Original NASA ASRS Text

Title: AN ACR CREW DEPARTS A SEASONALLY SERVED ARPT WITHOUT WX INFO FROM AN AUTH SOURCE.

Narrative: UPON ARR AT GUC, ACR X OPS DID NOT RESPOND TO CALL. VISUAL APCHS WERE BEING CONDUCTED TO GUC. ZDV CLRED US FOR FMS ARC TO RWY 6 PER OUR REQUEST. CONTACTED UNICOM AND RECEIVED WX FOR GUC AND LANDED UNEVENTFULLY. PRIOR TO DEP, CONTACTED ACR OPS AND ASKED ABOUT THE WX. THEY TOLD US THAT ACR Y HAD THE ONLY WX PERSON AROUND AND THEY COULD GET US THE WX. 15-20 MINS LATER, WE RECEIVED A WX RPT FROM ACR X OPS WHICH WE BELIEVED WAS WITH AN INCORRECT ALTIMETER. WE CORRECTED THIS WITH OTHER WX WE RECEIVED FROM ZDV. ALTHOUGH VFR CONDITIONS EXISTED AT THE TIME, UNICOM IS NOT AN AUTH SOURCE OF CURRENT WX, WHICH WE NEEDED TO BE LEGAL. I UNDERSTAND FROM DISPATCH, WHO I HAVE TALKED TO SINCE THIS EVENT AND WAS INFORMED THAT THIS IS AN ONGOING PROB WITH GUC.

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.