PPRuNe Forums

PPRuNe Forums (https://www.pprune.org/)
-   Tech Log (https://www.pprune.org/tech-log-15/)
-   -   AF 447 Thread No. 6 (https://www.pprune.org/tech-log/460625-af-447-thread-no-6-a.html)

MaxJack 3rd October 2011 09:07

Dear Experts
 
I have followed this thread since it started, and have tried to understand all technical terms, but I have a simple question, and, is there a simple answer?
If in a completed stall, at FL35-38, and then ”falling”. Could you recover, and if yes, how do you recover from the stall during the fall?
According to the Airbus Stall and Recovery Procedure, thrust is not an option, but could rudder settings bring it back again? And how then?
Or is there no way out, as in this case.

infrequentflyer789 3rd October 2011 09:48


Originally Posted by Lyman (Post 6730698)
Also, well before the THS acted UP automatically, the Stall would have occurred if the a/c had not been moderated by g prot. G protection (limit to 1.65+) allowed the a/c to Pitch up longer, delaying the STALL

G isn't anywhere near 1.65 apart from at the beginning of the climb - look at the traces.
If G limits kicked in, it wasn't in the stall.

AlphaZuluRomeo 3rd October 2011 10:02


Originally Posted by MaxJack (Post 6730978)
If in a completed stall, at FL35-38, and then ”falling”. Could you recover, and if yes, how do you recover from the stall during the fall?

Push the stick, thrust idle => dive.
Trade height for speed, while reducing AoA.
Then recover from the dive.

Why the rudder? Best to keep your aircraft symetrical, a spin is worse than a stall ;)

---------

About the THS & difference in normal/alternate law: we already discussed that some months ago.

rudderrudderrat 3rd October 2011 10:12


G isn't anywhere near 1.65 apart from at the beginning of the climb
Correct. That's why the stab trim was allowed to continue trimming.
In Alt Law, with side stick free - the FBW computers will continue to move the elevators whilst attempting to hold the attitude whilst the speed washes off.
In ALT2, the auto stab trim continues despite exceeding Alpha Prot / Max.
The natural nose drop at the stall is masked by the above.
The "Stall Stall" warning is all that remains but is unfortunately turned off when IAS<60kts despite being airborne.

It's going to be one heck of a Human Factors course.

airtren 3rd October 2011 12:48


Originally Posted by Old Carthusian (Post 6730837)
It is precisely a matter of knowing your machine, nothing more and nothing less. Knowing what it does, knowing what happens if the various flight states are in operation. It's really a simple thing - it's called professionalism. If the machine is complex then one needs to be able to work on a different level but one needs to prepare. It's called flying and it seems it isn't encouraged these days.

Of course "knowing your machine" is a very important element, and agree 100% with parts of the post that are about that. The training and policies failed to prepare the pilots to avoid the situation (first), and then to recover from it (second).


Originally Posted by Old Carthusian (Post 6730837)
But the aircraft is not responsible for this - the computer systems aren't responsible for this, the manufacturer isn't responsible for this. The airline is. Isn't it time to stop chasing after red herrings? The accident is the responsibility of the pilots flying and the airline which put them in the situation. It is not due to the complexity of the machine or even the interface but a failure in procedures, training, psychology and CRM. Human factors, gentlemen - focus on these.


Originally Posted by Old Carthusian (Post 6730837)
....The debate about trim, types of laws etc and whether the aircraft has an influence on the accident is sterile and irrelevant

But I disagree 100% on the parts of your post about the machine, and responsibilities associated to it, which include the procedures that only a manufacturer can develop.

The machine was brought to an extreme state, by a convergence of elements in which the machine itself, and procedures known at the time, had a complex contributing role. As a recovery from that extreme state was not successful, it was a fatal state. Such a scenario was never tested before, and the machine's behavior was not known in its totality. The machine is known better now, and the important resources spent to recover and analyze the CVR, FDR and parts of the machine were worth for that reason as well.

The procedures have been already changed. Recognizing the machine's contribution is a very important element for the improving and progress of technology, to avoid a repetition with the same type of machine, or for making new generation safer machines.

It's one of the elements that moves the technology forward. Not recognizing that would be a big failure for the technologists, for the manufacturers, for the industry.

CONF iture 3rd October 2011 13:02


Originally Posted by MaxJack
If in a completed stall, at FL35-38, and then ”falling”. Could you recover, and if yes, how do you recover from the stall during the fall?

What strikes me by reading the Airbus Flight Safety Magazine is :

It is important to know that if such a thrust increase was applied when the aircraft is already stalled, the longitudinal effect would bring the aircraft further into the stall, to a situation possibly unrecoverable.

AlphaZuluRomeo 3rd October 2011 13:13


Originally Posted by CONF iture (Post 6731304)
What strikes me by reading the Airbus Flight Safety Magazine is :

It is important to know that if such a thrust increase was applied when the aircraft is already stalled, the longitudinal effect would bring the aircraft further into the stall, to a situation possibly unrecoverable.

Indeed. And What strikes me by reading the same sentence is that a situation possibly unrecoverable is not clearly defined. Why would a situation be unrecoverable?
- Because the plane cannot recover ("locked in stall")? That's not demonstrated, and in fact AF447's FDR traces tend to prove the contrary.
- Because the plane may not have the height needed to perform the recovery, this height being larger as the stall is more pronounced/longer held? That's more how I understand "possibly", here. ;)

Lyman 3rd October 2011 13:21

In ALT LAW 2, there is no Bank limit, and it is clear that PF was focused (overly so?) on his rolling. Perhaps to the extent that he neglected PITCH. If he wanted climb (and his stick says so) he may have been eager to address the rolling. Isn't Pitch modulated by the computer? If so, that is my point, not the 2.5 g barrier, but the "comfort" g exhibited in the climb which allowed the a/c to lumber up to 38k low energy, to STALL in mush?

Had the a/c STALLED earlier, before it lost its energy, mightn't there have been a NOSE DROP, and an inescapable cue to get the NOSE DOWN?

I am not saying the PF was tuned to his a/c, but if the a/c wasn't trying to supply comfort instead of reality, could this have turned out differently?

AZR. The language re POWER and then possibility of unrecoverable flight demonstrates that the authors do not know what will happen. No harm in that, but it is crystal clear that they are comfortable in this lack of knowledge. The assumption is that all pilots will acquiesce to the instruction. Some pilots like to know WHY? Given the State of the ART it's also clear that to tell these pilots what will happen serves no purpose. There is a message in that.

CONF iture 3rd October 2011 14:04


It is important to know that if such a thrust increase was applied when the aircraft is already stalled, the longitudinal effect would bring the aircraft further into the stall, to a situation possibly unrecoverable.
AZR,
The way I see it is :
For obvious reasons a flight test cannot be risked.
AF447 was possibly unrecoverable the way the stall was initially engaged ...

airtren 3rd October 2011 14:20


Originally Posted by CONF iture
What strikes me by reading the Airbus Flight Safety Magazine is :


It is important to know that if such a thrust increase was applied when the aircraft is already stalled, the longitudinal effect would bring the aircraft further into the stall, to a situation possibly unrecoverable.



Originally Posted by AlphaZuluRomeo (Post 6731323)
Indeed. And What strikes me by reading the same sentence is that a situation possibly unrecoverable is not clearly defined....


I find too that the article and also the presentation need some refinement. The presentation - link posted also by:

Originally Posted by mm43;Post #1010 (Post 6723909)
.... Airbus power-point presentation on their revised Stall Recovery Procedure.

has some ambiguities that may lead to misunderstanding. While the "Loss of speed" for a certain AOA, is mentioned as an important element contributing to a STALL, on page 8, the text "Stall is an AOA problem only. It is NOT directly a speed issue" may be misinterpreted.

While removing the "increase of thrust" from the list of actions for "gaining speed" is understandable because of its effects for the type of engines mount, on increasing the AOA, contributing to the STALL, the "gaining of speed" is still important. It is part of the solution/recovery, and the change of AOA - bring the nose down - is a means to achieve just that. I think more clarity would be helpful, as the training should not have an ambiguity which would allow the interpretation that gaining speed when the nose is down is wrong.

CONF iture 3rd October 2011 15:32


Originally Posted by Old Carthusian
It is not due to the complexity of the machine or even the interface but a failure in procedures, training, psychology and CRM. Human factors, gentlemen - focus on these.

Why not including the complexity of the machine or even the interface in the equation ?


It is precisely a matter of knowing your machine, nothing more and nothing less. Knowing what it does, knowing what happens if the various flight states are in operation. It's really a simple thing - it's called professionalism.
I wish it would be that simple - Unfortunately the complexity involved makes it is not.


the manufacturer isn't responsible for this
What to expect when a Manufacturer puts on the market a product that's supposed to correct the pilot's errors to the point that its designer publicly announces that even his housekeeper could fly it ... ?

Lyman 3rd October 2011 15:41

On a more concrete note, I still have yet to see the timing of the PF's stick for duration that would not invigorate the Trimmable Horizontal Stabiliser. Offered as proof is the mere statement that "The THS didn't trim because the stick did not linger in NU long enough."

I'm calling bs........ Anyone?

Does some neutral party want to index the SS for duration/trim activation? Because if the THS did not move, and the SS commanded its action, what held it back? G? LAW?

Old Carthusian 4th October 2011 07:12

CONF iture
Quote
'Why not including the complexity of the machine of even the interface in the equation'

Because knowing your machine enables you to deal with its complexity. A level of professionalism is necessary. It is, in fact, a dangerous illusion to regard more modern computerised aircraft as more complex. In fact older aircraft were often the more complex requiring more attention and work. As technology has developed aircraft have in fact become simpler. Certainly aircraft can become even simpler but one cannot attribute what happened to the interface or the complexity of the machine. And if you pause and think how many A330s are flying and how many hours they have flown one cannot call these overly-complex machines. An overly-complex machine could not have survived for such a long time.
We have an aircraft which by all accounts flies well without protections. In fact those who've flown it state that it is one of the better ones to fly manually. We have a culture (that of Air France) in which a certain casualness has developed (an Air France safety audit identifies this). We have certain incidents involving Air France crews which seem to indicate a lack of knowledge of how to handle their aircraft. Putting a machine into an extreme situation then blaming the machine because it is operating outside the parameters it was designed for is futile. The PF put his aircraft into a state where it could not recover. It wasn't the machine that produced this situation but the humans. Understanding why they did so is the important factor here.
As things get safer and we develop more protection against danger paradoxically the danger increases. Humans tend to react to safer situations by dropping their guard. They do not act with caution and thus they pay less attention to safety. This is where training, CRM, culture and psychology all come into play. This is why knowing the machine and professionalism are so important. Remembering that you are responsible for more than one life. But all of this is to do with the people who operate the machine and their responsibility.

AlphaZuluRomeo 4th October 2011 10:01

CONF iture
Indeed, "possibly" as in "not demonstrated, and will not be either way". :D

airtren
the "gaining of speed" is still important. It is part of the solution/recovery, and the change of AOA - bring the nose down - is a means to achieve just that.
Uho... Perhaps is the procedure not perfectly written. On the other hand, I disagree when you write "the change of AoA is a means to achieve a gain of speed" (if I understood correctly?)
It's the other way : the gain of speed is a mean to lower AoA (all other parameters equals). And lowering the AoA is what is important to avoid/exit a stall.

DozyWannabe 4th October 2011 11:07


Originally Posted by CONF iture (Post 6731532)
What to expect when a Manufacturer puts on the market a product that's supposed to correct the pilot's errors to the point that its designer publicly announces that even his housekeeper could fly it ... ?

Here we go again. Once more with feeling, and hopefully for the last time.
  • Bernard Ziegler was not the "designer" of the A320, though as Engineering Director at the time he did have final sign off
  • The flight characteristics and systems functionality were tested and signed off by Gordon Corps, the archetypal "pilot's pilot" and successor to D.P. Davies at the ARB
  • "Correct[ing] the pilot's errors" is only one aspect of Normal Law, another important one being that a pilot can safely fly close to the design limits of the aircraft
  • As daft as the statement looks in hindsight, Ziegler didn't say anything about his concierge being able to land the aircraft or handle it in a degraded state
  • If the people still holding on to this nonsense as some kind of affront to the piloting fraternity would let it go (after all it did happen 24 years ago), then discourse would be a lot easier

Lyman 4th October 2011 13:17

Aviation owes its remarkable record of safety in one area.

One: Powerplant. Complexity existed because mechanical solutions could not keep up with how basically simple actual flight is. The Turbine and then the Fan made aviation wicked safe. The question we avoid, the Rhinoceros in the room: Why is it not much safer?

I submit that the actual flight control arena is a Straw man. 447 demonstrates this elegantly.

Carthusian is thus absolutely correct, imo.

Training? Skill? What about the rampant myopia present here on this thread?

AB have crafted for themselves a politically effective position of Carte Blanche from criticism.

With an arrogant ignorance of how simple the machine actually is, and not actually sophisticated as it is presented, they feign "misunderstanding" or "ignorance" on the part of the operator, as always, it is a fact.

It is indeed a machine that is safe and dependable. What is galling is the remarkable stubbornness they display when confronted with obvious blunders in its programming. These blunders include the attitude it takes to reactively defend them.

CONF iture 4th October 2011 15:15


Originally Posted by Old Carthusian
It is, in fact, a dangerous illusion to regard more modern computerised aircraft as more complex.

To the contrary, IMO, the illusion is to regard them as less complex.


We have an aircraft which by all accounts flies well without protections.
Exactly my point.
Cut down in the protections then, they are the ones to bring the over complexity you are not ready to look at.
An even better product will emerge.

If you're not ready to look in that direction as well, I’m afraid you miss a point.
It is a bit like Ziegler who doesn’t want any to touch its baby – It has to be all pilot’s fault :

http://www.crashdehabsheim.net/Films...emoignages.wmv

CONF iture 4th October 2011 15:24


Originally Posted by DozyWannabe
Bernard Ziegler was not the "designer" of the A320, though as Engineering Director at the time he did have final sign off

Bernard Ziegler will be glad to see you did finally promote him from sales department to Engineering Director, not after initially pretending he was not even an engineer at that time.

I hope that in your job or life when you put your mark at the end of a document you’re conscious on your involvement ...

Like it or not, Bernard Ziegler is still the father of the 320, and don’t take it too personal if he said stuff you disapprove.
Who’s talking about feelings …

DozyWannabe 4th October 2011 15:52


Originally Posted by CONF iture (Post 6733212)
Bernard Ziegler will be glad to see you did finally promote him from sales department to Engineering Director, not after initially pretending he was not even an engineer at that time.

The role he played in the actual specification and design was minimal, as you well know. He signed off on things, maybe did some arbitration - but that's about it.


Like it or not, Bernard Ziegler is still the father of the 320, and don’t take it too personal if he said stuff you disapprove.
That's denigrating Captain Corps' role more than a little, and the only reason more don't know about him was because of his untimely death in 1992.

BZ is the "father of the A320" in the same way Bill Gates is the "father of Windows" - it may have been his name on the press releases but the work itself was delegated.

Like certain other posters, you're fighting 24-year-old battles, which frankly makes you look a little ridiculous. This is about AF447, not AF296 - and there is no evidence - none - that complexity, whether perceived or real played any part.

The Airbus FBW design is here to stay - why can't you get over it?

[NB. If the protections were gone, your hero Asseline would not have been alive to lie about the aircraft in the first place. ]

airtren 4th October 2011 16:02


Originally Posted by AlphaZuluRomeo (Post 6732741)
airtren
the "gaining of speed" is still important. It is part of the solution/recovery, and the change of AOA - bring the nose down - is a means to achieve just that.
Uho... Perhaps is the procedure not perfectly written. On the other hand, I disagree when you write "the change of AoA is a means to achieve a gain of speed" (if I understood correctly?)
It's the other way : the gain of speed is a mean to lower AoA (all other parameters equals). And lowering the AoA is what is important to avoid/exit a stall.

Your rephrasing of my text is still in line with what I meant, in the context of the presentation, so I will explain from a different angle. I will use material from that presentation, as what I referred to was in its context:

The change of "AoA" affects the lift coefficient CI, according to the

CI curve, as a function of AoA. (page 5 of that presentation).

The CI is a member of the "lift" equation - see bellow - and thus it affects the "lift":

Lift = 1/2 pSv**2Ci, (page 4 of that presentation)

(where: p = air density, S=wing surface, v=CAS, v**2 is square of CAS, Ci=lift coefficient)


Examining just from a pure Mathematics perspective, given that the S is a constant, the other two elements that affect (and will increase) the "lift" are the "p" and "square of v" (if they increase).

Furthermore, if theoretically and abstractly one can assume that AoA does not affect speed - so the speed stays constant - as CI cannot go above a Maximum Value, one may try to change AoA as much as he wants, but that (Max) CI, with an insufficient "v" (speed), and insufficient "p" may still result in insufficient "lift" and thus no return to normal flight.

So my point again is that the change of AoA affecting the CI alone, may not be sufficient to cause the return to normal flight.

It is rather the combined effect of the AOA on the CI, with the AoA effect on increasing the speed and thus the "square of v" that from a possible "speed" insufficiency in a "insufficient lift", to a "sufficient speed", which by resulting in a sufficient "lift" makes the a/c return to normal flight.

I can understand why the written presentation may attempt to reduce the aspects of recovery from Stall that may be look too acrobatic, because of the drastic changes of speeds, and altitude. But I can see how the verbal communication during the presentation, or a training session may be very explicit on the dramatics of the change of AoA to aggressive Nose Down, and letting the a/c in a Nose Down fall to gain sufficient speed, to change the AoA again, to level off, and transform the falling speed into horizontal speed, get sufficient "lift", to get to normal flight.

....

You say, the "gain of speed is a means to lower AOA".

I don't see how the "gain of speed" has necessarily a "lower AoA" consequence. Perhaps your elaborating would help.

airtren 4th October 2011 16:57


Originally Posted by Old Carthusian (Post 6732544)
CONF iture

...It is, in fact, a dangerous illusion to regard more modern computerised aircraft as more complex. In fact older aircraft were often the more complex requiring more attention and work. As technology has developed aircraft have in fact become simpler.

In general - and thus independent of specifics pertaining to a certain manufacturer - the modern/current airplanes are hugely more complex, and there is a lot more work and attention than before when summing up all the work and attention on all the components packed into one airplane.

That more complexity and that more work and attention may not be obvious to a casual observer, but it is there, even if hidden by the huge reduction in electronics components dimensions, huge advance in electronics integration, and modularization, or by the physical character of the components - software - and the stages and different areas, disciplines, R&D, development or manufacturing facilities in which the attention and work is performed.

RR_NDB 4th October 2011 17:43

K.I.S.S.
 
Hi,

aitren:

the modern/current airplanes are hugely more complex
:ok::ok::ok:


And despite this immense complexity the basic is the same:

When the plane degrades (by any reason) you need:

1) Feel it
2) Aviate it (the same for all models)

