Customer : AHK Manual : TSM

Type : A300-600 Selected Effectivity : 001-008

Rev. Date : Jun 01, 2016
GUIDELINES FOR EVALUATION OF MEMORIZED FAULT INDICATIONS
** ON A/C ALL
5. GUIDELINES FOR EVALUATION OF MEMORIZED FAULT INDICATIONS
A. Procedure
This procedure can be utilized to determine the serviceability of a system that shows a Memorized Fault Annunciator (MFA) illuminated on any of the maintenance
panels (470VU, 471VU OR 472VU).
The MFA's can be divided into two types ;
(1) The first type of MFA will be lit when a fault has been detected and logged into a system memory. The fault will have caused some kind of visible warning
in the flight deck, which in turn will generate a pilot report (PIREP). The MFA will alert maintenance personnel to the existence of a memorized record of the
fault, to aid troubleshooting.
(2) The second variety of MFA illuminates when a fault is detected that is not exhibited in the flight deck, regardless of duration. These faults are effectively
'hidden' from the crew, to minimize flight deck workload. This second example are the MFA's that are called up to be 'read' by a routine job card.
B. Reading the Memorized Fault Annunciators
(1) On maintenance panel 472VU, select the READ/TEST switch to the READ position.
(2) Check and note whether the required MFA is illuminated. If not, then select READ/TEST switch to TEST, to check that MFA bulb is serviceable. Relamp if
necessary. Select READ/TEST switch back to READ.
(3) Press maintenance panel RESET switch(es) to turn off all illuminated MFA's. If the recorded MFA re-illuminates then the monitored system has either a hard
fault (most likely), or in some cases a memorized fault carried within the memory of the relevant system.
C. Evaluation of Result
(1) Faults can be divided into two categories.
(a) Hard fault
- The fault still exists at the time of interrogation and normal utilization of the troubleshooting manual (TSM) is recommended.
(b) Soft fault
- This is when a system has detected a failure at some time in the past and memorized it. Subsequently the fault condition has
cleared, but may be the first indication of an impending failure. Analysis in accordance with Para. D. should determine the
maintenance course of action.
D. Soft Failure Maintenance Action
(1) The course of maintenance action is dependant upon the MFA in question. ALL of the following noted MFA's indicate that a "hidden" fault has been detected
and requires action per this paragraph to ensure serviceable system operation:
SYSTEM RELATED MFA'S
CABIN AIR DISTRIBUTION "FWD, MID, AFT CABIN"/FANS MONITOR
TRIM AIR CONTROL "HOT AIR SUPPLY - HI PRESS"
CARGO COMPT TEMP CONTROL "FWD AND BULK CARGO"/FAN MONITOR
(IF INSTALLED)
Print Date: August 22, 2016 Page 1 of 2
© AIRBUS S.A.S. ALL RIGHTS RESERVED. CONFIDENTIAL AND PROPRIETARY DOCUMENT.
 Customer : AHK Manual : TSM
Type : A300-600 Selected Effectivity : 001-008
Rev. Date : Jun 01, 2016
GUIDELINES FOR EVALUATION OF MEMORIZED FAULT INDICATIONS

SYSTEM RELATED MFA'S

ELECTRICAL POWER "GPCU/BITE" DISPLAY
CARGO COMPT SMOKE DET "CONTROL UNIT/BITE DISPLAY"
(IF INSTALLED) (IF INSTALLED)
FUEL QUANTITY INDICATING "FUEL QTY/SYS MONITOR"
NORMAL BRAKING/ANTISKID "ANTISKID/BITE"
APU AIR INTAKE SYSTEM "FLAP CTL"
APU STARTING "START CTL"
APU POWER CONTROL ECB "ECB BITE" DISPLAY
CENTRAL WARNING SYSTEM "FWC1/FAULT" "FWC2 FAULT"
"ECAM BITE/LOAD"

- A bite test should be made on the relevant system, if possible.

- Any fault that is then detected should be troubleshot and rectified in accordance with the TSM.
- An operational test may be necessary if bite is not available.
(2) Any other MFA that is found illuminated should be treated in the following manner:
- Make reference to the flight log book to check for related system Pilot/Maint reports. If a related report is found then this will help to
determine if maintenance action is necessary.
For example, the "EFIS BITE/LOAD" MFA is found set while carrying out a routine "READ" operation on the ECAM BITE/LOAD
MFA. On the last leg the crew reported an EFIS display unit fault, which has already been replaced. In this case a genuine fault
was detected and rectified, but the MFA will relight after reset because the detected fault is still within the flight warning computer's
memory.
- When no Pilot/Maintenance reports exist then these MFA's can be considered as evidence of a spurious indication and erased (if
possible). No further maintenance action is necessary.

End of document

Print Date: August 22, 2016 Page 2 of 2

© AIRBUS S.A.S. ALL RIGHTS RESERVED. CONFIDENTIAL AND PROPRIETARY DOCUMENT.