<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: What Part of &#8220;Cloud&#8221; Don&#8217;t you Understand?</title>
	<atom:link href="http://blog.aopa.org/leadingedge/?feed=rss2&#038;p=914" rel="self" type="application/rss+xml" />
	<link>http://blog.aopa.org/leadingedge/?p=914</link>
	<description>A place to discuss safety-of-flight issues, procedures, techniques, and judgment.</description>
	<lastBuildDate>Tue, 21 May 2013 15:17:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Vin O'Leary</title>
		<link>http://blog.aopa.org/leadingedge/?p=914&#038;cpage=1#comment-29374</link>
		<dc:creator>Vin O'Leary</dc:creator>
		<pubDate>Sat, 22 May 2010 17:48:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.aopa.org/asfblog/?p=914#comment-29374</guid>
		<description><![CDATA[Bruce,

I think you still don&#039;t get it.  Both of the comments above yours describe situations in which FSS said the wx was fine.  They were NOT ignoring a VNR.  

My close call was similar.  Plus I&#039;ve had many, many occasions where I stayed on the ground due to predicted bad wx only to find out later that the wx was fine.  Those occasions did not result in accidents, but they did have negative consequences that I would like to have avoided.

The real learning is that you can&#039;t trust the wx predictions whether they are good or bad.  You make your best guess based on information available and have a Plan B on every flight.

You are guilty of &quot;selection error&quot; in your analysis.  You can&#039;t just look at those VFR-IMC accidents, you have to look at all flights.  Of course, those statistics are not available, so we will let you off without punishment. ]]></description>
		<content:encoded><![CDATA[<p>Bruce,</p>
<p>I think you still don&#8217;t get it.  Both of the comments above yours describe situations in which FSS said the wx was fine.  They were NOT ignoring a VNR.  </p>
<p>My close call was similar.  Plus I&#8217;ve had many, many occasions where I stayed on the ground due to predicted bad wx only to find out later that the wx was fine.  Those occasions did not result in accidents, but they did have negative consequences that I would like to have avoided.</p>
<p>The real learning is that you can&#8217;t trust the wx predictions whether they are good or bad.  You make your best guess based on information available and have a Plan B on every flight.</p>
<p>You are guilty of &#8220;selection error&#8221; in your analysis.  You can&#8217;t just look at those VFR-IMC accidents, you have to look at all flights.  Of course, those statistics are not available, so we will let you off without punishment. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce Landsberg</title>
		<link>http://blog.aopa.org/leadingedge/?p=914&#038;cpage=1#comment-29365</link>
		<dc:creator>Bruce Landsberg</dc:creator>
		<pubDate>Mon, 17 May 2010 20:36:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.aopa.org/asfblog/?p=914#comment-29365</guid>
		<description><![CDATA[Tommy.....

Didn&#039;t mean to come across as arrogant. You made an excellent point which I neglected to mention. What you see out the cockpit window trumps ANY forecast. If you see clouds - there are clouds. 

VFR pilots need to plan and perhaps more importantly, act accordingly. We hear of too many cases where the pilot says to FSS, his passengers or himself that he&#039;s just going to &quot;take a look.&quot; Often, however, the mindset is more mission focused.

Many thanks for your post .]]></description>
		<content:encoded><![CDATA[<p>Tommy&#8230;..</p>
<p>Didn&#8217;t mean to come across as arrogant. You made an excellent point which I neglected to mention. What you see out the cockpit window trumps ANY forecast. If you see clouds &#8211; there are clouds. </p>
<p>VFR pilots need to plan and perhaps more importantly, act accordingly. We hear of too many cases where the pilot says to FSS, his passengers or himself that he&#8217;s just going to &#8220;take a look.&#8221; Often, however, the mindset is more mission focused.</p>
<p>Many thanks for your post .</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William Campbell</title>
		<link>http://blog.aopa.org/leadingedge/?p=914&#038;cpage=1#comment-29362</link>
		<dc:creator>William Campbell</dc:creator>
		<pubDate>Sun, 16 May 2010 15:46:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.aopa.org/asfblog/?p=914#comment-29362</guid>
		<description><![CDATA[I encountered VFR into IMC, despite my best efforts to avoid it.  I was preparing to depart a non towered airport. I called FSS, before the transition but during the run-up to local FSS closures, and got a weather report.  I was assured the ceiling was above 10,000.  I disagreed with the briefer based on my vantage point on the ramp.  I was told again I was wrong.  I requested to file IFR.  I was told that it was not necessary.  I suggest it looked like it to me and was again declined.

I took off and watched the ceiling closely as I climbed to 6500.  It seemed I was rapidly approaching that &quot;10,000 ceiling&quot;, at about 4800 feet I observed a thin line in the overcast.  I knew immediately it was a separation line between two clouds.  The lighting and contrast made it very difficult to discern this until right on it.

My observation, recognition and penetration were almost simultaneous.  I immediately transitioned to an IFR mental process and leveled out the airplane.  I was monitoring the TRACON which had responsibility for this airspace, several calls to them when un-answered. (There are known dead spots in this region)  I was most concerned about &quot;cumulo-alumianous&quot;.  I commenced a 180 degree climbing turn to provide additional ground clearance and hopefully better reception.  CFIT was not a concern but radar/radio visibility was.

After several minutes I returned to clear air.  I descended and reversed course at a much lower altitude.  I continued to my destination VFR.  That FSS is now closed and I have never been talked out of filing IFR since.  This would have been a non-event IFR flight.  I now file most flight plans on line and make the decision without comment from the person in the cozy room sipping coffee.]]></description>
		<content:encoded><![CDATA[<p>I encountered VFR into IMC, despite my best efforts to avoid it.  I was preparing to depart a non towered airport. I called FSS, before the transition but during the run-up to local FSS closures, and got a weather report.  I was assured the ceiling was above 10,000.  I disagreed with the briefer based on my vantage point on the ramp.  I was told again I was wrong.  I requested to file IFR.  I was told that it was not necessary.  I suggest it looked like it to me and was again declined.</p>
<p>I took off and watched the ceiling closely as I climbed to 6500.  It seemed I was rapidly approaching that &#8220;10,000 ceiling&#8221;, at about 4800 feet I observed a thin line in the overcast.  I knew immediately it was a separation line between two clouds.  The lighting and contrast made it very difficult to discern this until right on it.</p>
<p>My observation, recognition and penetration were almost simultaneous.  I immediately transitioned to an IFR mental process and leveled out the airplane.  I was monitoring the TRACON which had responsibility for this airspace, several calls to them when un-answered. (There are known dead spots in this region)  I was most concerned about &#8220;cumulo-alumianous&#8221;.  I commenced a 180 degree climbing turn to provide additional ground clearance and hopefully better reception.  CFIT was not a concern but radar/radio visibility was.</p>
<p>After several minutes I returned to clear air.  I descended and reversed course at a much lower altitude.  I continued to my destination VFR.  That FSS is now closed and I have never been talked out of filing IFR since.  This would have been a non-event IFR flight.  I now file most flight plans on line and make the decision without comment from the person in the cozy room sipping coffee.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tommy Brazie</title>
		<link>http://blog.aopa.org/leadingedge/?p=914&#038;cpage=1#comment-29359</link>
		<dc:creator>Tommy Brazie</dc:creator>
		<pubDate>Fri, 14 May 2010 13:42:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.aopa.org/asfblog/?p=914#comment-29359</guid>
		<description><![CDATA[Bruce,
You have been arrogant.  I have twice been VFR into IMC and was more careful that almost anyone I know.  First time at new pilot. Forecast was solid VFR to Smith Mountain Lake from Andrews AFB in a C-150.  In those days I actually believed the FSS.  I was in constant contact as the wx got worse and was repeatedly assured that there was no weather across the flight path or at my distination.  I made one last call as I could still divert to Farmville or I was comitted.  They said, No problem and noted how inexperienced I was.  I believed them.  Finally I asked that they call by telephone, Roanoke.  They did and they were IMC.  I had to use special VFR.  I used all the information I had including a wx briefiing in person at the wx center on the Air Force base.

Second time was similar.  Night xcountry Scottsbluff to Dayton.  No wx forecast.  FSS said no weather anywhere with in three states.  Hit a cloud 
over the IL Iowa border area. Did immediate 360.  Had to do it three times (lowering altitudes to where FSS said was clear)  on my way to a precautionary landing in Champaign in a rain storm. (By the way the vacuum pump failed right after the first encounter with clouds.)  Each move was made consulting all available information.  STUFF happens.  Be trained to handle it.  My instructor insisted upon hours of unusual attitude training (ex Navy).  I never intenionallly fly into IMC and have landed or turned around dozens of times.  I also learned that what I see out the window in real no matter what things you have been told, or what the charts say should have happened.  I was nieve that one time.  The night flight was bizzare.  Twice into IMC with partial panel at night.  Gets your attention.]]></description>
		<content:encoded><![CDATA[<p>Bruce,<br />
You have been arrogant.  I have twice been VFR into IMC and was more careful that almost anyone I know.  First time at new pilot. Forecast was solid VFR to Smith Mountain Lake from Andrews AFB in a C-150.  In those days I actually believed the FSS.  I was in constant contact as the wx got worse and was repeatedly assured that there was no weather across the flight path or at my distination.  I made one last call as I could still divert to Farmville or I was comitted.  They said, No problem and noted how inexperienced I was.  I believed them.  Finally I asked that they call by telephone, Roanoke.  They did and they were IMC.  I had to use special VFR.  I used all the information I had including a wx briefiing in person at the wx center on the Air Force base.</p>
<p>Second time was similar.  Night xcountry Scottsbluff to Dayton.  No wx forecast.  FSS said no weather anywhere with in three states.  Hit a cloud<br />
over the IL Iowa border area. Did immediate 360.  Had to do it three times (lowering altitudes to where FSS said was clear)  on my way to a precautionary landing in Champaign in a rain storm. (By the way the vacuum pump failed right after the first encounter with clouds.)  Each move was made consulting all available information.  STUFF happens.  Be trained to handle it.  My instructor insisted upon hours of unusual attitude training (ex Navy).  I never intenionallly fly into IMC and have landed or turned around dozens of times.  I also learned that what I see out the window in real no matter what things you have been told, or what the charts say should have happened.  I was nieve that one time.  The night flight was bizzare.  Twice into IMC with partial panel at night.  Gets your attention.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
