AF 447 Thread No. 9
Join Date: Dec 2010
Location: Middle America
Age: 84
Posts: 1,167
Likes: 0
Received 0 Likes
on
0 Posts
Hi Gums,
Here is an article by Boeing where they discuss high altitude handling and stability in general terms.
High-Altitude Handling
It does describe the differences between the B-777 and the MD-11 in terms of longitudinal static stability and how it is achieved in both aircraft.
Here is an article by Boeing where they discuss high altitude handling and stability in general terms.
High-Altitude Handling
It does describe the differences between the B-777 and the MD-11 in terms of longitudinal static stability and how it is achieved in both aircraft.
Now - an interesting sim test would be to try stick-neutral just prior to the apogee, at the apogee and after the apogee (at the point where the PF slams the sick against the back stop) and see what the autotrim system makes of it. I'd be very surprised if the BEA haven't done precisely that, but a second opinion is always useful.
This is confirmed in the report on page 187 (chapter 2.2.5.)
When there are no protections left, the aeroplane no longer possesses positive longitudinal static stability even on approach to stall. This absence specifically results in the fact that it is not necessary to make or increase a nose-up input to compensate for a loss of speed while maintaining aeroplane altitude.
The specific consequence is that in this control law the aeroplane, placed in a configuration where the thrust is not sufficient to maintain speed on the flight path, would end up by stalling without any inputs on the sidestick.
Join Date: Jul 2009
Location: France - mostly
Age: 84
Posts: 1,682
Likes: 0
Received 0 Likes
on
0 Posts
Put another way, the pitch command ratio (NU:NEUTRAL:ND) over the 53 seconds following apogee/stall is approximately 49:3:1 in seconds
Join Date: Aug 2009
Location: Germany
Age: 67
Posts: 1,777
Likes: 0
Received 0 Likes
on
0 Posts
Simply levelling off and then letting the stick go should have helped until a speed of ~Mach 0,65 (Figure 65 in the report). After that even at level attitude the FCS would have started to trim into the stall once the propulsive limit had been exceeded. At that point sustained ND input would have been required.
That of the pilot ( pull the stick as a mad with a continued stall warning )
That of the Airbus system (hold the trim in up position when knowing this was a continuous stall)
If Airbus was in full manual both stupidities to put the plane into the water should have been made by the pilot
Pull the stick and put together manually the trim full up position
So I conclude that the auto trim really helped to put AF447 in the water because the system worked as per design
Last edited by jcjeant; 8th Aug 2012 at 19:43.
Join Date: Jul 2002
Location: UK
Posts: 3,093
Likes: 0
Received 0 Likes
on
0 Posts
At that point sustained ND input would have been required.
The stall warning parameters are encoded into the annunciator system, but the flight control computers are oblivious to stall in Alternate Law - and most would say rightly so, because for the computers to be able to override the human when in a degraded state would open the aircraft's safety to significant risk if the computers get it wrong (not to mention the fact that the backlash from the Airbus-sceptic brigade would be deafening if this were the case!).
The point is that outside of Normal Law, the systems are designed to defer to the pilot's inputs - no matter what those inputs are - for better or worse. This is based on the reasonable assumption that the human pilot will have a much better ability to adapt to circumstance than the computer ever could. In this case the crew were clearly overwhelmed and not only made mistakes, but repeated the same mistakes over and over again with tragic consequences.
DozyWannabe
It went all the way back in this case because the elevators were no longer sufficient to maintain the requested attitude as the speed bled off. The THS had moved approximately 5 degrees nose-up at the apogee of the climb. From that point onwards, the stick is held halfway back by the PF for a further 15 seconds, released for about 4 seconds with a small "blip" forward and then slammed against the back stop for an eye-watering 34 seconds. In short, the THS went where it was told to go by the PF. If he'd released the stick prior to the apogee, it would likely have stayed at a max of 5 degrees NU.
It went all the way back in this case because the elevators were no longer sufficient to maintain the requested attitude as the speed bled off. The THS had moved approximately 5 degrees nose-up at the apogee of the climb. From that point onwards, the stick is held halfway back by the PF for a further 15 seconds, released for about 4 seconds with a small "blip" forward and then slammed against the back stop for an eye-watering 34 seconds. In short, the THS went where it was told to go by the PF. If he'd released the stick prior to the apogee, it would likely have stayed at a max of 5 degrees NU.
From 02:10:25 until 02:10:50 the normal acceleration was below 1g. When PF after the stall warning 2 selected TOGA, the normal acceleration increased for a short time of about 10 seconds above 1 g. From that point on the normal acceleration was uninterrupted below 1 g until 02:12:00. When PF applied SS full NU at 02:11:40, the THS had already reached near full NU limit and the elevators moved now full NU. Despite those NU commands and despite the position of the THS the normal acceleration stayed below 1 g for another 20 seconds, until 02:12:00.
During all those times, where the aircraft was not able to maintain even 1 g, (and that started already before the apogee of the climb) the trim and the elevators would have moved on their own to achieve this 1 g with hands off SS neutral= 1g.
To stop the trim from further traveling, the SS would have to be moved and held at the present normal aceleration (which was below 1 g). To get the trim moving ND, the SS would have to be held to demand a g value well below the present normal aceleration.
Interesting, after PF started putting the SS to the NU stops and reduced the power at the same time to idle, the pitch of the aircraft decreased from +15° to -10° within 10 seconds. Power change and maybe the elevator deflection to full NU changed the forces of the airframe. What that did to the mental picture of the PF would be interesting to know. If PF would have gone to full ND at that point, the he might have had a chance to initiate recovery.
After the aircraft dropped outside the flightenvelope, which happened after the stall warning 2, any command except a definite ND command was bad, but the amount and the duration of the NU input or even a SS neutral input would not have saved the day and did not agrevate the NU travel of the trim. and the elevators. Because those were already maxed out by trying to maintain 1g.
BEA FR 2.1.3.2 Exit from the flight envelope
Subsequently, the position of the sidestick, maintained in its nose-up or neutral position, continued to exacerbate the situation and made the recovery uncertain, even impossible.
Subsequently, the position of the sidestick, maintained in its nose-up or neutral position, continued to exacerbate the situation and made the recovery uncertain, even impossible.
BEA FR 2.1.3.5 End of the flight
At about 2 h 12, descending though FL 315, the aeroplane’s angle of attack was established around an average value of about 40 degrees. Only an extremely purposeful crew with a good comprehension of the situation could have carried out a manoeuvre that would have made it possible to perhaps recover control of the aeroplane. In fact, the crew had almost completely lost control of the situation.
Up until the end of the flight, no valid angle of attack value was less than 35°.
At about 2 h 12, descending though FL 315, the aeroplane’s angle of attack was established around an average value of about 40 degrees. Only an extremely purposeful crew with a good comprehension of the situation could have carried out a manoeuvre that would have made it possible to perhaps recover control of the aeroplane. In fact, the crew had almost completely lost control of the situation.
Up until the end of the flight, no valid angle of attack value was less than 35°.
Henra
Given that Airbus is using C* based laws it would have tried to keep attitude. If the last commanded attitude was 10° NU, it would have tried to keep the nose there, if not corrected even into the stall.
Given that Airbus is using C* based laws it would have tried to keep attitude. If the last commanded attitude was 10° NU, it would have tried to keep the nose there, if not corrected even into the stall.
You would be correct however, when low speed stability protection is available, which was not in AF447 case in Alt2b law.
This is confirmed in the report on page 187 (chapter 2.2.5.)
Quote:
When there are no protections left, the aeroplane no longer possesses positive longitudinal static stability even on approach to stall. This absence specifically results in the fact that it is not necessary to make or increase a nose-up input to compensate for a loss of speed while maintaining aeroplane altitude.
and
Quote:
When there are no protections left, the aeroplane no longer possesses positive longitudinal static stability even on approach to stall. This absence specifically results in the fact that it is not necessary to make or increase a nose-up input to compensate for a loss of speed while maintaining aeroplane altitude.
and
Come on guys, we have been through this for years.
Last edited by RetiredF4; 8th Aug 2012 at 20:28.
Join Date: Jul 2002
Location: UK
Posts: 3,093
Likes: 0
Received 0 Likes
on
0 Posts
@franzl
I'm not disagreeing with your hypothesis in the slightest, I'm just saying we're so far outside of normal operational parameters that I'd like to see supporting experiments to attempt to prove it.
I suspect that the PF could have rescued the situation with full nose-down held as late as 02:12:20, but I can't prove it.
I'm not disagreeing with your hypothesis in the slightest, I'm just saying we're so far outside of normal operational parameters that I'd like to see supporting experiments to attempt to prove it.
I suspect that the PF could have rescued the situation with full nose-down held as late as 02:12:20, but I can't prove it.
If SS is left neutral it should keep constant attitude throughout. That is also what BEA considers neutrally speed stable.
Could you point me to any source that states that Airbus instead is using a pure C law?
Edit: Altitude is not a parameter in any FCS law. So FCS alone will probably not chase altitude. It may chase g or pitch or pitch rate or speed. That is what distinguishes C from C* and C*U (B777).
Altitude is only an A/P parameter.
Last edited by henra; 8th Aug 2012 at 20:35.
I suspect that the PF could have rescued the situation with full nose-down held as late as 02:12:20, but I can't prove it.
What you describe would be a pure C law. My understanding is that Airbus uses a C* law. A C* law will progressively switch from g command to pitch rate command when the speed decreases, i.e. at the stall it will be mainly pitch rate. That means if no SS inputs are made it will keep pitch rate 0 which means constant attitude.
If SS is left neutral it should keep constant attitude throughout. That is also what BEA considers neutrally speed stable.
Could you point me to any source that states that Airbus instead is using a pure C law and that BEA (and myself) are wrong?
If SS is left neutral it should keep constant attitude throughout. That is also what BEA considers neutrally speed stable.
Could you point me to any source that states that Airbus instead is using a pure C law and that BEA (and myself) are wrong?
As i understand it it only references the value to change, in low speed the reference will be pitch change, in other cases g command. But stick neutral it will be 1 g.
During all those threads i copied following sentence, source now unknown:
G command’ which is a desirable capability at high speeds, means that for a particular amount of control column force, you get (available energy permitting) the same ‘g’ regardless of prevailing airspeed. Similarly, in a pitch-rate command system, you get the same amount of pitch rate for a given control column force regardless of prevailing airspeed.
Last edited by RetiredF4; 8th Aug 2012 at 20:39.
Join Date: Aug 2009
Location: Germany
Age: 67
Posts: 1,777
Likes: 0
Received 0 Likes
on
0 Posts
Ah, but the flight control computers are not programmed with the concept of stall and to the best of my knowledge never have been.
The stall warning parameters are encoded into the annunciator system, but the flight control computers are oblivious to stall in Alternate Law - and most would say rightly so, because for the computers to be able to override the human when in a degraded state would open the aircraft's safety to significant risk if the computers get it wrong (not to mention the fact that the backlash from the Airbus-sceptic brigade would be deafening if this were the case!).
The point is that outside of Normal Law, the systems are designed to defer to the pilot's inputs - no matter what those inputs are - for better or worse. This is based on the reasonable assumption that the human pilot will have a much better ability to adapt to circumstance than the computer ever could. In this case the crew were clearly overwhelmed and not only made mistakes, but repeated the same mistakes over and over again with tragic consequences.
The stall warning parameters are encoded into the annunciator system, but the flight control computers are oblivious to stall in Alternate Law - and most would say rightly so, because for the computers to be able to override the human when in a degraded state would open the aircraft's safety to significant risk if the computers get it wrong (not to mention the fact that the backlash from the Airbus-sceptic brigade would be deafening if this were the case!).
The point is that outside of Normal Law, the systems are designed to defer to the pilot's inputs - no matter what those inputs are - for better or worse. This is based on the reasonable assumption that the human pilot will have a much better ability to adapt to circumstance than the computer ever could. In this case the crew were clearly overwhelmed and not only made mistakes, but repeated the same mistakes over and over again with tragic consequences.
In normal law (autopilot engaged or not) the automatic trim is a must and a great help in flying the aircraft (thank's also to the protections)
In alternate law .. things are not all the same
With the autopilot off (the pilot fly manually) .. alternate law says there is no more pitch protection ..
But still .. auto trim remains active
piloting in manual (pitch matter) is using the stick and the trim (the pilot is using both hands)
Not with Airbus ...
The pilot does not control the trim .. and this one continues to act as in normal law .. but then it is no longer active protection ....
To me this is a bad design .. the pilot don't control (full manual control) entirely the pitch ...
In alternate law the auto trim is not a help ... instead it's like throw a lead buoy at somebody drowning
Last edited by jcjeant; 8th Aug 2012 at 20:41.
Join Date: Jul 2002
Location: UK
Posts: 3,093
Likes: 0
Received 0 Likes
on
0 Posts
@franzl:
I know for a fact I'm neither, nor am I likely to be!
Incidentally, the "Normal Acceleration" parameter is very much present in Annex 3 of the BEA's final report - on pages 1-6.
I know for a fact I'm neither, nor am I likely to be!
Incidentally, the "Normal Acceleration" parameter is very much present in Annex 3 of the BEA's final report - on pages 1-6.
I beg your pardon, Doze, but this is what my copy of the FCOM states:
The attitude correction for the gee command ( load factor) provides an apparent "attitude" command, but it just ain't exactly the way HAL is working to "help" you. Additionally, this implementation also provides apparent "neutral speed stability". The basic aero of the jet still has positive speed stability, and positive longitudinal static stability, but HAL is trying to "help" you.
Only place I can find anything other than a gee command is in Direct Law.
show me how I am not getting my view of the control law from the text above from the FCOM.
As you, Doze, have pointed out many times, the primitive FBW system I flew back in the stone age would not be recommended for a commercial airliner EXCEPT FOR THE AoA LIMIT/PROTECTION!!! We also had a heavy AoA bias with the gear down to make the thing seem more like a "normal" jet.
Our gee command/AoA curve was designed for sustained turn rate at moderate gees - figure 5 or 6 gees. Think 25 degrees per second sustained rate with no loss of energy. And at 9 gees we got more than that for about two seconds until the AoA function kicked in - eat your heart out, heh heh.
For one more time, I iterate that I flew a no-kidding electric jet that did not have inherent static stability below 0.95 mach, yet had the apparent neutral speed stability that the 'bus has ( except when gear was down). We did not have the attitude gee correction for obvious reasons. We had no "direct law" except the manual pitch override deal when AoA was above 30 degrees and we were in a no-kidding deep stall, and that only gave us direct control of the horizontal tail. The 'bus has a lot more going for it and its pilots than the Viper, but ya gotta understand how the thing works and have some basic piloting skills.
The attitude correction for the gee command ( load factor) provides an apparent "attitude" command, but it just ain't exactly the way HAL is working to "help" you. Additionally, this implementation also provides apparent "neutral speed stability". The basic aero of the jet still has positive speed stability, and positive longitudinal static stability, but HAL is trying to "help" you.
Only place I can find anything other than a gee command is in Direct Law.
show me how I am not getting my view of the control law from the text above from the FCOM.
As you, Doze, have pointed out many times, the primitive FBW system I flew back in the stone age would not be recommended for a commercial airliner EXCEPT FOR THE AoA LIMIT/PROTECTION!!! We also had a heavy AoA bias with the gear down to make the thing seem more like a "normal" jet.
Our gee command/AoA curve was designed for sustained turn rate at moderate gees - figure 5 or 6 gees. Think 25 degrees per second sustained rate with no loss of energy. And at 9 gees we got more than that for about two seconds until the AoA function kicked in - eat your heart out, heh heh.
For one more time, I iterate that I flew a no-kidding electric jet that did not have inherent static stability below 0.95 mach, yet had the apparent neutral speed stability that the 'bus has ( except when gear was down). We did not have the attitude gee correction for obvious reasons. We had no "direct law" except the manual pitch override deal when AoA was above 30 degrees and we were in a no-kidding deep stall, and that only gave us direct control of the horizontal tail. The 'bus has a lot more going for it and its pilots than the Viper, but ya gotta understand how the thing works and have some basic piloting skills.
Retired F4;
I agree with everything you have written in your last post, but don't grasp the point you're making.
The exit of the flightpath was the failure of the crew, a following prolonged and prominent ND input could have corrected this failure in the early flight envelope extension.
I would agree even with your last quote from the Human Factors part of the BEA report, if you remove the words "an extremely purposeful".
Join Date: Jul 2002
Location: UK
Posts: 3,093
Likes: 0
Received 0 Likes
on
0 Posts
Not with Airbus ...
The pilot does not control the trim .. and this one continues to act as in normal law .. but then it is no longer active protection ....
The pilot does not control the trim .. and this one continues to act as in normal law .. but then it is no longer active protection ....
To me this is a bad design .. the pilot don't control (full manual control) entirely the pitch ...
In alternate law the auto trim is not a help ... instead it's like throw a lead buoy at somebody drowning
G command’ which is a desirable capability at high speeds, means that for a particular amount of control column force, you get (available energy permitting) the same ‘g’ regardless of prevailing airspeed. Similarly, in a pitch-rate command system, you get the same amount of pitch rate for a given control column force regardless of prevailing airspeed.
It does not describe the switching from one to the other which is happening with a C*.
When switching to the other prevailing command law it will do so also for stick neutral, i.e. it will keep pitch rate constant if SS is neutral.
Otherwise it would still be a G command law. However I'm not aware that the laws switch depending on SS deflection.
My understanding is the following:
At higher speeds (lets say above 230kts) it will keep 1 g at stick neutral and when deflecting the g load will always be the same for a certain stick position, independent of the speeds (so at 280 kts the same deflection will yield the same g as at 230kts).
Below a certain threshold (which was still quite a bit above stall speed IIRC) the law blends over to a pitch rate law. I.e. at SS neutral pitch rate is 0, thus pitch constant.
A certain deflection will always yield the same rate of pitch change once this law is the dominant one.
Last edited by henra; 8th Aug 2012 at 21:10.
Thanks, Retired, I think we are on the same page.
OTOH, I still believe the crew could have saved the day even after entering the stall. May have taken 15,000 feet, but a constant nose down command and manual trim should have done it.
The crew did not understand what was happening, and besides, "you can't stall the Airbus" mentality could have been at play.
I pray that many 'bus drivers are reading our excellent recap of the accident and all the ideas we have expressed to prevent a future repeat.
OTOH, I still believe the crew could have saved the day even after entering the stall. May have taken 15,000 feet, but a constant nose down command and manual trim should have done it.
The crew did not understand what was happening, and besides, "you can't stall the Airbus" mentality could have been at play.
I pray that many 'bus drivers are reading our excellent recap of the accident and all the ideas we have expressed to prevent a future repeat.
DozyWannabe
Incidentally, the "Normal Acceleration" parameter is very much present in Annex 3 of the BEA's final report - on pages 1-6.
Incidentally, the "Normal Acceleration" parameter is very much present in Annex 3 of the BEA's final report - on pages 1-6.
The normal acceleration in the following graph would be helpful.
http://www.bea.aero/fr/enquetes/vol..../figure.28.jpg
Join Date: Jul 2009
Location: France - mostly
Age: 84
Posts: 1,682
Likes: 0
Received 0 Likes
on
0 Posts
Its the exchange with DW and his continued saying, that the THS was driven by the NU SS input of the crew. And that is not correct, imho it had no effect at all, because only a continued SS ND input would have prevented the THS from moving NU.
Last edited by HazelNuts39; 8th Aug 2012 at 21:28. Reason: italics added