And this requires a SIMPLE THING: Known your machine in it's basic config.


may not be obvious to a casual observer
A Professional knows everything related and involved in his mission, specially when Murphy Law acts.

BOAC 4th October 2011 17:43

Not quite sure how we got to the lift equation in a thread about loc, but I think there may be some confusion growing here between a 'stall' and 'insufficient lift' for flight which can be two completely different phenomena.

SandyYoung 4th October 2011 20:13

"father of Windows"
 
DW,

A minor point - Windows appeared on the original Apple Mac well before Bill G. was involved. IIRC it was on the Apple Lisa before that.

I'm told the mouse part of the WIMPs interface (Windows, Icons, Menus and Pointing devices) was a spin-off from a Xerox trackball used in missile guidance well before the Mac.

I mention this only because MS and IBM are often given the credit for the PC. They were well behind.

DozyWannabe 4th October 2011 20:15

@SandyYoung - hence the capitalised W in "Windows" (implying the product, not the concept). Xerox invented it, Apple nicked it, Microsoft copied it - but the best early implementation was Workbench on the Commodore Amiga. Anyway - back to the regular scheduled programming...

gums 4th October 2011 20:54

Power outta a stall? Speed versus AoA?
 
Thanks, BOAC. ANd speed is a huge part of the lift equation, like a "squared" component.

