Incidente A330 Air France Rio-Parigi 01/06/2009

  • Autore Discussione Autore Discussione Edo75
  • Data d'inizio Data d'inizio

Vedendo la fonte dell'articolo non mi stupisco della bassezza di quanto scritto...ci manca solo che ora ci facciano una puntata di Lucignolo su questa immane tragedia....
Che disgusto....

ci manca vespinho col modellino del 330...e i personaggi implicati fatti tipo con barbie e ken con tanto di amante con le mutandine abbassate in first class..e poi gli immancabili esperti rettondini,marini,pariette tommasi...forse anche il comandante berti via....nomi minuscoli apposta...
 
Hai dimenticato crepet.....comunque tutta questa gente potrebbe essere utile, ci sono cosi' tante navicelle spaziali e cosi' tanto universo...
 
ci manca vespinho col modellino del 330...e i personaggi implicati fatti tipo con barbie e ken con tanto di amante con le mutandine abbassate in first class..e poi gli immancabili esperti rettondini,marini,pariette tommasi...forse anche il comandante berti via....nomi minuscoli apposta...

Purtroppo è pressochè certo che se una tale tragedia avesse coinvolto in modo più pesante e diretto l'Italia (prego che ciò mai accada) avremmo assistito a un teatrino del genere...:sconfortato:
 
Disgustoso davvero.
Se lo è, come è regolamentato il riposo per un pilota? Ci sono delle regole generali e/o di compagnia su cosa è permesso o non permesso fare durante questo turno?
 
" Chiamarono disperatamente Dubois ma, per ragioni mai del tutto chiarite, il comandante arrivò solo un minuto dopo. Un minuto che, forse, avrebbe potuto impedire lo schianto".

A parte che il "disperatamente" ce lo hanno scritto loro, perché sinceramente non ce lo vedo un professionista con 6500 ore di volo chiamare papà disperatamente. In ogni caso, per quel poco che ho capito dalle risultanze delle perizie tecniche, un minuto in più o in meno non avrebbe fatto alcuna differenza.
 
Tra l'altro dubito fortemente che dalla chiamata all'effettivo arrivo in cockpit possa trascorrere un solo minuto. Quindi doppia cazzata.
 
ci manca vespinho col modellino del 330...e i personaggi implicati fatti tipo con barbie e ken con tanto di amante con le mutandine abbassate in first class..e poi gli immancabili esperti rettondini,marini,pariette tommasi...forse anche il comandante berti via....nomi minuscoli apposta...
modellino del 330??? forse un 747... :wall:
 
che pena questi giornalai...

analizziamo i fatti:
-il cpt viaggiava con l'amante, anche fosse vero, cosa c'entra con l'incidente? di cattivo gusto scriverlo, punti in piu' per il cpt, io preferirei lavorare con uno che si e' appena "rilassato" con l'amante che con un australiano represso che non lo fa mai...
-1minuto per tornare in flightdeck, e quanto doveva metterci? 3secondi? 0,2 secondi? improvvisamente la turbolenza e' sparita per quel minuto?
-l'avvisatore di stallo ha suonato 70 volte, perche non spiegano questa, perche non spiegano che sotto gli "80kts" (non mi ricordo il numero), l'avvisatore smette di suonare anche se in stallo...

Perchè dici quelle cose sugli Australiani??Cosa ti hanno fatto?
 
Riporto due esperienze fatte al simulatore che possono rendere un'idea ,prese da altro forum .
Tenete presente che sono fatte nella massima tranquillita' e al simulatore , immaginate poi i piloti dell' AF447 , due del mattino , notte, in mezzo o dentro ai CB ....


Humbling sim experience
Had an interesting sim session today,

As a result of several high profile loss of control accidents recently my company introduced a special LOC sim session. Interesting training with a lot of background. My particular sim session was done with an ex air force guy. Lot of insight about recovering techniques! In my earlier years I did some acrobatics but no formal training and since then all my flying has been airline type. Aside from the occasional upset recovery during TQ's and occasional type recurrents not much experience in this regime.

One scenario in particular was eye watering/ego killing.

