AF447
Join Date: Jan 2008
Location: London, England
Age: 56
Posts: 300
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by [URL="http://www.pprune.org/members/302559-clippedcub"
ClippedCub[/URL]]Three pitots is double redundant, at best.
1. lose one, down to two - 1st level of redundancy, and singly redundant if you exclude human interaction.
2. IF one of the remainder disagree, the pilot chooses which one he likes - 2nd redundancy level, but only due to human interaction.
3. Lose the last one, no backup. System is doubly redundant.
1. lose one, down to two - 1st level of redundancy, and singly redundant if you exclude human interaction.
2. IF one of the remainder disagree, the pilot chooses which one he likes - 2nd redundancy level, but only due to human interaction.
3. Lose the last one, no backup. System is doubly redundant.
Per Ardua ad Astraeus
Join Date: Mar 2000
Location: UK
Posts: 18,579
Likes: 0
Received 0 Likes
on
0 Posts
I'm sure I asked this before, but cannot now recall if was answered/deleted whatever.
I hear 'undercurrents' that are talking about loss of attitude data. There is nothing specific on anything posted here from the ACARS list to suggest that. The question (again?) is would the loss of the AD part of an ADIRU render the IRU part unusable/unavailable either de facto or due to software intervention?
I hear 'undercurrents' that are talking about loss of attitude data. There is nothing specific on anything posted here from the ACARS list to suggest that. The question (again?) is would the loss of the AD part of an ADIRU render the IRU part unusable/unavailable either de facto or due to software intervention?
Join Date: Jan 2001
Location: France
Posts: 168
Likes: 0
Received 0 Likes
on
0 Posts
Mojomoh
It is a fact that the BEA might very well work on this possibility. I might be wrong but in this case the latest ACARS fault :
0214 21-31-00-2 WRN ADVSRY
CABIN VERTICAL SPEED
LOSS OF ADR DATA
that has just be re-ordered by Desert Dawg, would have been the first warning, not the latest to have been be sent....
Normally the BEA should publish a preliminary report today and not the 2nd of July. At this date is the press point.
It is a fact that the BEA might very well work on this possibility. I might be wrong but in this case the latest ACARS fault :
0214 21-31-00-2 WRN ADVSRY
CABIN VERTICAL SPEED
LOSS OF ADR DATA
that has just be re-ordered by Desert Dawg, would have been the first warning, not the latest to have been be sent....
Normally the BEA should publish a preliminary report today and not the 2nd of July. At this date is the press point.
Join Date: Jun 2009
Location: Paris
Posts: 691
Likes: 0
Received 0 Likes
on
0 Posts
Squawk_ident:
Mojomoh
It is a fact that the BEA might very well work on this possibility. I might be wrong but in this case the latest ACARS fault :
0214 21-31-00-2 WRN ADVSRY
CABIN VERTICAL SPEED
LOSS OF ADR DATA
that has just be re-ordered by Desert Dawg, would have been the first warning, not the latest to have been be sent....
Normally the BEA should publish a preliminary report today and not the 2nd of July. At this date is the press point.
Mojomoh
It is a fact that the BEA might very well work on this possibility. I might be wrong but in this case the latest ACARS fault :
0214 21-31-00-2 WRN ADVSRY
CABIN VERTICAL SPEED
LOSS OF ADR DATA
that has just be re-ordered by Desert Dawg, would have been the first warning, not the latest to have been be sent....
Normally the BEA should publish a preliminary report today and not the 2nd of July. At this date is the press point.
2. CABIN VERTICAL SPEED is an ADVISORY (a green button will flash by intermitence on the cabin pressure panel). A cabine decompression issue would be a major issue and full alarms would be displayed by sound and message all over the cockpit. At this point, this fault is about one cabin pressure controller (a second one is in stand-by). This cabin controller needs a differential pressure to work (Cabin pressure & outside air pressure). When two or more ADIRUs are faulted, the outside air pressure is lacking and the cabin pressure can not be monitored automatically anymore. That's why Mandala noted: LOSS OF ADR DATA.
=> This is not a decompression issue.
3. No preliminary BEA report is expected today as it should be released thursday at the press conference.
S~
Olivier
Last edited by takata; 30th Jun 2009 at 11:58.
Join Date: Jun 2009
Location: NZCH
Age: 55
Posts: 172
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by Squawk Ident
It is a fact that the BEA might very well work on this possibility. I might be wrong but in this case the latest ACARS fault :
0214 21-31-00-2 WRN ADVSRY
CABIN VERTICAL SPEED
LOSS OF ADR DATA
that has just be re-ordered by Desert Dawg.....
0214 21-31-00-2 WRN ADVSRY
CABIN VERTICAL SPEED
LOSS OF ADR DATA
that has just be re-ordered by Desert Dawg.....
Join Date: Oct 2006
Location: Gone Flying...
Age: 63
Posts: 274
Likes: 0
Received 0 Likes
on
0 Posts
BOAC:
BOAC:
Maybe the answer to your question is here.
I'm sure I asked this before, but cannot now recall if was answered/deleted whatever.
I hear 'undercurrents' that are talking about loss of attitude data. There is nothing specific on anything posted here from the ACARS list to suggest that. The question (again?) is would the loss of the AD part of an ADIRU render the IRU part unusable/unavailable either de facto or due to software intervention?
I hear 'undercurrents' that are talking about loss of attitude data. There is nothing specific on anything posted here from the ACARS list to suggest that. The question (again?) is would the loss of the AD part of an ADIRU render the IRU part unusable/unavailable either de facto or due to software intervention?
Maybe the answer to your question is here.
Join Date: Nov 2006
Location: SoCalif
Posts: 896
Likes: 0
Received 0 Likes
on
0 Posts
ACARS Detail
This is the first I have seen of the detail of the failures reported by the ACARS, the number after chapter, such as the -15-0 after 34-11. Indeed, what is the source of this detail? Was it obtained from the original transmissions, or?
GB
GB
Join Date: Nov 2006
Location: SoCalif
Posts: 896
Likes: 0
Received 0 Likes
on
0 Posts
Altimeter Fail, Too?
The other iced pitot incidents did not mention loss of altitude indication, yet this ACARS report shows loss of air data to the transponder. The transponder has no reason to use airspeed. This is one failure that does not relate to the others.
GB
GB
Join Date: Jun 2009
Location: ATL
Age: 66
Posts: 131
Likes: 0
Received 0 Likes
on
0 Posts
The level of redundancy is a count of the available resources, not the number you can afford to lose.
If you're a computer, three pitots are singly redundant, since the computer can't decide who's bad when down to two. And if you have five computers, the computers themselves are triply redundant for the same reason.
Last edited by ClippedCub; 30th Jun 2009 at 14:44.
Join Date: Jun 2009
Location: Somewhere out there
Age: 38
Posts: 65
Likes: 0
Received 0 Likes
on
0 Posts
egg and chicken again - who/what/which came first ?
0209 START
0210 34-11-15-0 FLR EFCS2
EFCS1, AFS - PROBE PITOT 1+2/2+3/1+3 (9DA)
9DA=HEATING ELEMENT PITOT 1 (6DA1/PHC1)
Heating Element Pitot 1 suspected failed.
0210 27-93-34-0 FLR EFCS1
EFCS2-FCPC2(2CE2) WRG:ADIRU1 BUS ADR1-2 TO FCPC2
No Data from ADIRU 1, ADR 1 & 2 no sending signal to FCPC2
No ADR Data from ADIRU 1 to PRIM2.
0210 34-11-15-0 FLR EFCS2
EFCS1, AFS - PROBE PITOT 1+2/2+3/1+3 (9DA)
9DA=HEATING ELEMENT PITOT 1 (6DA1/PHC1)
Heating Element Pitot 1 suspected failed.
0210 27-93-34-0 FLR EFCS1
EFCS2-FCPC2(2CE2) WRG:ADIRU1 BUS ADR1-2 TO FCPC2
No Data from ADIRU 1, ADR 1 & 2 no sending signal to FCPC2
No ADR Data from ADIRU 1 to PRIM2.
Thank you !!!
From flight qantas 72 interim report:
Probe heat computer
Some of the PFR messages indicated a potential fault with the number-1 probe heat
computer (PHC). Those messages could be generated by either a PHC fault or by an
ADIRU fault. The PHC (serial number 2083) was tested by an authorised agency
and no fault was found. Based on a review of available information, the messages
related to the PHC were considered to be spurious.
Join Date: Jun 2009
Location: Somewhere out there
Age: 38
Posts: 65
Likes: 0
Received 0 Likes
on
0 Posts
phc
from post 1190:
Quote:
At FL 370 with a SAT to -51 ° C and a wind from 080 to about 18 Kts on AWY UB612 with OFF SET 1R, between the OBD and MLK in radio contact with Khartoum, as we were at the edge of layer cloudy with some light turbulence, I tied PAX.
We were at dusk with low brightness.
Then we entered the layer, and soon after we started having a slight BURNING SMELL that lasted about twenty seconds and that did not appear to be of volcanic origin (no smell of rotten eggs), but rather electrical smell to me and smell the air conditioning for the OPL. Then the smell has disappeared. The odor was confirmed by the PAX booth and PNC between rows 3 and 14 thereafter.
from a poster at the (already famous) Tim Vasquez website:
Quote:
I am an Airbus A330/A340 Senior Training Captain (IRE/TRE) with Cathay Pacific in Hong Kong. As I'm sure you can imagine we experience our fair share of CB activity; and between June and October - Typhoons. We regularly get small ice deposits on the windscreen wipers and ice detector as cold as -54C. Very small amounts, but ice none the less. It only occurs in the upper levels of the anvil of active Cbs and enough to justify the use on engine anti-ice.
On 28th Sept 2004 ( I was a a brand new Captain) there was well defined typhoon ( I can't remember the name) centred on airway A1 between Taiwan and Kagoshima in southern Japan. The SAT at FL390 was around -56C. Heading South, it looked like we could make it over the top of the storm. As we reached the southern rim of the eye the temperature rose instantly to -39C and we entered a violent Cb. The ice build up was dramatic to say the least. Most of the lower half of the windscreen became encrusted and we encountered an electrical BURNING SMELL (which is not uncommon in the A330 in upper cloud).
Once we exited the cloud, the ice disappeared pretty quickly. There was no noticeable effect on the instruments
Quote:
At FL 370 with a SAT to -51 ° C and a wind from 080 to about 18 Kts on AWY UB612 with OFF SET 1R, between the OBD and MLK in radio contact with Khartoum, as we were at the edge of layer cloudy with some light turbulence, I tied PAX.
We were at dusk with low brightness.
Then we entered the layer, and soon after we started having a slight BURNING SMELL that lasted about twenty seconds and that did not appear to be of volcanic origin (no smell of rotten eggs), but rather electrical smell to me and smell the air conditioning for the OPL. Then the smell has disappeared. The odor was confirmed by the PAX booth and PNC between rows 3 and 14 thereafter.
from a poster at the (already famous) Tim Vasquez website:
Quote:
I am an Airbus A330/A340 Senior Training Captain (IRE/TRE) with Cathay Pacific in Hong Kong. As I'm sure you can imagine we experience our fair share of CB activity; and between June and October - Typhoons. We regularly get small ice deposits on the windscreen wipers and ice detector as cold as -54C. Very small amounts, but ice none the less. It only occurs in the upper levels of the anvil of active Cbs and enough to justify the use on engine anti-ice.
On 28th Sept 2004 ( I was a a brand new Captain) there was well defined typhoon ( I can't remember the name) centred on airway A1 between Taiwan and Kagoshima in southern Japan. The SAT at FL390 was around -56C. Heading South, it looked like we could make it over the top of the storm. As we reached the southern rim of the eye the temperature rose instantly to -39C and we entered a violent Cb. The ice build up was dramatic to say the least. Most of the lower half of the windscreen became encrusted and we encountered an electrical BURNING SMELL (which is not uncommon in the A330 in upper cloud).
Once we exited the cloud, the ice disappeared pretty quickly. There was no noticeable effect on the instruments
Do the PHCs share any buses with other computers/controllers ?
Join Date: Jun 2009
Location: Somewhere out there
Age: 38
Posts: 65
Likes: 0
Received 0 Likes
on
0 Posts
3 pitots...
0
Bye Bye dual/triple pitot failure hypothesis...
210 34-11-15-0 FLR EFCS2
EFCS1, AFS - PROBE PITOT 1+2/2+3/1+3 (9DA)
9DA=HEATING ELEMENT PITOT 1 (6DA1/PHC1)
Heating Element Pitot 1 suspected failed.
EFCS1, AFS - PROBE PITOT 1+2/2+3/1+3 (9DA)
9DA=HEATING ELEMENT PITOT 1 (6DA1/PHC1)
Heating Element Pitot 1 suspected failed.
Join Date: Jun 2009
Location: dublin
Posts: 7
Likes: 0
Received 0 Likes
on
0 Posts
Bleve post # 2562: that's a good article from AERO.
On the 330/340 you can put ''aoa'' into the ACMS on MCDU 3 and this gives a direct readout of aoa typically 2.2 - 2.4 degrees nose up at fl 370 M.81. Now if only AB would copy that info to the PFD, and better still to a separate instrument on the instr panel....
On the 330/340 you can put ''aoa'' into the ACMS on MCDU 3 and this gives a direct readout of aoa typically 2.2 - 2.4 degrees nose up at fl 370 M.81. Now if only AB would copy that info to the PFD, and better still to a separate instrument on the instr panel....
Quote:
210 34-11-15-0 FLR EFCS2
EFCS1, AFS - PROBE PITOT 1+2/2+3/1+3 (9DA)
9DA=HEATING ELEMENT PITOT 1 (6DA1/PHC1)
Heating Element Pitot 1 suspected failed.
Bye Bye dual/triple pitot failure hypothesis...
210 34-11-15-0 FLR EFCS2
EFCS1, AFS - PROBE PITOT 1+2/2+3/1+3 (9DA)
9DA=HEATING ELEMENT PITOT 1 (6DA1/PHC1)
Heating Element Pitot 1 suspected failed.
Bye Bye dual/triple pitot failure hypothesis...
That this failure indication shows a failed PTC heating resistor/or wire connection or that it was impossible to keep the PTC at a high enough temperature remains unknown at this stage.
Join Date: Apr 2009
Location: Petaluma
Posts: 330
Likes: 0
Received 0 Likes
on
0 Posts
Short of asking the computer to record a "burning smell", then tag it and transmit to mx, the question remains in general what brought this a/c down in a "seemingly" familiar way to other incidents? I am curious about the logic re: pitot sampling. With three pitot heads there are three possible pairs of "source", but when one head "fails" there is only one "source" left since the computer will fail both remaining if there is a "disagree?" Besides, why are pitots still "pointy"? Ice starts at the sharp bits.
Interface. The weakness as I see it. At the very least, I see the foundation as basically backwards. At a critical time in terrible weather at night, I don't want the box to fall all over itself telling me what's wrong, and what to do to fix the computer. I want the box to give me a few crucial cues so the a/c can continue to fly. In other words, give me the good news about what is working, not why the computer has to flop the a/c into my lap. The important cargo is not the computer.
Interface. The weakness as I see it. At the very least, I see the foundation as basically backwards. At a critical time in terrible weather at night, I don't want the box to fall all over itself telling me what's wrong, and what to do to fix the computer. I want the box to give me a few crucial cues so the a/c can continue to fly. In other words, give me the good news about what is working, not why the computer has to flop the a/c into my lap. The important cargo is not the computer.
Join Date: Jun 2009
Location: Paris
Posts: 691
Likes: 0
Received 0 Likes
on
0 Posts
augustusjeremy:
Bye Bye dual/triple pitot failure hypothesis...
210 34-11-15-0 FLR EFCS2
EFCS1, AFS - PROBE PITOT 1+2/2+3/1+3 (9DA)
9DA=HEATING ELEMENT PITOT 1 (6DA1/PHC1)
Heating Element Pitot 1 suspected failed.
EFCS1, AFS - PROBE PITOT 1+2/2+3/1+3 (9DA)
9DA=HEATING ELEMENT PITOT 1 (6DA1/PHC1)
Heating Element Pitot 1 suspected failed.
The ground maintenance will download the complete data report from each real time fault or event displayed by ACARS; once it is done, it will appear that nothing is wrong with the probes: from the other reports, by Airbus and Air France, which are describing this sequence of pitot-static line icing, the point is that nothing is discovered "failed" once landed, neither the probe heat units, neither the probe heat computer, neither the probes themselves: ice obstruction is gone.
This ACARS is just pointing at "what may have failed" (9DA: Heating element pitot 1) in order to get this part ready, but also, it is on the first pitot-probe because it is a shortened message send by an expensive system (SATCOM); this doesn't mean that the sequence of faults is anyway complete and that the following won't include one or two remaining probes. Moreover, the Rudder Control Limiter system wouldn't be stopped without an unreliable speed condition concerning two or more units. A single unit fault is considered a minor issue almost transparent for the flight management.
S~
Olivier
Join Date: Jun 2009
Location: Somewhere out there
Age: 38
Posts: 65
Likes: 0
Received 0 Likes
on
0 Posts
inertial reference (again)
Takata,
I am really getting very confused with all this conflicting information.
In the following message:
I know you didn't post it... but what do you think is a guess and what is indeed documented ?
How can you get a fault of a inertial reference unit out of conflicting raw air data ? Isn't inertial reference data independent from air data ?
And isn't this fault detected by simple comparison involving INERTIAL DATA only ?
This is a mess...
I am really getting very confused with all this conflicting information.
In the following message:
0211 34-12-34-0 FLR IR2
EFCS1X,IR1,IR3, ADIRU2 (1FP2)
ADIRU2(1FP2) - ADR2 self monitoring & PHC rejects own data
Loss of discrete data from ADR2 = PITOT 2, STATIC 2L, STATIC 2R, TAT 2, AOA 2.
NAV DISAGREE CONCLUSION DELAYED - ADDITIONAL FAILURES - RECOMMENCE FAULT ISOL
EFCS1X,IR1,IR3, ADIRU2 (1FP2)
ADIRU2(1FP2) - ADR2 self monitoring & PHC rejects own data
Loss of discrete data from ADR2 = PITOT 2, STATIC 2L, STATIC 2R, TAT 2, AOA 2.
NAV DISAGREE CONCLUSION DELAYED - ADDITIONAL FAILURES - RECOMMENCE FAULT ISOL
How can you get a fault of a inertial reference unit out of conflicting raw air data ? Isn't inertial reference data independent from air data ?
And isn't this fault detected by simple comparison involving INERTIAL DATA only ?
This is a mess...
