![]() |
DW I feared going into those kind of terms would cause folk to start dozing off.. |
Strictly speaking AoA and Cl are reciprocal functions of each other - i.e. a change in one will result in a change in the other. Agreed - but because of the relationship between AoA and Cl and the V(elocity) component of the Cl calculation there is an indirect relationship between airspeed, thrust and AoA - that's all I've been saying. But there we get into the quasi-religious aspect of pilot authority. While it would be possible to do such a thing, those who consider the Airbus FBW and modern FMS as a step too far* would likely kick up a hell of a stink. PS: It's getting late and I need to check, but I seem to remember that the stall warning AoA already defaults to something like 10 deg when no Mach is available (Hazlenuts?) |
BEA's 2nd interim report, page 47:
In alternate or direct law, the angle-of-attack protections are no longer available but a stall warning is triggered when the greatest of the valid angle-of-attack values exceeds a certain threshold. In clean confi guration, this threshold depends, in particular, on the Mach value in such a way that it decreases when the Mach increases. It is the highest of the valid Mach values that is used to determine the threshold. If none of the three Mach values is valid, a Mach value close to zero is used. For example, it is of the order of 10° at Mach 0.3 and of 4° at Mach 0.8. P.S. On page 20 of IR#3 BEA notes that the decrease in speed corresponding to an increase of 1° in the angle of attack depends on the flight conditions: 25 kt in cruise vs 5 kt in Takeoff/Approach. It is interesting to note in the following chart that the difference near the stall warning threshold is much smaller: 9 kt at FL350 vs 7 kt at sealevel. http://i.imgur.com/6sxcu.gif?1 |
Originally Posted by PJ2
(Post 7210297)
...your example isn't representative of a jet transport and isn't even generic, basic classroom material for airline pilots.
Machinbird began a very helpful diversion in the thread by opening the discussion about stall AoA's. You may recall that in the second AF447 thread...others had a lengthy discussion on the stall, AoA's, FPA's/Pitch and so on. I think that discussion is well worth reviewing. My own copy of HTBJ (which sits to my right as we speak) was bought as a result of that conversation. I hope this pointer to some of our previous discussions before the crash site was discovered, is both interesting and useful. I found it refreshing to re-read many of the thoughtful contributions of the time. I think it is a good thing to do so as it lends an ongoing check on one's thoughts, as well as providing some perspective to current discussions.
Originally Posted by RetiredF4
(Post 7210299)
No, i´m picking up some popcorn, looks to be lots of fun when you take it up with OW on the matter of aerodynamics:)
Originally Posted by Owain Glyndwr
(Post 7210314)
I take it you don't mean us to take reciprocal literally? Complementary perhaps?
There I don't agree - adopting a default value for the stall warning AoA threshold for use when a genuine Mach value is not available does nothing to limit the pilot's authority. Before I bow out for a bit - one of the things that puzzled me coming out of the sim session was that the A320 in Alternate had a definite hard limit on autotrim, which doesn't seem to have been the case for the A330 - I wonder why that is? |
AZR,
I do appreciate your sane honesty. That’s not a given to all … As you mention Habsheim, just a quick word to say that Alpha Max was never reached. But I don’t wish to discuss that thing here. As mentioned earlier, I will start a thread on it and it will be a pleasure to possibly debate then. Merci |
Originally Posted by CONF iture
(Post 7210580)
That’s not a given to all …
As you mention Habsheim, just a quick word to say that Alpha Max was never reached. |
CONF iture:
Thx. It was no so a misconception than a miswording, nevertheless "Errare humanum est, perseverare diabolicum" and I try to remember that, sometimes. :) I edited my #932 accordingly. Indeed, Alpha prot/max/floor don't belong here (AF447), will wait about your thread and will be happy to read it, and participate if I feel it useful. :) |
ITCZ Turbulence is not like 'academic' turbulence
From DozyWB
Lyman, This is the definition of "Moderate" turbulence, but the bolding is mine: Quote: Turbulence that is similar to Light Turbulence but of greater intensity. Changes in altitude and/or attitude occur but the aircraft remains in positive control at all times. It usually causes variations in indicated airspeed. or Turbulence that is similar to Light Chop but of greater intensity. It causes rapid bumps or jolts without appreciable changes in aircraft altitude or attitude. From : Tutorial: wind shear and turbulence Quote: The meteorological categories for wind gusts in general (as measured with an anemometer) are: Category 1: weak — ≥ 5 m/s to <10 m/s Category 2: moderate — ≥ 10 m/s to <15 m/s Category 3: strong — ≥ 15 m/s to <25 m/s Category 4: severe — ≥ 25 m/s The meteorological categorisation restated for vertical gust measurement might be: Weak — ≥ 16 fps to <25 fps Moderate to strong — ≥ 25 fps to <50 fps Strong to severe — ≥ 50 fps to <80 fps Extreme — ≥ 80 fps (or 66 fps [20 m/s] might be used) Note that Moderate doesn't even come close to the equivalent of 100kts (50fps = 29.6kts). Outside of the numbers, I sat in the sim - I saw it happen and I *heard* it happen. I experienced an infinitesimal fraction of the concern and fear those pilots felt as the aircraft ran away from me. I stand by the assertion that the climb, warning and deviation from assigned altitude were predominantly caused by deliberate action by the PF. I can't convince you - of this I'm sure. But I've gone to further lengths than I ever have before - assisted by people to whom I am in eternal debt - to prove that I'm not talking out of my ar*e here, and I'm as certain as it's possible to be that the aircraft did nothing to make things harder for them. I know this is late - but you really should have looked at turbulence as it occurs in the Inter-Tropical Convergence Zone. These are not weak mid-west thunderstorms - but a LOT more powerful: "ITCZ thunderstorms are slightly different from midlatitude storms. The differences are primarily due to the different atmospheric conditions in these 2 locations. The strong thunderstorms we endeavor to avoid in the midlatitudes are often due to 2 distinct air masses lying on top of each other. In these situations, warm, humid air gets trapped beneath a middle to upper-level cold and dry pool of air. A small temperature inversion caps the surface air until it builds up enough energy to burst through the cap and rise explosively. It is the excessive speed of the updraft and corresponding down drafts of cold, dry air that give these storms their immense danger to aviation. Vertical air movement can easily exceed 50 kts and has been measured in excess of 100 kts. Furthermore, the boundary between a strong updraft and a strong downdraft means a violent shear zone with air flowing through it at a combined speed of potentially well over 100 kts." Wx Brief Remember you are in moderate turbulence - until you hit extreme turbulence. If it was easy to see all the time it would always be avoided. |
Ian W;
While I agree with all that you say regarding the ITCZ, the key, (and I know you and many here, know this), is vigilance and avoidance, regardless of route. The thunderstorms in northern Canada differ markedly from those in the Caribbean and while one gives those in the Caribbean (and the ITCZ of course), more berth, both are avoided with as wide a margin as possible, commensurate with one's clearance, (to be clear, it is rare that the emergency authority of the commander must be used to deviate from course or altitude without a clearance). The circumstances where one has no options and must pick the best route out of a number of equally bad choices are rare but they do occur. The primary defence against surprise is the constant and knowledgeable use of radar for as long as necessary, bearing in mind two facts about the return signal - that it is moisture that returns the signal* and that TCu's can be hidden from radar by stronger returns closer in. On June 1, 2009 on the first thread (before it was quickly closed, as it should have been!), and based on experience as well as what Dave Gwinn (RIP) has had to say on radar tilt management (among many things he's said), I posted some comments on the use of radar. I believed then as I do now that the use of radar was not well understood and is poorly taught to airline pilots who must get their knowledge informally as well as through manufacturer's brochures. I think airlines just assumed that "pilots knew", just as they assume all their pilots understand a bit about high altitude, high Mach Number, swept-wing aerodynamics. The one superb source on the intelligent use of today's radar was Dave's work who has written. Along with Trammel's work, at the time it was the best information available. In keeping in touch with what some airlines are doing, I see that much more information is now available in FCOMs. PPRuNe is a good source, as always. In my experience with the ITCZ there wasn't always a way to avoid all weather so one picked one's way using radar for long-term planning, (A330/A340 radar - 160nm scale, varying tilt to take slices, making calculations of height, watching the changing picture, changing the gain but staying mostly on AUTO), and by watching outside for possible routings. Turbulence was a regular occurence and occasionally long-term characteristic of flight through the ITCZ (Pacific). Sometimes we'd get hammered, very sharply, sometimes when we expected to get hammered the ride was smooth. Diversions were routinely done. The introduction of CPDLC was in my view a tremendous safety enhancement for such diversions and altitude changes. Regarding AF447, it is difficult to come to any solid conclusions regarding their choice of routing. They did discuss altering course and indeed did so to the left, without an ATC clearance. In my view the turbulence indicated in the data was not unusual, (1.25 to 0.8g). To my knowledge, the notion of sleep inertia on the part of the PF has not been widely discussed but the UAS event occurred within about ten minutes of the call to the flight rest where he was sleeping. It will be interesting to see if the Final Report addresses this issue, as it is a known human factors matter. |
I have to note that my own experience with CB's in the tropics was that they were no where near the stuff I experienced in the U.S. mid west.
Hell, we even refueled in a thunderstorm on one ferry mission over the Pacific. Great boom operator and we could hold position within 10 or 15 feet. The U.S. mid west CB's routinely go up to 40,000 or 50,000 feet, and tornadoes are common. Then there's the mountain wave CAT if you are flying over Kansas or Nebraska. As with PJ's observation, we used our attack radar to tilt up and down to see how high the CB's went. Then turn left or right to minimize problems. In the final analysis, I don't see the choice of routes as the primary cause of the crash. out...... |
Originally posted by PJ2 ... To my knowledge, the notion of sleep inertia on the part of the PF has not been widely discussed but the UAS event occurred within about ten minutes of the call to the flight rest where he was sleeping. |
I think it quite possible PNF had not "cleared the cobwebs". If so, it may have played a major part in his reluctance to immediately gain control from someone who had been in the cockpit for the whole time. PNF had several things on his mind, including a vague command structure left by the Captain?
|
More than anything, IMO, the PNF never handflies from the left seat, why should he suddenly feel comfortable to manipulate the stick from that side ...
His job was to monitor and call the deviations, in this case : PITCH - WATCH THE ALTITUDE - PUSH in order to give a serious hand to his partner. Calling the Captain back was not the priority. |
Captain back please
I have the idea that the PM had a very good idea what was going on but for whatever reason he was content to watch as the pilot flying manoeuvered both of them to their deaths. + 100's of others of course.
I think it was a matter of seniority. Obviously the PM was not exactly content to die, however, I think that he did not have the bottle to avoid it. All he (PM) could think of was to hope that the Captain came back to save his life. Sadly his (PM) hope was misguided. It appears that the PF was determined to ignore the PM's opinions regardless of the consequences. |
It would be a bit risky to attribute the PF's failure to respond to the PNF as a matter of deliberate will. It may indeed have been that way but we do not have the information to back up this supposition. Just as likely was that the PF went into a state of shock and couldn't process any of the information directed at him by the PNF. We just don't have the information to form a conclusion one way or the other.
Rather it is worth focusing on the lack of professionalism in the cockpit. None of the crew can be said to have responded as one might have expected well trained pilots to respond. Clandestino's reference to the article 'Who killed MacMillan' is I think rather relevant as it illustrates an organisational structure which allows this unprofessional type of approach to develop. Airlines which seem to have developed this condition would seem to include Air France and indeed their own safety audit referred to similar issues. I am not convinced that this crew was professional and therein lies the key to this accident. But I would hesitate to ascribe a level of deliberate behaviour to the circumstances of the accident. |
mm43;
It was the PNF who said he had dozed and returned to the cockpit at about 0200 and took the LHS. The PF had been in the RHS from departure Rio de Janeiro. Your comment regarding sleep inertia is still relevant as it could well explain the PNF's lack of positive action over the next few minutes. Not to divert discussion but I think sleep inertia has not been sufficiently addressed as a long-haul/ultra-long haul matter. It is not just a crewing matter, (as in crewing with four pilots vs three, etc). I think sleep inertia was at work here. Along with the usual examinations of the crews' activities & sleep patterns prior to the cycle and during the layover, this phenomenon needs more focus in this report as well as generally in research. The 2011 pitch-down incident involving a B767 on the Atlantic is enough to cause wider examination of the matter no matter how caused of course, (bunk time or controlled rest on the flight deck). The issue has been demonstrated and airlines can no longer ignore its effects. |
O.C.;
Just as likely was that the PF went into a state of shock and couldn't process any of the information directed at him by the PNF. With 2900+ hrs TT and 807hrs in the A340/A330, (216hr on type), the PF almost certainly will not have experienced a significant failure with full application of adrenaline. Many will go an entire career without it, so highly-successful are the historical and present technological solutions to the safety of flight. So while the sim recurrent work will have covered the abnormals and emergency procedures for these aircraft, most transport pilots here likely including yourself OC, can tell us that when they do occur, an inflight abnormality or emergency places psychological demands on one that cannot be experienced or taught in training. An abnormality requires significant self-discipline to collect and order one's thoughts and actions. And each person has slightly different responses in such circumstances which is up to CRM to sort out and quickly make a "fighting team", as it were, out of two cockpit crew on a routine mission. We cannot look to individuals for what we may now consider as "their lack of experience", as every one of us who fly or used to have been there too. We cannot give a course in "More Experience". I think you have expressed it well. We have to look more broadly, which is one reason I considered broaching the sleep inertia matter. We can examine SS vs CC, last-remembered actions for an after-takeoff UAS drill, training, training records, script priorities, airline culture and so on. There are other matters that we could name. The fact is, the accident did occur when in 30+ UAS events it did not; Why here? If factors which are identified as primary and those that are categorized as contributing are fixed, where, in human factors especially, must we look towards next? |
Sleep inertia as a possible factor in this accident I think has considerable merit. Looking at how people function when they are sleep deprived does throw up interesting parallels with what we know of the reactions of this crew. It does tie in with the professionalism issue and here I should stress that I am not using professionalism as a value judgment but as a being able to act so as to provide the best possible set of responses in any situation. This issue is cultural but I don't think can be directly taught either. A pilot has to want to follow his exemplars and be like them. Any pilot needs to be aware of all the factors that might limit his/her performance and how to mitigate them as much as possible.
|
Any pilot needs to be aware of all the factors that might limit his/her performance and how to mitigate them as much as possible. Victory awaits him,who as everythings in order. Luck we call it. Defeats is definitely due for him,who has neglected to take the necessary precautions. Bad luck we call it. |
Stick & Rudder Skills v. Time of Day et al
As Human Factors are bound to be an important feature in the BEA's Final Report, consideration should be given to which particular disfunction will dominate.
In Post #27 AF447 - Thread No.6 there is an interesting link to a study on how people adapt to taking manual control when the automatics give up, and more. |
| All times are GMT. The time now is 05:47. |
Copyright © 2026 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.