Any "Latest & Greatest about Delta?" Part 2
#2761
Gets Weekends Off
Joined APC: Dec 2013
Posts: 2,319
Almost identical to the Delta Salt Lake City incident. Why on earth would you listen to a guy telling you to stay in a burning airplane after he tells you he is having difficulty containing the fire. I don’t care what tone is used. I’m evacuating, the only advice I’d listen to is which exits are passable. What is a “simple brake fire” and how do you know? A trained observer from a distance is seeing flames come from your aircraft. Why are you waiting? If it’s because you were told to, what reason did they have for wanting you to wait?
I’m curious when and how you know if/when simple becomes something not simple.
I’m curious when and how you know if/when simple becomes something not simple.
#2763
I did CQ this cycle and got a cargo smoke. No big deal, handled it well and was told all was well. Taxiing back after thermal gun and CFR said all was well, as well as interior cargo heat indications. The not so surprising, “you’re on fire” during the taxi in to force an evacuation occurs. Did it, no big deal, passed.
Anywho, my point, after reading all of this diatribe, is if that’s how training sets us up in the sim to listen to the ground personnel, why are we arguing it here. Not discounting stuff said, just an observation.
Anywho, my point, after reading all of this diatribe, is if that’s how training sets us up in the sim to listen to the ground personnel, why are we arguing it here. Not discounting stuff said, just an observation.
#2764
I also know you're going to argue "It wasn't a brake fire!", but let's use the example of China Air 120. The fire started below the wing near the engine nacelle. Imagine the situation for a second where ATC sees that and says "DL120, you have a fire near your landing gear!" and the pilots interpret that to mean a brake fire, then wait for the trucks to come and give more information. Half the people onboard would have died. I know it's not what happened, but it's pretty easy to see that chain of events.
I believe the FO from that flight is at Delta now.
I believe the FO from that flight is at Delta now.
Thanks for bringing up that incident. That was a wild read. No indication of fuel leak on taxi in. No fire warnings at all on shutdown. FO blown off escape rope when the plane exploded
#2765
All the more reason to evacuate early. The risk is lower when people are not panicking and the scene isn’t chaotic. Time is the most precious commodity when fire is involved. When CFR witnesses an evacuation in progress their response is altered to assist the evacuation. Fire propagation is unpredictable and the heat generated will weaken metal structure and make other materials more flammable. The situation is not predictable. You are better served by going back into the cabin and making you own observation. I’d even consider opening a door or window to look but that presents other problems. You might as well open the doors with the slides armed in preparation. None of this is what corporate wants to see.
Last edited by notEnuf; 08-31-2023 at 07:30 AM.
#2767
Gets Weekends Off
Joined APC: Sep 2016
Posts: 6,832
#2769
Gets Weekends Off
Joined APC: Jul 2023
Posts: 135
You might not be wrong to wait to order an evacuation.
You are definitely not wrong to order an evacuation (barring a glaringly obvious reason to wait).
I’m reminded of a quote on the back cover of an AF publication issued to UPT students called “Road to Wings”, from a long time ago filled with vignettes of various mishaps. It is permanently applicable:
You are definitely not wrong to order an evacuation (barring a glaringly obvious reason to wait).
I’m reminded of a quote on the back cover of an AF publication issued to UPT students called “Road to Wings”, from a long time ago filled with vignettes of various mishaps. It is permanently applicable:
#2770
I'm late to the conversation, as I first skimmed through the thread today. It is indeed thought provoking conversation, one that boils down to how swiftly crews should react to a potential fire. One need only study BA 2276 to get your answer. It's a useful to consider this near-disaster and actual triumph in the context of this conversation. Hard to believe that it's been almost eight years since the B-777-200ER had a catastrophic engine failure on the T/O roll at KLAS. A timely high speed abort, zero hesitation evac and pronto ARFF response transpired into a good day for all involved, versus a diametrically opposed potential outcome. I said high speed abort because many random online articles stated 12x mph, but I see the NTSB it pegged at 77 knots - doesn't matter, close enough to high speed for me. To acquaint yourself and/or re-familiarize, check it out: https://en.wikipedia.org/wiki/Britis...ys_Flight_2276. Many other more detailed sources available on the Net, of course. In the NTSB report, the crew (Captain mainly) is critiqued for calling for the evacuation before consulting the proper checklist. This lead to the unaffected engine remaining operational for longer than it should have, and messing up escape slides (43 secs from the evac order until the engine was shutdown) - the point being that the evac could have gone more swiftly if escape paths were not impeded by crew error. Nonetheless, the crew got things moving in a hurry and everyone survived.
Key points: after running the engine failure/fire checklist, indication of fire warning ceased; relief pilot entered cabin for a visual check and determined fire was "on." Captain was firm on getting people off despite of a lack of urgency from others. ARFF arrived less than two minutes after the captain's call for help and the evac was accomplished 2:32 after initial indication of engine failure. From standing up the throttles to onset of chaos, to all persons free and clear of the aircraft took less than five minutes. Of course it helped that the plane was around two thirds passenger capacity.
Speculative thoughts from me: a few more seconds rolling down the runway, whether it had been a later onset of engine failure or slow crew response time, could have lead to the largest single hull loss of life and property in the history of aviation. The local newspaper had an article that indicated a wing spar burn through and fire penetration across the cabin would have occurred within the time it would take to return for emergency landing, likely dropping the 777 into a densely populated Las Vegas residential neighborhood, or worse, the Strip. Also, it's quite possible that repair of the aircraft was a political stunt, mostly in favor of Boeing. In 2015, our own RA stated that used 777 values were about $10M, and proved it by purchasing a B-777-200 for $7.7M. I don't know the specs of what Delta purchased, but it couldn't have been too far away from the 17 year-old, 72,000 hour/10,600 cycle -200ER that BA repaired. Boeing stock reacted negatively to this new "valuation bar, " leading me to think scrapping the subject 777 was not a good option for parties outside of BA. Arguably, the repair cost approached or exceeded the aircraft's market value. The tragedy narrow-averted angle was never openly discussed, as far as I can tell. Was Lloyds of London "convinced" this was a viable repair, or did some other party contribute to the repair fund? IDK, but it's fun to think about.
There are many post-mortem fire scenarios worthy of study. Saudia 163, Air Canada 797 and N711Y (Ricky Nelson) are a few of the case studies my training has delved into over the years. My takeaway from it all is 1) act swiftly and deliberately when faced with the threat of fire, and
2) seek multiple forms of verification before assuming all is good .... when in doubt, get out!
Key points: after running the engine failure/fire checklist, indication of fire warning ceased; relief pilot entered cabin for a visual check and determined fire was "on." Captain was firm on getting people off despite of a lack of urgency from others. ARFF arrived less than two minutes after the captain's call for help and the evac was accomplished 2:32 after initial indication of engine failure. From standing up the throttles to onset of chaos, to all persons free and clear of the aircraft took less than five minutes. Of course it helped that the plane was around two thirds passenger capacity.
Speculative thoughts from me: a few more seconds rolling down the runway, whether it had been a later onset of engine failure or slow crew response time, could have lead to the largest single hull loss of life and property in the history of aviation. The local newspaper had an article that indicated a wing spar burn through and fire penetration across the cabin would have occurred within the time it would take to return for emergency landing, likely dropping the 777 into a densely populated Las Vegas residential neighborhood, or worse, the Strip. Also, it's quite possible that repair of the aircraft was a political stunt, mostly in favor of Boeing. In 2015, our own RA stated that used 777 values were about $10M, and proved it by purchasing a B-777-200 for $7.7M. I don't know the specs of what Delta purchased, but it couldn't have been too far away from the 17 year-old, 72,000 hour/10,600 cycle -200ER that BA repaired. Boeing stock reacted negatively to this new "valuation bar, " leading me to think scrapping the subject 777 was not a good option for parties outside of BA. Arguably, the repair cost approached or exceeded the aircraft's market value. The tragedy narrow-averted angle was never openly discussed, as far as I can tell. Was Lloyds of London "convinced" this was a viable repair, or did some other party contribute to the repair fund? IDK, but it's fun to think about.
There are many post-mortem fire scenarios worthy of study. Saudia 163, Air Canada 797 and N711Y (Ricky Nelson) are a few of the case studies my training has delved into over the years. My takeaway from it all is 1) act swiftly and deliberately when faced with the threat of fire, and
2) seek multiple forms of verification before assuming all is good .... when in doubt, get out!
Thread
Thread Starter
Forum
Replies
Last Post