VFR in IMC. - NASA ASRS

Attributes
ACN	125625
Time
Date	198910
Day	Sun
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : ptk
State Reference	MI
Altitude	msl bound lower : 2500 msl bound upper : 3000
Environment
Flight Conditions	Marginal
Light	Dusk
Aircraft 1
Controlling Facilities	artcc : zob tracon : fnt
Operator	general aviation : personal
Make Model Name	Small Aircraft, High Wing, 1 Eng, Fixed Gear
Flight Phase	cruise other cruise other
Flight Plan	None
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : private pilot : instrument
Experience	flight time last 90 days : 15 flight time total : 625 flight time type : 371
ASRS Report	125625
Person 2
Affiliation	Other
Function	observation : passenger
Events
Anomaly	inflight encounter : weather inflight encounter : vfr in imc non adherence : far
Independent Detector	other flight crewa
Resolutory Action	flight crew : exited adverse environment other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

1) I was told by ptk controllers conditions were MVFR at the field 2500 broken visibility 5. 2) it was not possible to get an IFR clearance due to ZOB handling dtw. 3) I attempted to go to ptk VFR and went into clouds. 4) I then contacted flint approach (fnt) and picked up an IFR clearance to flint where a normal approach and landing were made. 5) conditions at flint were 4000 to 4500 overcast with VFR visibilities. Passing over fnt toward pontiac I realized fnt was a good 'out' in case it was not possible to get to ptk. Having been advised of the VFR, I should say, MVFR conditions at pontiac, I thought I could safely attempt going to pontiac. I seriously considered stopping at fnt during the first pass but my wife persuaded me to try for ptk. My largest error in judgement was to think I could recognize that I would go IFR and then not do so. I looked down at my charts and back up and saw I was in the clouds. I immediately started a turn to the northwest and a climb to 3000'. I also immediately contacted fnt approach for a clearance. 6) one other factor is that the conditions were not forecasted. It was supposed to be good all day. I was aware conditions were getting worse, however, they were still to be VFR.

Original NASA ASRS Text

Title: VFR IN IMC.

Narrative: 1) I WAS TOLD BY PTK CTLRS CONDITIONS WERE MVFR AT THE FIELD 2500 BKN VISIBILITY 5. 2) IT WAS NOT POSSIBLE TO GET AN IFR CLRNC DUE TO ZOB HANDLING DTW. 3) I ATTEMPTED TO GO TO PTK VFR AND WENT INTO CLOUDS. 4) I THEN CONTACTED FLINT APCH (FNT) AND PICKED UP AN IFR CLRNC TO FLINT WHERE A NORMAL APCH AND LNDG WERE MADE. 5) CONDITIONS AT FLINT WERE 4000 TO 4500 OVCST WITH VFR VISIBILITIES. PASSING OVER FNT TOWARD PONTIAC I REALIZED FNT WAS A GOOD 'OUT' IN CASE IT WAS NOT POSSIBLE TO GET TO PTK. HAVING BEEN ADVISED OF THE VFR, I SHOULD SAY, MVFR CONDITIONS AT PONTIAC, I THOUGHT I COULD SAFELY ATTEMPT GOING TO PONTIAC. I SERIOUSLY CONSIDERED STOPPING AT FNT DURING THE FIRST PASS BUT MY WIFE PERSUADED ME TO TRY FOR PTK. MY LARGEST ERROR IN JUDGEMENT WAS TO THINK I COULD RECOGNIZE THAT I WOULD GO IFR AND THEN NOT DO SO. I LOOKED DOWN AT MY CHARTS AND BACK UP AND SAW I WAS IN THE CLOUDS. I IMMEDIATELY STARTED A TURN TO THE NW AND A CLIMB TO 3000'. I ALSO IMMEDIATELY CONTACTED FNT APCH FOR A CLRNC. 6) ONE OTHER FACTOR IS THAT THE CONDITIONS WERE NOT FORECASTED. IT WAS SUPPOSED TO BE GOOD ALL DAY. I WAS AWARE CONDITIONS WERE GETTING WORSE, HOWEVER, THEY WERE STILL TO BE VFR.

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