(1) Go to the appropriate section of the Index of Warnings and Malfunctions, find the text of the fault alphanumerically and note the ATA reference and section of the TSM chapter. Alternatively, if the user knows which system has generated the fault this step can be skipped and the trouble shooting started at the next text.
EFF : ALL
∞∞00-INTRO∞∞∞∞∞∞∞∞∞∞Page 26
Feb 01/05
R
CES
Trouble Shooting Faults Reported on the PFR
Figure 007
EFF : ALL
∞∞00-INTRO∞∞∞∞∞∞∞∞∞∞Page 27
Feb 01/05 R CES
Trouble Shooting Faults not Reported on the PFR
Figure 008
EFF : ALL
∞∞00-INTRO∞∞∞∞∞∞∞∞∞∞Page 28
Feb 01/05 R CES
(2) Go to the ATA chapter, locate the correct section of the FAULT SYMPTOMS (page block 101), find the correct sub-division (if applicable) and fault, correlate the CFDS fault message (if applicable) and note the associated task number and page number.
NOTE : For further fault isolation use the source (SOURCE column)
____ and/or CFDS fault message identifiers (IDENT block).
(3) Go to the FAULT ISOLATION PROCEDURES (P. Block 201) page number, confirm the task number (at the top left) and do the fault isolation procedure.
E. Trouble Shooting CFDS Fault Messages
(Ref. Fig. 009)
The following general procedure describes trouble shooting of CFDS Fault
Messages including class 3 messages. Class 3 Fault Messages are shown on
the SYSTEM/REPORT TEST CLASS 3 FAULT pages.
(1)
Note the CFDS fault message ATA chapter reference. Alternatively, the user can find the message alphanumerically in the Index of CFDS Fault Messages which gives the ATA chapter and section reference.
(2)
Go to the ATA chapter CFDS section, find the message and note the associated task and page number.
(3)
Go to FAULT ISOLATION PROCEDURES (page block 201) page number, confirm the task number (at the left) and do the fault isolation procedure.
F. Use of the Index of Warnings/Malfunctions and Index of CFDS Fault Messages
The indexes are provided mainly for additional information in situations
where either the ATA reference, or system (chapter) of a warning,
malfunction or CFDS fault message is not known. The indexes allow entry
using the text of a warning, malfunction or CFDS fault message and are
sorted alphanumerically to facilitate this.
In some cases it is possible for the trouble shooting to be covered in a
chapter different to that of the ATA reference given by the warning,
malfunction or CFDS fault message. In such a case the indexes are useful
to direct the trouble shooter to the correct chapter.
Use of the indexes is explained in Entry into the TSM (Ref. Para 3.B.(2)
and How to Use the TSM (Ref. Para. 3.B).
EFF : ALL
∞∞00-INTRO∞∞∞∞∞∞∞∞∞∞Page 29
Feb 01/05
R
CES
Trouble Shooting CFDS Fault Messages
Figure 009
EFF : ALL
∞∞00-INTRO∞∞∞∞∞∞∞∞∞∞Page 30
Feb 01/05 R CES
G. Trouble Shooting Tips
Tips for using the various TSM page blocks and useful additional information are given in the following paragraphs:
(1) Fault symptoms (P. Block 101) The primary fault only is given in the TSM to avoid confusion with too many associated faults. The list of faults in the Fault Symptoms (P. Block 101) is customized by airline. This means that one fault symptom is effective for at least one aircraft in the fleet.
(a) APU Fault Symptom Peculiarities (Ref. Fig. 010) Whenever the operation of the APU may result in damage to the aircraft, the APU or the Electronic Control Box (ECB) of the APU, the ECB shuts down the APU automatically. The cause of the shutdown and associated LRUs are stored in the ECB memory. This information is available on the APU system related CFDS menu page APU SHUTDOWNS.
i.e. NO FLAME (shutdown cause)
IGNITION EXCITER P12 (faulty LRU) In parallel the ECB generates a maintenance message with associated ATA Chapter and related Fault Class of the faulty LRU. This maintenance message is available on the Post Flight Report (PFR), which is, in the AIRBUS TSM philosophy, the entry point to the TSM.
中國航空網 www.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：A320 Trouble Shooting Manual 排故手冊 介紹 2(10)