So if I hold the same gee ( read lift you can feel in wings level flight), and I increase speed, then I can use a lower AoA for the same amount of lift.

Lowering AoA is the faster solution - get outta the part of the Cl curve that shows less lift and you also reduce induced drag. And for those jets with the underslung motors, adding power is not a good idea in some cases due to the nose up pitch moment.

For the swept wing jets the induced drag is a lot more evident that in the straight wings. The deltas were the worse ( or most low aspect ratio wings), then the good wings we developed in the 70's and 80's had much more gentle stall entries and less buffet and better directional control at high AoA. This is an insidious feature of the better wing designs we now have that may have contributed to the AF447 crew's failure to recognize their state and take appropriate corrective action. The lack of a good AoA indication also comes into play. That string taped to the side of the cockpit window would have been more helpful than the ambiguous stall warnings and such that the crew dealt with.

After talking with several folks here offline, I am suspecting a management influence on all the "laws" and "protections" and Otto functions versus "neat" features that the pilots demanded. The jet appears to be very well designed and easy to fly even with all the "old" mechanical/hydraulic control systems. And that is what bugs many of we old dinosaurs. I can't speak for all of us, but I would guess we would all like a very clear control system implementation we could hang our hats on when all the Otto functions and bank angle limits and pitch angle limits and such go away.

