Go Back  PPRuNe Forums > Flight Deck Forums > Rumours & News
Reload this Page >

AF 447 report out

Wikiposts
Search
Rumours & News Reporting Points that may affect our jobs or lives as professional pilots. Also, items that may be of interest to professional pilots.

AF 447 report out

Thread Tools
 
Search this Thread
 
Old 15th Aug 2012, 18:40
  #801 (permalink)  
 
Join Date: Jul 2002
Location: UK
Posts: 3,093
Likes: 0
Received 0 Likes on 0 Posts
The system "heeded" the "omens" perfectly well:

Originally Posted by BEA F-GZCP Final Report (En) P.124
On 24 November 2008, the issue of inconsistent airspeed indications was raised during a meeting between the technical divisions of Air France and Airbus. Air France requested an analysis of the root cause and a technical solution to resolve this problem, and suggested that BF Goodrich probes should be fitted, since their reliability appeared to be greater. Airbus confirmed its analysis and agreed to check the option of replacing the Thales probes with BF Goodrich probes. This point was followed by Air France and Airbus via the implementation of a "dashboard of indicators" approach.

At the end of March 2009, Air France experienced two further events involving the temporary loss of airspeed indication, including the first event on an A330. On 3 April 2009, in light of these two new cases, Air France once again asked Airbus during a technical meeting to find a definitive solution.

On 15 April 2009, Airbus informed Air France of the results of a study conducted by Thales. Airbus stated that the icing phenomenon involving ice crystals was a new phenomenon that was not considered in the development of the Thales C16195BA probe, but that the latter appeared to offer significantly better performance in relation to unreliable airspeed indications at high altitude. Airbus offered Air France an "in-service evaluation" of the C16195BA standard to check the behaviour of the probe under actual conditions.

Air France decided to extend this measure immediately to its entire A330/A340 longhaul fleet, and to replace all the airspeed probes. An internal technical document was drawn up to introduce these changes on 27 April 2009. The modification work on the aircraft was scheduled to begin as soon as the parts were received. On 19 May 2009, based on this decision, the monitoring of these incidents was considered as closed during the RX2 meeting. The first batch of Pitot C16195BA probes arrived at Air France on 26 May 2009, i.e. six days before F-GZCP crashed. The first aircraft was modified on 30 May 2009.
It just didn't fix the issue on this particular aircraft fast enough.

At the time of the accident, F-GZCP was fitted with the original C16195AA probes.
DozyWannabe is offline  
Old 15th Aug 2012, 19:02
  #802 (permalink)  
 
Join Date: Jul 2009
Location: DFW
Age: 61
Posts: 221
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by DozyWannabe
The system "heeded" the "omens" perfectly well:

It just didn't fix the issue on this particular aircraft fast enough.

Either the system heeded the omen and fixed the problem, or it didn't. We have 228 graves on exhibit to show that the problem wasn't fixed.
TTex600 is offline  
Old 15th Aug 2012, 19:32
  #803 (permalink)  
 
Join Date: Aug 2009
Location: Germany
Age: 67
Posts: 1,777
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by BEA F-GZCP Final Report (En) P.124
On 24 November 2008, the issue of inconsistent airspeed indications was raised during a meeting between the technical divisions of Air France and Airbus
In 2008 ? ....
Really ? that's in 2008 that this problem was discovered and raised in safety discussion ?
Seem's that the BEA have a limited or short memory ....
December 1995: TFU 34.13.00.005 (Appendix 1). Airbus made ​​the observation of the lack of
certification on the Pitot probes in the presence of ice crystals and launches development
probe Goodrich P / N 0851HL
Augustus 1996 : NTSB recommendation : Revise the icing certification testing regulation
to ensure that airplanes are properly tested for all conditions in which they are authorized to operate,
or are otherwise shown to be capable of safe flight into such conditions. If safe operations cannot be
demonstrated by the manufacturer, operational limitations should be imposed to prohibit flight in
such conditions and flight crews should be provided with the means to positively determine when
they are in icing conditions that exceed the limits for aircraft certification. (Class II, Priority Action)
(A‐96‐56)
January 1999: The BFU recommends changing the certification standards of the Pitot probes
(Annex 13).