Airplane type: B747-400

Flying at 35.000 with an heavy airplane you climb to 37.000 which is just*
Possible with the weight. Reason for the climb, you are flying just below the clouds in an area of embedded TS and it is bumpy.

Starting the climb(with just a small margin between upper and lower red band but still within normal operating parameters) you notice the the wind shifting to more HW. You anticipate and notice a speed increase and start to reduce power. To no avail, the airspeed keeps inching towards the upper red band. You reduce power more( not excessively) but still, just after level of you get into the upper red band and get an overspeed warning! You reduce power even more, the airspeed drops but still in the upper red band and all of the sudden you get the stick shaker together with the overspend warning!!!

Respect the stick shaker, you add power but there is not much power left and you are on the wrong side of the power curve, increase in power does not increase airspeed so there is no other action than to descend.

As you descend trying to recover from the stick shaker you notice the wind changing again to a TW and increasing(it shifted to a HW during climb, now it shifts back to a TW) correspondingly, you notice the speed to drop even more, causing you to lower the nose even more to get out of the stick shaker.

The TW increases and the speed drops even more! During the entire event you also have the stall buffet. Somewhere, the overspeed warning stops..the stick shacker stops, you still have the stall buffet and your airspeed reads below 30(which is the minimum reading) with a large TW( in excess of 200IAS).

This all happens completely unexpected!!!! And in the timespan of about 30 seconds ( really, to the best of my recollection) you have gone from 37.000 to 22.000.

I'll stop here to see what you can make of this! I have no military training, consider myself an above average pilot), this completely caught me of guard and left me humbled enough to post it here.

Really interested to see what you can make of it and try to figure it out in a short timespan( remember, it happened to me in a short timespan)
HW - head wind
TW- tail wind
 
We had a session with a good unreliable speed scenario, the airplane ended up pitching up a lot, speed decaying. PF was unable to arrest the pitch up. This was a 320. When I prompted him to pitch down he said "I can't, I,m trying"
We had lost quite a few thousand feet already, the airplane slowing down and descending, the stall warning all the time. I remembered the Air France and started to use the THS handwheel to pitch the airplane down. Eventually it worked. The TRE told us later that due to some computer, I don't recall which one, the THS had frozen!

We learnt a lot.

By the way I became to two conclusions:
1- the most difficult part is realising that speed is unreliable
2- when speed is unreliable you don't know for how long it has been unreliable, you can be well in overspeed or about to stall, ergo safety is compromised and you should do the memory items, which at high altitude are illogical, but at least you have to disconnect everyithing, level off and fly a reasonable pitch with thrust as required, then troubleshoot.

TRE - istruttore
THS - stabilizzatore orizzontale
 
Riporto due esperienze fatte al simulatore che possono rendere un'idea ,prese da altro forum .
Tenete presente che sono fatte nella massima tranquillita' e al simulatore , immaginate poi i piloti dell' AF447 , due del mattino , notte, in mezzo o dentro ai CB ....

Veramente interessanti entrambi. Grazie!
 
Final AF447 report set to re-ignite safety feud

By: David Kaminski-Morrow London

12:00 28 Jun 2012

Source: Flight

French investigation authority BEA appears likely to rekindle the smouldering conflict over the loss of Air France flight AF447 when it releases the final report into the accident on 5 July.

Air France and the main French pilots' union, SNPL, have previously clashed with Airbus over the circumstances of the crash and whether the fundamental reason for the loss centred on pilot competence or the design of the Airbus A330's flight-control and warning systems.

As expected, Airbus has submitted substantial comment to the inquiry following the release of the draft version of the report.

SNPL has already reiterated its concerns over aircraft functions and the alerts given to the crew, in a document published in February.

Airbus declines to comment on the AF447 report ahead of publication, but has previously strongly defended its aircraft and pointed out that three pilots appeared unable – despite clear warnings – to recognise the aerodynamic stall which downed the jet in June 2009.

Although the draft did not include recommendations it featured analysis by a human factors panel established to look into the crew's response to the stall.