If we, the SLF, wish to have "systems managers" up front versus folks that can fly the jet with little "help", than I'll cease to be SLF. Scares the hell outta me.

Lyman 4th October 2011 21:11

In no other a/c but the A330 is it more important to isolate NORMAL LAW from everything else. The type is trained to NL, and there is a disconnect in making anything except NORMAL LAW available in emergent or off standard flight path.

Except basic aero. Basic. It is counter intuitive to think other Laws in some sort of descending order will be helpful in an odd, or rare condition.

The a/c is dependable enough to eliminate the need for anything other than DIRECT LAW in such circumstances... Nothing but trouble if Pilots have to remain current in several ways to approach unusual conditioons.

As we see here.

DozyWannabe 4th October 2011 21:16


Originally Posted by gums (Post 6733727)
After talking with several folks here offline, I am suspecting a management influence on all the "laws" and "protections" and Otto functions versus "neat" features that the pilots demanded.

And at least one who told you there wasn't any. *All* the functions went throug hthe engineering pilots.


If we, the SLF, wish to have "systems managers" up front versus folks that can fly the jet with little "help", than I'll cease to be SLF. Scares the hell outta me.
That is press-fuelled garbage - I guarantee you no-one from Airbus ever said pilots should be no more than "systems managers".

AlphaZuluRomeo 4th October 2011 21:17