Last edited by jcjeant; 15th Aug 2012 at 19:42.
jcjeant is offline  
Old 15th Aug 2012, 19:39
  #804 (permalink)  
 
Join Date: Jul 2002
Location: UK
Posts: 3,093
Likes: 0
Received 0 Likes on 0 Posts
@jcj - as discussed, completely different type of both pitot tube and aircraft. The 1995 issue was with Rosemount tubes on older types.
DozyWannabe is offline  
Old 15th Aug 2012, 19:44
  #805 (permalink)  
 
Join Date: Aug 2009
Location: Germany
Age: 67
Posts: 1,777
Likes: 0
Received 0 Likes on 0 Posts
@jcj - as discussed, completely different type of both pitot tube and aircraft. The 1995 issue was with Rosemount tubes on older types.
More ...
July 2002: In the OIT 999.0068/02/VHR SE (Annex 4), Airbus made ​​the observation of defects
probe Thales (formerly Sextant) P / N C16195AA.
September 2007: The EASA made the finding of the lack of certification of the Pitot probes (Appendix
6)
Conclusion ... a full story (from 1995) of problems with Pitot (any brands) and their certification ....

And ...
On 24 November 2008, the issue of inconsistent airspeed indications was raised during a meeting between the technical divisions of Air France and Airbus

Last edited by jcjeant; 15th Aug 2012 at 19:52.
jcjeant is offline  
Old 15th Aug 2012, 19:49
  #806 (permalink)  
 
Join Date: Nov 2011
Location: Kentucky
Age: 77
Posts: 22
Likes: 0
Received 0 Likes on 0 Posts
Near Miss Aricle Link

TTex600

Here is a link to the full wired scinece article by Ben Paynter

Close Calls Are Near Disasters, Not Lucky Breaks | Wired Science | Wired.com
gleaf is offline  
Old 15th Aug 2012, 20:14
  #807 (permalink)  
 
Join Date: Jul 2003
Location: An Island Province
Posts: 1,257
Likes: 0
Received 1 Like on 1 Post
jcjeant, we might assume that BEA are intelligent enough to understand the difficulties and limitations of a systemic investigation; and any findings might not fit the ICAO format. The accident can be, and should be viewed as systemic; the events emerged from within a particular combination of circumstances.

As TTex600 notes, previous incidents were recovered safely – we must learn from these. Perhaps one aspect is that it wasn’t the successful outcomes which were important, which were used to justify continued operation; but the assessment of how much the safety margins had been eroded, - the training and ability of all crews, in all conditions (hindsight).

The final report is ‘interestingly’ formal and may have been crafted with wider aspects of flight safety in mind. It is a challenge to the industry, to consider what could or should be done generically (systemically) to improve safety.
The report avoids use of overt ‘error’, instead considering the many factors which could influence human behaviour. In several ways this invites a change or strengthening of the ‘new view of human error’.
Based on the apparent divide in this forum, even amongst the identifiable professionals, the industry has a long way to go before acceptance the ‘new (systemic) view’, which appears to be essential as the majority of our industry now resides in the ‘highly reliable’ category. This shortfall might also reflect the standard of HF and CRM training, but also the views of operator management and regulators, all possible contributors in this accident.

How to be safe by looking at what goes right instead of what goes wrong.

For factors limiting learning; see Fundamental on Situational Surprise.

Last edited by alf5071h; 15th Aug 2012 at 20:16.
alf5071h is offline  
Old 15th Aug 2012, 20:39
  #808 (permalink)  
 
Join Date: Aug 2009
Location: Germany
Age: 67
Posts: 1,777
Likes: 0
Received 0 Likes on 0 Posts
The report avoids use of overt ‘error’, instead considering the many factors which could influence human behaviour
The BEA can't use the word "error" because :
In particular, States must start an investigation in case of a civil aviation accident or serious incident on their territory. It is specified that "The sole objective of the investigation of an accident or incident shall be the prevention of accidents and incidents" and that "It is not the purpose of this activity to apportion blame or liability"
If you said that someone made ​​a mistake (error) .. is bring against him a charge
On the other hand it would have been interesting (for public information) that BEA put in annex the entire history of pitot tube (since at least 1995)
The pitot tube is an important element in this accident
This would give an insight into how are functioning the official bodies responsible for air safety

