Escolar Documentos
Profissional Documentos
Cultura Documentos
A 319/320/321
ATA 00-03
Trouble Shooting (TSM)
Line & Base Maintenance
Page: i
TABLE OF FIGURES
Figure 1 Post Flight Report (PFR) Example . . . . . . . . . . . . . . . . . . . 3
Figure 2 Intentionally left blank . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Figure 3 TSM Index of Warnings/Malfunctions . . . . . . . . . . . . . . . . 7
Figure 4 I-ECAM Page (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Figure 5 TSM Index of CMS Fault Messages . . . . . . . . . . . . . . . . . 11
Figure 6 I-CMS Page (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Figure 7 TSM INTRO Table of Contents . . . . . . . . . . . . . . . . . . . . . . 15
Figure 8 TSM ATA Chapter Table of Contents . . . . . . . . . . . . . . . . . 17
Figure 9 TSM Fault Symptoms (Page Block 101) . . . . . . . . . . . . . . 19
Figure 10 TSM Fault Symptom Page (Example) . . . . . . . . . . . . . . . 21
Figure 11 TSM Fault Isolation Procedures (Page Block 201) . . . . 23
Figure 12 TSM Block Diagrams (Page Block 301) . . . . . . . . . . . . . 25
Page: ii
Lufthansa Technical Training
TROUBLE SHOOTING A320/A321
Introduction
00
INTRODUCTION When you can find a corresponding FAILURE message, you have to report it
the log book ( ACTION field ).
When there is no FAILURE message in the PFR, you have to report in the log
MAINTENANCE PHILOSOPHY book:
”No CFDS Failure message”.
General
If you use ATA 2126 and the time 1712 in the part ECAM WARNING MES-
Entry in trouble shooting process is required,when a fault is reported by the
SAGES as a reference, you will find in the part FAILURE MESSAGES ATA
flight crew.(warnings/malfunctions)
212651 and also the time 1712. The associated FAILURE message runs:
As the CFDS (Centralized Fault Display System ) is the main aid for trouble- ”EXTRACT FAN 18HQ”.
shooting, the line mechanic has to verify in the PFR ( POST FLIGHT REPORT)
Next step of trouble shooting :
if a fault message is correlated to the reported warning/malfunction. This cor-
relation constitutes the fault symptom. Confirmation of the ECAM/FAILURE messages.
A back-up of the printed PFR is available on the MCDU (multipurpose control Normally the confirmation is done by a test .
/display unit) in form of the Last Leg Report and Last Leg ECAM Report. It Because there are several tests possible for different systems, you have to go
should only be used if the printed PFR is not available as the presentation is first to the TSM to find out, which one is the right one.
not so friendly.
Other reports in the log book, resulting from EIS flags, ECAM SD advisories,
local indications or crew observations require an immediate usage of the TSM
(Trouble Shooting Manual).
In the following the use of the TSM is described. This includes the description
of the layout of the TSM.
The philosophy of the troubleshooting manual is to guide the trouble shooter
from a reported fault ( log book entry, CFDS post flight report, ECAM status,
crew observations ) to a correct procedure to isolate the fault.
A copy of the POST FLIGHT REPORT printout is shown on the following page
( FIGURE 1 ).
In the part ECAM WARNING MESSAGES you can find conformity with the
entry of the log book.
A correlation between the ECAM message and a FAILURE message, send by
the system BITE of the corresponding system computer, is also possible.
The correlation will be done by comparing the ATA chapter and the time (GMT)
from ECAM message and FAILURE message. They must correspond.
INTRODUCTION (INTRO)
The introduction describes the purpose of the TSM and gives informations for
the usage of the TSM and the CFDS e.t.c.
The table of contents of the INTRO is shown on the next page (Figure 7).
For Training Purposes Only
8. Close-Up
Depending on the fault confirmation and /or fault isolation, a close-up pro-
cedure may be necessary in order to put the aircraft back to its initial con-
figuration.