Originally Posted by airtren (Post 6733284)
Your rephrasing of my text is still in line with what I meant

Thanks for confirming it :)


Originally Posted by airtren (Post 6733284)
So my point again is that the change of AoA affecting the CI alone, may not be sufficient to cause the exit from Stall.

:confused: :confused:
As for the maths: I'm sorry, I'm not fond of maths, I must say. Logic is enough to me :)
For that reason, I won't comment on your formula.

You may be unstalled (i.e. your wing is flying, producing lift & allowing control) but not have a CI big enough to support your weight. Then, you're descending. But no more stalled. :ok:


Originally Posted by airtren (Post 6733284)
You say, the "gain of speed is a means to lower AOA".

I don't see how the "gain of speed" has necessarily a "lower AoA" consequence. Perhaps your elaborating would help.

I wrote : "the gain of speed is a mean to lower AoA (all other parameters equals)" (my underlining)

Reverse: For the same velocity vector, your AoA is lower if you fly quick than if you fly slow.
That's why I wrote that if you fly quicker, you'll lower your AoA. Note that it was the spirit of the (now discarted IIRC) "approach to stall" procedure: To escape "falling" into an actual stall with more speed ; Without loosing altitude (<= maintaining the (level) velocity vector)

My point is : Speed is a consequence. AoA is what matters.
If stalled (or nearly stalled), you must lower AoA, be it by altering flight path (velocity vector => push the damn stick) or by gaining more speed (*)
The former is more efficient, as pitch control is a direct AoA control. That doesn't mean a bit more speed won't help: it will. But what you seeks, ultimately, is not more speed but less AoA.

