Go Back  Airline Pilot Central Forums > Airline Pilot Forums > Major
AA1400 - STL engine fire - what went wrong >

AA1400 - STL engine fire - what went wrong

Notices
Major Legacy, National, and LCC

AA1400 - STL engine fire - what went wrong

Old 10-02-2007, 04:32 PM
  #1  
Gets Weekends Off
Thread Starter
 
Joined APC: Jul 2006
Posts: 2,889
Default AA1400 - STL engine fire - what went wrong

Aircraft # N454AA had a deferred L Start Valve, wired shut due to a previous writeup in which the L START VALVE ON light did not illuminate during engine start. When the valve is wired shut, it must be manually opened by MTX for engine starts.

Supposedly, on the day of the emergency, the L START VALVE ON light illuminated while climbing out of 2500msl, and the starter exploded out through the top of the engine, taking out the L generator and somehow screwing up the L hydraulic system, and causing the engine fire. The crew performed a quick downwind but could not extend the gear due to the hydraulic issues. They performed a manual gear extension and landed. After ARFF doused the fire the pax were deplaned through airstairs.

The theory going around is that the start valve "unsecured" itself, allowing ram air to blow into the starter and spin it up to super high RPMs, causing its failure.

To the crew of AA1400, a fantastic, professional job well done!

I'm just wondering... do the pax on that flight (all 140 of them) think we are overpaid?

73
aa73 is offline  
Old 10-02-2007, 05:12 PM
  #2  
Gets Weekends Off
 
ERJ135's Avatar
 
Joined APC: Oct 2005
Position: CR7 Capt
Posts: 1,621
Default

Originally Posted by aa73 View Post
Aircraft # N454AA had a deferred L Start Valve, wired shut due to a previous writeup in which the L START VALVE ON light did not illuminate during engine start. When the valve is wired shut, it must be manually opened by MTX for engine starts.

Supposedly, on the day of the emergency, the L START VALVE ON light illuminated while climbing out of 2500msl, and the starter exploded out through the top of the engine, taking out the L generator and somehow screwing up the L hydraulic system, and causing the engine fire. The crew performed a quick downwind but could not extend the gear due to the hydraulic issues. They performed a manual gear extension and landed. After ARFF doused the fire the pax were deplaned through airstairs.

The theory going around is that the start valve "unsecured" itself, allowing ram air to blow into the starter and spin it up to super high RPMs, causing its failure.

To the crew of AA1400, a fantastic, professional job well done!

I'm just wondering... do the pax on that flight (all 140 of them) think we are overpaid?

73
Hey, was that you causing all the trouble out there
ERJ135 is offline  
Old 10-02-2007, 05:43 PM
  #3  
Gets Weekends Off
Thread Starter
 
Joined APC: Jul 2006
Posts: 2,889
Default

Originally Posted by ERJ135 View Post
Hey, was that you causing all the trouble out there
Hey bro, when I cause trouble, there is usually a high amount of feminine presence involved.... I save that aircraft emergency crAAp for the sim!!!
aa73 is offline  
Old 10-02-2007, 06:03 PM
  #4  
Line Holder
 
RobLAX's Avatar
 
Joined APC: Sep 2007
Posts: 81
Default

When did this happen? Where were they going to?
RobLAX is offline  
Old 10-02-2007, 09:43 PM
  #5  
AAmerican Way for AA Pay
 
B757200ER's Avatar
 
Joined APC: Oct 2005
Position: B-737 Pilot
Posts: 1,617
Default

STL-ORD. Nicely done, but I wonder---will NTSB and FAA inquire as to why the crew didn't evacuate? Usually, when landing with a confirmed fire, that's pretty standard. I wasn't there, but I would ask the question.
B757200ER is offline  
Old 10-02-2007, 09:53 PM
  #6  
Gets Weekends Off
 
Pilotpip's Avatar
 
Joined APC: Jun 2005
Position: Retired
Posts: 2,934
Default

I was listening to tower freq while this was going on and it seemed like the crew didn't know there was still a fire. CFR got to the aircraft in short order and foamed it. With the fire contained quick do you think the crew might have thought it more dangerous to have 140 pax pushing their way towards the slides?

Would the hyd system failure explain the nose gear not coming down the first time around? I thought that they would all free-fall like the mains do (gear doors were open). They did a single engine go-around. As they flew past the tower the mains were down but the nose was not.
Pilotpip is offline  
Old 10-03-2007, 04:51 AM
  #7  
Gets Weekends Off
 
captjns's Avatar
 
Joined APC: Feb 2006
Position: B-737NG preferably in first class with a glass of champagne and caviar
Posts: 5,886
Default

More injuries occur during an evaction than not... proper judgement comes with proper experience. Good job to the crew... both front and back end.
captjns is offline  
Old 10-03-2007, 05:26 AM
  #8  
Gets Weekends Off
Thread Starter
 
Joined APC: Jul 2006
Posts: 2,889
Default

Originally Posted by B757200ER View Post
STL-ORD. Nicely done, but I wonder---will NTSB and FAA inquire as to why the crew didn't evacuate? Usually, when landing with a confirmed fire, that's pretty standard. I wasn't there, but I would ask the question.
B757,

From what I've heard the fire was extinguished pretty quickly after rolling to a stop. During these scenarios the crew maintains communication with the tower/ARFF to assess the situation. In many cases, if the threat is no longer there, it makes sense NOT to evacuate because there is always the possibility of injury during an evacuation. We must balance the importance of slight injury during evacuation vs. the risk of greater injury or death by NOT evacuating. (That's why we get paid the big bucks!)

In this case, I think it was the right call. Now, if the ARFF/tower would have told them they were still on fire, I think an evacuation would have been warranted.

A few years ago we had a Fokker100 in DFW land and collapse a main gear. The aircraft slid to a stop on the runway with no fire and no injury to anyone. After evaluating with the tower, the captain decided not to evacuate. It was also the right call, since based on the conditions outside, there was no real threat that warranted an evacuation.

Decisions, decisions...

73
aa73 is offline  
Old 10-03-2007, 05:27 AM
  #9  
Gets Weekends Off
Thread Starter
 
Joined APC: Jul 2006
Posts: 2,889
Default

Originally Posted by Pilotpip View Post
I was listening to tower freq while this was going on and it seemed like the crew didn't know there was still a fire. CFR got to the aircraft in short order and foamed it. With the fire contained quick do you think the crew might have thought it more dangerous to have 140 pax pushing their way towards the slides?

Would the hyd system failure explain the nose gear not coming down the first time around? I thought that they would all free-fall like the mains do (gear doors were open). They did a single engine go-around. As they flew past the tower the mains were down but the nose was not.
Yes, the Hyd failure accounted for the gear not coming down right away. On the 80, it doesn't free fall, you have to manually crank it down.
aa73 is offline  
Old 10-03-2007, 07:10 AM
  #10  
Gets Weekends Off
 
CVG767A's Avatar
 
Joined APC: Apr 2005
Position: 767ER capt
Posts: 1,190
Default

Originally Posted by aa73 View Post
Yes, the Hyd failure accounted for the gear not coming down right away. On the 80, it doesn't free fall, you have to manually crank it down.
Huh? If so, AA's MD80s must be radically different from Delta's. Our DC9s and MD88s had a handle in the floor by the F/O's left foot. Pulling that lever would mechanically release the main gear door latches and nose gear over-center lock, and place the gear hydraulic system in bypass, allowing the gear to free fall and lock into the down position.

According to the manual, nose oscillations might be required to get the nose gear to lock.
CVG767A is offline  

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Thread Tools
Search this Thread
Your Privacy Choices