Page 350 - (KU)01-75GAJ-1.5 - Change 1

INTRO

EP'S (KU)01-75GAJ-1.5 FIGURES

1.10.7 DATA BUS FAILURES
ACAWS
The probability of any data bus failure is extremely remote and requires
failure of both channels of a given bus. In all cases, data bus failures
result in an MC failure but the impact and indications depend on the GROUND
location of the failure in relation to the remaining MC. In many cases,
the remaining MC will most likely take over the full functionality of the
bus with no additional failure indications. In the unlikely event both data TAKEOFF
bus channels of the remaining MC also fail, a data bus failure ACAWS
will be given and the function of that bus will be lost.
FIRE/SMK
NORM Refer to the accompanying procedure for crew actions and possible
mission impacts. A partial bus failure is also possible (but equally unlikely)
and will be indicated by an MC fail and loss of those components not PRES/OXY
NOT FOR FLIGHT
in communication with the remaining MC. A bus failure ACAWS will
most likely not be given. In this case, the associated ACAWS should be
referenced for the failed components. ENG/PROP

NOTE
FUEL
Reference to level of ACAWS message is indicated by
(W) Warning, (C) Caution, or (A) Advisory.
AAR
NOTE
SPEC The following ACAWS messages include a list of likely ELEC
associated ACAWS messages that also appear. However,
there may be some variability in which messages are
DFWXDOO\ GLVSOD\HG GXH WR WKH FRQ¿JXUDWLRQ RI WKH DLUFUDIW HYD
at the time of the failure.

(End of Procedure) FLT CTRL

1.10.7.1 L AV DATA BUS FAIL* GEAR

Condition:
DOR/RMP
Both channels of the data bus have failed. Failure will be preceded by
PERF an MC failure.

Associated ACAWS: JETTISON

‡ MC 1 (or 2) FAIL (C)
‡ RADAR DEGRADED (C) LANDING

‡ NIU 1 FAIL (C)
‡ NIU 4 FAIL (C) DITCHING
‡ ATCS DEGRADED (C)
‡ INU 1 FAIL (C) BAILOUT
‡ TCAS FAULT (A)

OPER ‡ GCAS FAIL (A) FAULT LG

1 -310 Use, copying and/or disclosure is
governed by the statement on the
BACK title page of this document. CHARTS