Narrative:

Encountered WX, landed. Waited 2 hours. WX was up and down at destination upon many calls to AWOS. WX at departure point was 1900 ft and 5 mi visibility upon final departure for ewn. Flight visibility and ceiling were good VFR along entire route to ewn. Began calling ewn WX observer at 15 mi out -- no reply. Landed uneventfully -- no conflicts. Saw beacon on while taxiing in. WX observer outside sitting on bench. Called AWOS and it was reporting IFR conditions. Although flight visibility was VFR, I should have checked the AWOS airborne. Thought monitoring unicom was more important, to avoid traffic conflicts. Would suggest more frequent observations by the WX observer to update actual conditions. Also would suggest constant monitoring of unicom by WX observer.

Google
 

Original NASA ASRS Text

Title: PLT FINDS FLT VISIBILITY OK FOR VFR FLT. ARRIVES AT DEST TO FIND BEACON ON INDICATING IFR CONDITIONS.

Narrative: ENCOUNTERED WX, LANDED. WAITED 2 HRS. WX WAS UP AND DOWN AT DEST UPON MANY CALLS TO AWOS. WX AT DEP POINT WAS 1900 FT AND 5 MI VISIBILITY UPON FINAL DEP FOR EWN. FLT VISIBILITY AND CEILING WERE GOOD VFR ALONG ENTIRE RTE TO EWN. BEGAN CALLING EWN WX OBSERVER AT 15 MI OUT -- NO REPLY. LANDED UNEVENTFULLY -- NO CONFLICTS. SAW BEACON ON WHILE TAXIING IN. WX OBSERVER OUTSIDE SITTING ON BENCH. CALLED AWOS AND IT WAS RPTING IFR CONDITIONS. ALTHOUGH FLT VISIBILITY WAS VFR, I SHOULD HAVE CHKED THE AWOS AIRBORNE. THOUGHT MONITORING UNICOM WAS MORE IMPORTANT, TO AVOID TFC CONFLICTS. WOULD SUGGEST MORE FREQUENT OBSERVATIONS BY THE WX OBSERVER TO UPDATE ACTUAL CONDITIONS. ALSO WOULD SUGGEST CONSTANT MONITORING OF UNICOM BY WX OBSERVER.

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.