But a source familiar with the situation indicates that the airframer is concerned whether the conclusions will focus too narrowly on the human-machine interface.

"If there are things to improve on the aircraft, [Airbus] won't try to escape in any way," says the source, but adds that the manufacturer “would like to see a report in which all the issues are being dealt with”.

The source also suggests that Airbus is likely to "become vocal" if it feels the breadth of the report is too narrow.

Former BEA deputy chief Jean Pariès - who heads human factors consultancy Dédale and took part in an Air France safety review - told an operations forum in Oslo in April that current safety models assume pilots will recognise and identify abnormal situations, then implement relevant procedures.

However in reality, he said, emergency situations generate surprise, causing momentary loss of cognitive control as well as resistance to recognising a loss of comprehension.

Pariès cited 16 events similar to AF447, all of which showed poor understanding, rare implementation of unreliable airspeed procedures and stall warnings which were "perceived but mostly not believed".

He suggests the problem cannot simply be reduced to "automation complacency" or loss of basic skills. Pariès claims crew training aims to prepare pilots for anticipated emergencies, not the unexpected, and highlights the irony that the competencies needed to cope with the unexpected "are those that are lost in a continuous effort to anticipate and respond to all potential threats".

Investigations into a strikingly similar event to AF447, involving an Air France A340 in July 2011, recommended that pilot training include shock and surprise elements.
 
Speriamo che Airbus e AF non facciano un braccio di ferro su chi ha ragione/torto.
 
The French BEA is just holding the press conference to release the final report into the crash of the flight, this coverage is going to be updated as soon as important statements are being made. The summary of final report will be summarized as soon as the report has been released and processed as usual.

The aircraft had been flying normally crossing Natal with the captain being pilot monitoring and the first officer being pilot flying. The second first officer was taking his rest. The captain was not worried about the forecast weather conditions along the route, and while over the Atlantic left the cockpit for his rest period with the second first officer taking the left hand seat. There was no briefing, especially not with regards to the Intertropical Convergence Zone. After the captain left the cockpit the two first officers discussed the echos visible on the weather radar.

Ice crystals blocked the dynamic ports of the pitot probes, the autopilot disconnected and the altitude warning sounded, the aircraft climbed up to 38,000 feet with up to more than 6000 feet per minute climb rate.

The stall warning activated, several signals were sent to the captain by the pilot not flying (second first officer), the aircraft entered "pronounced stall" and the aircraft started to descend at more than 7000 feet per minute with an angle of attack of more than 40 degrees.

Just when the captain entered the cockpit the stall warning ceased and re-occurred, the AoA was between 35 and 40 degrees and the vertical rate of descent between 11000 and 15000 feet per minute until impact with the water.

The starting point was the formation of icy crystals which disrupted the air flow and pressure measured by the dynamic ports of the pitot tubes leading to airspeed inconsistencies and the disconnection of the autopilot and autothrust system. The pilot flying is supposed to take control manually monitoring the systems, detecting the airspeed inconsistencies and maintain a proper pitch attitude and thrust setting.

Instead of keeping the pitch at a maximum of 6 degrees, at which the aircraft would stall at high altitude, the pilot flying pitched up beyond that angle. The crew did not follow standard operating procedures.

The pilot not flying did not detect the deviation from the flight trajctory and speeds and did not call the deviations. The lack of such interventions led the pilot flying to take actions that did not reduce the pitch angle.

The flight directors provided indications to increase the nose up attitude.


The aircraft subsequently departed its flight envelope, the control stick remained in the nose up position.

The crew never referred to the stall alarm and the buffeting that occured. The crew never understood they were stalling.

The captain came back into the cockpit certainly having heard the stall warning and certainly having felt the strong vibrations caused by the buffets but also did NOT identify the aircraft was stalling.

The absence of training in manual handling of the aircraft at high altitude, especially also with regards to unreliable airspeeds can explain the reaction of the crew, also the trained procedure related to airspeed anomalies misled the crew to false required pitch angles.

25 safety recommendations were made with regards to pilot training, knowledge of systems especially in degraded modes, manual handling training, knowledge of flight dynamics.