In January 1999, due to a serious incident in Frankfurt April 5, 1998, the BFU (German) recommended changing certification standards Pitot probes
(Annex 13), the standards may be the cause of accidents.

01/99 The specification for the Pitot tubes should be changed so as
to allow unrestricted flight operations in heavy rain and under severe
icing conditions.

This safety recommendation was ignored.
Standards certification probes Pitot were modified by EASA after the accident in August 2009 (Appendix 50).
Note: The BEA has done it again this recommendation in its second interim report.
It confirms its importance

Last edited by jcjeant; 15th Aug 2012 at 21:58.
jcjeant is offline  
Old 15th Aug 2012, 22:16
  #809 (permalink)  
 
Join Date: Dec 2010
Location: Middle America
Age: 84
Posts: 1,167
Likes: 0
Received 0 Likes on 0 Posts
A "near miss", probability wise, is not a success. They are indicators of failure. If a flaw is systemic, it requires only a small twist of fate for the next incident to result in disaster. "Rather than celebrate then ignoring close calls, we should be learning from them and doing our best to prevent their recurrence." ......"most accident investigations work backward to determine the cause. A more effective way to curtail disasters is to get better at spotting the near miss"
and
In context of AF447, and considering the continued emphasis of some board participants on previously successful near misses (thirty something UAS incidents caused by pitot ice), I suggest that we begin to view those previous A330 UAS incidents as omens. Omens that the system failed to heed.
I don't necessarily agree with the tying together of these two quotes. First of all, going back for a long time in aviation, it has been a known fact that pitot tubes can clog for various reasons. Starting with the A-300, Airbus addressed this fact along with explanations and what to expect should it occur:



Additionally, AF, Airbus, EASA and other regulatory agencies discussed the pitot issue during various meetings. EASA interviewed pilots that experienced pitot clogging resulting in UAS situation. The interviewed pilots responses varied from being ho-hum to a non-incident although they reported it as being unusual. Other pilots never reported Pitot/UAS incidents at all. This feedback lead to EASA not issuing an immediate change out of Thales for Goodrich pitots.
Be Forewarned: The problem with pitots icing still exists, it can bite you at any time, there is no magical solution and there may not be in our lifetimes. And then too, the pitots themselves may not be entirely the problem. The location of the pitots in relationship to the airstream at their location could be a factor: Per Airbus, "Depending on the probe design and aircraft installation these installation effects can lead to the Liquid Water Content (LWC) at the probe location several times greater than the free-stream conditions." This could be true for ice crystals as well. Not much is actually known about ice crystal sizes, shapes, distributions and concentrations at high altitudes. Test chambers can only do so much without specific knowledge that would be variable at best, think snowflake differences. So now - the pilots:
Recognizing UAS can and will occur, every pilot receives some training regarding UAS and what to do should it happen. In the instance of AF, there was prior training and emphasis to the point of issuing every flight crew a handout notification of recent AF UAS occurrences and reminding them of what to do upon experience of UAS.
For all the the 30+crews and probably many, many more, it wasn't good luck, an indication of failure or an omen, it was a success due to good aviating.
Enough said....
Turbine D is offline  
Old 16th Aug 2012, 00:36
  #810 (permalink)  
 
Join Date: Jul 2009
Location: DFW
Age: 61
Posts: 221
Likes: 0
Received 0 Likes on 0 Posts
Yep, the AF447 crew received UAS training. But somewhere buried in the reports, it mentioned that said training was low altitude and that they never received any training for UAS or stall at cruise. The low alt/take off scenario has a memory item. 15 degrees nose up. Ring any bells?
TTex600 is offline  
Old 16th Aug 2012, 01:28
  #811 (permalink)  
 
