<?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: Gotcha! &#8211; Hold for release</title>
	<atom:link href="http://www.pilotbug.com/archives/1585/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pilotbug.com/archives/1585</link>
	<description>Aviation information and introspection</description>
	<lastBuildDate>Sun, 31 Oct 2010 22:34:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Av8rrr</title>
		<link>http://www.pilotbug.com/archives/1585/comment-page-1#comment-305</link>
		<dc:creator>Av8rrr</dc:creator>
		<pubDate>Tue, 10 Nov 2009 03:23:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.pilotbug.com/?p=1585#comment-305</guid>
		<description>If you still have an active IFR flight plan, but a &quot;hold for release&quot; has not been issued, then you can still depart VFR and pick up an IFR flight plan in the air.  I don&#039;t think that the AIM has been contradicted by the post.  The statement was &quot;depart without first canceling either your IFR flight plan or clearance&quot;.  I think you are being held up by the canceling the clearance part.  You still have an IFR flight plan, but the clearance to hold airspace has been rescinded.  Departing VFR is still allowed</description>
		<content:encoded><![CDATA[<p>If you still have an active IFR flight plan, but a &#8220;hold for release&#8221; has not been issued, then you can still depart VFR and pick up an IFR flight plan in the air.  I don&#8217;t think that the AIM has been contradicted by the post.  The statement was &#8220;depart without first canceling either your IFR flight plan or clearance&#8221;.  I think you are being held up by the canceling the clearance part.  You still have an IFR flight plan, but the clearance to hold airspace has been rescinded.  Departing VFR is still allowed</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron Levy</title>
		<link>http://www.pilotbug.com/archives/1585/comment-page-1#comment-304</link>
		<dc:creator>Ron Levy</dc:creator>
		<pubDate>Tue, 10 Nov 2009 02:48:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.pilotbug.com/?p=1585#comment-304</guid>
		<description>The AIM section which you referenced directly contradicts your statement that after receiving a &quot;hold for release&quot; instruction, &quot;you are not authorized to depart without first canceling either your IFR flight plan or clearance/&quot;  Section 5-2-6 of the AIM says, &quot;The ATC instruction, &#039;hold for release,&#039; applies to the IFR clearance and does not prevent the pilot from departing under VFR.&quot;</description>
		<content:encoded><![CDATA[<p>The AIM section which you referenced directly contradicts your statement that after receiving a &#8220;hold for release&#8221; instruction, &#8220;you are not authorized to depart without first canceling either your IFR flight plan or clearance/&#8221;  Section 5-2-6 of the AIM says, &#8220;The ATC instruction, &#8216;hold for release,&#8217; applies to the IFR clearance and does not prevent the pilot from departing under VFR.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Heath Kel</title>
		<link>http://www.pilotbug.com/archives/1585/comment-page-1#comment-290</link>
		<dc:creator>Heath Kel</dc:creator>
		<pubDate>Wed, 04 Nov 2009 18:07:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.pilotbug.com/?p=1585#comment-290</guid>
		<description>Several crew at my company got violated this way.  Know before you go!</description>
		<content:encoded><![CDATA[<p>Several crew at my company got violated this way.  Know before you go!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
