Narrative:

Problem arose when returning from wkend trip. I hold an instrument rating but am not current and did not have current IFR charts on board. I do fly computer simulators frequently and did have out of date charts on board. Publication approach indicated light rain with occasional moderate showers between publication and cos. I initially decided to divert to publication to wait for showers to diminish but then a large break in the clouds that extended for several mi (15-20) to the north passed by the right side of the aircraft. I decided to see if we could follow that break north to cos that was reporting 2700 ft scattered and 9 mi visibility. Publication was 5 mi visibility at the time. After being handed off to cos approach, I was told to expect a straight-in to runway 35L. Wanting to get positioned for that approach. I turned more wnw into precipitation. For 5-8 mins, precipitation was light but spattering on windscreen so as to make forward visibility reduced (side visibility was 4-5 mi). Having an inoperative DME I called cos approach to get a vector to airport. I was told to maintain VFR. Since I had been doing cloud avoidance I wanted the vector to determine how much longer I had to go. I looked down to check my altitude and when I looked up I had entered a cloud. I started to make a call to approach to request an approach and then broke clear (IMC for 5-10 seconds). My landing was uneventful from there onward. Looking back, I continue to debate the choice of requesting an IFR approach with old charts or continuing to run scud. I also should not have tried to set up the straight-in approach by abandoning clearly better conditions.

Related reports:

Google
 

Original NASA ASRS Text

Title: CESSNA PLT INADVERTENTLY ENTERS CLOUDS WHEN ASKED TO REMAIN VFR PRIOR TO RECEIVING CLRNC INTO CLASS C AIRSPACE.

Narrative: PROB AROSE WHEN RETURNING FROM WKEND TRIP. I HOLD AN INST RATING BUT AM NOT CURRENT AND DID NOT HAVE CURRENT IFR CHARTS ON BOARD. I DO FLY COMPUTER SIMULATORS FREQUENTLY AND DID HAVE OUT OF DATE CHARTS ON BOARD. PUB APCH INDICATED LIGHT RAIN WITH OCCASIONAL MODERATE SHOWERS BTWN PUB AND COS. I INITIALLY DECIDED TO DIVERT TO PUB TO WAIT FOR SHOWERS TO DIMINISH BUT THEN A LARGE BREAK IN THE CLOUDS THAT EXTENDED FOR SEVERAL MI (15-20) TO THE N PASSED BY THE R SIDE OF THE ACFT. I DECIDED TO SEE IF WE COULD FOLLOW THAT BREAK N TO COS THAT WAS RPTING 2700 FT SCATTERED AND 9 MI VISIBILITY. PUB WAS 5 MI VISIBILITY AT THE TIME. AFTER BEING HANDED OFF TO COS APCH, I WAS TOLD TO EXPECT A STRAIGHT-IN TO RWY 35L. WANTING TO GET POSITIONED FOR THAT APCH. I TURNED MORE WNW INTO PRECIP. FOR 5-8 MINS, PRECIP WAS LIGHT BUT SPATTERING ON WINDSCREEN SO AS TO MAKE FORWARD VISIBILITY REDUCED (SIDE VISIBILITY WAS 4-5 MI). HAVING AN INOP DME I CALLED COS APCH TO GET A VECTOR TO ARPT. I WAS TOLD TO MAINTAIN VFR. SINCE I HAD BEEN DOING CLOUD AVOIDANCE I WANTED THE VECTOR TO DETERMINE HOW MUCH LONGER I HAD TO GO. I LOOKED DOWN TO CHK MY ALT AND WHEN I LOOKED UP I HAD ENTERED A CLOUD. I STARTED TO MAKE A CALL TO APCH TO REQUEST AN APCH AND THEN BROKE CLR (IMC FOR 5-10 SECONDS). MY LNDG WAS UNEVENTFUL FROM THERE ONWARD. LOOKING BACK, I CONTINUE TO DEBATE THE CHOICE OF REQUESTING AN IFR APCH WITH OLD CHARTS OR CONTINUING TO RUN SCUD. I ALSO SHOULD NOT HAVE TRIED TO SET UP THE STRAIGHT-IN APCH BY ABANDONING CLRLY BETTER CONDITIONS.

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.