Safety recommendations have also been made to search and rescue operations.

8 safety recommendation concern pilot training, 8 safety recommendations concern aircraft certification.

The accident is categorized as loss of control as result of loss of situational awareness.

The automated systems have improved safety substantially in the last years, however, as soon as the automated systems disconnect flight crew are increasingly unable to comprehend the resulting scenario. Information presented to the pilots as well as the cognitive capabilities of humans are in the focus of attention in this regard.


This concluded the factual presentation by the BEA, now the conference has entered the question and answer part.

In the last few seconds of the descent the aircraft had entered deep stall during which recovery was next to impossible except to specially trained to crew, no pilot could have recovered from this final stall. The aircraft should never have been allowed to leave the flight envelope and come into a situation of a developed stall, not to mention a deep stall.

The Airbus family of aircraft has never been put through stall recovery during certification opposite to the Boeing 787. The Boeing test crew flying the stall were surprised by the very different sounds associated with the stall of the aircraft in comparism to a Cessna.

In an intensive stress scenario the humans blank out aural signals first. Every military pilot, every test pilot knows that in intense stress situations aural alerts are not being heard.

Goodrich probes are not immune to icing as well, however, far fewer events have been registed with these probes.

At the start of the event the altitude indication dropped by 400 feet as result of the loss of Mach number due to the computed corrections, the loss of 400 feet of altitude has further provided incentive to increase the pitch angle.

Had the pilots done nothing after the autoflight systems disconnected it is difficult to know/estimate whether the accident would have happened or not. It is true however that in a number of other events the aircraft maintained its general flight envelope with the crew doing nothing following autoflight system disconnection.

There is no proof that the crew followed flight director indications. The green bars however are very attractive, pilots are used to continue what they do normally, and it is not implausible that the crew did follow the green bars of the flight director.

The flight director indications were not recorded by the flight data recorders, but were recomputed following the preliminary report #3, these computations and knowledge resulted thereof are a new element beyond report #3.

The false data off the air data computers following the obstruction of the pitot probes by ice crystals resulting in false instrument readings as well as the immediate actions by the crew created confusion making it impossible for the crew to determine what flight status they were in.

The obstruction of the pitot probes triggered the sequence of events, the subsequent actions by the crew de-stabilized the aircraft trjactory and led the aircraft to leave its flying envelope.

The pilot actions can be explained by the crew being afraid of getting into an overspeed scenario mainly also due to the noises that occurred at the flight deck. As a result the crew never realised they were stalling.

The 25 safety recommendations in the final report add to the 16 safety recommendations issued so far in the preliminary reports.

During the final 4 minutes of flight the flight directors disappeared and reappeared multiple times, the modes changed. The flight director indications did not provide for a recovery of the aircraft, however, at the initial stages of the aircraft leaving its assigned trajectory and approaching the boundaries of its flying envelope it was possible to recover the aircraft. As the crew never realized they were stalling they were never able to disregard the flight director and take the appropriate actions to lower the nose. Appropriate action to lower the nose and the flight director indications were inconsistent. The flight director indications would need to be taken in the context of the active mode indicated in the according announciators. The flight directors were NOT disengaged as they SHOULD have been. The modus of flight director operation is being further looked into.

There had been other similiar occurrences during which the altitude was maintained within +/- 500 feet. It is not possible to state, whether another crew could have kept the aircraft within its flying envelope or not, it is impossible to tell whether the accident would have happened with another crew at the controls or not. It is likely however that the accident would have happened to other crews as well.

A test flight verified that the stall buffeting was perceived at the pilot seats, bringing the nose down would have quickly returned (recovered) the aircraft into the flying envelope.

It is true that in FBW normal law it is not necessary to train pilots for a stall situation, and it is true that pilots are not really trained for stall scenarios.

The certification bodies have reviewed the unreliable airspeed procedures at high altitude and confirmed that maintaining a pitch angle of 5 degrees nose up would have provided time to sort out the unreliable airspeed and would have kept the aircraft flying.

This concluded the press conference. The final report is to be released in the next few hours.


fonte: Avherald.com
 
Ultima modifica: