Taxiing A320 on snow - spurious ECAMs from Rad Alt
Thread Starter
Join Date: May 2005
Location: On a good day - at sea
Posts: 263
Likes: 0
Received 0 Likes
on
0 Posts
Taxiing A320 on snow - spurious ECAMs from Rad Alt
FCOM 2.04.10 P12 states something to the effect of -
"...During taxi on surfaces contaminated with snow the radio altimeters may not compute any data which results in 'DUAL ENG FAILURE', 'ANTI ICE CAPT TAT FAULT', 'ANTI-ICE F/O TAT FAULT: 'LG SHOCK ABSORBER FAULT' ECAM warnings that may be triggered. These ECAMs may be disregarded...."
Theses spurious ECAMs pop up 2-3 times a yr in a midsized fleet but for an individual crew member they're a rare occurrence. So rare in fact that if it happens, there's little hope they'll remember a few obscure FCOM comments on the issue so everything stops to deal with ECAMs.
Even if they did remember the obscure comment, who in their right mind would simply (Airbus words) disregard them?
A call to Maint just proves the problem is as obscure to them as it is to crew.
I suppose it's easy enough to publish a little reminder on the anomaly but even so how can they simply be disregarded.
Anybody have any insight here?
Any suggestions on how to deal with the problem when they do pop up?
eg In the absence of indications to the contrary (Engs still running) just clear them and use RCL to check for latched msgs then do an FWC reset?
"...During taxi on surfaces contaminated with snow the radio altimeters may not compute any data which results in 'DUAL ENG FAILURE', 'ANTI ICE CAPT TAT FAULT', 'ANTI-ICE F/O TAT FAULT: 'LG SHOCK ABSORBER FAULT' ECAM warnings that may be triggered. These ECAMs may be disregarded...."
Theses spurious ECAMs pop up 2-3 times a yr in a midsized fleet but for an individual crew member they're a rare occurrence. So rare in fact that if it happens, there's little hope they'll remember a few obscure FCOM comments on the issue so everything stops to deal with ECAMs.
Even if they did remember the obscure comment, who in their right mind would simply (Airbus words) disregard them?
A call to Maint just proves the problem is as obscure to them as it is to crew.
I suppose it's easy enough to publish a little reminder on the anomaly but even so how can they simply be disregarded.
Anybody have any insight here?
Any suggestions on how to deal with the problem when they do pop up?
eg In the absence of indications to the contrary (Engs still running) just clear them and use RCL to check for latched msgs then do an FWC reset?
Join Date: May 2007
Location: Europe
Posts: 99
Likes: 0
Received 0 Likes
on
0 Posts
Resets to the FWC would do nothing. The problem comes from the readio altimeter data. I`ve seen this once but can`t remember wich warning it gave. You will notice it`s spurrious because ECAM warning will appear and disapear in seconds and Radio altitude data will be constantly changing in your PFD, has usually happens with wet taxyways and ramps. Disregard those warning until you`re on the runway. Runways are always clean and radio altimeter will then give valid data. By then all warnings will disapear. If not... well in that case I would treat it has a serious warning.
Join Date: Apr 2005
Location: Stockholm Sweden
Age: 74
Posts: 569
Likes: 0
Received 0 Likes
on
0 Posts
then do an FWC reset?
Just cycling the FWC cbs will do nothing, you will not erase the FWC memory.
Thread Starter
Join Date: May 2005
Location: On a good day - at sea
Posts: 263
Likes: 0
Received 0 Likes
on
0 Posts
Thanks folks - some good info here
Swede
Could you clarify that. Wouldn't you clear a latched AVNS SMK or CARGO SMK on the ground after the fact. Wouldn't you clear them by doing a FWC reset ie dumping the memory?
Swede
Could you clarify that. Wouldn't you clear a latched AVNS SMK or CARGO SMK on the ground after the fact. Wouldn't you clear them by doing a FWC reset ie dumping the memory?