Join Date: Jul 2003
Location: An Island Province
Posts: 1,257
Likes: 0
Received 1 Like on 1 Post
Thanks jcjeant.
In this instance, pitots are a ‘local’ technical problem ( Fundamental on Situational Surprise, para 3.2. ), and as you note, focus of attention on these would overlook an important aspect of ‘learning’ as to why the initial recommendation was ignored.
Opposed to ‘ignored’, I suspect that there was consideration and justification (risk assessment) as to why modifications or other mitigating action was not required at that time (Turbine D). Thus an important lesson might be to reconsider the process of risk assessment, by whom, and the assumptions made. Also, if BFU was really concerned, why wasn’t the recommendation’s rejection pursued?

Many of these issues have been discussed individually, but if reconsidered with a wider remit for safety and not just by ‘official bodies’, then we might identify some really important lessons, and aspects which can be improved.
For example, ‘officialdom’ is not responsible for safety, we all are. Thus why weren’t all of the blinding obvious issues in hindsight identified before the accident, or at least after the preceding incidents? If we could answer that we might be safer, but the answer involves understanding ourselves.
How can everyone in the industry improve their ability to generate foresight and act?
Do we really think about safety as we should; do we think?
Not always, because we are human, but we could do better if we thought about it.
alf5071h is offline  
Old 16th Aug 2012, 01:45
  #812 (permalink)  
 
Join Date: Aug 2011
Location: Grassy Valley
Posts: 2,074
Likes: 0
Received 0 Likes on 0 Posts
alf5071h

"Do we really think about safety as we should; do we think?
Not always, because we are human, but we could do better if we thought about it.


We would not be discussing this, if some off the reservation AF employee had not leaked ACARS. Neither would the wreck have been discovered....

Make no mistake, full damage control was applied, and missed the mark, completely. Subtract popular opinion and continued discussion, the final search would never have been mounted......

So to answer the question, we think about it when we have the facts, and are not misled and lied to by two bit managers and "Presidents".

Credit the Brasilians, and those who would not succumb to standard drill bs in the media...

imo
Lyman is offline  
Old 16th Aug 2012, 02:26
  #813 (permalink)  
 
Join Date: Dec 2010
Location: Middle America
Age: 84
Posts: 1,167
Likes: 0
Received 0 Likes on 0 Posts
But somewhere buried in the reports, it mentioned that said training was low altitude and that they never received any training for UAS or stall at cruise.
Yes, you are correct, they never received any SIM training at high altitudes for UAS or stall.
The low alt/take off scenario has a memory item. 15 degrees nose up. Ring any bells?
Yes, I am aware of the memory items. In the Airbus & AF English versions it reads 15º/TOGA but in the AF French version it reads TOGA/15º. We will never know for sure the significance of the 15º NU applied by the PF upon loss of the AP & A/THR. We would know if TOGA was applied at the same time or a few seconds later after pitch up.
Turbine D is offline  
Old 16th Aug 2012, 02:37
  #814 (permalink)  
 
Join Date: Aug 2009
Location: Germany
Age: 67
Posts: 1,777
Likes: 0
Received 0 Likes on 0 Posts
if some off the reservation AF employee had not leaked ACARS
Indeed .. those ACARS are a bombshell .. a kick in the anthill
Experts (other than the BEA) have early conduct an investigation and their findings was not the least (some members of PPrunes are not strangers to those discoveries)
Who was the AF "Assange" .. probably we'll never know ...

Last edited by jcjeant; 16th Aug 2012 at 02:39.
jcjeant is offline  
Old 16th Aug 2012, 02:43
  #815 (permalink)  
 
Join Date: Aug 2011
Location: Grassy Valley
Posts: 2,074
Likes: 0
Received 0 Likes on 0 Posts
Jcjeant
Who was the AF "Assange" .. probably we'll never know ...


Check the register for June 2, 2009, for recently fired employees.

Easy peasy......

Lyman is offline  
Old 16th Aug 2012, 06:49
  #816 (permalink)  
 
Join Date: Feb 2005
Location: Correr es mi destino por no llevar papel
Posts: 1,422
Received 1 Like on 1 Post
Originally Posted by TTex600
Why bother checking your posts if you can't tell the truth on your personal page? Are you not really a flight sim fan?

