If the pitots blocked with ice, which they clearly did, you’ll get an IAS Mismatch, this will disconnect the AP & AThr (as the report said). But what you now have is conflicting airspeed readings, they were clearly nearing the edge of “Coffin Corner” (you do know what this is? Don’t you?) and were unable to climb to their optimum altitude due to the turbulence which could have sent them into this small window. You now have blocked pitots, and the very likely scenario here is that they are over reading, and the speed is pushing them close to coffin corner (but not in reality).
So what they did was pitch the aircraft up in order to slow it down (no idea why they didn’t try reducing power, but I wasn’t there), all this did was cause the airspeed to increase further because you now have a pitot system that is acting like an altimeter (static element available – maybe), so they pitched even further.
No, not the way it works. That is physically impossible given the way a pitot-static tube works and the supposed overspeed you postulate earlier.
If you had an underspeed earlier, then yes, you could possibly have a speed increase with altitude increase (Pitot probe is blocked while static probe reduces pressure due to ambient). But you can’t have both.
Conversely, if the static port was blocked earlier, and you had an overspeed, then when you increase altitude and bleed off real airspeed, your indicated speed will reduce.
Pt/P = [1 + {(gamma-1)/2}*Mach^2] ^ (gamma/[gamma-1])
gamma is ratio of specific heats, Pt is total pressure (pitot probe), P is static pressure (static probe).
Then you have the stall warning go off. How confusing do you think that is for anyone flying in those conditions?
It is confusing only if you mis-diagnose the problem in the first place.
In that instance, it would be more than confusing, it would be alarming.
If you think that is black and white then you are very much mistaken.
First thought should always be; retain control of the aircraft. Everything else is a distant second to that.
They had faulty airspeeds, they knew that. Yet they made the decision to try and react to those airspeed readings. Why on earth would you make the decision to try and respond to what you know to be potentially bad airspeed readings?
That is why it is black and white to me.
They should have went with set attitude and thrust. They should have known to go with set attitude and thrust. That is why it is extremely bad airmanship and that is why I am not happy at the authorities dancing around the issue (my rants in here are reflective of that – call a spade a spade – being politically correct when lives matter helps no-one).
The report, and your good self makes no reference to this at all,
http://www.bea.aero/docspa/2009/f-cp090601e3/pdf/f-cp090601e3.pdf
pg 44
The traces are all there.
Climb initiation at ~2:10:12, then starts to tail off around 2:10:34 – not even 25 secs.
and make out like they had all the time in the world, but they didn’t.
They had all the time in the world if they had given themselves it.
It is also interesting to note the crew previously decelerated to Mach 0.8. Quite a ways short of the A330 0.86 limit.
As for ‘coffin corner’ – explain their rational for climbing then…
Also lets not forget the severe icing conditions. Do you know what an accretion of severe ice does to your stall speed? Do you know how this will affect the aerodynamic capability of the aircraft at that altitude?
No idea. Please enlighten me. :rolleyes:
No, but as I said they will ask for it and its a reason why we need to know our altitude.
You aren’t going to lose control of your aircraft if you do not know your altitude (with the obvious caveat of being well above the ground).
It seems you are unwilling to admit that. You do not need to know your altitude to retain control of the aircraft. Hung up on little checklists and unable to realise what the important bits are. Like an administrator and their precious little “procedures” and “processes”.
So considering there was many error messages how could they be so sure the Artificial Horizon was working?
Because it is not dependent on any external factor, it is also a mechanical gyro, if it jams, that will become abundantly clear when it fails to track any change in aircraft attitude.
Of course, if you understand your aircraft – instead of merely pushing button A, B and C in the order prescribed in the FCOM – then you’d know that automatically.
Used to be an ATPL with 20,000hrs… or a PPL student with 5hrs training? I’m not trying to discredit you in any way
Nearer the latter than the former.
But I am not commenting on this based on my personal experience as a pilot. I’m doing it in my professional capacity as an engineer.
but it appears to be that you disagree with every pilot on the forum and are making us out to be incompetent.
Just the majority – obviously there are exceptions to every rule :diablo:
Whether you deem yourself to be an exception is up to you to judge. :dev2:
If pilots fail to react as they should in a given situation what else can be at fault except training?
Bad judgment.
Sorry, but sticking the thing in a consistent 10deg nose up attitude near the limit of the flight envelope and expecting nothing bad to happen is not a lack of training – it is incompetence.
If you dont include your altitude in your call to ATC they’ll probably ask for it 😉
But they aren’t gonna shoot you down for not saying it. :rolleyes:
I do understand primary and secondary concerns however most of this was started with your AF447 outburst and no one properly knows what went on that night. Assuming they did stall – a stall, over sea in the middle of the night with no visual reference is no laughing matter.
The what happened is very well understood – the telemetry traces show exactly what happened. The why and how is less well understood.
They had a “visual reference” – its called the artificial horizon. They chose to ignore it and chase after airspeed readings instead (incidentally completely ignoring altitude). If they’d paid heed to it, they wouldn’t have stalled – unfortunately it is more or less that simple.
You folks may want to blame it on bad training. I blame allowing an altitude drift of a couple of thousand feet beyond what was known to be the safe flight envelope as stupid and negligent, nothing less.
So, riddle me this. If the stall warning is sounding, and you are climbing (through 37 kft) – why continue to pull back on the stick?
(a) you haven’t been training to realise that pushing forward puts the nose down.
(b) you have been trained but forgot
(c) that stall warning sounds nice – like leaving a mobile ringing ‘cos you like the ringtone
(d) you know pulling back stops us hitting the sea… right?
(e) ANOther
The cockpit voice recorder transcript makes for damning reading.
http://www.flightglobal.com/articles/2011/08/12/360432/af447s-initial-altitude-drift-went-virtually-unchallenged.html
You still didnt answer my question as to whether your a pilot of some sort or not?
Used to be.
Not in Severe turbulence they’re not.
You actually saying the gyros used for modern AHs are screwed by a bit of turbulence? :confused:
Anyway I think we are going waaaaaay off topic with this one.
No we aren’t. There seems to be a string of pilots in here that have forgot what is actually important.
Amiga, you are failing to answer any of the queries posted to you in page 2 of this discussion
The only remotely technical query was around my studying of FADEC or EEC. The answer to that is yes.
The rest – well I’m not going to bother parading my qualifications on here – but for this discussion, they are comfortably more than sufficient.
and are using the series of so called “technical discussions” to dissuade the attention away from your original, and nonsensical outburst
Nonsensical my ****.
You bunch still haven’t been able to grasp what is a primary and what is a secondary concern.
which damned the crew of AF447
And correctly so.
Unfortunately, judging by the reaction in here – I should be damning the training much more. Which is more worrying.
So come on, answer the queries with some substance and stick to the topic in hand, which is “Pilots Rusty Because Of Automation”.
Ask a query of substance.
In my experience, during normal VFR flying in a SEP plane, you rely primarily on the position of the upper edge of the instrument panel, windshield/canopy rails etc. in relation to the outside horizon in order to set the correct attitude for level flight, climbing turns and so on.
Yep – with the implicit assumption what is ahead of you is the same ground height as what is to the side. But thats kinda irrelevant here – what you need is a means of recognising aircraft attitude, whether that is the horizon or the VH, doesn’t really matter to the core of this argument.
A functioning altimeter is very handy even if a failure won’t necessarily ruin the day immediately.
Of course it is – I’m not saying it isn’t a vital piece of equipment. But, if things start failing you need to reduce you sensor inputs to what is absolutely needed – luckily the AH and throttle are relatively reliable sensor suites, the throttle being (to a degree) a closed loop system which self-checks.
It doesnt matter if they track you or not, in certain calls to ATC you state your altitude, even if making a call to a station that doesn’t have radar facilities. You even plan your altitude before flying when filling out a flightplan etc. So even under VFR you need to know your altitude.
Arrgh!
See – this is what is really annoying me.
Youse are unable to differentiate between nice to know and need to know. It is reflective of the greater problem here.
If you don’t know your altitude, but do know you aren’t going to hit the ground anytime soon – then you don’t need to know your altitude. If you don’t include the altitude in your ATC call, you are not going to burst into flames instantly, killing 300 odd people.
Do you not see the difference between primary and secondary concerns?
Still no need (strictly speaking) for an artificial horizon when flying VFR. You seem to be making a contradiction here as far as VFR flying is concerned.
If you can accurately judge your attitude from the real horizon… then yes, I suppose there is no need for it.
Regaining control – yes. Stall recovery procedures may involve using airspeed readings once the initial attitude and power setting for recovery have been established, though (at least the ones I’ve done in smaller airplanes). Also, regardless of attitude (more or less), other factors such as vertical winds can affect the ROD.
Of course – I’m not discounting the other sensors are important – I’m driving at the core fact that they in themselves, are not absolutely needed to fly an aircraft.
If your instruments start playing up – AH and throttle. Thats it. Give yourself time to diagnose and work-around the problems. Till then – don’t make things worse by making half-assed guesses and focussing on items of secondary concern.
EGTC mentions altitude for air traffic – yep. But thats not gonna kill you unless someone else crashes into you. Also, if your in an air traffic zone and they can track you – you have a completely independent source for ground speed and altitude.
I’ll do the J-10 and J-20 once I pirate photoshop,
Ach – photoshop. :rolleyes:
Get GIMP (GNU Image Manipulation Program) and Inkscape. Both free and IMO, better.
You guys not try engauge?
Pretty useful tool for digitising graphs etc – but can be used for stuff like this.
Its open source (or maybe its actually freeware):
despite your adherence to some sort of conspiracy theory
:confused:
Erm – the BEA are publically at odds with the pilots union over it. I’d hardly call it a conspiracy.
I don’t understand why you included the AH while excluding the altimeter
‘Cos under VFR if, you can see you are not going to hit the ground, the altimeter is superfluous. You don’t need to know your altitude as long as you know you aren’t gonna hit the ground anytime soon. Nice-to-know and need-to-know.
I include the AH to prevent you trying to climb too quick and stalling. That is something you need-to-know.
If you know what power you have* – you should know the sustained attitude envelope the a/c is capable of – otherwise you don’t really know your aircraft.
*which, as I pointed out earlier, the FADEC will be able to calculate to a reasonable degree as its much more than a passive sensor suite.
In a repeat of AF447 – when you cannot trust the readings of instruments, and you know your stall margin is preciously small due to altitude. The objective should be retaining control of the aircraft, everything else is second to that. Altitude, airspeed, heading – all secondary considerations.
Thus – you aim for a minus 2 deg pitch on the AH and keep your throttles at cruise setting, or (like an AF A340, if you think your approaching Vmax – throttle back and drop the nose to minus 4 or 5 deg). From 35,000 ft that is over 15 minutes of descent time to get yourself sorted out (at -2deg).
The AF crew got fixated on secondary concerns and gave themselves 3 minutes to diagnose the problem, find a solution and implement it.
you seem to lack a certain understanding of cockpit work, potential threats, human factors etc.
Sorry, but I really think many in this thread are over-complicating what the core parameters of flying are.
See that post above. Attitude and thrust.
Assuming you had a compass, there are only two instruments (well, one isn’t really an instrument) you need to fly from A to B.
These are an artificial horizon, and a throttle.
You don’t need airspeed, you don’t need altitude*, you don’t even need angle of attack. All these are nice to have.
*well, not in VFR and for the purposes of this discussion, the ground is not an immediate danger to aircraft recovery at 35+ kft.
May I ask about your professional background?
You can if you want. I might chose not to reveal all details though.
Hmm.
FADEC uses static pressure for example even for ‘core’ computations. Static pressure is affected by external fluctuations. Therefore, an external influence. Normal control law is derived from sensors from the aircrafts digital air data computers i.e airspeed, altitude etc. All external influences.
Even using basic control law, ram air is a major influence on thrust produced no matter what state the control is on. You can’t get a much bigger external influence that the mass of air entering the inlet!
EDIT: As an aside, does the A330 have standby pitot static instruments available?
You are mis-understanding me.
1. The core FADEC sensors are not reliant on the aircraft interface; it would never be signed off otherwise.
2. If you perturb something, then measure the change and compare to what you would have expected – then you are not relying on an external influence. Hence what I mean when I specifically mention measurements within the compressor/turbine. If the mass of air entering is not the same as expected – your closed loop algorithms will very quickly ascertain that as the turbine temperatures are not matching up. Therefore, the sensor is reliant on an internal influence – if they don’t match, you know there is a problem.
3. You can also derive from fuel rate, turbine temperature and pressure ratios what your likely (it’ll not be perfect, but it’ll be good enough) real gross thrust is.
The two core parameters a pilot controls on an aircraft are aircraft attitude (you can include roll and yaw if you want) and thrust. Everything else stems from that. When the sh!t hits the fan – the artificial horizon and the throttle settings are the things to go to. I don’t know how you folks can’t see that – and I don’t know how the Air France crew didn’t – unless the training is shambolic.
Have you ever studied how an E.E.C works or any FADEC system? They use airspeed, pressures, pressure altitudes, temperatures, ram air effect. All classed as external effects perhaps? All affecting thrust? Definitely.
I wouldn’t class them in the same bracket.
If your measuring your effect on something – like turbine temperature [which is affected by things like core massflow rate, pressure, compressor exit temperature and fuel rate], then your decoupling yourself from being wholly reliant on a “passive” (not quite the right word) sensor.
Anyhoo – Israel Dagg has just scored a try for my fantasy rugby team – I’ve more important things to be doing right now. It begins with w and rhymes with ‘watching the rugby’. :diablo:
edit: Two tries now 😀