Originally posted by Gabriel
View Post
Announcement
Collapse
No announcement yet.
Plane crash in Nigeria
Collapse
X
-
Originally posted by Evan View PostWith foreign object ingestion (birds, hail, what-have-you) one important factor is in how the compressor stalls are handled. If the engines are not throttled down sufficiently, the engines can suffer destructive effects beyond the deformation of fan blades. This had led to two DC-9/MD-80 dual engine failure crashes that I can think of...
I wonder if we have a third case on our hands?
Comment
-
-
On Jun 10th 2012 Dana Air's Director of Flight reported on Lagos' TV, that the remains of one or more birds have been found in one of the engines recovered from the crash site. However, the cause of the crash is still to be determined.
Comment
-
Originally posted by ErwinS View PostOn Jun 10th 2012 Dana Air's Director of Flight reported on Lagos' TV, that the remains of one or more birds have been found in one of the engines recovered from the crash site. However, the cause of the crash is still to be determined.
If correct, the "reallistic" choices for a double engine failure have pretty much narrowed to:
- Double bird ingestion
- Wrong-engine shut-down
--- Judge what is said by the merits of what is said, not by the credentials of who said it. ---
--- Defend what you say with arguments, not by imposing your credentials ---
Comment
-
Originally posted by Gabriel View PostCopy-pasted from AvHerald. Give credit.
If correct, the "reallistic" choices for a double engine failure have pretty much narrowed to:
- Double bird ingestion
- Wrong-engine shut-down
Not only Avherald had that quote
Comment
-
The probe into the June 3 Dana Air crash traced the cause "to the loss of two engines and non-functionality of the throttles on final descent from Abuja to Lagos", the Accident Investigation Bureau (AIB) report said.
Comment
-
From the link above:
At 15:43:27 hours, the captain informed the FO (flight officer), 'we just lost everything, we lost an engine. I lost both engines'.
During the next 25 seconds until the end of the CVR (cockpit voice recorder) recording, the flight crew was attempting to restart the engines
no flaps/slats (which would stay at their last position)
no spoilers (which, more important than for airbrake and lift killer, they are an integral part of the roll control)
no antiskid, no autobrakes, no reversers (as if they were of any use with the engines off)
no nosewheel steering
no rudder
no trim
no elevator boost (that kicks in when you command large nose-down inputs to help recover a stall)
no pressurization, no air conditioning
no pneumatic pressure to feed the engine start motors
30 minutes of essential DC (feed from the battery)
Reserve hydro pressure in the accumulators for the brakes
"Gravity powered" alternate landing gear extension
And, most important of all, the famous "aerodynamically powered" ailerons and elevator.
So you have degraded but enough flight control for the glide:
In pitch, normal elevator (except boost) but no trim.
In roll, normal ailerons but no spoilers.
In yaw, nothing but that's not so severe (the main functions of the rudder is to arrest asymmetric thrust, to give directional control on the ground at high speeds, and to allow sideslips which is mostly used to make smooth landings in crosswind).
At altitude cruise altitude, the usual procedure would be to make a descent to the altitude and speed needed for the windmilling restart and attempt a restart, or to descend below the max APU altitude, start the APU (the APU start motor is DC which you have from the batteries, and the APU will give you AC, hidro from the electric pump, and pneumatic pressure for the engine start motors), and attempt an engine restart. Even if the engines fail to restart, the APU will give you most of the systems back.
During all that you should be considering that the engines might not relight so from the start you act like you are going to make a power-off landing, that means finding a suitable (or the least unsuitable) place to put the plane down, navigating to there, brief the cabin, advice ATC, etc.
Now, if you are really low, somehow slow (windmill start not possible), and are flying over a densely populated area, like in this case, you better concentrate all of your efforts in the best way to crash the plane. It takes maybe 1.5 minute to start the APU and get the systems on-line and then maybe another half a minute to start an engine and have it spooled up. So if you don't have 2 minutes of glide, don't even bother: the engines don't work very well underground, and the chances of a restart are not very good anyway (the engine quit for something after all).
I know it's easy from this chair and very difficult in the real life, but at some point one has to accept that you are going to crash and change from "complete the flight" mode to "survive the crash" mode. The captain should take the controls, keep the plane within its envelope, concentrate on finding a highway, a patch of green, an avenue, even a river, where to crash-land it, advise the ATC and the cabin, (that is: aviate, navigate, communicate) and forget about any troubleshooting. That he can leave to the FO, or maybe (if it is clear that there is not time to even start the APU and put the systems on-line) even the FO should forget that too and help the captain find a place, lowering the gear, briefing the cabin, etc...
I don't know how much time passed since the captain called the double engine failure until the crash. Probably it was more than the 25 seconds mentioned because the CVR and FDR stop working when the generators are lost (the 25 seconds was probably the spool down if the last engine) and because it makes no sense a time so short, even with very little altitude they would have more than that while trading altitude to keep speed and then bleeding off excess speed. But it sounds that, at least for those 25 seconds, both of them were concentrated with the restart of the engines. The article is not clear, but they mention only that and not any comment about where to put it down.
--- Judge what is said by the merits of what is said, not by the credentials of who said it. ---
--- Defend what you say with arguments, not by imposing your credentials ---
Comment
-
The core of the report
The cockpit voice recorder (CVR) retained about 31 minutes of the flight and starts about 1515 [Gabriel's note: the plane was already at cruise] at which time
the captain and first officer were in a discussion of a nonnormal condition regarding the correlation between the engine throttle setting and an engine power indication3.
However, they did not voice concerns then that the condition would affect the continuation of the flight. The flight crew continued to monitor the condition and became increasingly concerned as the flight transition through the initial descent from cruise altitude at 1522 and the subsequent approach phase. DAN 992 reported passing through 18,100 and 7,700 ft, respectively, at 1530 and 1540 hours. After receiving a series of heading and altitude assignments from the controller, DAN 992 was issued the final heading to intercept the final approach course for runway 18R.
During the period of 1537 and 15:41 the flight crew engaged in pre-landing tasks including deployment of the slats, and extension of the flaps and landing gear. At
15:41:16 the first officer (FO) inquired, "both engines coming up?" and the captain (Capt) replied “negative.” The flight crew subsequently discussed and agreed to declare an emergency. At 1542:10, DANA 992 radioed an emergency distress call indicating "dual engine failure . . . negative response from throttle."
At 1542:35, the flight crew lowered the flaps further and continued with the approach and discussed landing alternatively on runway 18L. At 1542:45, the Capt reported the runway in sight and instructed the FO to raise the flaps up and 4 seconds later to raise the landing gear.
At 1543:27 hours, the Capt informed the FO "we just lost everything, we lost an engine. I lost both engines". During the next 25 seconds until the end of the CVR recording, the flight crew was attempting to restart the engines.
Underlining is mine. It called my attention that they lowered the flaps farther after declaring a dual engine failure (which apparently was not total yet) and, 10 seconds later, retracted the flaps and the gear.
It's another tough call: flaps, slats and gear add drag and worsen the glide ratio and hence the distance that you can glide from a given altitude. On the other hand, the slats and flaps reduce the stall speed (and hence the crash speed) a lot, and the gear can absorb a good bunch of energy during a crash landing.
If I knew that my engines would quit in a minute and that I can reach the runway (or some very flat, smooth and long place) gliding only if I clean up the plane, then I would happily trade the benefit of a slower speed and gear cushion for the benefit of the runway. On the other hand, if I knew that my engines would quit in a minute and that I will not reach a runway or equivalent place, I want the slats out and some flaps (a take-off-ish config) right now, while I have power to move them. Slats and a bit of flaps give you most of the reduction in stall speed with no so much drag (further flaps add more drag than they increase lift). If the crash is not imminent and I want to preserve glide ratio, the landing gear can come down later with the alternate gravity extension.
The problem is that when you see the runway out there, it is very hard to avoid the temptation to try to reach it because a runway is so much more a safe for a crash landing than the middle of the city, but on the other hand the middle of the city and with twice the energy and no landing gear is even more dangerous and a runway beyond reach is useless. That's why I praised Sully not for the water landing itself, but for his decision making, like he himself said "The Hudson river was the only place long enough, wide enough and smooth enough that I KNEW that I could reach". Later, simulation showed that if he did everything perfect he could have reached La Guardia, but he didn't know that at that time. Of course he didn't know that he could not reach it either, and that's why I applauded him for resisting the temptation of trying. That is really hard for a pilot: to accept that you are not only not reaching your destination, but that you are going to crash this plane and that loss of lives might be involved. But that acceptance is crucial to change to survival mode and start to concentrate not on reaching a runway but on how to crash to maximize the chances of saving some lives (including yours).
--- Judge what is said by the merits of what is said, not by the credentials of who said it. ---
--- Defend what you say with arguments, not by imposing your credentials ---
Comment
-
Not that it is related to the accident, but someone please explain this:
He [the FO] had 1,143 hours of total time, including about 200 hours as pilot-in-command. The first officer had 808 hours in the accident model airplane all of which was second-in-command [...] had accrued about 3, 42, and 154 flight hours, respectively, during the preceding 24 hours, 30 and 90 days.
Again, not that it is related to the accident. If it is for the experience only, given a 1100 hours FO I choose one with 800 hours in the type (and who's been flying some 50 hours a month on the type) over one with 20 hours in the type.
--- Judge what is said by the merits of what is said, not by the credentials of who said it. ---
--- Defend what you say with arguments, not by imposing your credentials ---
Comment
-
A question (or comment request) to our resident senior MD-80 pilot forum user:
In planes like these, that lack RAT, I've always thought it would be a good idea to keep the APU running during the take-off and climb to some "safe" altitude and fire it up again before starting the approach, again at a "safe" altitude, as to be able to keep most systems on-line and attempt an engine restart in the event of a dual engine failure, "safe" meaning precisely that you have time (altitude) to, while gliding, asses the situation, start the APU, bring the systems on-line and attempt an engine re-start with some margin of altitude to spare. As a minimum, the APU will be running whenever the plane is not "clean".
I know that it can be done. However, AFAIK that is not the usual practice. The APU is typically turned off after engine start and turned back on after landing. I know this practice saves a bit of fuel, but still...
--- Judge what is said by the merits of what is said, not by the credentials of who said it. ---
--- Defend what you say with arguments, not by imposing your credentials ---
Comment
-
Originally posted by Gabriel View PostA question (or comment request) to our resident senior MD-80 pilot forum user:
In planes like these, that lack RAT, I've always thought it would be a good idea to keep the APU running during the take-off and climb to some "safe" altitude and fire it up again before starting the approach, again at a "safe" altitude, as to be able to keep most systems on-line and attempt an engine restart in the event of a dual engine failure, "safe" meaning precisely that you have time (altitude) to, while gliding, asses the situation, start the APU, bring the systems on-line and attempt an engine re-start with some margin of altitude to spare. As a minimum, the APU will be running whenever the plane is not "clean".
I know this practice saves a bit of fuel
Comment
-
There are news in the internet that Dana Air re-started their flight ops on Thursday (January 3rd) with a flight from Lagos to Abuja.
Regardshttp://www.MD-80.com / MD-80.com on facebook https://www.facebook.com/MD80com / MD-80.com on Twitter: https://twitter.com/MD80com
Comment
Comment