<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Follow-up - Southwest Engine Failure</title>
	<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/</link>
	<description>The Aviation Blog</description>
	<pubDate>Sat, 05 Jul 2008 19:27:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.2</generator>

	<item>
		<title>By: FAA Report - 11/19/2007 at Flightstory.net - Aviation Blog</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9209</link>
		<author>FAA Report - 11/19/2007 at Flightstory.net - Aviation Blog</author>
		<pubDate>Tue, 27 Nov 2007 12:58:50 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9209</guid>
					<description>[...] Date &#38; Time: 11/17/2007 21:10 Location: Dallas, TX Aircraft Type: Boeing 737 Registration: N/A Airline: Southwest Airlines Flight: 438 Phase: Take-off Damage: Unknown Injuries &#38; Fatalities: none Description: Southwest Airlines flight 438, a Boeing 737, on departure experienced a vibration in the number 2 engine, engine sustained unknown damage, aircraft returned and landed without incident. UPDATE: Visit: Follow-up - Southwest Engine Failure [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Date &#38; Time: 11/17/2007 21:10 Location: Dallas, TX Aircraft Type: Boeing 737 Registration: N/A Airline: Southwest Airlines Flight: 438 Phase: Take-off Damage: Unknown Injuries &#38; Fatalities: none Description: Southwest Airlines flight 438, a Boeing 737, on departure experienced a vibration in the number 2 engine, engine sustained unknown damage, aircraft returned and landed without incident. UPDATE: Visit: Follow-up - Southwest Engine Failure [&#8230;]</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: kc</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9218</link>
		<author>kc</author>
		<pubDate>Tue, 27 Nov 2007 15:04:48 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9218</guid>
					<description>Hard to take this too serious when those commenting cant spell hardly anything.</description>
		<content:encoded><![CDATA[<p>Hard to take this too serious when those commenting cant spell hardly anything.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Alan</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9223</link>
		<author>Alan</author>
		<pubDate>Tue, 27 Nov 2007 15:44:57 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9223</guid>
					<description>But the pictures seem to confirm.  Sad that it sounds like they lied to cover their asses.  If this is all true, instead of justifiably commending the skills of their pilot in getting everyone down safely and promising a complete investigation, they look completely untrustworthy.</description>
		<content:encoded><![CDATA[<p>But the pictures seem to confirm.  Sad that it sounds like they lied to cover their asses.  If this is all true, instead of justifiably commending the skills of their pilot in getting everyone down safely and promising a complete investigation, they look completely untrustworthy.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: jason</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9224</link>
		<author>jason</author>
		<pubDate>Tue, 27 Nov 2007 15:45:39 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9224</guid>
					<description>@KC
You should learn to write before making comments like that.</description>
		<content:encoded><![CDATA[<p>@KC<br />
You should learn to write before making comments like that.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: mrp</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9227</link>
		<author>mrp</author>
		<pubDate>Tue, 27 Nov 2007 15:51:06 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9227</guid>
					<description>@kc:  Sadly, most people can't spell or use proper grammar in the first place.  I work with a lot of copywriters, people who should know the English language and how to use it at an expert level, and I am constantly fixing simple mistakes that even pass the proof-readers as well!</description>
		<content:encoded><![CDATA[<p>@kc:  Sadly, most people can&#8217;t spell or use proper grammar in the first place.  I work with a lot of copywriters, people who should know the English language and how to use it at an expert level, and I am constantly fixing simple mistakes that even pass the proof-readers as well!</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: JP</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9228</link>
		<author>JP</author>
		<pubDate>Tue, 27 Nov 2007 15:51:47 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9228</guid>
					<description>Oh really Mr. "cant spell hardly anything"?  The photos speak for themselves in volumes.</description>
		<content:encoded><![CDATA[<p>Oh really Mr. &#8220;cant spell hardly anything&#8221;?  The photos speak for themselves in volumes.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Mark</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9234</link>
		<author>Mark</author>
		<pubDate>Tue, 27 Nov 2007 16:22:23 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9234</guid>
					<description>Let me explain it to you.

When you take pictures, you do not ASK PERMISSION to publish them.

That is what people do in mainland China. Not here in the US. In the US, we are a free country. You publish your pictures first, and let the FAA ask questions later. Not the other way around.</description>
		<content:encoded><![CDATA[<p>Let me explain it to you.</p>
<p>When you take pictures, you do not ASK PERMISSION to publish them.</p>
<p>That is what people do in mainland China. Not here in the US. In the US, we are a free country. You publish your pictures first, and let the FAA ask questions later. Not the other way around.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Alex</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9236</link>
		<author>Alex</author>
		<pubDate>Tue, 27 Nov 2007 16:39:32 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9236</guid>
					<description>&#62; Hard to take this too serious when those commenting cant spell hardly anything.

Um. Use a lot of windex, huh?</description>
		<content:encoded><![CDATA[<p>&gt; Hard to take this too serious when those commenting cant spell hardly anything.</p>
<p>Um. Use a lot of windex, huh?</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Dark-Star</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9239</link>
		<author>Dark-Star</author>
		<pubDate>Tue, 27 Nov 2007 16:53:14 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9239</guid>
					<description>You people are a bunch of nitpickers. *Forget* the spelling already; take a good look at the pictures, they're what's important!

People almost died, and southwest lied, to coin a phrase. All I can say is hooray for cellphone cameras and quick-thinking average people.</description>
		<content:encoded><![CDATA[<p>You people are a bunch of nitpickers. *Forget* the spelling already; take a good look at the pictures, they&#8217;re what&#8217;s important!</p>
<p>People almost died, and southwest lied, to coin a phrase. All I can say is hooray for cellphone cameras and quick-thinking average people.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: natas</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9240</link>
		<author>natas</author>
		<pubDate>Tue, 27 Nov 2007 16:54:06 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9240</guid>
					<description>@KC

Do you find comfort in pointing out others mistakes? A serious matter is being discussed and you can't 'hardly' take the matter seriously due to their spelling and grammar usage? grow up.....</description>
		<content:encoded><![CDATA[<p>@KC</p>
<p>Do you find comfort in pointing out others mistakes? A serious matter is being discussed and you can&#8217;t &#8216;hardly&#8217; take the matter seriously due to their spelling and grammar usage? grow up&#8230;..</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Alex U.</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9242</link>
		<author>Alex U.</author>
		<pubDate>Tue, 27 Nov 2007 17:11:14 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9242</guid>
					<description>I had a teacher in high school who worked for Boeing, designing the rotary blades for the engines.  He says he left because he did not believe in making weapons.  I think this story will sadden him.
At least everyone got back on the ground alright.  Just try to put yourself in that situation, you might not care about spelling vibration right after that either.</description>
		<content:encoded><![CDATA[<p>I had a teacher in high school who worked for Boeing, designing the rotary blades for the engines.  He says he left because he did not believe in making weapons.  I think this story will sadden him.<br />
At least everyone got back on the ground alright.  Just try to put yourself in that situation, you might not care about spelling vibration right after that either.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: PENIX</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9243</link>
		<author>PENIX</author>
		<pubDate>Tue, 27 Nov 2007 17:17:18 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9243</guid>
					<description>This doesn't speak well for Southwest's maintenance crew... but are any of the other airlines any better?</description>
		<content:encoded><![CDATA[<p>This doesn&#8217;t speak well for Southwest&#8217;s maintenance crew&#8230; but are any of the other airlines any better?</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: evgen</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9251</link>
		<author>evgen</author>
		<pubDate>Tue, 27 Nov 2007 17:55:53 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9251</guid>
					<description>So a engine fan came apart... big deal.  Let's review the facts here.  An engine that spins large metal blades at thousands of revolutions per minute eventually came apart.  The fan blades were contained by the engine structure and safely ejected from the now non-operative engine.  When something like this happens the pilots will feel a vibration and then the engine failure warnings will start (including things like fail-safe engine fire warnings, etc.)  Since you cannot even see the engines from the cockpit of a 737 the pilots would report the vibration and engine failure to ATC and begin emergency procedures.  While one pilot was working on making sure the plane did not crash the other would be working the engine shutdown and fire suppression checklist.  Frankly these guys have better things to do than calm down passengers (that is the flight attendants job and it sounds like they were the only ones to screw-up here.)

There was no "cover up" and I am certain that if you dig through the FAA web site you will find the actual report that details both what the pilots thought was happening and the report from the ground that lists the actual damage.

Get a grip people.</description>
		<content:encoded><![CDATA[<p>So a engine fan came apart&#8230; big deal.  Let&#8217;s review the facts here.  An engine that spins large metal blades at thousands of revolutions per minute eventually came apart.  The fan blades were contained by the engine structure and safely ejected from the now non-operative engine.  When something like this happens the pilots will feel a vibration and then the engine failure warnings will start (including things like fail-safe engine fire warnings, etc.)  Since you cannot even see the engines from the cockpit of a 737 the pilots would report the vibration and engine failure to ATC and begin emergency procedures.  While one pilot was working on making sure the plane did not crash the other would be working the engine shutdown and fire suppression checklist.  Frankly these guys have better things to do than calm down passengers (that is the flight attendants job and it sounds like they were the only ones to screw-up here.)</p>
<p>There was no &#8220;cover up&#8221; and I am certain that if you dig through the FAA web site you will find the actual report that details both what the pilots thought was happening and the report from the ground that lists the actual damage.</p>
<p>Get a grip people.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: The Champ</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9253</link>
		<author>The Champ</author>
		<pubDate>Tue, 27 Nov 2007 18:00:11 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9253</guid>
					<description>Guys: Don't be too hard on the spelling/grammar of the original comments, they were written by Southwest passengers after all......</description>
		<content:encoded><![CDATA[<p>Guys: Don&#8217;t be too hard on the spelling/grammar of the original comments, they were written by Southwest passengers after all&#8230;&#8230;</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Don</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9255</link>
		<author>Don</author>
		<pubDate>Tue, 27 Nov 2007 18:11:32 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9255</guid>
					<description>Why are some many people's online comments about spelling or grammer?</description>
		<content:encoded><![CDATA[<p>Why are some many people&#8217;s online comments about spelling or grammer?</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: o_krush</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9259</link>
		<author>o_krush</author>
		<pubDate>Tue, 27 Nov 2007 18:30:18 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9259</guid>
					<description>I will make it short:

Can't damn a maintenance crew until you know a cause.

Has anyone considered the possibility of some sort of debris (which seems unlikely but not impossible) entering the engine?

It is even possible the crew followed absolute standards and received a substandard part.


The only real issue is the lie by the airline regarding the incident.   PR nightmare for them.</description>
		<content:encoded><![CDATA[<p>I will make it short:</p>
<p>Can&#8217;t damn a maintenance crew until you know a cause.</p>
<p>Has anyone considered the possibility of some sort of debris (which seems unlikely but not impossible) entering the engine?</p>
<p>It is even possible the crew followed absolute standards and received a substandard part.</p>
<p>The only real issue is the lie by the airline regarding the incident.   PR nightmare for them.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: August</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9260</link>
		<author>August</author>
		<pubDate>Tue, 27 Nov 2007 18:30:31 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9260</guid>
					<description>737's are designed to fly on one engine.  Yes, this isn't an ideal way to fly a plane, but it is designed and engineered so that if there is a critical failure of one engine, the flight crew have the ability to control the plane and put it safely on the ground.  This is called a redundant system and are designed into practically everything where complete failure can cost human lives.  This event shows how important these systems are.  Even if the second engine failed there is still another redundant system on board to allow the pilots to use the hydraulic powered flight controls.   The people on that plane were not in significantly greater danger after the engine failed then when they first stepped onto the plane.  People didn't almost loose their lives; the engineering SAVED lives.</description>
		<content:encoded><![CDATA[<p>737&#8217;s are designed to fly on one engine.  Yes, this isn&#8217;t an ideal way to fly a plane, but it is designed and engineered so that if there is a critical failure of one engine, the flight crew have the ability to control the plane and put it safely on the ground.  This is called a redundant system and are designed into practically everything where complete failure can cost human lives.  This event shows how important these systems are.  Even if the second engine failed there is still another redundant system on board to allow the pilots to use the hydraulic powered flight controls.   The people on that plane were not in significantly greater danger after the engine failed then when they first stepped onto the plane.  People didn&#8217;t almost loose their lives; the engineering SAVED lives.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: SW customer</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9261</link>
		<author>SW customer</author>
		<pubDate>Tue, 27 Nov 2007 18:32:16 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9261</guid>
					<description>Compared to other airlines out there Southwest has done an amazing job - not to mention, just like cars planes break down too. The pilots in this case did an awesome job at getting everyone back on the ground safely. An investigation will take place and I'm sure that whatever the findings are Southwest will step up to the plate to address them. The plane was a Boeing - could be something Boeing needs to address. I fly with Southwest and will continue to fly with them because among the other airlines, they are the best option.</description>
		<content:encoded><![CDATA[<p>Compared to other airlines out there Southwest has done an amazing job - not to mention, just like cars planes break down too. The pilots in this case did an awesome job at getting everyone back on the ground safely. An investigation will take place and I&#8217;m sure that whatever the findings are Southwest will step up to the plate to address them. The plane was a Boeing - could be something Boeing needs to address. I fly with Southwest and will continue to fly with them because among the other airlines, they are the best option.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: John</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9262</link>
		<author>John</author>
		<pubDate>Tue, 27 Nov 2007 18:34:16 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9262</guid>
					<description>Not leaning either way, I do not understand how anyone can say whether Southwest is lying or these passengers are lying??? For those of you who say the pictures don't lie, who said anyone was lying about the damage? Those pictures do not say word one that Southwest is lying. Those pictures show ground personnel and AFFR responding to an incident. As much as you say this proves Southwest is covering something up, I say it proves nothing. Who is to say this Joe and Jen are not making up their stories? I am sure they were scared but to say that because these two people gave their stories that it must be so is ludicrous. I say have each of the 133 passengers on board give the same account, without having talked to each other prior, and then we'll talk.</description>
		<content:encoded><![CDATA[<p>Not leaning either way, I do not understand how anyone can say whether Southwest is lying or these passengers are lying??? For those of you who say the pictures don&#8217;t lie, who said anyone was lying about the damage? Those pictures do not say word one that Southwest is lying. Those pictures show ground personnel and AFFR responding to an incident. As much as you say this proves Southwest is covering something up, I say it proves nothing. Who is to say this Joe and Jen are not making up their stories? I am sure they were scared but to say that because these two people gave their stories that it must be so is ludicrous. I say have each of the 133 passengers on board give the same account, without having talked to each other prior, and then we&#8217;ll talk.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Avinsurer</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9263</link>
		<author>Avinsurer</author>
		<pubDate>Tue, 27 Nov 2007 18:36:02 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9263</guid>
					<description>Sorry PENIX...but that's not true.  This problem could've been something the naked eye or even a magnifying glass could've seen.  Let the facts play out and read what the NTSB, FAA, and GE/CFM inspectors have to say.  There have been other uncontained engine failures that have resulted in deaths (UA 292, DL MD80 in PNS(?)) and others that haven't (Mesa out of DEN and numerous Bizjets).  Too many variables to come out and blatently say "poor maintenance" until the investigation is done.</description>
		<content:encoded><![CDATA[<p>Sorry PENIX&#8230;but that&#8217;s not true.  This problem could&#8217;ve been something the naked eye or even a magnifying glass could&#8217;ve seen.  Let the facts play out and read what the NTSB, FAA, and GE/CFM inspectors have to say.  There have been other uncontained engine failures that have resulted in deaths (UA 292, DL MD80 in PNS(?)) and others that haven&#8217;t (Mesa out of DEN and numerous Bizjets).  Too many variables to come out and blatently say &#8220;poor maintenance&#8221; until the investigation is done.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: monsterlib</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9266</link>
		<author>monsterlib</author>
		<pubDate>Tue, 27 Nov 2007 18:50:07 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9266</guid>
					<description>there is little risk of ejected fan blades penetrating into the fuselage.  if you notice, there are no passenger windows in plane with the engine primary compressor.  the manufacturer has armored plate here instead to prevent penetration.  i believe they do the same thing on the inboard wall of the engine cowling - there are no pictures, but i'm curious if there are any holes through the in-board side of the engine.  it is surprising the amount of system redundancies on modern air and spacecraft.  

we should all be impressed how this craft safely made it home.</description>
		<content:encoded><![CDATA[<p>there is little risk of ejected fan blades penetrating into the fuselage.  if you notice, there are no passenger windows in plane with the engine primary compressor.  the manufacturer has armored plate here instead to prevent penetration.  i believe they do the same thing on the inboard wall of the engine cowling - there are no pictures, but i&#8217;m curious if there are any holes through the in-board side of the engine.  it is surprising the amount of system redundancies on modern air and spacecraft.  </p>
<p>we should all be impressed how this craft safely made it home.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Alex A. Hutnik &#187; Blog Archive &#187; And This is Why I Hate Flying</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9271</link>
		<author>Alex A. Hutnik &#187; Blog Archive &#187; And This is Why I Hate Flying</author>
		<pubDate>Tue, 27 Nov 2007 19:05:56 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9271</guid>
					<description>[...] Southwest Engine Failure at Flightstory.net - Aviation Blog [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Southwest Engine Failure at Flightstory.net - Aviation Blog [&#8230;]</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: testpilot</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9276</link>
		<author>testpilot</author>
		<pubDate>Tue, 27 Nov 2007 19:57:04 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9276</guid>
					<description>Clearly, this forum needs a dose of knowledgeable reality from someone with a bit of experience in this area.  Let me help set the record straight.  I apologize for the length, but this needs to be done!

The pictures show what's called an "uncontained turbine failure" or "uncontained compressor failure".  That means that some "rotary blades" (actually, turbine or compressor blades) fractured or disintegrated while the engine was rotating and were shot outward, with parts completely penetrating the engine cowling, the external, visible cover of the engine.  

(As an aside for Alex U., Boeing has never built jet engines or turbine or compressor blades, so either your HS teacher was mistaken or your memory of what he said is faulty.)

Because jet engines rotate at incredibly high speeds (20,000 rpm is not uncommon) the engine cowling is designed to contain parts that come apart, as another commenter stated.  Occasionally, as in this case, the dynamics of the engine failure resulted in a few small pieces completely exiting the engine cowling.    

Yes, passengers have been killed when high-speed metal debris penetrated the fuselage but, relative to the number of passengers flown in a year, your odds are better of winning the lottery.  It is also highly unlikely the aircraft would have crashed due to debris penetrating the fuselage.  Multiple redundant systems make this extremely rare.  Again, you're more likely to actually win playing PowerBall.

One of the comments mentioned that "a big chunk of the engine flew off."  This is not uncommon either.  The whole cowling  around the outside of the engine is actually several pieces that have hinges and latches so they can be opened to perform  maintenance on the engine.

In an uncontained engine failure it's possible for flying debris to destroy the latches and cause the cowling to pop open, and then the slipstream (the high velocity air passing over the airplane as it flies) will peel the cowling all the way off, just like the hood of a NASCAR racer does in a high-speed collision. 

I'd like to also set the record straight on this quote:  "If an engine managed to explode in a fireball, it’s mostly likely going to take the whole plane out"  Simply not true.  An engine failure, even an explosive, uncontained high-speed turbine  failure like this one, is extremely unlikely to "take the whole plane out".  The aircraft has two engines for exactly this reason -- lose one, keep flying.

There are numerous safety systems built into the design of the aircraft, the engines and the attachment point of the engine to the airplane (the pylon) that prevent this.  Modern jet engines are some of the most reliable devices ever built, but they are mechanical systems and still occasionally fail, sometimes in spectacular fashion, but they almost never blow-up like a bomb and destroy an entire aircraft.  

To impugn SWA maintenance for this incident is also extremely premature.  The investigation will probably find the root cause of the blade failure, but without any facts it's irresponsible to say "it doesn't speak well for Southwest's maintenance crew."  Sometimes things just break, so let's wait for the facts before casting judgment.

As for the details of Southwest "lying" about what actually happened, you folks need to understand how aviation mishap reporting systems work.  Most systems (including the one the USAF uses, with which I'm intimately familiar) include a data field for the phase of flight in which the mishap occurred.  

The FAA system may lump takeoff in with "departure", the portion of the flight immediately after takeoff until the aircraft reaches cruise altitude.  This is also a "preliminary report" -- someone's best guess what happened immediately after it happened, before an investigation is completed, before all the facts are in, and minor errors like the phase of flight, if it is an error, are not uncommon early on.
 
The narrative from the report also says "on departure experienced a vibration in the number 2 engine" so the assumption that SWA  is lying about when it happened is just silly.  At worst it could be a clerical error, not some attempt to deceive.  Does it really matter when the engine came apart?  The note below this report also says "Source: FAA - Correctness not guaranteed,  completeness not intended" -- that's "FAA" not "SWA", so be careful when you start throwing around charges of "covering their asses..." [Alan].

Commenter Joe also said "there was no vidration [sic]", a reference to the report stating the aircraft "experienced a vibration in the number 2 engine."  Based on where Joe was sitting he may not have felt any, but up in the cockpit I'll bet you the pilots felt some pretty hefty vibrations as the engine came apart.  

This has to do with the dynamics of structural vibration -- bending modes, nodes, propagation, etc. -- basically, there are points in the aircraft  where the vibratory waves cancel each other out and can't be felt or multiply so they are very noticeable.  Where Joe sat he may not have felt any vibrations, but the pilots most likely did.  

Realize also that the pilots probably had numerous other indications of a problem, from gauges showing out-of-limit or fluctuating readings to warning lights and horns.  Some aircraft even have indicators that precisely show engine vibrations though I doubt a modern 737 has these.  

So, bottom line, for the pilots to say there were "vibrations" isn't a lie.  There's not an "engine exploded" light in the cockpit, and the safety report describes the indications the PILOTS had, not what the non-aviator passenger thinks they saw and felt.

Lastly, if the flight attendants were crying and hyperventilating they need to be counseled for a lack of  professional discipline.  The aircraft had a fairly major problem but the cockpit crew were handling it in accordance with the flght manual and company procedures.  Flight attendants are trained to remain calm so they can actually peform their duties, assist the pilots as necessary and take care of the passengers.  If they were getting hysterical it sounds like there may have been a breakdown in discipline.

One thing I would like to know from someone who was actually on the aircraft:  Did the Captain or First Officer walk back into the cabin inflight and look at the engine to survey the damage?

I hope this clears up many of the misconceptions and conjecture that this incident has generated.  No, I'm not a pilot for SWA, though I think they are a very good airline.  I am a USAF test pilot and have dozens of friends who fly for Southwest, and to the man they are some of the best,  most professional aviators I've ever known.  

Kudos to the two guys who got this jet back on the ground safely despite the "fatal engine failure", tearful goodbyes and hyperventilating stewardesses.</description>
		<content:encoded><![CDATA[<p>Clearly, this forum needs a dose of knowledgeable reality from someone with a bit of experience in this area.  Let me help set the record straight.  I apologize for the length, but this needs to be done!</p>
<p>The pictures show what&#8217;s called an &#8220;uncontained turbine failure&#8221; or &#8220;uncontained compressor failure&#8221;.  That means that some &#8220;rotary blades&#8221; (actually, turbine or compressor blades) fractured or disintegrated while the engine was rotating and were shot outward, with parts completely penetrating the engine cowling, the external, visible cover of the engine.  </p>
<p>(As an aside for Alex U., Boeing has never built jet engines or turbine or compressor blades, so either your HS teacher was mistaken or your memory of what he said is faulty.)</p>
<p>Because jet engines rotate at incredibly high speeds (20,000 rpm is not uncommon) the engine cowling is designed to contain parts that come apart, as another commenter stated.  Occasionally, as in this case, the dynamics of the engine failure resulted in a few small pieces completely exiting the engine cowling.    </p>
<p>Yes, passengers have been killed when high-speed metal debris penetrated the fuselage but, relative to the number of passengers flown in a year, your odds are better of winning the lottery.  It is also highly unlikely the aircraft would have crashed due to debris penetrating the fuselage.  Multiple redundant systems make this extremely rare.  Again, you&#8217;re more likely to actually win playing PowerBall.</p>
<p>One of the comments mentioned that &#8220;a big chunk of the engine flew off.&#8221;  This is not uncommon either.  The whole cowling  around the outside of the engine is actually several pieces that have hinges and latches so they can be opened to perform  maintenance on the engine.</p>
<p>In an uncontained engine failure it&#8217;s possible for flying debris to destroy the latches and cause the cowling to pop open, and then the slipstream (the high velocity air passing over the airplane as it flies) will peel the cowling all the way off, just like the hood of a NASCAR racer does in a high-speed collision. </p>
<p>I&#8217;d like to also set the record straight on this quote:  &#8220;If an engine managed to explode in a fireball, it’s mostly likely going to take the whole plane out&#8221;  Simply not true.  An engine failure, even an explosive, uncontained high-speed turbine  failure like this one, is extremely unlikely to &#8220;take the whole plane out&#8221;.  The aircraft has two engines for exactly this reason &#8212; lose one, keep flying.</p>
<p>There are numerous safety systems built into the design of the aircraft, the engines and the attachment point of the engine to the airplane (the pylon) that prevent this.  Modern jet engines are some of the most reliable devices ever built, but they are mechanical systems and still occasionally fail, sometimes in spectacular fashion, but they almost never blow-up like a bomb and destroy an entire aircraft.  </p>
<p>To impugn SWA maintenance for this incident is also extremely premature.  The investigation will probably find the root cause of the blade failure, but without any facts it&#8217;s irresponsible to say &#8220;it doesn&#8217;t speak well for Southwest&#8217;s maintenance crew.&#8221;  Sometimes things just break, so let&#8217;s wait for the facts before casting judgment.</p>
<p>As for the details of Southwest &#8220;lying&#8221; about what actually happened, you folks need to understand how aviation mishap reporting systems work.  Most systems (including the one the USAF uses, with which I&#8217;m intimately familiar) include a data field for the phase of flight in which the mishap occurred.  </p>
<p>The FAA system may lump takeoff in with &#8220;departure&#8221;, the portion of the flight immediately after takeoff until the aircraft reaches cruise altitude.  This is also a &#8220;preliminary report&#8221; &#8212; someone&#8217;s best guess what happened immediately after it happened, before an investigation is completed, before all the facts are in, and minor errors like the phase of flight, if it is an error, are not uncommon early on.</p>
<p>The narrative from the report also says &#8220;on departure experienced a vibration in the number 2 engine&#8221; so the assumption that SWA  is lying about when it happened is just silly.  At worst it could be a clerical error, not some attempt to deceive.  Does it really matter when the engine came apart?  The note below this report also says &#8220;Source: FAA - Correctness not guaranteed,  completeness not intended&#8221; &#8212; that&#8217;s &#8220;FAA&#8221; not &#8220;SWA&#8221;, so be careful when you start throwing around charges of &#8220;covering their asses&#8230;&#8221; [Alan].</p>
<p>Commenter Joe also said &#8220;there was no vidration [sic]&#8221;, a reference to the report stating the aircraft &#8220;experienced a vibration in the number 2 engine.&#8221;  Based on where Joe was sitting he may not have felt any, but up in the cockpit I&#8217;ll bet you the pilots felt some pretty hefty vibrations as the engine came apart.  </p>
<p>This has to do with the dynamics of structural vibration &#8212; bending modes, nodes, propagation, etc. &#8212; basically, there are points in the aircraft  where the vibratory waves cancel each other out and can&#8217;t be felt or multiply so they are very noticeable.  Where Joe sat he may not have felt any vibrations, but the pilots most likely did.  </p>
<p>Realize also that the pilots probably had numerous other indications of a problem, from gauges showing out-of-limit or fluctuating readings to warning lights and horns.  Some aircraft even have indicators that precisely show engine vibrations though I doubt a modern 737 has these.  </p>
<p>So, bottom line, for the pilots to say there were &#8220;vibrations&#8221; isn&#8217;t a lie.  There&#8217;s not an &#8220;engine exploded&#8221; light in the cockpit, and the safety report describes the indications the PILOTS had, not what the non-aviator passenger thinks they saw and felt.</p>
<p>Lastly, if the flight attendants were crying and hyperventilating they need to be counseled for a lack of  professional discipline.  The aircraft had a fairly major problem but the cockpit crew were handling it in accordance with the flght manual and company procedures.  Flight attendants are trained to remain calm so they can actually peform their duties, assist the pilots as necessary and take care of the passengers.  If they were getting hysterical it sounds like there may have been a breakdown in discipline.</p>
<p>One thing I would like to know from someone who was actually on the aircraft:  Did the Captain or First Officer walk back into the cabin inflight and look at the engine to survey the damage?</p>
<p>I hope this clears up many of the misconceptions and conjecture that this incident has generated.  No, I&#8217;m not a pilot for SWA, though I think they are a very good airline.  I am a USAF test pilot and have dozens of friends who fly for Southwest, and to the man they are some of the best,  most professional aviators I&#8217;ve ever known.  </p>
<p>Kudos to the two guys who got this jet back on the ground safely despite the &#8220;fatal engine failure&#8221;, tearful goodbyes and hyperventilating stewardesses.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: eddie</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9277</link>
		<author>eddie</author>
		<pubDate>Tue, 27 Nov 2007 20:03:54 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9277</guid>
					<description>RE: When you take pictures, you do not ASK PERMISSION to publish them.

I'm with you on that, buddy. I did a double take there, too, but then went back and read the post. But you missed the point. The pilot took the photos. The original poster asked the pilot to submit them so he could publish them, but other photos showed up online first.</description>
		<content:encoded><![CDATA[<p>RE: When you take pictures, you do not ASK PERMISSION to publish them.</p>
<p>I&#8217;m with you on that, buddy. I did a double take there, too, but then went back and read the post. But you missed the point. The pilot took the photos. The original poster asked the pilot to submit them so he could publish them, but other photos showed up online first.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: JETGURU</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9279</link>
		<author>JETGURU</author>
		<pubDate>Tue, 27 Nov 2007 20:18:09 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9279</guid>
					<description>Sorry Dude No Armor Plating on this aircraft.  If the blades would have penetrated the other way it would have ripped a hole in the fuselage and there would have been massive decompression and the plane would have probably went down.</description>
		<content:encoded><![CDATA[<p>Sorry Dude No Armor Plating on this aircraft.  If the blades would have penetrated the other way it would have ripped a hole in the fuselage and there would have been massive decompression and the plane would have probably went down.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Scramblejams</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9281</link>
		<author>Scramblejams</author>
		<pubDate>Tue, 27 Nov 2007 20:30:04 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9281</guid>
					<description>What a typical thread. 24 messages, only one comment (testpilot's) with a correct, detailed response.</description>
		<content:encoded><![CDATA[<p>What a typical thread. 24 messages, only one comment (testpilot&#8217;s) with a correct, detailed response.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Fatebringer</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9283</link>
		<author>Fatebringer</author>
		<pubDate>Tue, 27 Nov 2007 21:07:16 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9283</guid>
					<description>No, the plane would not have gone down even in the event of a rather large hole in the plane.

Airliners are amazingly redundant things, and the pilots have oxygen masks readily available for just such an emergency.

take a look at a similar (albeit older) 737 that survived a BIT of hole at 24k ft and made a safe landing (albeit with a few fewer people on board)

http://en.wikipedia.org/wiki/Aloha_Flight_243

Also in the case of the PNS engine failure (a DL MD-88) the cause was shoddy work on the blades done by a contractor overseas (pakistan?)</description>
		<content:encoded><![CDATA[<p>No, the plane would not have gone down even in the event of a rather large hole in the plane.</p>
<p>Airliners are amazingly redundant things, and the pilots have oxygen masks readily available for just such an emergency.</p>
<p>take a look at a similar (albeit older) 737 that survived a BIT of hole at 24k ft and made a safe landing (albeit with a few fewer people on board)</p>
<p><a href="http://en.wikipedia.org/wiki/Aloha_Flight_243" rel="nofollow">http://en.wikipedia.org/wiki/Aloha_Flight_243</a></p>
<p>Also in the case of the PNS engine failure (a DL MD-88) the cause was shoddy work on the blades done by a contractor overseas (pakistan?)</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Anglictina</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9285</link>
		<author>Anglictina</author>
		<pubDate>Tue, 27 Nov 2007 21:14:14 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9285</guid>
					<description>WOW, beautiful images.</description>
		<content:encoded><![CDATA[<p>WOW, beautiful images.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: turbineheat</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9286</link>
		<author>turbineheat</author>
		<pubDate>Tue, 27 Nov 2007 21:32:10 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9286</guid>
					<description>testpilot got this right. just about everyone else, wasting space here. incredible the amount of unhappy people out there nitpicking. important thing, nobody got hurt. now to see what caused the failure. for those not in the know, it is a mechanical device, which is prone to failure believe it or not. like testpilot said, this is an uncontained failure. lucky they went mostly away from the aircraft. i was an a &#38; p tech. this is not a blame game thing. and truly, not a very big deal. that is why the shroud around the engine is made very sturdy, just in case. these things will happen.</description>
		<content:encoded><![CDATA[<p>testpilot got this right. just about everyone else, wasting space here. incredible the amount of unhappy people out there nitpicking. important thing, nobody got hurt. now to see what caused the failure. for those not in the know, it is a mechanical device, which is prone to failure believe it or not. like testpilot said, this is an uncontained failure. lucky they went mostly away from the aircraft. i was an a &amp; p tech. this is not a blame game thing. and truly, not a very big deal. that is why the shroud around the engine is made very sturdy, just in case. these things will happen.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Markus Diersbock</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9287</link>
		<author>Markus Diersbock</author>
		<pubDate>Tue, 27 Nov 2007 21:33:46 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9287</guid>
					<description>It is easy to explain why some people would feel vibrations and some wouldn't.
It's the same reason people will feel turbulence and others won't.

The wings (with engines) act as a fulcrum in flight, much like the
middle of a see-saw.

People at the front and back of the plane will feel movement more acutely
than people near the wings -- just as you would sitting in the middle
of a see-saw.

Also, like ripples in a pond when you drop a stone, vibrations move outward,
and are felt greater at the ends.

Markus Diersbock</description>
		<content:encoded><![CDATA[<p>It is easy to explain why some people would feel vibrations and some wouldn&#8217;t.<br />
It&#8217;s the same reason people will feel turbulence and others won&#8217;t.</p>
<p>The wings (with engines) act as a fulcrum in flight, much like the<br />
middle of a see-saw.</p>
<p>People at the front and back of the plane will feel movement more acutely<br />
than people near the wings &#8212; just as you would sitting in the middle<br />
of a see-saw.</p>
<p>Also, like ripples in a pond when you drop a stone, vibrations move outward,<br />
and are felt greater at the ends.</p>
<p>Markus Diersbock</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Ex Boeing Engineer</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9292</link>
		<author>Ex Boeing Engineer</author>
		<pubDate>Tue, 27 Nov 2007 22:05:27 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9292</guid>
					<description>Just to correct a couple of errors in the postings above:

1) Boeing airliners are designed so that flight critical systems are not inline with the turbine blades. So, turbine blades flying out will not take out critical systems.

2) Turbine blades penetrating the fuselage will not cause explosive decompression. The pressurized cabin will not fail like a balloon does when punctured, Boeing has spent a great deal of effort prevent this problem. You'll probably hear a loud hissing sound and get a gradual decompression, and that's it.

3) Jet engines are highly stressed and full of energy. Thus, Boeing airliners are designed with the presumption that they will fail, so the plane must continue to fly safely. That's why there are two engines, and why they are on pylons, and why critical flight controls are not in the way of engine failure, etc.

4) This incident shows how well Boeing airliners are built, and the professionalism of the pilots. The airframe handled the mishap gracefully, continued to fly successfully, and the pilots did everything right and brought the airplane down safely with no injury or loss of life.</description>
		<content:encoded><![CDATA[<p>Just to correct a couple of errors in the postings above:</p>
<p>1) Boeing airliners are designed so that flight critical systems are not inline with the turbine blades. So, turbine blades flying out will not take out critical systems.</p>
<p>2) Turbine blades penetrating the fuselage will not cause explosive decompression. The pressurized cabin will not fail like a balloon does when punctured, Boeing has spent a great deal of effort prevent this problem. You&#8217;ll probably hear a loud hissing sound and get a gradual decompression, and that&#8217;s it.</p>
<p>3) Jet engines are highly stressed and full of energy. Thus, Boeing airliners are designed with the presumption that they will fail, so the plane must continue to fly safely. That&#8217;s why there are two engines, and why they are on pylons, and why critical flight controls are not in the way of engine failure, etc.</p>
<p>4) This incident shows how well Boeing airliners are built, and the professionalism of the pilots. The airframe handled the mishap gracefully, continued to fly successfully, and the pilots did everything right and brought the airplane down safely with no injury or loss of life.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: testpilot2</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9293</link>
		<author>testpilot2</author>
		<pubDate>Tue, 27 Nov 2007 22:32:33 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9293</guid>
					<description>Just one point to clarify on testpilot's otherwise spot-on disection of this event.  The 737NG (NG=next generation; that is, models 737-600, -700, -800, -900) have vibration indicators installed.  You can bet that if the fan or compressor lost a blade, the vibration gage would have shown it.  The engine may very well have kept running even with the damage sustained, in which case the pilots would reduce the power to the engine to reduce the vibration and shut it down if necessary.</description>
		<content:encoded><![CDATA[<p>Just one point to clarify on testpilot&#8217;s otherwise spot-on disection of this event.  The 737NG (NG=next generation; that is, models 737-600, -700, -800, -900) have vibration indicators installed.  You can bet that if the fan or compressor lost a blade, the vibration gage would have shown it.  The engine may very well have kept running even with the damage sustained, in which case the pilots would reduce the power to the engine to reduce the vibration and shut it down if necessary.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Meow</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9295</link>
		<author>Meow</author>
		<pubDate>Tue, 27 Nov 2007 22:37:43 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9295</guid>
					<description>"Mark 
Nov 27th, 2007 at 5:22 pm 
Let me explain it to you.

When you take pictures, you do not ASK PERMISSION to publish them.

That is what people do in mainland China. Not here in the US. In the US, we are a free country. You publish your pictures first, and let the FAA ask questions later. Not the other way around."



Who cares? I would take pictures THEN publish them. Big deal! pfffttt</description>
		<content:encoded><![CDATA[<p>&#8220;Mark<br />
Nov 27th, 2007 at 5:22 pm<br />
Let me explain it to you.</p>
<p>When you take pictures, you do not ASK PERMISSION to publish them.</p>
<p>That is what people do in mainland China. Not here in the US. In the US, we are a free country. You publish your pictures first, and let the FAA ask questions later. Not the other way around.&#8221;</p>
<p>Who cares? I would take pictures THEN publish them. Big deal! pfffttt</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Glenn</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9300</link>
		<author>Glenn</author>
		<pubDate>Tue, 27 Nov 2007 23:57:59 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9300</guid>
					<description>From FAR 14 CFR Part 33.94 Blade containment and rotor unbalance tests.  ...it must be demonstrated by engine tests that the engine is capable of containing damage without catching fire and without failure of its mounting attachments when operated for at least 15 seconds...after each of the following events:
(1) Failure of the most critical compressor or fan blade 
(2) Failure of the most critical turbine blade 

By this federal regulation, the engine performed properly.  It contained the damage, did not catch fire and obviously remained mounted.</description>
		<content:encoded><![CDATA[<p>From FAR 14 CFR Part 33.94 Blade containment and rotor unbalance tests.  &#8230;it must be demonstrated by engine tests that the engine is capable of containing damage without catching fire and without failure of its mounting attachments when operated for at least 15 seconds&#8230;after each of the following events:<br />
(1) Failure of the most critical compressor or fan blade<br />
(2) Failure of the most critical turbine blade </p>
<p>By this federal regulation, the engine performed properly.  It contained the damage, did not catch fire and obviously remained mounted.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Joe</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9302</link>
		<author>Joe</author>
		<pubDate>Wed, 28 Nov 2007 00:05:47 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9302</guid>
					<description>Neither the captain or the first officer came back to check out the engine, the just so happened to be another pilot for southwest was traveling on the plane with us. He is the one that checked out the engine.</description>
		<content:encoded><![CDATA[<p>Neither the captain or the first officer came back to check out the engine, the just so happened to be another pilot for southwest was traveling on the plane with us. He is the one that checked out the engine.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Bunky</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9304</link>
		<author>Bunky</author>
		<pubDate>Wed, 28 Nov 2007 00:09:33 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9304</guid>
					<description>Kudos to testpilot and Ex Boeing Engineer.

People like jetguru are grossly ignorant about what the capabilities of an airliner are. Their prognostications about the plane "going down" are simply incorrect.

For starters, the issues regarding the initial statement are simply incorrect. The statement linked is an FAA document stating only the basic event items. Plane departed, engine failed, plane returned. That is called an "incident report" and is simply a concise statement of what occured.To cast aspersions on Southwest for "trying to cover things up" is just plain stupid. In this litigious society, booger eating morons are regularly courted by shady attorneys who want to creat issues upon which to make money. This completely ignores the fact that the SWA crew did the right things and saved the day. I believe if you do some checking, SWA sends their engines off for repair/overhaul to FAA approved engine facilities. Blaming SWA simply flies in the face of reality.

As for decompression, Boeing has over-engineered every plane since the 707. When the 707 was being tested, they shot scores of steel daggers through the hull of a fully pressurized 707 immersed in a huge pool to demonstrate the failsafe nature of the airframe structure (dual loadpaths, just like a WWII bomber). The 737 is nearly identical to the 707 airframe and, in fact, still flies with the 707 nose that first flew nearly 60 years ago. Look at a KC-135 tanker nose if you don't believe me. Identical, except the radome.

To the credit of those who stated the obvious, an airliner is comprised of over a million parts, many of them under extremely high pressure. The engines typify this stress and the fan hub/compressor core takes the brunt of this stress. For the record, the initial failure appears to have been a fan failure, not the turbine section. (Notice in one of the pictures the entire fan and spinner are gone.) The fan is like the propeller and pulls the plane through the air. A fan failure is often followed by a compressor/turbine hot section failure as parts from the fan section are ingested into the engine taking out compressor blades and turbine blades until the engine is either damaged partially or rendered completely inoperative. That is why every airliner comes with at least another engine. One breaks, you go land and get another jet.

As for the flight attendant tears, please remember that they are people too. Some of them may have been on their first trip or first month of flying. Despite being air crew, they often have little understanding of airworthiness issues other than what they learn on the job over time. Their prime reason for being is to get your butt safely off the plane once it touches down. They have been well trained to do this and their training has been well documented time and again. In the seconds after an inflight event, the pilots are busy trying to ascertain what/where/why and trying to make sense of the instruments on the dash before them. To make matters worse, in a vibration event, often times it is very hard to read the instruments so drawing any quick conclusions is out of the question. The "prime directive" in aviation is "DO NOT ACT WITHOUT DELIBERATION BECAUSE IT MAY WORSEN YOUR SITUATION." While these pilots were trying to figure out what was going on, the flight attendants were on their own, awaiting info from the cockpit. If the passengers demand attention for their fear of imminent peril, the same consideration must be offered to the inflight crewmembers. A badge doesn't mean you are not human as well.

The facts speak for themselves. An unintended and possibly unavoidable incident occurred inflight. The company trained crewmembers did their job and recovered the aircraft safely to the ground and all passemgers were safely deplaned. What other outcome is preferable to this outcome? 

Additional note: I believe this aircraft was a 300 model. Only the "Classic" 737's have engine vibration indicators and in this type event, the severity of vibration on the failed engine may have pegged the opposing indicator. (The NG 737's have no vibe indicators.)

Engine failure in high-bypass turbo fans is incredibly rare when measured across the millions of hours jets fly each year. Uncontained engine failure is many magnitudes rarer yet. This track record is testimony to the safety and reliability offered by airline travel.

The Internet is a wonderful place to get information. Unfortunately, in the absence of factual data, mob rule often occurs. Hopefully, the readers of this blog are now more educated as to the events that occurred.</description>
		<content:encoded><![CDATA[<p>Kudos to testpilot and Ex Boeing Engineer.</p>
<p>People like jetguru are grossly ignorant about what the capabilities of an airliner are. Their prognostications about the plane &#8220;going down&#8221; are simply incorrect.</p>
<p>For starters, the issues regarding the initial statement are simply incorrect. The statement linked is an FAA document stating only the basic event items. Plane departed, engine failed, plane returned. That is called an &#8220;incident report&#8221; and is simply a concise statement of what occured.To cast aspersions on Southwest for &#8220;trying to cover things up&#8221; is just plain stupid. In this litigious society, booger eating morons are regularly courted by shady attorneys who want to creat issues upon which to make money. This completely ignores the fact that the SWA crew did the right things and saved the day. I believe if you do some checking, SWA sends their engines off for repair/overhaul to FAA approved engine facilities. Blaming SWA simply flies in the face of reality.</p>
<p>As for decompression, Boeing has over-engineered every plane since the 707. When the 707 was being tested, they shot scores of steel daggers through the hull of a fully pressurized 707 immersed in a huge pool to demonstrate the failsafe nature of the airframe structure (dual loadpaths, just like a WWII bomber). The 737 is nearly identical to the 707 airframe and, in fact, still flies with the 707 nose that first flew nearly 60 years ago. Look at a KC-135 tanker nose if you don&#8217;t believe me. Identical, except the radome.</p>
<p>To the credit of those who stated the obvious, an airliner is comprised of over a million parts, many of them under extremely high pressure. The engines typify this stress and the fan hub/compressor core takes the brunt of this stress. For the record, the initial failure appears to have been a fan failure, not the turbine section. (Notice in one of the pictures the entire fan and spinner are gone.) The fan is like the propeller and pulls the plane through the air. A fan failure is often followed by a compressor/turbine hot section failure as parts from the fan section are ingested into the engine taking out compressor blades and turbine blades until the engine is either damaged partially or rendered completely inoperative. That is why every airliner comes with at least another engine. One breaks, you go land and get another jet.</p>
<p>As for the flight attendant tears, please remember that they are people too. Some of them may have been on their first trip or first month of flying. Despite being air crew, they often have little understanding of airworthiness issues other than what they learn on the job over time. Their prime reason for being is to get your butt safely off the plane once it touches down. They have been well trained to do this and their training has been well documented time and again. In the seconds after an inflight event, the pilots are busy trying to ascertain what/where/why and trying to make sense of the instruments on the dash before them. To make matters worse, in a vibration event, often times it is very hard to read the instruments so drawing any quick conclusions is out of the question. The &#8220;prime directive&#8221; in aviation is &#8220;DO NOT ACT WITHOUT DELIBERATION BECAUSE IT MAY WORSEN YOUR SITUATION.&#8221; While these pilots were trying to figure out what was going on, the flight attendants were on their own, awaiting info from the cockpit. If the passengers demand attention for their fear of imminent peril, the same consideration must be offered to the inflight crewmembers. A badge doesn&#8217;t mean you are not human as well.</p>
<p>The facts speak for themselves. An unintended and possibly unavoidable incident occurred inflight. The company trained crewmembers did their job and recovered the aircraft safely to the ground and all passemgers were safely deplaned. What other outcome is preferable to this outcome? </p>
<p>Additional note: I believe this aircraft was a 300 model. Only the &#8220;Classic&#8221; 737&#8217;s have engine vibration indicators and in this type event, the severity of vibration on the failed engine may have pegged the opposing indicator. (The NG 737&#8217;s have no vibe indicators.)</p>
<p>Engine failure in high-bypass turbo fans is incredibly rare when measured across the millions of hours jets fly each year. Uncontained engine failure is many magnitudes rarer yet. This track record is testimony to the safety and reliability offered by airline travel.</p>
<p>The Internet is a wonderful place to get information. Unfortunately, in the absence of factual data, mob rule often occurs. Hopefully, the readers of this blog are now more educated as to the events that occurred.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Arik</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9323</link>
		<author>Arik</author>
		<pubDate>Wed, 28 Nov 2007 02:05:49 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9323</guid>
					<description>Just one thing,

If no one died, why did the post call it a "fatal engine failure"? Was there any fatality?

-- Arik</description>
		<content:encoded><![CDATA[<p>Just one thing,</p>
<p>If no one died, why did the post call it a &#8220;fatal engine failure&#8221;? Was there any fatality?</p>
<p>&#8211; Arik</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Andrew</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9330</link>
		<author>Andrew</author>
		<pubDate>Wed, 28 Nov 2007 03:37:27 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9330</guid>
					<description>@JETGURU

Airliner engines are most certainly "armoured" against potential blade failures. Should any blade in the engine fail and break off, the casing of the engine is specifically designed to safely contain the huge amount of energy released and prevent any debris from hitting the fuselage or wing.

This video demonstrates blade-off testing for the A380's engines.

http://www.youtube.com/watch?v=j973645y5AA</description>
		<content:encoded><![CDATA[<p>@JETGURU</p>
<p>Airliner engines are most certainly &#8220;armoured&#8221; against potential blade failures. Should any blade in the engine fail and break off, the casing of the engine is specifically designed to safely contain the huge amount of energy released and prevent any debris from hitting the fuselage or wing.</p>
<p>This video demonstrates blade-off testing for the A380&#8217;s engines.</p>
<p><a href="http://www.youtube.com/watch?v=j973645y5AA" rel="nofollow">http://www.youtube.com/watch?v=j973645y5AA</a></p>
]]></content:encoded>
				</item>
	<item>
		<title>By: testpilot</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9335</link>
		<author>testpilot</author>
		<pubDate>Wed, 28 Nov 2007 04:01:02 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9335</guid>
					<description>Thanks, Joe, I was just curious if the captain and FO had a trained eye look at the engine while they were up front running checklists and heading back to the airport.  Did the pilot who was in the back relay his findings to the cockpit?</description>
		<content:encoded><![CDATA[<p>Thanks, Joe, I was just curious if the captain and FO had a trained eye look at the engine while they were up front running checklists and heading back to the airport.  Did the pilot who was in the back relay his findings to the cockpit?</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: vanity smurf</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9336</link>
		<author>vanity smurf</author>
		<pubDate>Wed, 28 Nov 2007 04:11:43 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9336</guid>
					<description>i believe in the giblet. kc is a genius sent here to destroy us.

why not do it?</description>
		<content:encoded><![CDATA[<p>i believe in the giblet. kc is a genius sent here to destroy us.</p>
<p>why not do it?</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Male Flight Attendant</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9339</link>
		<author>Male Flight Attendant</author>
		<pubDate>Wed, 28 Nov 2007 04:17:09 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9339</guid>
					<description>"STEWARDESSES" Testpilot, c'mon. That is so last generation and UN-PC...  And with regard to hyperventilating, we are trained that if there is suspected pressurization issues, take oxygen, immediately. 

Care to comment on the time of useful consciousness in rapid decompression, let me help you here... It would be as little as six seconds at altitude.

She should have and seems that she did strap on the oxygen tank. In a situation such as this, better to error on the side of caution. I know that I would not want to be without oxygen in a rapid decompression, for if I was, all the passengers would have much more to worry about than grammar and spelling errors.

Generally, your post was spot on and seemingly professionally sound, you just lost my vote with your careless use of the outdated word, "stewardess" and your uninformed assumption that the flight attendants would be fired.

Typical after the fact, arm chair quarterbacking at its best.</description>
		<content:encoded><![CDATA[<p>&#8220;STEWARDESSES&#8221; Testpilot, c&#8217;mon. That is so last generation and UN-PC&#8230;  And with regard to hyperventilating, we are trained that if there is suspected pressurization issues, take oxygen, immediately. </p>
<p>Care to comment on the time of useful consciousness in rapid decompression, let me help you here&#8230; It would be as little as six seconds at altitude.</p>
<p>She should have and seems that she did strap on the oxygen tank. In a situation such as this, better to error on the side of caution. I know that I would not want to be without oxygen in a rapid decompression, for if I was, all the passengers would have much more to worry about than grammar and spelling errors.</p>
<p>Generally, your post was spot on and seemingly professionally sound, you just lost my vote with your careless use of the outdated word, &#8220;stewardess&#8221; and your uninformed assumption that the flight attendants would be fired.</p>
<p>Typical after the fact, arm chair quarterbacking at its best.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Future 737 pilot</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9343</link>
		<author>Future 737 pilot</author>
		<pubDate>Wed, 28 Nov 2007 04:39:57 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9343</guid>
					<description>From someone studying for a 737 type rating:

JetGuru is completely wrong when he speculates of all the ways the airplane would have broken apart, become uncontrollable, crashed, etc.  I can't imagine what his motivation is.

Testpilot and the Ex-Boeing engineer have it completely correct.  Let's review the systems and design features in place to protect the passengers in the event of an engine problem.

First - the airplane is designed to fly on one engine, maintain cabin pressurization with only one engine operating, and provide adequate electrical and hydraulic power with only one engine operating.  There's also an Auxiliary Power Unit (APU), a small jet engine in the back of the airplane that can be operated to provide additional electrical and bleed air energy.  The worst case is that a fully loaded 737 might have to descend somewhat from it's normal cruise altitude of 33000-41000 feet when operating on a single engine, but you can believe that for any domestic operation an engine failure calls for a descent and landing at the nearest suitable airport anyway.

Second - There are no critical flight components in the ejection plane of the engine fan or compressor stages.  This ensures that if a blade separates, and the energy is not fully contained within the kevlar belts lining the cowling and the cowling itself, that any penetration of the wing structure or fuselage (I believe the fuse does have some additional kevlar in it) will be minor and absorbable, and leave the airplane fully controllable.  Additionally, the pylons the engine is mounted on are designed to protect the wing by failing first and separating the engine from the wing if sufficient stress is placed on them.  

Third - You may not be aware that an pressurized airplane is not actually completely sealed.  Pressurized Air (called bleed air)from the engines is pumped into the aircraft after being cooled, and it flows out through an adjustable outflow valve in the fuselage.  The pressurization comes from the difference in the amount of air pumped in (lots) and the amount of air allowed to exit through the outflow (less, but NOT zero).   If the cabin were to spring a small leak (say the size of your fist), the outflow valve would simply close a bit to compensate, and it would be noisy by the hole, but pressure would probably still be adequate to not require supplemental oxygen.  Only if structural maintenance were terribly deficient (as in the case of ?Aloha?) would there be a chance of significant skin loss and depressurization, and even in that case the airplane landed safely.

Bottom line, an engine failure of this type is something the designers anticipated, designed for, TESTED their designs, and the FAA certified the design as being safe.  You have a better chance of winning the lottery then you do of dying in a plane crash due to a design defect in the aircraft or engine.  Most plane crashes are a result of pilot error (sad but true), or in rare cases terribly gross negligence on the part of the maintenance staff or ATC, or deliberate sabotage/terrorism.</description>
		<content:encoded><![CDATA[<p>From someone studying for a 737 type rating:</p>
<p>JetGuru is completely wrong when he speculates of all the ways the airplane would have broken apart, become uncontrollable, crashed, etc.  I can&#8217;t imagine what his motivation is.</p>
<p>Testpilot and the Ex-Boeing engineer have it completely correct.  Let&#8217;s review the systems and design features in place to protect the passengers in the event of an engine problem.</p>
<p>First - the airplane is designed to fly on one engine, maintain cabin pressurization with only one engine operating, and provide adequate electrical and hydraulic power with only one engine operating.  There&#8217;s also an Auxiliary Power Unit (APU), a small jet engine in the back of the airplane that can be operated to provide additional electrical and bleed air energy.  The worst case is that a fully loaded 737 might have to descend somewhat from it&#8217;s normal cruise altitude of 33000-41000 feet when operating on a single engine, but you can believe that for any domestic operation an engine failure calls for a descent and landing at the nearest suitable airport anyway.</p>
<p>Second - There are no critical flight components in the ejection plane of the engine fan or compressor stages.  This ensures that if a blade separates, and the energy is not fully contained within the kevlar belts lining the cowling and the cowling itself, that any penetration of the wing structure or fuselage (I believe the fuse does have some additional kevlar in it) will be minor and absorbable, and leave the airplane fully controllable.  Additionally, the pylons the engine is mounted on are designed to protect the wing by failing first and separating the engine from the wing if sufficient stress is placed on them.  </p>
<p>Third - You may not be aware that an pressurized airplane is not actually completely sealed.  Pressurized Air (called bleed air)from the engines is pumped into the aircraft after being cooled, and it flows out through an adjustable outflow valve in the fuselage.  The pressurization comes from the difference in the amount of air pumped in (lots) and the amount of air allowed to exit through the outflow (less, but NOT zero).   If the cabin were to spring a small leak (say the size of your fist), the outflow valve would simply close a bit to compensate, and it would be noisy by the hole, but pressure would probably still be adequate to not require supplemental oxygen.  Only if structural maintenance were terribly deficient (as in the case of ?Aloha?) would there be a chance of significant skin loss and depressurization, and even in that case the airplane landed safely.</p>
<p>Bottom line, an engine failure of this type is something the designers anticipated, designed for, TESTED their designs, and the FAA certified the design as being safe.  You have a better chance of winning the lottery then you do of dying in a plane crash due to a design defect in the aircraft or engine.  Most plane crashes are a result of pilot error (sad but true), or in rare cases terribly gross negligence on the part of the maintenance staff or ATC, or deliberate sabotage/terrorism.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Paul</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9346</link>
		<author>Paul</author>
		<pubDate>Wed, 28 Nov 2007 05:01:33 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9346</guid>
					<description>One of the spinner bolts is missing (or at least the bolt head is missing) and would have been injested (wacked by several fan blades). Damage that resulted from this spinner bolt impacting one or more fan blades may have eventually caused a crack that propogated until the blade failed which then caused this catastrophic, uncontained failure.</description>
		<content:encoded><![CDATA[<p>One of the spinner bolts is missing (or at least the bolt head is missing) and would have been injested (wacked by several fan blades). Damage that resulted from this spinner bolt impacting one or more fan blades may have eventually caused a crack that propogated until the blade failed which then caused this catastrophic, uncontained failure.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Mensajero</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9350</link>
		<author>Mensajero</author>
		<pubDate>Wed, 28 Nov 2007 05:59:02 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9350</guid>
					<description>Testpilot, you are my hero.</description>
		<content:encoded><![CDATA[<p>Testpilot, you are my hero.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Paul</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9357</link>
		<author>Paul</author>
		<pubDate>Wed, 28 Nov 2007 06:47:15 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9357</guid>
					<description>This is an exceptionally rare failure (ignoring whatever the actual root cause) because of the amount of damage. Most of the time when the fan sustains heavy damage (even from a large bird strike for example) you usually don't see this kind of damage. The fan blade containment is the engine outer fan case (not any of the cowls), but because of the amount of "shrapnel" in this case, some of it came out either in front of, or aft, of the fan blade containment section of the outer fan case. There is heavy fan case damage at 6 o'clock inline with the blade tips though. It was not designed to withstand quite this much, or kind of damage. The engine is certified to withstand a failure of one whole fan blade at Take-off Power and to be safely shutdown, mind you. Vibration monitoring is of no value in this case. The failure was I'm quite sure, instantaneous, very violent, recognized by the crew who would have immediately shutdown the engine. I had a look (a zoom) of another one of the fan photos and it sure does look like that one spinner attach bolt is completely gone.</description>
		<content:encoded><![CDATA[<p>This is an exceptionally rare failure (ignoring whatever the actual root cause) because of the amount of damage. Most of the time when the fan sustains heavy damage (even from a large bird strike for example) you usually don&#8217;t see this kind of damage. The fan blade containment is the engine outer fan case (not any of the cowls), but because of the amount of &#8220;shrapnel&#8221; in this case, some of it came out either in front of, or aft, of the fan blade containment section of the outer fan case. There is heavy fan case damage at 6 o&#8217;clock inline with the blade tips though. It was not designed to withstand quite this much, or kind of damage. The engine is certified to withstand a failure of one whole fan blade at Take-off Power and to be safely shutdown, mind you. Vibration monitoring is of no value in this case. The failure was I&#8217;m quite sure, instantaneous, very violent, recognized by the crew who would have immediately shutdown the engine. I had a look (a zoom) of another one of the fan photos and it sure does look like that one spinner attach bolt is completely gone.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: mattbna</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9361</link>
		<author>mattbna</author>
		<pubDate>Wed, 28 Nov 2007 07:20:10 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9361</guid>
					<description>testpilot: According to a report filed by one of the F/As, there were 3 WN pilots that were flying non-rev on this flight and one of them called the cockpit from the interphone in the rear galley and informed the cockpit of what was going on with the engine.  This same non-rev pilot entered the cockpit and was in the jump seat for the landing.

testpilot2: This particular aircraft was a -300 - no dice on the vibration indicator unless they were available on the earlier models.

It absolutely cracks me up to come in here and read all of these comments from people that know ABSOLUTELY NOTHING about aircraft!  Thanks for providing me some entertainment this evening.  (Obviously that wasn't directed at the last few folks that have posted and actually know what they are taking about!)


Matt
My photos on Airliners.net: http://tinyurl.com/u4vro

--</description>
		<content:encoded><![CDATA[<p>testpilot: According to a report filed by one of the F/As, there were 3 WN pilots that were flying non-rev on this flight and one of them called the cockpit from the interphone in the rear galley and informed the cockpit of what was going on with the engine.  This same non-rev pilot entered the cockpit and was in the jump seat for the landing.</p>
<p>testpilot2: This particular aircraft was a -300 - no dice on the vibration indicator unless they were available on the earlier models.</p>
<p>It absolutely cracks me up to come in here and read all of these comments from people that know ABSOLUTELY NOTHING about aircraft!  Thanks for providing me some entertainment this evening.  (Obviously that wasn&#8217;t directed at the last few folks that have posted and actually know what they are taking about!)</p>
<p>Matt<br />
My photos on Airliners.net: <a href="http://tinyurl.com/u4vro" rel="nofollow">http://tinyurl.com/u4vro</a></p>
<p>&#8211;</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: SWAspirit1</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9367</link>
		<author>SWAspirit1</author>
		<pubDate>Wed, 28 Nov 2007 07:50:00 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9367</guid>
					<description>I just want to thank the Test pilots and the Boeing representative on here by clarifying all of the details of what a Boeing 737 really is all about....Guess thats why we fly them! And yes our pilots are very highly trained individuals and some of our pilots are even retired astronauts and even retired Air Force One pilots...yeah guess I'm bragging, but I am proud to work with some of the finest pilots out there....And for those of you who do not know, don't know! So...until you know, you really have no room to talk. 

If I'm correct, our 300 and 500 series also have the vibration gauge. I think it's located where the N1, N2, and the oil temp gauges are right directly in front of the throttles on the panel under the dash...Boeing am I correct?  and for the civilians out there that thinks I'm a fool because I dont know where something is in the cockpit..it is because I work in Ground Operations, but possess    a Private Pilots Certificate. Also...this armor plating you guys talk about..is really not what you think..its not metal...its Kevlar.. and theres alot of it in the engine where the blades turn. when you see a plane land and they engage the Thrust Reverser's, you can see a green color inside the cowling....thats all Kevlar. There was a program on the Discovery Channel on a/c engines and they had an engine intentionally lose the blades and all you saw was the cowling bow up like a flexed bicep...it was really neat...Boeing or Test can you vouch?</description>
		<content:encoded><![CDATA[<p>I just want to thank the Test pilots and the Boeing representative on here by clarifying all of the details of what a Boeing 737 really is all about&#8230;.Guess thats why we fly them! And yes our pilots are very highly trained individuals and some of our pilots are even retired astronauts and even retired Air Force One pilots&#8230;yeah guess I&#8217;m bragging, but I am proud to work with some of the finest pilots out there&#8230;.And for those of you who do not know, don&#8217;t know! So&#8230;until you know, you really have no room to talk. </p>
<p>If I&#8217;m correct, our 300 and 500 series also have the vibration gauge. I think it&#8217;s located where the N1, N2, and the oil temp gauges are right directly in front of the throttles on the panel under the dash&#8230;Boeing am I correct?  and for the civilians out there that thinks I&#8217;m a fool because I dont know where something is in the cockpit..it is because I work in Ground Operations, but possess    a Private Pilots Certificate. Also&#8230;this armor plating you guys talk about..is really not what you think..its not metal&#8230;its Kevlar.. and theres alot of it in the engine where the blades turn. when you see a plane land and they engage the Thrust Reverser&#8217;s, you can see a green color inside the cowling&#8230;.thats all Kevlar. There was a program on the Discovery Channel on a/c engines and they had an engine intentionally lose the blades and all you saw was the cowling bow up like a flexed bicep&#8230;it was really neat&#8230;Boeing or Test can you vouch?</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Andy</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9370</link>
		<author>Andy</author>
		<pubDate>Wed, 28 Nov 2007 08:28:58 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9370</guid>
					<description>I suppose Mr. KC works for southwest, no?</description>
		<content:encoded><![CDATA[<p>I suppose Mr. KC works for southwest, no?</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Paul</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9376</link>
		<author>Paul</author>
		<pubDate>Wed, 28 Nov 2007 09:01:32 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9376</guid>
					<description>With the one missing spinner attach bolt, one has to wonder if some or all of the rest of them were ever torqued and could this be the cause of the spinner "departing" and wiping out the fan. It appears that at all or most of the remaining spinner bolts there is a broken remnant of the spinner attach flange still under the head of the bolt. Improperly torqued bolts could cause unequal loads being applied at the bolt hole locations of the flange leading to cracking and subsequent flange failure.</description>
		<content:encoded><![CDATA[<p>With the one missing spinner attach bolt, one has to wonder if some or all of the rest of them were ever torqued and could this be the cause of the spinner &#8220;departing&#8221; and wiping out the fan. It appears that at all or most of the remaining spinner bolts there is a broken remnant of the spinner attach flange still under the head of the bolt. Improperly torqued bolts could cause unequal loads being applied at the bolt hole locations of the flange leading to cracking and subsequent flange failure.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: cw737</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9379</link>
		<author>cw737</author>
		<pubDate>Wed, 28 Nov 2007 09:10:23 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9379</guid>
					<description>To testpilot, testpilot2, ex boeing engineer, turbineheat, and a few of the others who obviously have a handle on the subject matter - good job.  To testpilot:  there were actually four company pilots in the back of the plane and, yes, they did report their findings to the cockpit through the intercom system as one would expect.  To testpilot2:  you are correct as to the presence of vibration indicators on the NGs.  There are vibration gauges on the Classic fleet as well - the 
-300,400,500 series. The -200s we used to fly had no vibration gauges.  To the others out there: don't let your emotions get the best of you.  Southwest is not trying to cover anything up.  Together, the NTSB, FAA and Southwest will do a thorough investigation to determine what caused the failure and publish their findings when the investigation is complete.  To the captain of the Southwest flight (who I know personally, but will not mention his name):  Great job!</description>
		<content:encoded><![CDATA[<p>To testpilot, testpilot2, ex boeing engineer, turbineheat, and a few of the others who obviously have a handle on the subject matter - good job.  To testpilot:  there were actually four company pilots in the back of the plane and, yes, they did report their findings to the cockpit through the intercom system as one would expect.  To testpilot2:  you are correct as to the presence of vibration indicators on the NGs.  There are vibration gauges on the Classic fleet as well - the<br />
-300,400,500 series. The -200s we used to fly had no vibration gauges.  To the others out there: don&#8217;t let your emotions get the best of you.  Southwest is not trying to cover anything up.  Together, the NTSB, FAA and Southwest will do a thorough investigation to determine what caused the failure and publish their findings when the investigation is complete.  To the captain of the Southwest flight (who I know personally, but will not mention his name):  Great job!</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Bunky</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9398</link>
		<author>Bunky</author>
		<pubDate>Wed, 28 Nov 2007 11:43:51 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9398</guid>
					<description>Correction: In one of the pictures above you can see a portion of the fan assembly still attached. Initial pictures I saw (grainy cell phone shots) made the engine look like it was stator blades alone -minus fan.

Additional note: Once the NTSB gets the incident, SWA CANNOT make any comments about the incident. The NTSB makes ALL statements about what did and didn't happen. Their comments will come as the investigation continues. The holidays throw a wrench in the usual timing but, assuming they have a good idea and testing verifies the damage pattern, we should have some official report out in 60-90 days.</description>
		<content:encoded><![CDATA[<p>Correction: In one of the pictures above you can see a portion of the fan assembly still attached. Initial pictures I saw (grainy cell phone shots) made the engine look like it was stator blades alone -minus fan.</p>
<p>Additional note: Once the NTSB gets the incident, SWA CANNOT make any comments about the incident. The NTSB makes ALL statements about what did and didn&#8217;t happen. Their comments will come as the investigation continues. The holidays throw a wrench in the usual timing but, assuming they have a good idea and testing verifies the damage pattern, we should have some official report out in 60-90 days.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: 737LUVR</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9408</link>
		<author>737LUVR</author>
		<pubDate>Wed, 28 Nov 2007 13:55:47 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9408</guid>
					<description>"""evgen 
Nov 27th, 2007 at 6:55 pm 
So a engine fan came apart… big deal. Let’s review the facts here. An engine that spins large metal blades at thousands of revolutions per minute eventually came apart. The fan blades were contained by the engine structure and safely ejected from the now non-operative engine. When something like this happens the pilots will feel a vibration and then the engine failure warnings will start (including things like fail-safe engine fire warnings, etc.) Since you cannot even see the engines from the cockpit of a 737 the pilots would report the vibration and engine failure to ATC and begin emergency procedures. While one pilot was working on making sure the plane did not crash the other would be working the engine shutdown and fire suppression checklist. Frankly these guys have better things to do than calm down passengers (that is the flight attendants job and it sounds like they were the only ones to screw-up here.)

There was no “cover up” and I am certain that if you dig through the FAA web site you will find the actual report that details both what the pilots thought was happening and the report from the ground that lists the actual damage.

Get a grip people."""


Thank you, Evgen.  I was hoping someone with a brain would post a reply.  It is quite obvious that the F/A's were the only ones who screwed up... the pilots safely got the plane on the ground as trained. Hopefully Herb will give them a fat Christmas Bonus.

Southwest has one of the best MX crew in the world, but sometimes you just can't tell when things like this will happen.  When they do, you just have to count on a good Boeing airframe to get you down in one piece.

Turbofans are a very complex (and beautifully engineered) piece of equipment, and are designed with saftey in mind.  The reason none of the blades passed through the inner wall is because a layer of protective 'armor' (designed specifically for this purpose) is placed between the moving engine parts and the passenger cabin.  

I would certainly say it was not a birdstrike, as most commercial turbofans are required to 'swallow' a large bird in testing without a major failure.</description>
		<content:encoded><![CDATA[<p>&#8220;&#8221;"evgen<br />
Nov 27th, 2007 at 6:55 pm<br />
So a engine fan came apart… big deal. Let’s review the facts here. An engine that spins large metal blades at thousands of revolutions per minute eventually came apart. The fan blades were contained by the engine structure and safely ejected from the now non-operative engine. When something like this happens the pilots will feel a vibration and then the engine failure warnings will start (including things like fail-safe engine fire warnings, etc.) Since you cannot even see the engines from the cockpit of a 737 the pilots would report the vibration and engine failure to ATC and begin emergency procedures. While one pilot was working on making sure the plane did not crash the other would be working the engine shutdown and fire suppression checklist. Frankly these guys have better things to do than calm down passengers (that is the flight attendants job and it sounds like they were the only ones to screw-up here.)</p>
<p>There was no “cover up” and I am certain that if you dig through the FAA web site you will find the actual report that details both what the pilots thought was happening and the report from the ground that lists the actual damage.</p>
<p>Get a grip people.&#8221;"&#8221;</p>
<p>Thank you, Evgen.  I was hoping someone with a brain would post a reply.  It is quite obvious that the F/A&#8217;s were the only ones who screwed up&#8230; the pilots safely got the plane on the ground as trained. Hopefully Herb will give them a fat Christmas Bonus.</p>
<p>Southwest has one of the best MX crew in the world, but sometimes you just can&#8217;t tell when things like this will happen.  When they do, you just have to count on a good Boeing airframe to get you down in one piece.</p>
<p>Turbofans are a very complex (and beautifully engineered) piece of equipment, and are designed with saftey in mind.  The reason none of the blades passed through the inner wall is because a layer of protective &#8216;armor&#8217; (designed specifically for this purpose) is placed between the moving engine parts and the passenger cabin.  </p>
<p>I would certainly say it was not a birdstrike, as most commercial turbofans are required to &#8217;swallow&#8217; a large bird in testing without a major failure.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Embraer 145 Person</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9409</link>
		<author>Embraer 145 Person</author>
		<pubDate>Wed, 28 Nov 2007 14:15:35 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9409</guid>
					<description>I think it would be unwise for a pilot to get out of the cockpit to check on an engine from the cabin. All indications and controls are in the cockpit. From n1 and n2 speeds it is possible to determine whether the engine is developing thrust. Abnormal engine vibration, fuel flow, or temperature can be indications of failure. Activated fire detection loops indicate fire while a detection loop failure in conjunction with other failures likely means something flew apart and/or is on fire. When an engine is out there may be no urgent need to secure it by closing fuel valves, bleed air lines, or hydraulics lines but something should be done in a timely manner due to competent decision making - either try to restart it or secure it and land. When the affected engine is secured the main focus should be to land, not look at the engine. What is the point of looking from the cabin when there are several separate systems telling you something is wrong. Furthermore, a decompression might follow a rotor burst since the pressure vessel may have been weakened critically due to impinging debris and leaving the cockpit means leaving the quick don O2. Both pilots are needed in the cockpit. One runs checklists and enlists the help of air traffic control, the other flies. Both pilots watch and listen to what the other is doing to detect errors. The Captain sets the pace and delegates. I know nothing about a 737 but I do have experience flying an Embraer 145 in passenger service. On my airplane it is impossible to see much of anything except the engine inlet from the cabin.</description>
		<content:encoded><![CDATA[<p>I think it would be unwise for a pilot to get out of the cockpit to check on an engine from the cabin. All indications and controls are in the cockpit. From n1 and n2 speeds it is possible to determine whether the engine is developing thrust. Abnormal engine vibration, fuel flow, or temperature can be indications of failure. Activated fire detection loops indicate fire while a detection loop failure in conjunction with other failures likely means something flew apart and/or is on fire. When an engine is out there may be no urgent need to secure it by closing fuel valves, bleed air lines, or hydraulics lines but something should be done in a timely manner due to competent decision making - either try to restart it or secure it and land. When the affected engine is secured the main focus should be to land, not look at the engine. What is the point of looking from the cabin when there are several separate systems telling you something is wrong. Furthermore, a decompression might follow a rotor burst since the pressure vessel may have been weakened critically due to impinging debris and leaving the cockpit means leaving the quick don O2. Both pilots are needed in the cockpit. One runs checklists and enlists the help of air traffic control, the other flies. Both pilots watch and listen to what the other is doing to detect errors. The Captain sets the pace and delegates. I know nothing about a 737 but I do have experience flying an Embraer 145 in passenger service. On my airplane it is impossible to see much of anything except the engine inlet from the cabin.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: 737pilot</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9412</link>
		<author>737pilot</author>
		<pubDate>Wed, 28 Nov 2007 15:05:52 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9412</guid>
					<description>About 5 of you know what your talking about.  The crew did a supurb job. This was a very serious engine failure and it was handled textbook. Kudos to the SWA pilots and Flight Attendants!!!!</description>
		<content:encoded><![CDATA[<p>About 5 of you know what your talking about.  The crew did a supurb job. This was a very serious engine failure and it was handled textbook. Kudos to the SWA pilots and Flight Attendants!!!!</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: swaguy</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9419</link>
		<author>swaguy</author>
		<pubDate>Wed, 28 Nov 2007 15:45:27 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9419</guid>
					<description>1. There is no way for a pilot in the 737 to determine that it was an "explosion" or "uncontained" engine failure. In this case it appears the vibration gauge for the engine went off scale high and the engine then failed. That is why the report references "vibration" and is in no way hiding anything.

2. The pilots of this aircraft were fully busy flying the airplane on a single engine and did not need to leave the cockpit in flight to see the damage as (1) there was nothing they could do to fix it at that point and (2) they had SWA pilots in the cabin giving them reports about what they saw.

3. Early FAA reports are nearly always a broad stroke description meant only to start the reporting process, you can be sure the final document will include full details of the failure and an accurate description of the event. This is IN no way a cover up of anything.

4. Blaming this on SWA maintenance is extremely premature. Losing and engine blade is actually a very common event but it is true that having the blade come through the casing is rare. Why this all happened is yet to be determined.</description>
		<content:encoded><![CDATA[<p>1. There is no way for a pilot in the 737 to determine that it was an &#8220;explosion&#8221; or &#8220;uncontained&#8221; engine failure. In this case it appears the vibration gauge for the engine went off scale high and the engine then failed. That is why the report references &#8220;vibration&#8221; and is in no way hiding anything.</p>
<p>2. The pilots of this aircraft were fully busy flying the airplane on a single engine and did not need to leave the cockpit in flight to see the damage as (1) there was nothing they could do to fix it at that point and (2) they had SWA pilots in the cabin giving them reports about what they saw.</p>
<p>3. Early FAA reports are nearly always a broad stroke description meant only to start the reporting process, you can be sure the final document will include full details of the failure and an accurate description of the event. This is IN no way a cover up of anything.</p>
<p>4. Blaming this on SWA maintenance is extremely premature. Losing and engine blade is actually a very common event but it is true that having the blade come through the casing is rare. Why this all happened is yet to be determined.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: TECHDUDE</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9428</link>
		<author>TECHDUDE</author>
		<pubDate>Wed, 28 Nov 2007 16:41:48 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9428</guid>
					<description>It is simply amazing the number of blithering idiots that come out and offer utterly stupid commentaries on subjects that are well above their stupid little heads.  Except for the entertainment factor, they absolutely have zero credibility.  Probably the same dummies that think the World Trade Center was a controlled explosion.</description>
		<content:encoded><![CDATA[<p>It is simply amazing the number of blithering idiots that come out and offer utterly stupid commentaries on subjects that are well above their stupid little heads.  Except for the entertainment factor, they absolutely have zero credibility.  Probably the same dummies that think the World Trade Center was a controlled explosion.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: sunspot baby</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9431</link>
		<author>sunspot baby</author>
		<pubDate>Wed, 28 Nov 2007 17:07:12 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9431</guid>
					<description>So a engine fan came apart… big deal. Let’s review the facts here. An engine that spins large metal blades at thousands of revolutions per minute eventually came apart. The fan blades were contained by the engine structure and safely ejected from the now non-operative engine. When something like this happens the pilots will feel a vibration and then the engine failure warnings will start (including things like fail-safe engine fire warnings, etc.) Since you cannot even see the engines from the cockpit of a 737 the pilots would report the vibration and engine failure to ATC and begin emergency procedures. While one pilot was working on making sure the plane did not crash the other would be working the engine shutdown and fire suppression checklist. Frankly these guys have better things to do than calm down passengers (that is the flight attendants job and it sounds like they were the only ones to screw-up here.)

There was no “cover up” and I am certain that if you dig through the FAA web site you will find the actual report that details both what the pilots thought was happening and the report from the ground that lists the actual damage.

Get a grip people.
--------------------------------------------------------------------------
Well said Evgen, well said</description>
		<content:encoded><![CDATA[<p>So a engine fan came apart… big deal. Let’s review the facts here. An engine that spins large metal blades at thousands of revolutions per minute eventually came apart. The fan blades were contained by the engine structure and safely ejected from the now non-operative engine. When something like this happens the pilots will feel a vibration and then the engine failure warnings will start (including things like fail-safe engine fire warnings, etc.) Since you cannot even see the engines from the cockpit of a 737 the pilots would report the vibration and engine failure to ATC and begin emergency procedures. While one pilot was working on making sure the plane did not crash the other would be working the engine shutdown and fire suppression checklist. Frankly these guys have better things to do than calm down passengers (that is the flight attendants job and it sounds like they were the only ones to screw-up here.)</p>
<p>There was no “cover up” and I am certain that if you dig through the FAA web site you will find the actual report that details both what the pilots thought was happening and the report from the ground that lists the actual damage.</p>
<p>Get a grip people.<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;<br />
Well said Evgen, well said</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: M</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9445</link>
		<author>M</author>
		<pubDate>Wed, 28 Nov 2007 20:47:57 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9445</guid>
					<description>I am a Southwest pilot. I just want to thanks you for posting the photos.</description>
		<content:encoded><![CDATA[<p>I am a Southwest pilot. I just want to thanks you for posting the photos.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Paul</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9453</link>
		<author>Paul</author>
		<pubDate>Wed, 28 Nov 2007 21:27:05 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9453</guid>
					<description>Lets get one thing clear here......any kind of rotor failure including blade failure, wether it be fan, compressor or turbine does happen but it is "not common" and it is NOT normally inherent because of......the basic engine design, or the time or cycles on the engine. It is not just destined to happen. I worked for a company that had operated this engine and two other similar versions for 19 yrs. when I retired, and I can't recall any fan/booster or compressor blade failures. Rotor/blade failure of any kind, even if it only initially causes an inflight shutdown is still a very expensive event for the company/owners/insurers and it always causes concern (initially for the passengers and crew of course) and then for the company, the aircraft manufacturer and particularly the engine manufacturer and the FAA. It can literally cost millions of dollars in engine repairs. This engine is worth about $6 mill. US, give or take. Don't kid youself.......it is considered a very serious event. This one was worse being uncontained and it wasn't just your basic fan blade failure by the look of it.</description>
		<content:encoded><![CDATA[<p>Lets get one thing clear here&#8230;&#8230;any kind of rotor failure including blade failure, wether it be fan, compressor or turbine does happen but it is &#8220;not common&#8221; and it is NOT normally inherent because of&#8230;&#8230;the basic engine design, or the time or cycles on the engine. It is not just destined to happen. I worked for a company that had operated this engine and two other similar versions for 19 yrs. when I retired, and I can&#8217;t recall any fan/booster or compressor blade failures. Rotor/blade failure of any kind, even if it only initially causes an inflight shutdown is still a very expensive event for the company/owners/insurers and it always causes concern (initially for the passengers and crew of course) and then for the company, the aircraft manufacturer and particularly the engine manufacturer and the FAA. It can literally cost millions of dollars in engine repairs. This engine is worth about $6 mill. US, give or take. Don&#8217;t kid youself&#8230;&#8230;.it is considered a very serious event. This one was worse being uncontained and it wasn&#8217;t just your basic fan blade failure by the look of it.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: PlatinumRRMember</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9463</link>
		<author>PlatinumRRMember</author>
		<pubDate>Wed, 28 Nov 2007 22:31:55 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9463</guid>
					<description>GEEZ, I wish you people would read all of the posts before jumping down and putting in your two-cents worth.  Only a few of you had something intelligent to say, particularly TestPilot and ExBoeingEngineer.  Thanks for setting the record straight for us!  The rest was just a bunch of mumbo jumbo eating up white space.

And for the handful of you that followed with your redundant attempts at explaining what really happened, you were only successful in displaying your "Let me show you how smart I am" mentality.

And to "Future 737 pilot", what did you possibly think you could add to TestPilot's very detailed and highly accurate synopsis?  Considering that you're only studying to become 737 rated you're not exactly what we would consider a "qualified expert".  You sound like you're going to be a know-it-all, but right now you're J.A.F.O.

Contrary to popular belief, people don't read these posts for all the drama.  But rather they usually end up here after googling for information to satisfy their questions about a particular incident or safety related information.  So let's try to keep it on point and cut out all the BS.  (yes, mine included!)

Thanks and be sure and let me know if I misspelled any words.

&lt;i&gt;-No trees were killed in the posting of this message. However, a great many electrons were inconvenienced.&lt;/i&gt;</description>
		<content:encoded><![CDATA[<p>GEEZ, I wish you people would read all of the posts before jumping down and putting in your two-cents worth.  Only a few of you had something intelligent to say, particularly TestPilot and ExBoeingEngineer.  Thanks for setting the record straight for us!  The rest was just a bunch of mumbo jumbo eating up white space.</p>
<p>And for the handful of you that followed with your redundant attempts at explaining what really happened, you were only successful in displaying your &#8220;Let me show you how smart I am&#8221; mentality.</p>
<p>And to &#8220;Future 737 pilot&#8221;, what did you possibly think you could add to TestPilot&#8217;s very detailed and highly accurate synopsis?  Considering that you&#8217;re only studying to become 737 rated you&#8217;re not exactly what we would consider a &#8220;qualified expert&#8221;.  You sound like you&#8217;re going to be a know-it-all, but right now you&#8217;re J.A.F.O.</p>
<p>Contrary to popular belief, people don&#8217;t read these posts for all the drama.  But rather they usually end up here after googling for information to satisfy their questions about a particular incident or safety related information.  So let&#8217;s try to keep it on point and cut out all the BS.  (yes, mine included!)</p>
<p>Thanks and be sure and let me know if I misspelled any words.</p>
<p><i>-No trees were killed in the posting of this message. However, a great many electrons were inconvenienced.</i></p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Want to fly SouthWest? - MTW Forums</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9488</link>
		<author>Want to fly SouthWest? - MTW Forums</author>
		<pubDate>Thu, 29 Nov 2007 02:12:00 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9488</guid>
					<description>[...] this little bit of new that I'm sure is true, but still wounder if any one else heard about it.   Follow-up - Southwest Engine Failure at Flightstory.net - Aviation Blog  I've seen things along this line, but not this bad. If I had to guess one of the first stage [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] this little bit of new that I&#8217;m sure is true, but still wounder if any one else heard about it.   Follow-up - Southwest Engine Failure at Flightstory.net - Aviation Blog  I&#8217;ve seen things along this line, but not this bad. If I had to guess one of the first stage [&#8230;]</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: SWAspirit1</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9514</link>
		<author>SWAspirit1</author>
		<pubDate>Thu, 29 Nov 2007 06:43:23 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9514</guid>
					<description>I spoke with maintenance manager tonight on my way from getting off of work here in DAL and he said that it WAS NOT a blade malfunction...so that has been ruled out. I asked him about the spinner coming off, he said that was another possibility. He said that they were about to send the engine out for rebuild, but the NTSB wanted to look into the engine further for more investigation work. I must also say that our MX team does an awesome job aswell as our pilots....guess the track record proves that.</description>
		<content:encoded><![CDATA[<p>I spoke with maintenance manager tonight on my way from getting off of work here in DAL and he said that it WAS NOT a blade malfunction&#8230;so that has been ruled out. I asked him about the spinner coming off, he said that was another possibility. He said that they were about to send the engine out for rebuild, but the NTSB wanted to look into the engine further for more investigation work. I must also say that our MX team does an awesome job aswell as our pilots&#8230;.guess the track record proves that.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Michael</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9523</link>
		<author>Michael</author>
		<pubDate>Thu, 29 Nov 2007 08:29:01 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9523</guid>
					<description>Thanks for the informative comments of at least some of you. Very much appreciated.</description>
		<content:encoded><![CDATA[<p>Thanks for the informative comments of at least some of you. Very much appreciated.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Ray</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9560</link>
		<author>Ray</author>
		<pubDate>Thu, 29 Nov 2007 16:41:56 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9560</guid>
					<description>As a retired airline pilot with over 25,000 hours in the cockpit, let me assure you that professional pilots realize that engines do fail. That's why you have more than one engine. No one was hurt in this incident and the pilots did a great job handling the problem. Grow up and move on to the next crisis!</description>
		<content:encoded><![CDATA[<p>As a retired airline pilot with over 25,000 hours in the cockpit, let me assure you that professional pilots realize that engines do fail. That&#8217;s why you have more than one engine. No one was hurt in this incident and the pilots did a great job handling the problem. Grow up and move on to the next crisis!</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: SWA Engine &#34;Exploded&#34;!! - ExpressJet Pilots</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9593</link>
		<author>SWA Engine &#34;Exploded&#34;!! - ExpressJet Pilots</author>
		<pubDate>Fri, 30 Nov 2007 04:35:26 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9593</guid>
					<description>[...] Engine &#34;Exploded&#34;!!     Follow-up - Southwest Engine Failure at Flightstory.net - Aviation Blog    __________________ Texas Here I [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Engine &quot;Exploded&quot;!!     Follow-up - Southwest Engine Failure at Flightstory.net - Aviation Blog    __________________ Texas Here I [&#8230;]</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: arffguy</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9599</link>
		<author>arffguy</author>
		<pubDate>Fri, 30 Nov 2007 05:43:43 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9599</guid>
					<description>Actually "PlatinumRRMember", whatever the hell that is, I thought "Future737Pilot" did add something to the conversation. Meanwhile yours didn't! Who are you anyway? Great job to the SWA crew who did what they were supposed to do and to the engineers, mechanics and aircraft/engine assemblers that made it work like it was supposed to. And a great job to the people on this blog who actually know what they are talking about.</description>
		<content:encoded><![CDATA[<p>Actually &#8220;PlatinumRRMember&#8221;, whatever the hell that is, I thought &#8220;Future737Pilot&#8221; did add something to the conversation. Meanwhile yours didn&#8217;t! Who are you anyway? Great job to the SWA crew who did what they were supposed to do and to the engineers, mechanics and aircraft/engine assemblers that made it work like it was supposed to. And a great job to the people on this blog who actually know what they are talking about.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: RealPro</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9600</link>
		<author>RealPro</author>
		<pubDate>Fri, 30 Nov 2007 06:07:35 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9600</guid>
					<description>With all due respect to testpilot and these other supposedly knowledgeable insiders, you've got this all wrong.  Drawing upon vast amounts of experience as an air traveler, sky gazer, Oliver Stone movie watcher and web surfer, let me fill you in:  This was a near-total disaster of biblical proportions caused by the gross negligence of the SWA mechanics and a million design defects by Boeing and IBM.  First of all, understand that an engine is very, highly dangerous.  'Nuff said.  The fan blades which spin very, very fast -- sometimes over one million rpms -- are razor sharp with very jagged edges.  People in Row 15 always go first, because that's where the flying shrapnel coated with flammable jet fuel and the green stuff enters the fuselage on its way to blowing up the whole fuel system, which is next to the overhead oxygen tanks -- which act like little bombs when they go off.  Need I point out that the only SWA employee to post above didn't even know where the switch/gauge thingy was located on the control panel!!!  And the fact that the engine totally blew up in a massive explosion which almost consumed the whole jet should be a warning to all of us that, despite the PROPAGANDA about all those "successful" flight hours, Greyhound is the better option.  Frankly, it was the bravery of those of us on the ground who willed the plane to stay together which led to the happy ending, and you alleged experts should stop posting your meaningless techno-babble lies -- we can see right through you guys.</description>
		<content:encoded><![CDATA[<p>With all due respect to testpilot and these other supposedly knowledgeable insiders, you&#8217;ve got this all wrong.  Drawing upon vast amounts of experience as an air traveler, sky gazer, Oliver Stone movie watcher and web surfer, let me fill you in:  This was a near-total disaster of biblical proportions caused by the gross negligence of the SWA mechanics and a million design defects by Boeing and IBM.  First of all, understand that an engine is very, highly dangerous.  &#8216;Nuff said.  The fan blades which spin very, very fast &#8212; sometimes over one million rpms &#8212; are razor sharp with very jagged edges.  People in Row 15 always go first, because that&#8217;s where the flying shrapnel coated with flammable jet fuel and the green stuff enters the fuselage on its way to blowing up the whole fuel system, which is next to the overhead oxygen tanks &#8212; which act like little bombs when they go off.  Need I point out that the only SWA employee to post above didn&#8217;t even know where the switch/gauge thingy was located on the control panel!!!  And the fact that the engine totally blew up in a massive explosion which almost consumed the whole jet should be a warning to all of us that, despite the PROPAGANDA about all those &#8220;successful&#8221; flight hours, Greyhound is the better option.  Frankly, it was the bravery of those of us on the ground who willed the plane to stay together which led to the happy ending, and you alleged experts should stop posting your meaningless techno-babble lies &#8212; we can see right through you guys.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: JR.</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9642</link>
		<author>JR.</author>
		<pubDate>Fri, 30 Nov 2007 18:28:29 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9642</guid>
					<description>I will explain a few things. I work for a competitive airline. The maintenance crew for SWA and many airlines are top notch. The planes go in for maintenance and looked at in great detail. They are even given a walk around by pilots before it takes off. There is no way to predict a loose nut, a flat tire, etc. 
When you drive your car, do you check the lug nuts or do a walk around for anything that might be wrong with the car....no, most people do not. So, do you blame the maker of the car or yourself when you get a flat tire or other damage happens? 
The stress of working for an airline is great for EVERYONE working in this industry. Thousands of lives are in our hands every day. 
There is no gross negligence, the worse that SWA did was try to minimize what happened. Get a life you pompous, know everthing asses!</description>
		<content:encoded><![CDATA[<p>I will explain a few things. I work for a competitive airline. The maintenance crew for SWA and many airlines are top notch. The planes go in for maintenance and looked at in great detail. They are even given a walk around by pilots before it takes off. There is no way to predict a loose nut, a flat tire, etc.<br />
When you drive your car, do you check the lug nuts or do a walk around for anything that might be wrong with the car&#8230;.no, most people do not. So, do you blame the maker of the car or yourself when you get a flat tire or other damage happens?<br />
The stress of working for an airline is great for EVERYONE working in this industry. Thousands of lives are in our hands every day.<br />
There is no gross negligence, the worse that SWA did was try to minimize what happened. Get a life you pompous, know everthing asses!</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: aeronut</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9671</link>
		<author>aeronut</author>
		<pubDate>Sat, 01 Dec 2007 05:01:38 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9671</guid>
					<description>Those were some very entertaining comments in the first few posts.  I've been in the aerospace industry for 14 years.  From the pics, it looks like the spinner decided to exit the vehicle.  I'd say it bounced around a couple times after coming loose and took some blades along with it and it finally exited through the engine cowl or at least what was left of the spinner.  That part of the cowl in front of the N1 fan is not reinforced with kevlar(I believe).  The sides of the engine cowl which are inline with the compressor blades and turbine blades are reinforced with kevlar to contain blade failures, as has been mentioned in previous posts.  It could be a possible bird strike, a pretty descent size bird, but there is no evidence of a bird strike.  I can't wait to see the final NTSB report on this incident.  Does anyone have the date or tail number to this aircraft?  Thanks.</description>
		<content:encoded><![CDATA[<p>Those were some very entertaining comments in the first few posts.  I&#8217;ve been in the aerospace industry for 14 years.  From the pics, it looks like the spinner decided to exit the vehicle.  I&#8217;d say it bounced around a couple times after coming loose and took some blades along with it and it finally exited through the engine cowl or at least what was left of the spinner.  That part of the cowl in front of the N1 fan is not reinforced with kevlar(I believe).  The sides of the engine cowl which are inline with the compressor blades and turbine blades are reinforced with kevlar to contain blade failures, as has been mentioned in previous posts.  It could be a possible bird strike, a pretty descent size bird, but there is no evidence of a bird strike.  I can&#8217;t wait to see the final NTSB report on this incident.  Does anyone have the date or tail number to this aircraft?  Thanks.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Lee</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9677</link>
		<author>Lee</author>
		<pubDate>Sat, 01 Dec 2007 07:31:07 +0000</pubDate>
		<guid>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9677</guid>
					<description>While SouthWest should accurately report the incident, you have to look at how skilled the pilot was to be able to land such a disabled aircraft.  This is the precise reason that planes have two engines....</description>
		<content:encoded><![CDATA[<p>While SouthWest should accurately report the incident, you have to look at how skilled the pilot was to be able to land such a disabled aircraft.  This is the precise reason that planes have two engines&#8230;.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: DGTCB</title>
		<link>http://blog.flightstory.net/437/follow-up-southwest-engine-failure/#comment-9705</link>
		<author>DGTCB</author>
		<pubDate>Sat, 01 Dec 2007 13:27:45 +0000</p