<?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: When an ATC change isn&#8217;t really a change at all</title>
	<atom:link href="http://blog.aopa.org/blog/?feed=rss2&#038;p=813" rel="self" type="application/rss+xml" />
	<link>http://blog.aopa.org/blog/?p=813</link>
	<description>Online perspective from the editors of "AOPA Pilot".</description>
	<lastBuildDate>Wed, 22 May 2013 00:22:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: satrap</title>
		<link>http://blog.aopa.org/blog/?p=813&#038;cpage=1#comment-76776</link>
		<dc:creator>satrap</dc:creator>
		<pubDate>Fri, 13 Nov 2009 01:40:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.aopa.org/blog/?p=813#comment-76776</guid>
		<description><![CDATA[great post. i just cant get my head around the idea of not taking this oppertunities to get what you want online.]]></description>
		<content:encoded><![CDATA[<p>great post. i just cant get my head around the idea of not taking this oppertunities to get what you want online.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joel Blue</title>
		<link>http://blog.aopa.org/blog/?p=813&#038;cpage=1#comment-51656</link>
		<dc:creator>Joel Blue</dc:creator>
		<pubDate>Tue, 05 May 2009 01:39:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.aopa.org/blog/?p=813#comment-51656</guid>
		<description><![CDATA[GPT  33-56-33N/118-24-25W LAX]]></description>
		<content:encoded><![CDATA[<p>GPT  33-56-33N/118-24-25W LAX</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joel Blue</title>
		<link>http://blog.aopa.org/blog/?p=813&#038;cpage=1#comment-51655</link>
		<dc:creator>Joel Blue</dc:creator>
		<pubDate>Tue, 05 May 2009 01:35:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.aopa.org/blog/?p=813#comment-51655</guid>
		<description><![CDATA[The biggest problem is the &quot;old&quot; center computers, each center computer only knows all the fixes in it&#039;s own airspace, and some of the bigger fixes in all the other airspace. If you file fixes (i.e. GPT..LAX)  the computer computes a fix close to the center boundaries and adds them to the flight plan information then you get a FRC, because the computer needs a fix to figure the next sector to get the flight progress strip sent to. But if you file departure airport fix direct to a Lat/Long (i.e. GPT..Lat/Long..LAX &amp; add remarks Lat/Long is LAX) the computer somehow knows how to send the flight progress strips to the right sectors, &amp; never adds an unnecessary fix (at least I&#039;ve never seen an added fix, but I&#039;ve only been a controller since 1977).]]></description>
		<content:encoded><![CDATA[<p>The biggest problem is the &#8220;old&#8221; center computers, each center computer only knows all the fixes in it&#8217;s own airspace, and some of the bigger fixes in all the other airspace. If you file fixes (i.e. GPT..LAX)  the computer computes a fix close to the center boundaries and adds them to the flight plan information then you get a FRC, because the computer needs a fix to figure the next sector to get the flight progress strip sent to. But if you file departure airport fix direct to a Lat/Long (i.e. GPT..Lat/Long..LAX &amp; add remarks Lat/Long is LAX) the computer somehow knows how to send the flight progress strips to the right sectors, &amp; never adds an unnecessary fix (at least I&#8217;ve never seen an added fix, but I&#8217;ve only been a controller since 1977).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Goforth</title>
		<link>http://blog.aopa.org/blog/?p=813&#038;cpage=1#comment-51430</link>
		<dc:creator>Paul Goforth</dc:creator>
		<pubDate>Sun, 03 May 2009 14:09:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.aopa.org/blog/?p=813#comment-51430</guid>
		<description><![CDATA[&quot;Pilots and controllers&quot; are much like &quot;Labor and Management&quot; they have been gravelling for years and somehow just tolerate each other!.]]></description>
		<content:encoded><![CDATA[<p>&#8220;Pilots and controllers&#8221; are much like &#8220;Labor and Management&#8221; they have been gravelling for years and somehow just tolerate each other!.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jean Paul</title>
		<link>http://blog.aopa.org/blog/?p=813&#038;cpage=1#comment-51289</link>
		<dc:creator>Jean Paul</dc:creator>
		<pubDate>Sat, 02 May 2009 17:28:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.aopa.org/blog/?p=813#comment-51289</guid>
		<description><![CDATA[After reading the comments from Joe Shugart and Brian Veazy I now understand where the problem lies.]]></description>
		<content:encoded><![CDATA[<p>After reading the comments from Joe Shugart and Brian Veazy I now understand where the problem lies.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Shugart</title>
		<link>http://blog.aopa.org/blog/?p=813&#038;cpage=1#comment-51162</link>
		<dc:creator>Joe Shugart</dc:creator>
		<pubDate>Sat, 02 May 2009 05:15:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.aopa.org/blog/?p=813#comment-51162</guid>
		<description><![CDATA[Correction on the airway dimensions: the protected airspace extends beyond 4nm when 51nm from the navaid on a 45 degree angle until, at 130nm, it reaches its maximum distance of 10nm from the centerline.]]></description>
		<content:encoded><![CDATA[<p>Correction on the airway dimensions: the protected airspace extends beyond 4nm when 51nm from the navaid on a 45 degree angle until, at 130nm, it reaches its maximum distance of 10nm from the centerline.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Shugart</title>
		<link>http://blog.aopa.org/blog/?p=813&#038;cpage=1#comment-51161</link>
		<dc:creator>Joe Shugart</dc:creator>
		<pubDate>Sat, 02 May 2009 05:02:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.aopa.org/blog/?p=813#comment-51161</guid>
		<description><![CDATA[Yes, David, from an ATC separation perspective, a direct clearance from X VOR to Y intersection is not the same as one from X VOR V123 to Y intersection.  The reason is that a direct clearance has no defined dimension upon which to base separation from terrain or other aircraft.  In contrast, airways, as you mentioned, are defined as plus and minus four miles (up to 10 at 51nm from the navaid).  It helps to remember that the clearance issued prior to departure is primarily a non-radar routing.  Even when using radar separation, controllers must know the heading of the &quot;direct&quot; aircraft in order to assign a sufficiently divergent heading to another IFR aircraft before discontinuing vertical separation.]]></description>
		<content:encoded><![CDATA[<p>Yes, David, from an ATC separation perspective, a direct clearance from X VOR to Y intersection is not the same as one from X VOR V123 to Y intersection.  The reason is that a direct clearance has no defined dimension upon which to base separation from terrain or other aircraft.  In contrast, airways, as you mentioned, are defined as plus and minus four miles (up to 10 at 51nm from the navaid).  It helps to remember that the clearance issued prior to departure is primarily a non-radar routing.  Even when using radar separation, controllers must know the heading of the &#8220;direct&#8221; aircraft in order to assign a sufficiently divergent heading to another IFR aircraft before discontinuing vertical separation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Heileman</title>
		<link>http://blog.aopa.org/blog/?p=813&#038;cpage=1#comment-51115</link>
		<dc:creator>David Heileman</dc:creator>
		<pubDate>Fri, 01 May 2009 21:18:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.aopa.org/blog/?p=813#comment-51115</guid>
		<description><![CDATA[Brian Veazey, it helps me to know that you are a controller; I am a pilot.  Since VOR equipment on aircraft is only required to be accurate +/- 6 degrees, and since a VOR can be misaligned (relative to true north) by as much as 2 degrees before the FAA will re-align it, the whole system is inherently &quot;fuzzy&quot;, and is designed to be safe despite the fact that it is fuzzy.  The AIM (section 5-3-5) addresses the reality that airplanes do not turn instantaneously, and also talks about the 4nm of &quot;latitude&quot; on each side of an airway/route centerline.  I still don&#039;t understand how, when one is talking only about VOR navigation, a clearance of &quot;X direct Y&quot; (where Y is an intersection on the 123 radial of X) is any different than a clearance to go &quot;X X123R Y&quot;.   If these clearances really have different meanings, I would love to understand exactly how they are different, because I was taught to treat them exactly the same. 

To Joe Shugart&#039;s comment, are you really saying that a direct clearance from X VOR to Y intersection (where Y is defined by a radial of X) does not provide traffic separation or terrain clearance!?!?  I hope you are incorrect!  It certainly contradicts my understanding...

I gave up filing a specific route shortly after getting my instrument rating because it seemed that my filed route was always ignored by the system anyway.  For the two routes I fly most frequently, the system always gives me the same clearance no matter what I file, and I don&#039;t think I&#039;ve actually flown the entire clearance even once -- I always get amended clearances in the air -- although usually the amendments are vectors, or allow me to shortcut (i.e., direct to MXE VOR when the original clearance was EMI V419 MXE).

I do have a couple of pet peeves with ATC clearances (please don&#039;t take this personally).

#1 peeve is getting clearance direct to an intersection when I am not RNAV-capable and I am not on one of the radials defining the intersection.  This happens to me all the time. Hello!  Isn&#039;t this why I specified slant alpha when I filed the flight plan?

#2 peeve is getting clearance to an intersection or waypoint that is not depicted on the low altitude chart.  This has only happened to me once.  I had already accepted the clearance before discovering that I had no way to fly it.  Fortunately my radios did not pick that moment to fail, so I was able to request an amended clearance.  But shouldn&#039;t a pilot be able to assume that any fix given in a clearance will be charted?]]></description>
		<content:encoded><![CDATA[<p>Brian Veazey, it helps me to know that you are a controller; I am a pilot.  Since VOR equipment on aircraft is only required to be accurate +/- 6 degrees, and since a VOR can be misaligned (relative to true north) by as much as 2 degrees before the FAA will re-align it, the whole system is inherently &#8220;fuzzy&#8221;, and is designed to be safe despite the fact that it is fuzzy.  The AIM (section 5-3-5) addresses the reality that airplanes do not turn instantaneously, and also talks about the 4nm of &#8220;latitude&#8221; on each side of an airway/route centerline.  I still don&#8217;t understand how, when one is talking only about VOR navigation, a clearance of &#8220;X direct Y&#8221; (where Y is an intersection on the 123 radial of X) is any different than a clearance to go &#8220;X X123R Y&#8221;.   If these clearances really have different meanings, I would love to understand exactly how they are different, because I was taught to treat them exactly the same. </p>
<p>To Joe Shugart&#8217;s comment, are you really saying that a direct clearance from X VOR to Y intersection (where Y is defined by a radial of X) does not provide traffic separation or terrain clearance!?!?  I hope you are incorrect!  It certainly contradicts my understanding&#8230;</p>
<p>I gave up filing a specific route shortly after getting my instrument rating because it seemed that my filed route was always ignored by the system anyway.  For the two routes I fly most frequently, the system always gives me the same clearance no matter what I file, and I don&#8217;t think I&#8217;ve actually flown the entire clearance even once &#8212; I always get amended clearances in the air &#8212; although usually the amendments are vectors, or allow me to shortcut (i.e., direct to MXE VOR when the original clearance was EMI V419 MXE).</p>
<p>I do have a couple of pet peeves with ATC clearances (please don&#8217;t take this personally).</p>
<p>#1 peeve is getting clearance direct to an intersection when I am not RNAV-capable and I am not on one of the radials defining the intersection.  This happens to me all the time. Hello!  Isn&#8217;t this why I specified slant alpha when I filed the flight plan?</p>
<p>#2 peeve is getting clearance to an intersection or waypoint that is not depicted on the low altitude chart.  This has only happened to me once.  I had already accepted the clearance before discovering that I had no way to fly it.  Fortunately my radios did not pick that moment to fail, so I was able to request an amended clearance.  But shouldn&#8217;t a pilot be able to assume that any fix given in a clearance will be charted?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elliott Schiffman</title>
		<link>http://blog.aopa.org/blog/?p=813&#038;cpage=1#comment-51098</link>
		<dc:creator>Elliott Schiffman</dc:creator>
		<pubDate>Fri, 01 May 2009 19:08:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.aopa.org/blog/?p=813#comment-51098</guid>
		<description><![CDATA[Stop making excuses about .01% when it is computer programming.  I often file through the NY airspace over JFK where V1, V16 and V229 overlap.  It is common, regardless of how I file, to get &quot;Standby for route change, advise when ready to copy&quot; and the change will be simply changing one of the above for another when all three are collocated.]]></description>
		<content:encoded><![CDATA[<p>Stop making excuses about .01% when it is computer programming.  I often file through the NY airspace over JFK where V1, V16 and V229 overlap.  It is common, regardless of how I file, to get &#8220;Standby for route change, advise when ready to copy&#8221; and the change will be simply changing one of the above for another when all three are collocated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Veazey</title>
		<link>http://blog.aopa.org/blog/?p=813&#038;cpage=1#comment-51095</link>
		<dc:creator>Brian Veazey</dc:creator>
		<pubDate>Fri, 01 May 2009 18:53:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.aopa.org/blog/?p=813#comment-51095</guid>
		<description><![CDATA[David Heileman--

I&#039;ve been a big-city controller for 27 years now and have had more than one unpleasant experience with this issue.  A airplane two miles south of where he&#039;s expected to be can be a problem.  

A couple of points:

1.  I should have said it&#039;s been better with FMS, not necessarily GPS.
2.  Where in the heck did you get the four miles of latitude you cite above?  You&#039;re 
 expected to be on the route centerline.
3.  You sort of answered the question for yourself:  &quot;...no decent pilot would ever home to  a fix.&quot;  Whoever wrote the original ASRS complaint above sure as heck isn&#039;t a decent pilot.  He gets a clearance and then complains about having to get a chart out to check it.  Give me a break.  A decent pilot checks the SID, route, and STAR against the FMS (or whatever)every trip.  That FAR is 91.103.
4.  Mr. Darby above is quite correct.  NAS computers do spit out loads of superfluous PDRs, etc., and ATC is remiss to issue them in clearances.]]></description>
		<content:encoded><![CDATA[<p>David Heileman&#8211;</p>
<p>I&#8217;ve been a big-city controller for 27 years now and have had more than one unpleasant experience with this issue.  A airplane two miles south of where he&#8217;s expected to be can be a problem.  </p>
<p>A couple of points:</p>
<p>1.  I should have said it&#8217;s been better with FMS, not necessarily GPS.<br />
2.  Where in the heck did you get the four miles of latitude you cite above?  You&#8217;re<br />
 expected to be on the route centerline.<br />
3.  You sort of answered the question for yourself:  &#8220;&#8230;no decent pilot would ever home to  a fix.&#8221;  Whoever wrote the original ASRS complaint above sure as heck isn&#8217;t a decent pilot.  He gets a clearance and then complains about having to get a chart out to check it.  Give me a break.  A decent pilot checks the SID, route, and STAR against the FMS (or whatever)every trip.  That FAR is 91.103.<br />
4.  Mr. Darby above is quite correct.  NAS computers do spit out loads of superfluous PDRs, etc., and ATC is remiss to issue them in clearances.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
