Machinbird

IAN-W, excellent post. It fits well with the aerodynamic noise.
Alcorfr, very sad and totally believable. With warnings all over the place and funky airspeed indications, you grab for cues wherever you can, but your interpretation of what you are perceiving, although intuitive, can be very incorrect.

The source of noise is probably the air rushing by the fuselage itself and becoming turbulent around the crown of the aircraft.

But that does not explain, the initial nose up leading to a stall.

gums

Saw a post from A33Z about this:
Nuts cracked the "nut" with this:

Why does the system, not the pilot, try to maintain an AoA that is not necessary?

If the "protection" limit is "x", no problem. But the system should strive to achieve the trimmed gee ( one gee for the 'bus", as the pilots can't trim for a gee as in the other FBW system that has over 4,000 jets flying in dozens of countries) ? Pilots input commands other than one gee, to the limits, but the jet should not insist upon flying at the alpha-prot value, which is higher than necessary for most flight conditions. In that "other" jet, if you relaxed stick pressure, then it tried to achieve the commanded gee, not the alpha.

The alpha-prot should be a "limit", and not a "command" from the system.

I continually bring up "that other jet", as there are thousands more than the Airbus flying and thousands more pilots flying it. The number of LOC incidents due to sensor failures and system failures is down in the noise level considering the thousands of flights each day for the last 30 years.

just more thots .....

grity

thank you very much PP, it needs only quite a few weaks for me, since I tried to understand the zoom climb of the AB 340, to found my question for the elevator deflection convention...... every time wondering why a pull generates lower G, and a push ends in a climb..... every thing is opposite!

http://www.aaib.gov.uk/cms_resources...%2006-2001.pdf

RR_NDB

infrequentflyer789, Please refer first to my post here made when answering to A33Zab

Why not to have before (Laser AS meters*) hotter Pitotīs?

Not necessarily as i am sure you know. IMHO A and B are wrong in this important design aspect.

