<?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: Hudson River Recap</title>
	<atom:link href="http://blog.aopa.org/leadingedge/?feed=rss2&#038;p=1137" rel="self" type="application/rss+xml" />
	<link>http://blog.aopa.org/leadingedge/?p=1137</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: Mike Hayden</title>
		<link>http://blog.aopa.org/leadingedge/?p=1137&#038;cpage=1#comment-29822</link>
		<dc:creator>Mike Hayden</dc:creator>
		<pubDate>Sat, 25 Sep 2010 10:52:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.aopa.org/asfblog/?p=1137#comment-29822</guid>
		<description><![CDATA[The comment I submitted  9/25/10 at 5;46 am was meant for the &quot;Bad Day at Huntington&quot; accident review and not &quot;Hudson River Recap&quot;..]]></description>
		<content:encoded><![CDATA[<p>The comment I submitted  9/25/10 at 5;46 am was meant for the &#8220;Bad Day at Huntington&#8221; accident review and not &#8220;Hudson River Recap&#8221;..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Hayden</title>
		<link>http://blog.aopa.org/leadingedge/?p=1137&#038;cpage=1#comment-29821</link>
		<dc:creator>Mike Hayden</dc:creator>
		<pubDate>Sat, 25 Sep 2010 10:46:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.aopa.org/asfblog/?p=1137#comment-29821</guid>
		<description><![CDATA[Had the pilot used something as simple and easy as Flight Following he would have some warning from ATC of the deteriorating weather on his route. I recall a VFR flight I made from Boston using Flight Following when I was told by ATC of a long line of severe thunderstorms over the Columbus, Ohio area that the controller said I could neither go over nor conveniently go around.  I landed at a nearby airport and spent several hours safely on the ground waiting for it to pass.]]></description>
		<content:encoded><![CDATA[<p>Had the pilot used something as simple and easy as Flight Following he would have some warning from ATC of the deteriorating weather on his route. I recall a VFR flight I made from Boston using Flight Following when I was told by ATC of a long line of severe thunderstorms over the Columbus, Ohio area that the controller said I could neither go over nor conveniently go around.  I landed at a nearby airport and spent several hours safely on the ground waiting for it to pass.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce Landsberg</title>
		<link>http://blog.aopa.org/leadingedge/?p=1137&#038;cpage=1#comment-29799</link>
		<dc:creator>Bruce Landsberg</dc:creator>
		<pubDate>Thu, 23 Sep 2010 17:29:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.aopa.org/asfblog/?p=1137#comment-29799</guid>
		<description><![CDATA[Craig....

Thank you for the reference - we will review it in detail.]]></description>
		<content:encoded><![CDATA[<p>Craig&#8230;.</p>
<p>Thank you for the reference &#8211; we will review it in detail.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: C. Craig Morris</title>
		<link>http://blog.aopa.org/leadingedge/?p=1137&#038;cpage=1#comment-29790</link>
		<dc:creator>C. Craig Morris</dc:creator>
		<pubDate>Mon, 20 Sep 2010 23:41:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.aopa.org/asfblog/?p=1137#comment-29790</guid>
		<description><![CDATA[Bruce, you&#039;re off the mark in this article, and you&#039;re doing a disservice to general aviation, pilots, and their passengers.  See and avoid is the root problem of all midair collisions, not just this one with its interesting, but hardly germane, peculiarities.  For an exact analysis of limitations of the see and avoid concept, see: http://www.ingentaconnect.com/content/asma/asem/2005/00000076/00000004/art00007.]]></description>
		<content:encoded><![CDATA[<p>Bruce, you&#8217;re off the mark in this article, and you&#8217;re doing a disservice to general aviation, pilots, and their passengers.  See and avoid is the root problem of all midair collisions, not just this one with its interesting, but hardly germane, peculiarities.  For an exact analysis of limitations of the see and avoid concept, see: <a href="http://www.ingentaconnect.com/content/asma/asem/2005/00000076/00000004/art00007" rel="nofollow">http://www.ingentaconnect.com/content/asma/asem/2005/00000076/00000004/art00007</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MJSchwartz</title>
		<link>http://blog.aopa.org/leadingedge/?p=1137&#038;cpage=1#comment-29777</link>
		<dc:creator>MJSchwartz</dc:creator>
		<pubDate>Fri, 17 Sep 2010 17:08:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.aopa.org/asfblog/?p=1137#comment-29777</guid>
		<description><![CDATA[I believe the NTSB got it right. Both aircraft were VFR. The foundation for Visual Flight Rules is to see and avoid terrain, other aircraft, etc. Anyone who has been flying for a while, and is honest with themselves, completely understands that there are serious limitations to seeing and avoiding other small aircraft in the daytime. It&#039;s a lot easier at night (with strobes, beacons and position lights). I&#039;ve been flying with a TCAD system for the past 5 years and I am amazed at how many aircraft I miss with my normal visual scan (and that&#039;s in relatively uncongested airspace).]]></description>
		<content:encoded><![CDATA[<p>I believe the NTSB got it right. Both aircraft were VFR. The foundation for Visual Flight Rules is to see and avoid terrain, other aircraft, etc. Anyone who has been flying for a while, and is honest with themselves, completely understands that there are serious limitations to seeing and avoiding other small aircraft in the daytime. It&#8217;s a lot easier at night (with strobes, beacons and position lights). I&#8217;ve been flying with a TCAD system for the past 5 years and I am amazed at how many aircraft I miss with my normal visual scan (and that&#8217;s in relatively uncongested airspace).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Wyker</title>
		<link>http://blog.aopa.org/leadingedge/?p=1137&#038;cpage=1#comment-29775</link>
		<dc:creator>John Wyker</dc:creator>
		<pubDate>Fri, 17 Sep 2010 12:23:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.aopa.org/asfblog/?p=1137#comment-29775</guid>
		<description><![CDATA[They missed the entire point of it.  The controller was talking on his phone while he was supposed to be controlling traffic.  The railroad industry had a wake-up call in this area last year when an engineer was texting instead of paying attention to operating his train.  He ran by a &quot;Stop&quot; signal and had a head-on collision with another train.  Personal phones should be banned in the cockpit and in the control tower, approach or center.]]></description>
		<content:encoded><![CDATA[<p>They missed the entire point of it.  The controller was talking on his phone while he was supposed to be controlling traffic.  The railroad industry had a wake-up call in this area last year when an engineer was texting instead of paying attention to operating his train.  He ran by a &#8220;Stop&#8221; signal and had a head-on collision with another train.  Personal phones should be banned in the cockpit and in the control tower, approach or center.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris P.</title>
		<link>http://blog.aopa.org/leadingedge/?p=1137&#038;cpage=1#comment-29767</link>
		<dc:creator>Chris P.</dc:creator>
		<pubDate>Thu, 16 Sep 2010 06:06:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.aopa.org/asfblog/?p=1137#comment-29767</guid>
		<description><![CDATA[I concur with Bob H. to an extent. I watched the entire Board Meeting via web cast. 

Tom Haueter, an aviation safety expert  and staff member employed by the NTSB for over 26 years, vigorously argued to the Board to place the Teterboro tower controller&#039;s non-pertinent &quot;dead cat&quot; telephone call at the top of the probable cause list. Although he was unsuccessful, it was clear to anyone watching the logic of his case was incontrovertible.

Why the Board placed the limitations of &quot;see and avoid&quot; at the top is anyone&#039;s guess. Chairman Hersman&#039;s Vice Chairman, Christopher Hart, was absent. It seemed as though the Board was frustrated and tired. They had difficultly getting the exact language of the probable cause adopted. The FAA has termination proceedings against the controller in question and his supervisor.

As Mr. Haueter argued, the limitations of &quot;see and avoid&quot; has been known since the deadly mid air over the Grand Canyon in 1956. That accident was the catalyst for sweeping changes in regulating air traffic.

Only time will tell if the lessons of this tragedy are learned.]]></description>
		<content:encoded><![CDATA[<p>I concur with Bob H. to an extent. I watched the entire Board Meeting via web cast. </p>
<p>Tom Haueter, an aviation safety expert  and staff member employed by the NTSB for over 26 years, vigorously argued to the Board to place the Teterboro tower controller&#8217;s non-pertinent &#8220;dead cat&#8221; telephone call at the top of the probable cause list. Although he was unsuccessful, it was clear to anyone watching the logic of his case was incontrovertible.</p>
<p>Why the Board placed the limitations of &#8220;see and avoid&#8221; at the top is anyone&#8217;s guess. Chairman Hersman&#8217;s Vice Chairman, Christopher Hart, was absent. It seemed as though the Board was frustrated and tired. They had difficultly getting the exact language of the probable cause adopted. The FAA has termination proceedings against the controller in question and his supervisor.</p>
<p>As Mr. Haueter argued, the limitations of &#8220;see and avoid&#8221; has been known since the deadly mid air over the Grand Canyon in 1956. That accident was the catalyst for sweeping changes in regulating air traffic.</p>
<p>Only time will tell if the lessons of this tragedy are learned.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob H.</title>
		<link>http://blog.aopa.org/leadingedge/?p=1137&#038;cpage=1#comment-29766</link>
		<dc:creator>Bob H.</dc:creator>
		<pubDate>Thu, 16 Sep 2010 01:20:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.aopa.org/asfblog/?p=1137#comment-29766</guid>
		<description><![CDATA[Alternate ending: The NTSB finds that mediocrity and complacency on the part of ATC were deadly factors in the crash.  

The pilot in command of the aircraft requested 3500 and NO ONE has provided a sufficiently reasonable justification for why that request was ignored. Organizational intransigence is not a a sufficient justification, but ymmv.

&quot;Do it right or not at all,&quot; needs to come right after &quot; ...safe, orderly and expeditious....&quot;]]></description>
		<content:encoded><![CDATA[<p>Alternate ending: The NTSB finds that mediocrity and complacency on the part of ATC were deadly factors in the crash.  </p>
<p>The pilot in command of the aircraft requested 3500 and NO ONE has provided a sufficiently reasonable justification for why that request was ignored. Organizational intransigence is not a a sufficient justification, but ymmv.</p>
<p>&#8220;Do it right or not at all,&#8221; needs to come right after &#8221; &#8230;safe, orderly and expeditious&#8230;.&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
