<?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: The Glass is Half Full</title>
	<atom:link href="http://blog.aopa.org/leadingedge/?feed=rss2&#038;p=1059" rel="self" type="application/rss+xml" />
	<link>http://blog.aopa.org/leadingedge/?p=1059</link>
	<description>A place to discuss safety-of-flight issues, procedures, techniques, and judgment.</description>
	<lastBuildDate>Sat, 25 May 2013 13:42:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Rich Romaine</title>
		<link>http://blog.aopa.org/leadingedge/?p=1059&#038;cpage=1#comment-29576</link>
		<dc:creator>Rich Romaine</dc:creator>
		<pubDate>Tue, 17 Aug 2010 19:54:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.aopa.org/asfblog/?p=1059#comment-29576</guid>
		<description><![CDATA[First, my regards to all of Chris&#039; family and friends.  For a time I was in the hangar next door and he was always a pleasant soul.  

Article is timely for me (I&#039;m just reading today), having just spent a night on a friendly FBO&#039;s couch Sunday night after refusing to continue VFR into IMC.  Though I&#039;m IFR, aircraft was not, so I spent some time working the available weather info to come up with the best wx info beyond the standard &quot;VFR not recommended&quot;.  I believe the pat answer of &quot;VFR not recommended&quot; has stymied progress on getting all the available weather info into the system.  As I built my own picture, I was reminded of a continued oversight in the readily available weather info.  AWOS info to briefers/online is not as fresh as it could be.

When dialing the AWOS tel#&#039;s the data is at most a couple minutes old, online (XM too) some was an hour old (or days old if the briefer/briefee doesn&#039;t notice the zulu date)...even an hour is forever in fog/mist conditions.  Now that LockMart has the contract and probably the capability...shouldn&#039;t we push to improve the latency of AWOS derived info in the system?

My opinion is that in some number of the VFR into IMC mishaps, the failure to have the latest info leads folks into thinking conditions are better than they are (time late info is useless even in XM linked glass cockpits; I&#039;ve seen the cheerful symbols, only to curse the report time when digging deeper).  In researching this further, there look to be several back door approaches online, but our target audience is going to be using the official weather products and may not have that insight.

The info is already collected, the sites are already there, it just needs a technology push to match our other 21st century capabilities.

Thoughts?
Rich Romaine]]></description>
		<content:encoded><![CDATA[<p>First, my regards to all of Chris&#8217; family and friends.  For a time I was in the hangar next door and he was always a pleasant soul.  </p>
<p>Article is timely for me (I&#8217;m just reading today), having just spent a night on a friendly FBO&#8217;s couch Sunday night after refusing to continue VFR into IMC.  Though I&#8217;m IFR, aircraft was not, so I spent some time working the available weather info to come up with the best wx info beyond the standard &#8220;VFR not recommended&#8221;.  I believe the pat answer of &#8220;VFR not recommended&#8221; has stymied progress on getting all the available weather info into the system.  As I built my own picture, I was reminded of a continued oversight in the readily available weather info.  AWOS info to briefers/online is not as fresh as it could be.</p>
<p>When dialing the AWOS tel#&#8217;s the data is at most a couple minutes old, online (XM too) some was an hour old (or days old if the briefer/briefee doesn&#8217;t notice the zulu date)&#8230;even an hour is forever in fog/mist conditions.  Now that LockMart has the contract and probably the capability&#8230;shouldn&#8217;t we push to improve the latency of AWOS derived info in the system?</p>
<p>My opinion is that in some number of the VFR into IMC mishaps, the failure to have the latest info leads folks into thinking conditions are better than they are (time late info is useless even in XM linked glass cockpits; I&#8217;ve seen the cheerful symbols, only to curse the report time when digging deeper).  In researching this further, there look to be several back door approaches online, but our target audience is going to be using the official weather products and may not have that insight.</p>
<p>The info is already collected, the sites are already there, it just needs a technology push to match our other 21st century capabilities.</p>
<p>Thoughts?<br />
Rich Romaine</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve C.</title>
		<link>http://blog.aopa.org/leadingedge/?p=1059&#038;cpage=1#comment-29568</link>
		<dc:creator>Steve C.</dc:creator>
		<pubDate>Thu, 12 Aug 2010 19:30:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.aopa.org/asfblog/?p=1059#comment-29568</guid>
		<description><![CDATA[&quot;Travel in Alaska would be  impossible without aircraft and it can’t all be in Boeing 737s going to 6,000-foot paved runways. Just isn’t possible. &quot;

Thank you.

Now if we could just figure out how to make the MSM, whose understanding of aviation stops at the terminal concourse window, understand this.

Not that we haven&#039;t expressed this lament before...]]></description>
		<content:encoded><![CDATA[<p>&#8220;Travel in Alaska would be  impossible without aircraft and it can’t all be in Boeing 737s going to 6,000-foot paved runways. Just isn’t possible. &#8221;</p>
<p>Thank you.</p>
<p>Now if we could just figure out how to make the MSM, whose understanding of aviation stops at the terminal concourse window, understand this.</p>
<p>Not that we haven&#8217;t expressed this lament before&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
