background
x
loader
Troubleshooting
arrow By ATA By Message Color By Observed Faults by MDCBy Tips

Select color for CAS message that you wish to troubleshoot

(WARNING)
RED MESSAGE
(CAUTION)
AMBER MESSAGE
(ADVISORY)
CYAN MESSAGE
(STATUS)
WHITE MESSAGE
Require immediate crew attention. These messages are accompanied by flashing master warning, triple chime attenson with or without voice message or dedicated tone. Require immediate crew awareness and future crew action may be required in the form of alternate system selection or performance limitation. These message are accompanied by flashing master caution and a single chime. Indicate safe or normal system operation which require crew awareness, over and above the dark cockpit philosophy. Indicate minor failures or reduction in systems capability, which require no crew action.

For AOG assistance contact:

CRC Montreal (YUL)
Quick Links

Cabin temperature during descent:

Please refer to the following AW:

Multiple Faults Reported By IASC

Multiple faults from IASC associated with various systems.

The Integrated Air Management Controller (IASC) controls multiple systems on the aircraft. There’s a possibility of an internal failure affecting multiple systems of the aircraft at the same time. This makes it an easy target for removals and generates a higher number of NFF at the vendor level when units are removed early in the troubleshooting process.

In cases where multiple CAS messages are posted on systems that are not directly associated, we may consider the IASC as the most probable cause.

For example, CAS messages posting at aircraft power-up for the Pressurization system and the Bleed Detection System.

As a reminder, the IASC reports fault(s) for the Air Conditioning (PACK), Bleed and Pressurization systems.

When this type of fault on various systems are reported by the IASC and are posting at power-up do as follows:

  • Confirm with crew or MDC timestamp that the fault occurs at the same time.
  • Reset the IASC and look if both faults still post after the PBIT.
  • Swap the IASC and see if the faults have transferred to the opposite side or to different systems.

If the faults transferred and the IASC is clearly identified as faulty replace it.

If the fault stays on original side the sub-system will need to be troubleshoot independently based on the reported MDC fault.

The recommendation is to find the B3 code in the MDC and carry out the troubleshooting procedure of the sub-system as per the SmartFix Plus Troubleshooting procedure associated with the MDC Fault code.

Registered and/or unregistered trademarks of Bombardier Inc. or its subsidiaries. © 2015 Bombardier Inc. All rights reserved.