On Aug 20, at 14.45LT a Spanair flight JK5022, from Madrid-Barajas to Las Palmas (Gran Canarias), crashed shortly after take off from runway 36L. The MD82 (EC-HFP) had 164 passengers and 9 crew on board; 153 died in the accident. As soon as the first news agencies began reporting that the aircraft caught fire during take-off maneuvers because of an engine problem, I was immediately asked from many people, how an engine fire on the ground could destroy an airplane causing so many fatalities.
I answered that, in my opinion, unless the aircraft had collided with “something” (another plane, a truck, a building), a “simple” engine fire on the ground could not be so catastrophic. A departing aircraft is loaded with much fuel and so vulnerable to fire, but if it hasn’t taken off yet, there’s plenty of time to disembark people, to extinguish fire, to request firefighters intervention, etc, before the aircraft explodes.
In fact, it was later explained, the aircraft was actually taking off, meaning that the engine exploded or caught fire when the MD-82 was already some 200 feet above the runway.
What could have happened then? Impossible to say now, since no clear details explaining the crash itself have been provided by the Spanish authorities. What I can say and what I think is that loosing an engine during take off is not a good news for a pilot, even if it is one of the emergencies he’s been trained to face and he has many chances to manage it a bring the plane safely back on the runway. If an emergency, like an engine fire or an engine flame out (caused for example by a birdstrike or a FOD, Foreign Object Damage), occurs after V1, the calculated decision speed, the aircraft can’t abort take off and has to continue the take off procedure. He couldn’t stop the aircraft using full brakes and would overrun the runway. So he continues the take off and will assess the situation once airborne. We obviously don’t know if the aircraft experienced the problem before or after V1. This could be an interesting information to know. According to some witnesses, the plane took off, then after climbing a few hundred feet (500 feet was speculated), passengers heard an explosion and the aircraft began to fall. There are in fact another couple of important speeds in aviation: the VR, rotation speed, at which the pilot rotates the aircraft, and V2, safety speed, the one that ensures the aircraft will continue the take off even with a single engine. At 500 feet (even at 200 ft), the aircraft has already reached the V2 and is still flyable in case of engine failure.
If an explosion occurred at low altitude, it may have put the airplane into a nose-high attitude causing a stall (T-tails, like the MD80s have poor stall recovery characteristics). However, basing on the information known so far, I couldn’t imagine why the aircraft could react with a pitch-up to an engine loss. What is more likely to happen and it is always trained in simulator session is a violent yaw caused by asymmetric thrust. The MD82 has both engines located in the rear part of the fuselage: should an engine fail, it can be still flown (aircraft like B767 and 777 with wing mounted engines, would react more violently to asymmetric thrust, even if the DC9 and MD80s seems to be very aggressive to asymmetric thrust, just like other aircraft). Obviously, if the asimmetric situation happens during take off, unless the engine explosion causes other damages to other aircraft systems (hydraulic system for example) the possibility to survive depends on the reaction speed of the pilot. He has to apply the emergency procedure (and yaw correction) as soon as possible. Above all he has to apply the right correction, meaning that he has to understand in a split second which engine failed and how to use the rudder to prevent yaw and roll that could be unrecoverable. I don’t know what happened to flight JK5022, but human factor could be a contributing cause, according to the few information surfaced so far.
Comments are closed.
Why don’t you people start speculating right away. Are you calling yourselves smart doing such?
There is a very valid reason why the accident investigations take weeks if not months!
Hi,
as I already explained in this website, I’ve noticed that media inaccuracy is extremely high after accidents and major emergencies. Just think to the CVR transcription of the Argentinian TV: the conversation between CDR and F/O was just a fake one. The journalist who did the scoop later admitted that the transcription was simply hyphotetical since it was based on the information he gained from various aviation sources and pilots flying the same aircraft type.
Unfortunately this is only the last occurrence of such kind of “mistake”. It is for this reason that I started to talk a bit more about aviation safety on my website. I’ve already said that I’m not an investigor nor are the majority of those who visit my site but almost always I try, with help of everyone who write me via email or comment my posts, to provide readers a possible explaination and a few answers. If you read this post: http://cencio4.wordpress.com/2008/08/23/spanair-5022-stall-theory/ you’ll see that I’ve provided a possible explaination of the crash, basing on the few information available, weeks before an initial report was issued.
Best Regards,
David
hello
did you see this msnbc report stating a malware infection on ground maintenance computers may have caused the crash?
http://www.msnbc.msn.com/id/38790670
the original spanish article ( I can’t read spanish)
http://www.elpais.com/articulo/espana/ordenador/Spanair/anotaba/fallos/aviones/tenia/virus/elpepuesp/20100820elpepinac_11/Tes
Hi, thank you very much indeed. I didn’t hear about malware in the maintenance system. Anyway, we can consider it a contributing factor, as the root cause of the crash was of course that the aircraft took off with flaps and slats retracted. Thanks again, Best Regards, David