I will provide a hint: Redundancy works when you have elements failure. AFAIK the Pitotīs in all registered UAS cases didnīt fail. The parts (P/N#) were used in the subsequent legs/flights.

(*) Airbus SAS filed patent(s) on that as showed and posted earlier.

I am not against A or B. IMHO there is a wrong application of the Redundancy Concept for a very important parameter, the AS.

macdee

On the Airbus what are the indications to pilots that the cg has moved aft? What would be the normal for the routine fuel balancing during flight,is it on a time/distance basis .Would/could this have contributed to the extreme nose up if 'tail heavy'- I believe 29% was mentioned in long ago posts.
How would this be indicated.

Thank you.

thermalsniffer

Assuming they thought is was an overspeed situation. Why select TOGA thrust?

sensor_validation

Rhetorical question I guess but altitude also rose above 'the maximum cruising level displayed on the Flight Management and Guidance System (FMGS)' = FL360+1000ft. So I believe the aircraft was below a speed where it could maintain steady level flight which is one definition of 'stall speed', recovery required 'flying the ballistic trajectory' keeping the nose pointing the right direction to avoid an aerodynamic stall, which was successfully received in the A340.

My calcs give peak FPA around 8 degrees, so it does all add up. Interesting thought exercise - what would have happened if pilot didn't recover Normal control?

A33Zab

The answer might be in your question...........Heating ~120° C, selfregulating heater, 115V AC.

How much hotter should it be? +1 or red hot, temperature just below pitot meltdown?
What about surrounding Alu. skin if it gets heated on and off?
If you're a technician so should now. Buckling in RVSM clean area? Skinfailure due increased aging?

Not only A and B are using Pitots as measuring equipment, C thru Z are using the same, in general simple but effective system, operating flawlessly 99% of the time.

Linktrained

Hand flying Yorks, only 60 years ago, when the Captain went aft to where the toilets were situated, as the F/O hand-flying, I found that it was easier to get the aircraft to fly "on the step" with an increase of perhaps 1 or even 2 kts. IAS. When the Captain returned, the speed reverted.
Our A/Ps seldom worked and when they did they would often pump the elevator about 30 to 40 times a minute, causing our SLF to use a paper bag, while they enjoyed (?) the PURR of four Merlins.

An earlier thread suggested that S/S were very sensitive controls. Do pilots ever hand fly at cruising level? Another thread implied, if I read it correctly, that "our company forbids this."

There have been a number of references to other sources of information, like Davies' HTBJ. There may be some help to be found in D.Beaty's "The Human Factor in Aircraft Accidents." ( Published in 1969 - aircraft may have changed but not humans !)

Ian W. says #565
"... fly the aircraft..." Just as true today as it was 60 years ago, when we learned that someone had tried to do something else in bad weather...

HazelNuts39

Not rhetorical at all. Stall speeds are determined power off. The ability to maintain level flight is not part of the definition. Nothing in the report indicates the airplane went below Vs1g.
Interesting indeed. I think a simulator exercise or computer simulation is needed to answer that question. EDIT:: The airplane ultimately probably ends up in 1g flight at a speed corresponding to alpha-prot, descending or climbing depending on the thrust that has been set. It will probably do that in a phugoid (oscillatory) motion. How it does that can be established in a simulation. The important thing is: it won't stall before the pilots have finished their coffee, IMO.

Machinbird

What we need for airspeed measurement is a diversity of methods. Even if new technology is less robust than the pitot concept for measuring, you will be less likely to get common mode failure which is the real Achilles heel for the pitot tube systems.

Turbine D indicated that you can also get data from the engines that will be useful to infer airspeed. (The engines need to know their operating dynamic pressure too).
Since the engines have fans at the front end that may sling ice and in any case will have a different environment than a naked pitot tube, this may provide part of that airspeed diversity.

The laser airspeed systems seem to be on the verge of availability for operational use. Someone just needs to decide to build a design using them. Then we will have at least 3 levels of diversity.

Having one pitot running hot may also provide some diversity, but this may have some problems with pressurization of the system through vaporization of moisture.

These approaches all take engineering study and imagination in implementation.

HazelNuts39

Since the problem may be caused (in part) by heating (ice particles clinging to heated surfaces), maybe cycling the heat (as ice detectors do) is an option to consider?

PJ2

Ian_W;

While I don't disagree that cognitive overload can and does occur (we can experience it in a demanding simulator exercise just as it may be experienced in the aircraft under a series of cascading failures resulting from a primary system failure), I want to offer a slightly different POV.

My bolding in your quoted passage:
Not just "perhaps", but without doubt, that is the key requirement in an unreliable airspeed event.

Rather than saying "disregard all those messages as they aren't important", let me put it another way: "Look through", all those messages while establishing stable flight. "Note and absorb", but do not be distracted by all those messages.

It is not that they are not important. It is that they are far less important than establishing and maintaining stable flight.

This is what I have always meant by stating that, "doing nothing" while taking over and flying manually to wait for the situation to stabilize, is an appropriate response. Such a calm response gives oneself a chance to absorb what's happening.

To emphasize as strongy as possible, stabilizing the situation to ensure the continued safety of flight is primary - the ECAM messages, (none of which required a memory drill) can wait.

Executing the UAS drill memory items as written in the UAS drill and checklist is the way to maintaining the primary goal of stable flight. That kind of crew response is NOT stated in any ECAM message or aural warning. It is (hopefully) trained for just as other memory responses are trained and checked for.

I will not say that the checklist is without its problems. It has been modified a number of times since its appearance in ~2002. I have said before and will say it again here: The UAS drill and memory items are confusing and that is a "support" factor, ('support' meaning well-written drills, checklists and procedures), which may even be relevant to this accident.

The aircraft was under control before the UAS event, pitch and power set for stable flight, notwithstanding some turbulence and a possible change in TAT.

A loss of airspeed information does not change that state. Without airspeed information the aircraft is still under control.

It will remain under control so long as that stable relationship between pitch and power and the resulting stable AoA, is not substantially altered.

Again, to emphasize, providing this stable state of affairs is maintained by the crew the series of ECAM messages, aural warnings, autopilot/autothrust disconnections does and will not change this state of affairs.

Putting it another way, stable flight is not affected by the ECAM and aural series of messages and warnings, provided pitch and power settings are set, by all means available and necessary, to maintain stable flight.

An unreliable airspeed event would be no time to make large changes in pitch or power.

The Airbus and Air France memory drill and checklist for UAS, (reproduced below for reference) which was in force at the time is cited in the First BEA Interim Report.

If safe conduct of the flight is not impacted, the UAS memory drill items do not require any immediate action by the crew when the aircraft is in stable cruise flight. The checklist requires that the aircraft be "leveled off for troubleshooting". That troubleshooting is to set pitch and power to initial settings and, under "Flying technique to stabilize speed" in the UAS checklist section, watch the results for deteriorating trends and adjust either/both accordingly.

Any departure from stabilized flight immediately takes the crew away from "known, stable circumstances". Eliminating the "knowns" makes returning to stable flight a difficult but not impossible task but one must set pitch and power according to the QRH very quickly to avoid true disorientation not in pitch attitudes or power settings but in terms of the energy state of the aircraft and returning the aircraft to pre-event values.
I address this point above, but it requires elaboration. It is not as though the designers and engineers didn't think these messages were not important, because of course they were/are.

Let us consider that there are other ways of seeing this and not just an "either/or", (as in, "either they were important or they were not"). The ARE important. But flying the airplane is THE most important priority and no designer or engineer would disagree. The airplane is not on fire, it is not depressurizing, it has not had an engine fire or failure and at the start of the event it is stable, with lots of energy. There is no "emergency" here.

So I don't think the implication (that the messages were 'unimportant'), applies in this accident.
It is not as though we dismiss the difficulties faced by this crew by setting the events they faced on timelines from which we then "armchair" our views.

I don't think any of us here doubt that these factors will indeed have been "at work" to some degree in this cockpit. But it is slowly being forgotten in this line of thought in the thread that aircrews are heavily trained, checked and otherwise supported by a very large infrastructure and are not "on their own" when it comes to dealing with such events.

Attending to surprise is not an unaddressed, foreign cognitive phenomenon in this industry. Intense training is the way a form of cognitive dissonance is addressed. This doesn't deny the normal, immediate human reaction to an emergency but when such circumstances occur, the crew is not on their own and that level of response is precisely the intended outcome of training and checking.

In other words, a crew's response to an emergency does not "begin in the cockpit" - it starts a long way upstream, the entire goal being the reduction of cognitive surprise and distraction.

The UAS drill and checklist cited earlier is reproduced below. I and others have discussed this checklist at length, mainly on the previous AF447 threads.

The first memory item is a requirement to assess the safety risk to the aircraft. This is a "bifurcation point", an if-then point which bifurcates to two different course of action. The two courses of action available are the listed items under MEMORY ITEMS in the box and the dot-pointed item, "To level off for troubleshooting".

The Memory Items in the box require that the autoflight system (including flight directors and autothrust) be turned off and then pitch and power settings be established depending upon at which point the aircraft is in the takeoff/climbout sequence. These are emergency settings which are intended to keep the aircraft out of immediate danger close to the ground.

If the safe conduct of the flight is not impacted then the other memory item is "To level off for troubleshooting". The memory items there require that the GPS Altitude be displayed on the MCDU, and that the autoflight system and autothrust be disconnected. The pitch and power settings are then listed for initial level off.

The appropriate settings indicated in this checklist for the "CLEAN configuration are: FL 200 - FL 360" > 260kts > 3.5deg pitch and 71.9% N1 in this A333 checklist. The A332 checklist (in French in the BEA Report) states "FL 250 - FL 370 > 260kts > 2deg pitch & 83.9%N1). The processes are the same regardless of individual aircraft settings.

Once the aircraft is stabilized in level cruise flight, the ECAM items would be dealt with.

The time frame under examination here is between the initial UAS event and the pitch-up event. Once the aircraft was at the apogee and in a partially-ballistic trajectory, with the aircraft pitched up at 16deg, the AoA rapidly increased as the aircraft started down establishing the stall, the aircraft was essentially doomed. There are discussions about stall warnings, THS positions and so on but at what point do we demand that the designers and engineers "protect" against such operations, without creating a host of further, unanticipated, possibly serious problems in different circumstances?

There are arguments which claim that "the computers" pitched the aircraft up, beyond the control and intentions of the crew. Despite some very interesting arguments which have demonstrated the possibility, I doubt if automated flight (the EFCS) per se, was involved in the initiating event.

If the sidestick was unintentionally moved so as to strongly pitch the aircraft up and it was permitted to exceed a pitch of 10deg and a rate of climb of 7000fpm without added thrust, and with only a few mild ND sidestick inputs, as has been observed by others who know their stuff, the swiftly approaching outcome would be blindingly obvious to any aircrew - a huge loss of energy and an inevitable rapid descent in some way or another, (stalled or high speed and a lot of altitude lost).





The notion and activity of "blame" is irrelevant at the level of this discussion intends.

In this accident we simply cannot look to the crew alone, (if at all). As we all know too well, they did not set out to "have an accident" yet an accident occurred.

A form of cognitive dissonance in heavily demanding and distracting circumstances may be one of many (initial) human factors involved in this accident but the investigation will certainly not be stopping there.

A33Zab

Why does the system, not the pilot, try to maintain an AoA that is not necessary?



HIGH ANGLE-OF-ATTACK (AOA) PROTECTION
High AOA protection enables the PF to pull the sidestick full aft in dangerous situations, and thus consistently achieve the best possible aircraft lift. This action on the sidestick is instinctive, and the
high AOA protection minimizes the risk of stalls or control loss.
High AOA protection is an aerodynamic protection:
• The PF will notice if the normal flight envelope is exceeded for any reason, because the autopitch trim will stop, the aircraft will sink to maintain its current AOA (alpha PROT, strong static stability), and a significant change in aircraft behavior will occur.
• If the PF then pulls the sidestick full aft, a maximum AOA (approximately corresponding to CL Max) is commanded. In addition, the speedbrakes will automatically retract, if extended.

Idle Thrust

PJ2 - you have been rather quiet here of late but your post above was well worth the wait. Well said sir!
IT

Peter H

A33Zab
Not only A and B are using Pitots as measuring equipment, C thru Z are using the same, in general simple but effective system, operating flawlessly 99% of the time.

Agreed, but occasionally liable to common-mode failures.

Besides working (or not), a pitot could provide an indication of its operating temperature. [Earlier posts have stated that the heating element has thermistor-like properties.]

It would seem sensible for the temperature to be monitored, and a severe-weather warning issued when it goes outside normal limits. Indicating the increased likelihood of common-mode pitot failures.

Note that does not require a new pitot design, simply monitoring the voltage and current. Obviously trials would be needed to see how far the temperature of a pitot experiencing high-altitude icing differs from that during extremes of normal operation.

HazelNuts39

Ian_w and PJ2;

With all due respect to you both, I cannot fully agree with your views. In my view, disregarding ECAM messages has to do with setting priorities and the different roles that PF and PNF have at times of crisis.

I believe the prime motivation for "pitch and power" does not lie there but in flight dynamics. A string of incidents and accidents in the early years of jet transport operations led to the insight that chasing airspeed and altitude in turbulence very quickly leads to combinations of pitch and power (e.g. high pitch, low power) at which the airplane is very vulnerable to the next gust, frequently leading to loss of control. It was quickly realized that the better strategy is to concentrate on maintaining a safe combination of pitch and power, while allowing airspeed and altitude to float (within limits, of course). Since that became standard practice, the frequency of those events dropped dramatically. In my perception, the often abused term 'coffin corner' really belongs to those early years.

CONF iture

A33Zab,
Reading the Perpignan report, I have learned that for the 320, electric stop and mechanical stop for the THS were different.
Does it also apply to the 330 ?
Could it be that the electric stop is at 13 degrees UP ?

A33Zab

Described monitoring is task of the installed Probe Heat Computer (3x)

I realize these probes failed (iced up) more on A. than other A/C recently, while there only few suppliers (also GOODRICH had problems on these A/C).
The same design was used from launch to let say 10 years of operation without -major- problems.

So what is changed? Environmental issues, seeking the limits due operational demand, lack of training or taking more risk because sophisticated weather radar is installed nowadays?

A33Zab

No, not that I am aware of.
It's nowhere mentioned in the manuals.

On ground Autotrim is disabled (Ground Direct Law) so we are unable to simulate.

IMO the THS was arriving @ 13 Up when all the speeds went off (02:11:50) due hi AOA (40) and (15 Pitch) = (60* degrees on pitot mouth) and therefore PRIMS cancelled any further THS command. (DIRECT monitoring??)

* Even a few degrees more because pitot is pointed some degrees above horizontal.