ACARS failure message
Thread Starter
Joined: May 2010
Posts: 230
Likes: 138
From: Usually on top
ACARS failure message
Hi all,
is anyone able to decode this?
#CFB.1/FLR/FR1608161633 46213406AFS 1,FWS,,,,,,ATSU(1TX1)/MCDU2(2CA2),HARD
systems affected:
Autoflight system 1
Flybywire system
MCDU2
and ?
any ideas what kind of failure might provoke that sequence?
is anyone able to decode this?
#CFB.1/FLR/FR1608161633 46213406AFS 1,FWS,,,,,,ATSU(1TX1)/MCDU2(2CA2),HARD
systems affected:
Autoflight system 1
Flybywire system
MCDU2
and ?
any ideas what kind of failure might provoke that sequence?
Joined: Mar 2009
Posts: 60
Likes: 0
From: Prague
This message is in very unusual format,what was source?
Looks like ATSU(1TX1)/MCDU2(2CA2),HARD fault, fault code 46-21-34, flight phase 06, detected by AFS,FWS, date 160816, time 1633, unable identify A/C.
Most probably cause from my point of view is failure of ATSU.
Looks like ATSU(1TX1)/MCDU2(2CA2),HARD fault, fault code 46-21-34, flight phase 06, detected by AFS,FWS, date 160816, time 1633, unable identify A/C.
Most probably cause from my point of view is failure of ATSU.
Joined: Feb 2002
Aviation Qualifications: AME
Posts: 4,184
Likes: 1,123
From: UK
Why do you want to know?
A snag like this would only be of interest to maintenance engineers and flight crew.
ATSU/ATIMS reset probably a quick fix.
Unless it's part of received data from a missing aircraft........
A snag like this would only be of interest to maintenance engineers and flight crew.
ATSU/ATIMS reset probably a quick fix.
Unless it's part of received data from a missing aircraft........