(*) which, as shown above, will allow you a lesser AoA for the same flight path, or a higher flight path with the same AoA.

airtren 5th October 2011 12:41


Originally Posted by AlphaZuluRomeo (Post 6733762)
...
As for the maths: I'm sorry, I'm not fond of maths, I must say. Logic is enough to me

The beauty of it is that it can embed a certain logic in an abstract way in an equation, allowing reference to the logic, or its elements, just by way of referring to the equation, and its elements...


You may be unstalled (i.e. your wing is flying, producing lift & allowing control) but not have a CI big enough to support your weight. Then, you're descending. But no more stalled.
Exactly!

My point is : Speed is a consequence. AoA is what matters.
The explanation helped seeing that I've missed your implicit reference to the speed vector's scalar (magnitude) as a constant element, with the changes of the vector's direction coinciding with the AoA changes, and vector axial components changes.
With the rephrasing, I think we're in sync (unintentional rime). :)
The "speed change” I was referring to “is a consequence of change of AOA" , with both energy conservation and momentum conservation playing their roles.

CONF iture 5th October 2011 14:57


Originally Posted by DozyWannabe
Also, CONF is a long-time hater of everything the 'bus stands for, so of course he's going to say that.


Originally Posted by DozyWannabe
If the protections were gone, your hero Asseline would not have been alive to lie about the aircraft in the first place.