Your Honor, this pertains because it speaks to the credibility of the witness.
I am really a fan of certain flight sims. Also there are both photos of me and by me on airliners.net. Now, what effect does it have on my posts? Why are you not refuting the claims I made instead of mounting ad hominem attack?

Originally Posted by TTex600
Why would one place information on their personal info that is "unbelievable"?
To add apparent gravity to his claims. To help spread sciolism. To elicit certain reaction, e.g. : "Oh look, according to his public profile he is a pilot but he makes all kind of outrageously unrealistic statements. He's a living proof today's pilot are insufficiently trained" - take note I've used it merely as a hypothetical example and not as the reaction someone would want to be elicited.

But I submit that (some level of) decorum and respect is required before there can be a credible discussion.
That would be putting the form above the substance and while such an approach works fine while discussing art or philosophy, engineering & scientific facts we are supposed to be discussing here gain or lose nothing from their wrap. Nonsenses packed in respect & decorum have not helped and will not help understanding AF477 a bit.

Originally Posted by Organfreak
Why the Airbus Must Never Be Criticized, Upon Pain of Ridicule.
Those fearing "the pain of ridicule" would do well to try posting something true instead of promoting their misunderstandings as it. I don't find truth ridiculeworthy.

Originally Posted by Retired F4
It was flightpath stable in the pitch axis, roll axis being in roll direct.
Let me explain: flightpath is aeroplane's 4D trajectory through atmosphere, roll is a part of attitude, which is aeroplane's angular position relative to local gravity's vector. The two are extremely interdependent but are not the same and should not be confused. Now we have dealt with the terminology, your statement can be considered somewhat true but is irrelevant as we are not discussing the aeroplane which flipped on her back and dove inverted into the ground but one in which minor roll excursions were brought under control while she was pulled into stall.

I find insistence on discussing details before essentials are dealt with interesting form psychological PoW, slightly amusing and not particularly helpful in discussion.

Originally Posted by Retired F4
Not irrelevant in context to wrong statements like DW´s post.
Both are dealing with trivialities. It is my choice to ignore them.

Originally Posted by Retired F4
In the real world of air transport flying LOC´s are not common and recognition of high altitude LOC seems to be dubious, due to never trained (only in low altitude) and never talked about.
Real world's limit spread far beyond AF447. There was many an incident with all the precursors of AF447 that ended uneventfully. There are many a LoCs that are recovered before ground impact so they don't involve untimely dead therefore not causing emotions to run high. Consequently they seldom make it to second page on the PPRuNe thread, if they get discussed at all. Attempts to make judgment on how the whole world works just on one single accident are extremely unlikely to produce meaningful results.

Originally Posted by BEA
it is clear that almost all the crews that heard the stall warning considered it to be surprising and irrelevant.
While engineering part of the report was pretty solid, HF parts is pretty disappointing. It almost seems as if engineering analysis left many a head at BEA scratching, so they took a bunch of psychologists, taught them a bit about how aeroplanes work and let them loose on their findings. After they have returned with verdict "it-could-be-this-or-it-could-be-that", not a word was changed in final redaction for fear of altering the meaning experts wanted to convey. So we got some interesting ideas such as that it is more difficult to set the pitch when outside visual references are unavailable and stick forces in conventional and synthetic pitch feel aircraft were discussed in the context of stall testing, where trim stops at prescribed speed, while in the real world autopilots kept trimming well bellow minimum clean and usually dropped mistrimmed aeroplane into crews' hands at stall warning. "Almost all crews" certainly doesn't include those discussed at page 87.

Originally Posted by TTex600
In the August 2012 issue of Wired magazine, author Ben Paynter penned an article named, "The Fire Next Time". "The Fire Next Time"s discusses the paradox of the "close call".
Very nice, but FDM precedes Mr Paynter's article by a few decades.

Originally Posted by alf5071h
The report avoids use of overt ‘error’,
As does any. In official language of accident investigations there is no "pilot error", just probable and contributing causes.

