<?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 Paradox of &#8216;Simplicity&#8217;</title>
	<atom:link href="http://trueslant.com/milesobrien/2009/06/10/the-paradox-of-simplicity/feed/" rel="self" type="application/rss+xml" />
	<link>http://trueslant.com/milesobrien/2009/06/10/the-paradox-of-simplicity/</link>
	<description>[Please go to &#039;Settings&#039; to change your Tagline]</description>
	<lastBuildDate>Mon, 27 Jun 2011 15:24:24 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: fjcastil</title>
		<link>http://trueslant.com/milesobrien/2009/06/10/the-paradox-of-simplicity/comment-page-1/#comment-375</link>
		<dc:creator>fjcastil</dc:creator>
		<pubDate>Tue, 23 Jun 2009 04:28:00 +0000</pubDate>
		<guid isPermaLink="false">http://trueslant.com/milesobrien/?p=882#comment-375</guid>
		<description>Could not agree with you more! That is why I note my suspicion of flaws with the designs of Airbus, specially them being so dependent on the FBW. In the case of AA587, the plane had been maintained in Miami before flying to NY a few days before the crash. That plus that same plane had encountered severe turbulence during a flight a few months before the accident. I also remember that at one point, AA had to ground their fleet of Airbus A300&#039;s due to redundancy problems with their flight computers.
And just today, another Quantas A330 on route from Hong Kong to Perth, encoutered severe turbulence and 12 passengers were injured. Only this time there were no further incident, thanks be to God!
But like Miles has said, we just do not know how many situations have been saved by the same FBW systems.
In the end I also tend to think that the media and the entire airline industry tend to cover up details and a lot of the truth in order not to scare people from flying. As many ATP&#039;s know, there are many incidents on a daily basis that simpy go unknowned and untold. But if you fly enough, like some of us have to do, you may end up experiencing these situations &quot;live&quot;!
Unfortunately today, AF447 is not big news, and soon it will be out of mind.</description>
		<content:encoded><![CDATA[<p>Could not agree with you more! That is why I note my suspicion of flaws with the designs of Airbus, specially them being so dependent on the FBW. In the case of AA587, the plane had been maintained in Miami before flying to NY a few days before the crash. That plus that same plane had encountered severe turbulence during a flight a few months before the accident. I also remember that at one point, AA had to ground their fleet of Airbus A300&#8217;s due to redundancy problems with their flight computers.<br />
And just today, another Quantas A330 on route from Hong Kong to Perth, encoutered severe turbulence and 12 passengers were injured. Only this time there were no further incident, thanks be to God!<br />
But like Miles has said, we just do not know how many situations have been saved by the same FBW systems.<br />
In the end I also tend to think that the media and the entire airline industry tend to cover up details and a lot of the truth in order not to scare people from flying. As many ATP&#8217;s know, there are many incidents on a daily basis that simpy go unknowned and untold. But if you fly enough, like some of us have to do, you may end up experiencing these situations &#8220;live&#8221;!<br />
Unfortunately today, AF447 is not big news, and soon it will be out of mind.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fjcastil</title>
		<link>http://trueslant.com/milesobrien/2009/06/10/the-paradox-of-simplicity/comment-page-1/#comment-374</link>
		<dc:creator>fjcastil</dc:creator>
		<pubDate>Tue, 23 Jun 2009 04:00:13 +0000</pubDate>
		<guid isPermaLink="false">http://trueslant.com/milesobrien/?p=882#comment-374</guid>
		<description>Miles, miss you from your CNN days but finally caught with you! 
May the grace of God be with all the victims of AF447 and their families. But for business people like me that have to fly over 60K miles a year, both domestic and overseas, this incident leaves even more questions about airplane safety and pilot decision making than ever before. 
The pictures of flight AA587, an Airbus 300, bound to DR (where I am originally from) that crashed in NYC are still vivid in my head. If these airplanes are so safe and sophisticated, how come the flight computer allowed the pilots on AA587 A300 to yank the rudder so hard that the tail was ripped apart?! To this day I am still not entirely convinced we know for certain what happened on AA587.
Also, since pilots receive an on-route weather briefing before take off, why not choose a different route from the get go? As you have well indicated, initial investigations clearly show flight AF447 might have been at the wrong place, at the wrong time, in an area of heavy towering stoms.
Personally I think that many times having and depending on so much technology gives pilots a dose of false sense of security and over confidence, and sometimes (some of them with me as a passenger) pilots decide to fly through weather that turns out to be more serious than expected. Afterall, these machines are not flying tanks, and this humble passenger thinks that many storm systems should be avoided, and not flown thru, period. Deep inside my head, I hate to think that there may be serious flaws with the design of an Airbus airplane flown outside of &quot;normal&quot; circumstances or beyond the FC capabilities. In my book, right or wrong, the only two airplanes that I know in recent times have broken apart in mid-air due to unexpected turbulence have been Airbus. I pray to God that they do find the blackbox of AF447 so many questions and doubts can be answered. Meanwhile I say safety must always come first!</description>
		<content:encoded><![CDATA[<p>Miles, miss you from your CNN days but finally caught with you!<br />
May the grace of God be with all the victims of AF447 and their families. But for business people like me that have to fly over 60K miles a year, both domestic and overseas, this incident leaves even more questions about airplane safety and pilot decision making than ever before.<br />
The pictures of flight AA587, an Airbus 300, bound to DR (where I am originally from) that crashed in NYC are still vivid in my head. If these airplanes are so safe and sophisticated, how come the flight computer allowed the pilots on AA587 A300 to yank the rudder so hard that the tail was ripped apart?! To this day I am still not entirely convinced we know for certain what happened on AA587.<br />
Also, since pilots receive an on-route weather briefing before take off, why not choose a different route from the get go? As you have well indicated, initial investigations clearly show flight AF447 might have been at the wrong place, at the wrong time, in an area of heavy towering stoms.<br />
Personally I think that many times having and depending on so much technology gives pilots a dose of false sense of security and over confidence, and sometimes (some of them with me as a passenger) pilots decide to fly through weather that turns out to be more serious than expected. Afterall, these machines are not flying tanks, and this humble passenger thinks that many storm systems should be avoided, and not flown thru, period. Deep inside my head, I hate to think that there may be serious flaws with the design of an Airbus airplane flown outside of &#8220;normal&#8221; circumstances or beyond the FC capabilities. In my book, right or wrong, the only two airplanes that I know in recent times have broken apart in mid-air due to unexpected turbulence have been Airbus. I pray to God that they do find the blackbox of AF447 so many questions and doubts can be answered. Meanwhile I say safety must always come first!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dhiscock</title>
		<link>http://trueslant.com/milesobrien/2009/06/10/the-paradox-of-simplicity/comment-page-1/#comment-367</link>
		<dc:creator>dhiscock</dc:creator>
		<pubDate>Tue, 16 Jun 2009 16:50:53 +0000</pubDate>
		<guid isPermaLink="false">http://trueslant.com/milesobrien/?p=882#comment-367</guid>
		<description>I wonder if we are jumping too soon to conclusions on the pitot tube.  There are several other indicators (throttle, radar, gps, etc.) that would have given the pilots the same information.  I think it is more important to note the A330 is the common link.  How exactly flight controls work or do not work in certain control situations, and how robust those algorithms are is an open question.  Seems to me the easy answer is to question the A330 as the open cause...this could be a ground the fleet problem...changing the pitot tube could be like putting chewing gum on a crack in the Hoover Dam...</description>
		<content:encoded><![CDATA[<p>I wonder if we are jumping too soon to conclusions on the pitot tube.  There are several other indicators (throttle, radar, gps, etc.) that would have given the pilots the same information.  I think it is more important to note the A330 is the common link.  How exactly flight controls work or do not work in certain control situations, and how robust those algorithms are is an open question.  Seems to me the easy answer is to question the A330 as the open cause&#8230;this could be a ground the fleet problem&#8230;changing the pitot tube could be like putting chewing gum on a crack in the Hoover Dam&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: willcushman</title>
		<link>http://trueslant.com/milesobrien/2009/06/10/the-paradox-of-simplicity/comment-page-1/#comment-365</link>
		<dc:creator>willcushman</dc:creator>
		<pubDate>Mon, 15 Jun 2009 20:45:08 +0000</pubDate>
		<guid isPermaLink="false">http://trueslant.com/milesobrien/?p=882#comment-365</guid>
		<description>Some anecdotal information I got today from an aviator friend implies that the Airbus has had a history of vertical stabilizer and control surfaces failures linked to attachment hardware structural failure. Apparently these attachments are made from composite materials rather than machined aluminum, as in most commercial aircraft.  The use of composites is common for flight control surfaces but not for attachment hardware. Perhaps the vertical stab failed in the severe loads caused by the storm.  The anecdotal info I got was from a professional aircraft  dismantler who salvages airliner airframes for a living.  He has taken apart A310 and A320 aircraft.  Maybe the recovered vertical stabilizer will shed some light on this but will we ever know the chain of events that led up to the structural failures? Maybe they will find the flight data recorders.</description>
		<content:encoded><![CDATA[<p>Some anecdotal information I got today from an aviator friend implies that the Airbus has had a history of vertical stabilizer and control surfaces failures linked to attachment hardware structural failure. Apparently these attachments are made from composite materials rather than machined aluminum, as in most commercial aircraft.  The use of composites is common for flight control surfaces but not for attachment hardware. Perhaps the vertical stab failed in the severe loads caused by the storm.  The anecdotal info I got was from a professional aircraft  dismantler who salvages airliner airframes for a living.  He has taken apart A310 and A320 aircraft.  Maybe the recovered vertical stabilizer will shed some light on this but will we ever know the chain of events that led up to the structural failures? Maybe they will find the flight data recorders.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: robert</title>
		<link>http://trueslant.com/milesobrien/2009/06/10/the-paradox-of-simplicity/comment-page-1/#comment-364</link>
		<dc:creator>robert</dc:creator>
		<pubDate>Mon, 15 Jun 2009 20:41:46 +0000</pubDate>
		<guid isPermaLink="false">http://trueslant.com/milesobrien/?p=882#comment-364</guid>
		<description>In 2008 the Hubble Space Telescope had a failure in a data unit.  I think it took them months to change over to the backup unit.  And that was with the help of who knows how many PHDs.  That shows the high level of complication with technology today.</description>
		<content:encoded><![CDATA[<p>In 2008 the Hubble Space Telescope had a failure in a data unit.  I think it took them months to change over to the backup unit.  And that was with the help of who knows how many PHDs.  That shows the high level of complication with technology today.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: newsfan</title>
		<link>http://trueslant.com/milesobrien/2009/06/10/the-paradox-of-simplicity/comment-page-1/#comment-360</link>
		<dc:creator>newsfan</dc:creator>
		<pubDate>Sun, 14 Jun 2009 17:40:34 +0000</pubDate>
		<guid isPermaLink="false">http://trueslant.com/milesobrien/?p=882#comment-360</guid>
		<description>The more I read about this the more interested I am in the software that is used by the ADIRS to interpret information from the ADIRU&#039;s.  The Time article said that the Quantas Flight 72 investigation showed that the ADIRS software did not choose to use the accurate information from the properly functioning ADIRU, instead choosing to use the inaccurate information from the malfunctioning ADIRU.  This faulty information then fed into the autopilot software causing it to choose an incorrect angle of attack sending the plane into sharp dives that nearly caused an accident.  The redundancy of the multiple ADIRU&#039;s did not help because the software problem caused the ADIRS to choose  the malfunctioning ADIRU as the source of it&#039;s information.  Quote from Time, &quot;For some reason, the damn computer disregarded the healthy channels,&quot; says Hans Weber, an aviation expert who heads Tecop International, an aviation-consulting firm in San Diego. &quot;Instead, it acted upon the information from the rogue channel.&quot;
  
And it&#039;s not comforting when Time reports that Airbus officials say the problematic algorithm is only found in the mathematical models used for it&#039;s Airbus A330 and A340 models.  Here&#039;s some good questions for a reporter to ask Airbus:  What have you done to fix the algorithm problem in the ADIRS software that caused the pitch down problem on the Quantas flight?  If nothing, why not?  What would the cost be to Airbus to fix that sort of software problem?  Isn&#039;t the software problem as large of a problem as the Pitot tubes?           


The other thing that interests me is the redundancy of systems on Airbus.  On Wikepedia it says that this redundancy of back up systems will sometimes cause airline companies to delay maintenance of backup systems.  If Wikepedia is accurate on it&#039;s write up of ADIRS/ADIRU&#039;s it says the A330 has 3 ADIRU&#039;s.  If I was a reporter I&#039;d be asking Air France whether any of the ADIRU&#039;s on AF Flight 447 were in need of maintenance.  What was the status of backup ADIRU?  What was the status of the rest of the ADIRS system for that plane?  

The other thing that is interesting about the redundancy systems in the Airbus is how they can be confusing to the pilots during an emergency situation.  This is described in Wikepedia, in regards to Quantas Flight 72:  &quot;Analysis of complex systems is itself so difficult as to be subject to errors in the certification process. Complex interactions between flight computers and ADIRU&#039;s can lead to counter-intuitive behaviour for the crew in the event of a failure. In the case of Qantas Flight 72, the captain switched the source of IR data from ADIRU1 to ADIRU3 following a failure of ADIRU1; however ADIRU1 continued to supply ADR data to the captain&#039;s primary flight display. In addition, the master flight control computer (PRIM1) was switched from PRIM1 to PRIM2, then PRIM2 back to PRIM1, thereby creating a situation of uncertainty for the crew who did not know which redundant systems they were relying upon.&quot;  In a moment of emergency everything must work in an extremely synchronized fashion and after reading this report of the Quantas flight I&#039;m not confident that switching between back up systems in an emergency is as easy as advertised.</description>
		<content:encoded><![CDATA[<p>The more I read about this the more interested I am in the software that is used by the ADIRS to interpret information from the ADIRU&#8217;s.  The Time article said that the Quantas Flight 72 investigation showed that the ADIRS software did not choose to use the accurate information from the properly functioning ADIRU, instead choosing to use the inaccurate information from the malfunctioning ADIRU.  This faulty information then fed into the autopilot software causing it to choose an incorrect angle of attack sending the plane into sharp dives that nearly caused an accident.  The redundancy of the multiple ADIRU&#8217;s did not help because the software problem caused the ADIRS to choose  the malfunctioning ADIRU as the source of it&#8217;s information.  Quote from Time, &#8220;For some reason, the damn computer disregarded the healthy channels,&#8221; says Hans Weber, an aviation expert who heads Tecop International, an aviation-consulting firm in San Diego. &#8220;Instead, it acted upon the information from the rogue channel.&#8221;</p>
<p>And it&#8217;s not comforting when Time reports that Airbus officials say the problematic algorithm is only found in the mathematical models used for it&#8217;s Airbus A330 and A340 models.  Here&#8217;s some good questions for a reporter to ask Airbus:  What have you done to fix the algorithm problem in the ADIRS software that caused the pitch down problem on the Quantas flight?  If nothing, why not?  What would the cost be to Airbus to fix that sort of software problem?  Isn&#8217;t the software problem as large of a problem as the Pitot tubes?           </p>
<p>The other thing that interests me is the redundancy of systems on Airbus.  On Wikepedia it says that this redundancy of back up systems will sometimes cause airline companies to delay maintenance of backup systems.  If Wikepedia is accurate on it&#8217;s write up of ADIRS/ADIRU&#8217;s it says the A330 has 3 ADIRU&#8217;s.  If I was a reporter I&#8217;d be asking Air France whether any of the ADIRU&#8217;s on AF Flight 447 were in need of maintenance.  What was the status of backup ADIRU?  What was the status of the rest of the ADIRS system for that plane?  </p>
<p>The other thing that is interesting about the redundancy systems in the Airbus is how they can be confusing to the pilots during an emergency situation.  This is described in Wikepedia, in regards to Quantas Flight 72:  &#8220;Analysis of complex systems is itself so difficult as to be subject to errors in the certification process. Complex interactions between flight computers and ADIRU&#8217;s can lead to counter-intuitive behaviour for the crew in the event of a failure. In the case of Qantas Flight 72, the captain switched the source of IR data from ADIRU1 to ADIRU3 following a failure of ADIRU1; however ADIRU1 continued to supply ADR data to the captain&#8217;s primary flight display. In addition, the master flight control computer (PRIM1) was switched from PRIM1 to PRIM2, then PRIM2 back to PRIM1, thereby creating a situation of uncertainty for the crew who did not know which redundant systems they were relying upon.&#8221;  In a moment of emergency everything must work in an extremely synchronized fashion and after reading this report of the Quantas flight I&#8217;m not confident that switching between back up systems in an emergency is as easy as advertised.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rcp727</title>
		<link>http://trueslant.com/milesobrien/2009/06/10/the-paradox-of-simplicity/comment-page-1/#comment-359</link>
		<dc:creator>rcp727</dc:creator>
		<pubDate>Sat, 13 Jun 2009 20:32:20 +0000</pubDate>
		<guid isPermaLink="false">http://trueslant.com/milesobrien/?p=882#comment-359</guid>
		<description>Hello Miles,

Very informative article, again. In particular, the comparisons to &quot;old generation&quot; cockpits and FBW.

An interesting overview, would be the safety record of Airbus and Boeing in the lat 15 years, and in particular, US Airlines / Aircraft operating under Part 121. The only FBW comparison would be including the 777, with certain criteria added.

Also, two other points:

1. There seems to be much discussion of the total time of the Captain (approx. 11,000 hours). There is no proof the Captain was even in the cockpit, since many long leg commercial flights are operating with an augmented crew (additional crew member(s). Quite often the &quot;Senior&quot; Captain may take a sleep break in a berthed area or of First Class seat.

2. It was quite odd to me that terrorism was initially &quot;ruled out&quot; by the network coverage before any investigation began.

Regards</description>
		<content:encoded><![CDATA[<p>Hello Miles,</p>
<p>Very informative article, again. In particular, the comparisons to &#8220;old generation&#8221; cockpits and FBW.</p>
<p>An interesting overview, would be the safety record of Airbus and Boeing in the lat 15 years, and in particular, US Airlines / Aircraft operating under Part 121. The only FBW comparison would be including the 777, with certain criteria added.</p>
<p>Also, two other points:</p>
<p>1. There seems to be much discussion of the total time of the Captain (approx. 11,000 hours). There is no proof the Captain was even in the cockpit, since many long leg commercial flights are operating with an augmented crew (additional crew member(s). Quite often the &#8220;Senior&#8221; Captain may take a sleep break in a berthed area or of First Class seat.</p>
<p>2. It was quite odd to me that terrorism was initially &#8220;ruled out&#8221; by the network coverage before any investigation began.</p>
<p>Regards</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: newsfan</title>
		<link>http://trueslant.com/milesobrien/2009/06/10/the-paradox-of-simplicity/comment-page-1/#comment-358</link>
		<dc:creator>newsfan</dc:creator>
		<pubDate>Sat, 13 Jun 2009 19:20:27 +0000</pubDate>
		<guid isPermaLink="false">http://trueslant.com/milesobrien/?p=882#comment-358</guid>
		<description>Miles,

Here&#039;s some info from a Time article that ties in with your article about equipment/fly by wire/software issues. Looks like some of the Ptiot tubes are defective and so are some of the ADIRU&#039;s.

&quot;It is not yet known whether Air France 447, an A330, carried the troublesome variety of ADIRU. But if it did, and if the Air France plane plummeted into an uncommanded dive while traveling through a downdraft generated by storms — a common occurrence over the region of the Atlantic Ocean where the plane went down — it could have been doomed as it entered a steep dive and likely broke up.&quot;

&quot;Aviation authorities around the world have ordered inspections and procedures to try to eliminate the problem. &quot;In these fly-by-wire systems, one never really knows if one has checked out all possible combinations of events to make sure that the computer properly reacts,&quot; Weber says of modern flight control. Fly-by-wire systems use computers and wires instead of mechanics and hydraulics to control a plane&#039;s flight. Electronic systems are more reliable than mechanical processes but are prone to software errors that can&#039;t always be anticipated. &quot;There could be some other sequence of events that could cause another bad software reaction,&quot; says Weber.&quot;

&quot;The Australians&#039; March report concluded that the October dive was due to a series of events that, when combined, was &quot;close to the worst possible scenario that could arise from the design limitation in the AOA processing algorithm.&quot; Airbus also told investigators that this particular mathematical formula for flying the plane is found only on its A330 and A340 models. &quot;Different algorithms were in use on other Airbus types, which were reported to be more robust to AOA spikes,&quot; the report said. &quot;The manufacturer advised that AOA spikes matching the above scenario would not have caused a pitch-down event on Airbus aircraft other than an A330 or A340.&quot;</description>
		<content:encoded><![CDATA[<p>Miles,</p>
<p>Here&#8217;s some info from a Time article that ties in with your article about equipment/fly by wire/software issues. Looks like some of the Ptiot tubes are defective and so are some of the ADIRU&#8217;s.</p>
<p>&#8220;It is not yet known whether Air France 447, an A330, carried the troublesome variety of ADIRU. But if it did, and if the Air France plane plummeted into an uncommanded dive while traveling through a downdraft generated by storms — a common occurrence over the region of the Atlantic Ocean where the plane went down — it could have been doomed as it entered a steep dive and likely broke up.&#8221;</p>
<p>&#8220;Aviation authorities around the world have ordered inspections and procedures to try to eliminate the problem. &#8220;In these fly-by-wire systems, one never really knows if one has checked out all possible combinations of events to make sure that the computer properly reacts,&#8221; Weber says of modern flight control. Fly-by-wire systems use computers and wires instead of mechanics and hydraulics to control a plane&#8217;s flight. Electronic systems are more reliable than mechanical processes but are prone to software errors that can&#8217;t always be anticipated. &#8220;There could be some other sequence of events that could cause another bad software reaction,&#8221; says Weber.&#8221;</p>
<p>&#8220;The Australians&#8217; March report concluded that the October dive was due to a series of events that, when combined, was &#8220;close to the worst possible scenario that could arise from the design limitation in the AOA processing algorithm.&#8221; Airbus also told investigators that this particular mathematical formula for flying the plane is found only on its A330 and A340 models. &#8220;Different algorithms were in use on other Airbus types, which were reported to be more robust to AOA spikes,&#8221; the report said. &#8220;The manufacturer advised that AOA spikes matching the above scenario would not have caused a pitch-down event on Airbus aircraft other than an A330 or A340.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lgordonj</title>
		<link>http://trueslant.com/milesobrien/2009/06/10/the-paradox-of-simplicity/comment-page-1/#comment-355</link>
		<dc:creator>lgordonj</dc:creator>
		<pubDate>Sat, 13 Jun 2009 01:23:27 +0000</pubDate>
		<guid isPermaLink="false">http://trueslant.com/milesobrien/?p=882#comment-355</guid>
		<description>The Dash 8 SOP suggests disconnecting the AP in known icing conditions.  And not be used during the landing.  The link will provide you with some interesting info on the Dash 8, icing and other stuff.

Lon

http://www.upsetrecovery.com/forum/viewtopic.php?f=5&amp;t=44
sequence.</description>
		<content:encoded><![CDATA[<p>The Dash 8 SOP suggests disconnecting the AP in known icing conditions.  And not be used during the landing.  The link will provide you with some interesting info on the Dash 8, icing and other stuff.</p>
<p>Lon</p>
<p><a href="http://www.upsetrecovery.com/forum/viewtopic.php?f=5&amp;t=44" rel="nofollow">http://www.upsetrecovery.com/forum/viewtopic.php?f=5&amp;t=44</a><br />
sequence.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lgordonj</title>
		<link>http://trueslant.com/milesobrien/2009/06/10/the-paradox-of-simplicity/comment-page-1/#comment-354</link>
		<dc:creator>lgordonj</dc:creator>
		<pubDate>Sat, 13 Jun 2009 00:21:00 +0000</pubDate>
		<guid isPermaLink="false">http://trueslant.com/milesobrien/?p=882#comment-354</guid>
		<description>Debris photographs of the Air France Airbus Flt 447 breakup suggests that the vertical stabilizer separated, more or less intact, from the aircraft just as it did on the American Airlines Airbus that crashed at JFK on 11/12/2001.  The NTSB determined that the JFK accident  was caused, in part, by excessive rudder input (Part of the stabilizer) while reacting to wake turbulence.  These aircraft are “Fly by Wire” meaning that control surfaces are reacting to inputs from by the crew via computers.  One would think that the software that drives these computers would be able to sense dangerous inputs by the crew and dampen it before it becomes catastrophic.  Especially when one considers that crew reactions to unusual attitudes of the aircraft responding to turbulence may be spontaneous.

Lon Wilmington, NC

NTSB report on causes of the American Airlines accident at JFK on 11/12/2001 http://www.ntsb.gov/ntsb/AccList.asp?month=11&amp;year=2001</description>
		<content:encoded><![CDATA[<p>Debris photographs of the Air France Airbus Flt 447 breakup suggests that the vertical stabilizer separated, more or less intact, from the aircraft just as it did on the American Airlines Airbus that crashed at JFK on 11/12/2001.  The NTSB determined that the JFK accident  was caused, in part, by excessive rudder input (Part of the stabilizer) while reacting to wake turbulence.  These aircraft are “Fly by Wire” meaning that control surfaces are reacting to inputs from by the crew via computers.  One would think that the software that drives these computers would be able to sense dangerous inputs by the crew and dampen it before it becomes catastrophic.  Especially when one considers that crew reactions to unusual attitudes of the aircraft responding to turbulence may be spontaneous.</p>
<p>Lon Wilmington, NC</p>
<p>NTSB report on causes of the American Airlines accident at JFK on 11/12/2001 <a href="http://www.ntsb.gov/ntsb/AccList.asp?month=11&amp;year=2001" rel="nofollow">http://www.ntsb.gov/ntsb/AccList.asp?month=11&amp;year=2001</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