Once again, behave your comments DozyWannabe.

That I look "little ridiculous" in your eyes is OK to me.
If you are at the end of the rope for your argumentation, I cannot help you.

Lyman 5th October 2011 16:01

Sorry, who was Asseline employed by? What was his rank in the company?

'Reality' is a boulevard with a reciprocal. It cuts both ways.

The company beverage at Airbus is 'KoolAde'...tm

jcjeant 5th October 2011 19:45

Hi,

And another news (transparency and credibility .. we said .. ?)

Rio-Paris: l'Agence européenne de la sécurité aérienne a-t-elle quelque chose à cacher ? - Libération

Google Traduction

VGCM66 5th October 2011 23:01

Air France Flight 447 Crash Probe Shows Confused Crew, Misread Instruments - Bloomberg

jcjeant 5th October 2011 23:08

Hi,

I just made a little review of the French press this past October 5 dealing with the matter of legal side AF447
I think that I am right in reckoning that the process will be in 10 or 15 years (St Odile and Concorde style) and no doubt many players will disappear naturally before those days (even the "experts") and everything will be already a "souvenir" in the shadow
It goes without saying that this does not show the famous independence .. the famous transparency .. the famous search for the truth .. very credible to the general public

AlphaZuluRomeo 5th October 2011 23:21

airtren
We're on synch indeed. :)
Except perhaps re-the beauty of maths, but it's a religious matter for me (joking).:p

jcjeant
How interesting! Let's hope the "technical constraints" may be soon solved...

infrequentflyer789 5th October 2011 23:26


Originally Posted by Lyman (Post 6735039)
Sorry, who was Asseline employed by? What was his rank in the company?

'Reality' is a boulevard with a reciprocal. It cuts both ways.

Asseline was AF, just like crew of 447.

Rank ? Not sure, but I have seen at least one reference to him being (ironically) one of those who were consulted by Airbus in the flight control system design. Since there are some here who believe Airbus didn't consult pilots on the design... that would imply Asseline was not a pilot.

infrequentflyer789 5th October 2011 23:42


Originally Posted by jcjeant (Post 6735372)
Hi,

And another news (transparency and credibility .. we said .. ?)


I wonder what severity Airbus suggested for the issue. If regulator overruled them and downgraded it, that might even let Airbus / Thales off the hook for the pitots.

infrequentflyer789 5th October 2011 23:47


Originally Posted by Lyman (Post 6733754)
In no other a/c but the A330 is it more important to isolate NORMAL LAW from everything else. The type is trained to NL, and there is a disconnect in making anything except NORMAL LAW available in emergent or off standard flight path.

You should at least be referring to the range of Airbus models, which all (since A320) have same modes.

Also, so does Boeing (777, not sure on 787 but believe it is the same). Secondary mode on 777 is very similar to alt law on bus - still the same control laws but no protections (which on 777 are "soft" only and operate through the artifical feel). 777 also has direct mode too.

wozzo 5th October 2011 23:50

I think there is some new information in that report:


“I’ve lost VSI,” the junior co-pilot said of the Airbus’s vertical-speed indicator, according to a recording detailed in the report from court-appointed experts. In fact, the instrument was functioning normally, its analog needle immobilized at the lower limit because the plane was hurtling toward the ocean at 15,000 feet a minute, the document seen by Bloomberg News shows.
Makes horrible and sad sense: misinterpretation of VSI => no knowledge of losing height fast => unaware of stall => misinterpretation of ambient noise as overspeed.


All times are GMT. The time now is 09:30.


Copyright © 2026 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.