Originally Posted by TTex600
The low alt/take off scenario has a memory item. 15 degrees nose up. Ring any bells?
Is it really so complicated to recognize you are above acceleration altitude if you have taken off four hours ago?
Clandestino is offline  
Old 16th Aug 2012, 09:50
  #817 (permalink)  
 
Join Date: Jun 2010
Location: Dortmund
Age: 54
Posts: 63
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by Clandestino
There are many a LoCs that are recovered before ground impact so they don't involve untimely dead therefore not causing emotions to run high. Consequently they seldom make it to second page on the PPRuNe thread, if they get discussed at all.
By the way, has the China Airlines 747 already been mentioned in this context? (Lost an engine at FL 410, stalled, tumbled wildly, and was recovered at 9000 ft. ASN Aircraft accident Boeing 747SP-09 N4522V San Fransisco, CA, USA) It is kind of ironic that they recovered, whereas the Air France and West Caribbean Airways crews didn't.
noske is offline  
Old 16th Aug 2012, 10:37
  #818 (permalink)  
 
Join Date: Jun 2009
Location: Oxford, England
Posts: 297
Received 0 Likes on 0 Posts
as discussed, completely different type of both pitot tube and aircraft. The 1995 issue was with Rosemount tubes on older types.
Muddying the waters yet again. Rather than writing the comment off in a
pithy one liner that says nothing in context, it might be usefull to have
some tech discussion on the actual point being made. Don't want to appear
offensive, but over sensitivity and constant refutations only add to the
noise.

What he was implying was that the general problem had been known about in
1995. No pointing fingers etc.

Having said that, this issue looks like one of complacency and regulatory
failure to take the problem seriously enough, probably with pressure from
the airline industry.

From what I can see, airbus have been working on this for years, but can
only make recommendations. They have no power to impose mandatory changes...
syseng68k is offline  
Old 16th Aug 2012, 11:12
  #819 (permalink)  
 
Join Date: Mar 2006
Location: Choroni, sometimes
Posts: 1,974
Likes: 0
Received 0 Likes on 0 Posts
Always remember

An Air France Airbus Axxx-300, registration F-Gxxx performing flight AF-4xx from xxx to Paris Charles de Gaulle (France), was enroute at FL350 about 145nm northeast of Point xxx in night and instrument meteorological conditions at around 01:11Z when the crew received an overspeed alert, the autopilot disconnected, the crew observed the indicated airspeeds had increased to 0.88 mach (MMO 0.86 mach) and 304 knots, the aircraft gradually increased its pitch attitude to 11 degrees and climbed with up to 5000 feet/minute up to FL380, reaching FL380 at 0.66 mach/ 205 KIAS - stall speed was computed at 202 KIAS - before the pitch attitude decreased again
- weather radar in 320NM range
- 19 kts below VLS
- "The pilot flying noticed the decreasing speed and selected Mach 0.93,"
- "the vertical speed increases through 5700 feet per minute, the crew does not notice the excessive climb rate, engine N1 is at 100%"


Yes this wasn't AF447, two years later an A340, same company.

Chilling....

Incident: Air France A343 near Guadeloupe on Jul 22nd 2011, rapid climb and approach to stall in upset

Last edited by hetfield; 16th Aug 2012 at 11:13.
hetfield is offline  
Old 16th Aug 2012, 13:05
  #820 (permalink)  
 
Join Date: Jul 2002
Location: UK
Posts: 3,093
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by syseng68k
Muddying the waters yet again. Rather than writing the comment off in a pithy one liner that says nothing in context, it might be usefull to have some tech discussion on the actual point being made.
Actually I was just a little loath to repeat myself and go around the hamster wheel yet again (post 494 this thread):

http://www.pprune.org/rumours-news/4...ml#post7334399

Pitot tube issues with occasional UAS problems are not specific to Airbus types and never have been.

Also, all this talk of an "AF Assange" who leaked a record that the French authorities would have preferred stayed hidden and swept the issue under the carpet is in very poor taste and deserves no more credence than the crackpot "WTC inside job" suggestions.
DozyWannabe is offline  


Contact Us - Archive - Advertising - Cookie Policy - Privacy Statement - Terms of Service

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