TSM - HIM - A318/A319/A320/A321 REV DATE: May 01/2022

Tail Number - MSN - FSN: ALL

8. Philosophy and Use
swap

INTRODUCTION
** ON A/C FSN ALL
8. Philosophy and Use
A. Philosophy
(1) The Maintenance concept is based on the use of Centralized Fault Display System (CFDS) and
TSM.
(2) CFDS
The CFDS directly monitors and identifies faulty Line Replaceable Units (LRUs) in the aircraft
systems and displays items identified as faulty to the maintenance crew. This is essentially
achieved by analysis of all cockpit events which are triggered by the monitoring of the aircraft
systems. Refer to paragraph 8 for a description of the CFDS and how to use it.
The CFDS contributes also to avoid unjustified removals of equipment because the CFDS
makes a detailed analysis to identify the responsible LRUs and to confirm that the event was
actually due to a hardware failure and not an intermittent fault.
To achieve its purpose, the CFDS has several major functions which supply:
- A maintenance Post Flight Report (PFR) which is printed at the end of each flight. The
PFR (Ref. Para. 8.E.(1) allows association of ECAM warnings and CFDS maintenance
messages.
- Directly usable maintenance messages which identify faulty LRUs.
- Access to test of the aircraft systems.
(3) TSM philosophy
The TSM is a trouble shooting guide of all probable aircraft faults monitored and displayed by
the aircraft systems. Faults not monitored by the aircraft systems are also covered.

NOTE: Based on the guidance from the TSM, it is the operator responsibility to establish
specific procedures regarding fault management in accordance with their local
regulations.
B. How to Use the TSM
(1) Types of faults
In the TSM, there are two basic types of faults : monitored faults and non-monitored faults.
Monitored faults are those which are monitored and displayed by the aircraft systems (mainly
ECAM and CFDS).
Non-monitored faults are generally not displayed by the aircraft systems and can be of a general
nature, such as: "Nose landing gear doors slow to move".
(a) Monitored faults:
- ECAM
- EFIS
- CFDS
(b) Non-monitored faults

JCP Title: swap © AIRBUS S.A.S. ALL RIGHTS RESERVED. Page 1 of 7

CONFIDENTIAL AND PROPRIETARY DOCUMENT. PRINT DATE: May 08/2022
 TSM - HIM - A318/A319/A320/A321 REV DATE: May 01/2022
Tail Number - MSN - FSN: ALL
8. Philosophy and Use
swap

- Crew and/or maintenance observations.

- local effects.

NOTE: All these types of fault are used as entry points into the TSM.
(2) Trouble Shooting Function
Trouble shooting function is initiated by a logbook entry from the flight crew or maintenance
crew.
The logbook entry serves as an entry point into the TSM using Fault Symptoms, Warnings
/Malfunctions, or CFDS Fault Message, depending on the type of fault. The troubleshooter is
directed to the procedure to isolate the fault.
The monitored faults (ECAM, EFIS) reported by the flight crew are usually associated with CFDS
fault messages. The association principle of a Warning Malfunction and a CFDS fault message
is described in paragraph 8.E.(1)(b).
CFDS fault messages are used by maintenance crews. They can be displayed alone without an
associated warning or malfunction, in which case they may be the entry point for maintenance-
related troubleshooting. TSM entry is via the appropriate reported effect (monitored or non-
monitored) or the CFDS Fault Messages using the message text.
Crew or maintenance observations are usually a single fault without an associated CFDS fault
message. TSM entry is via fault text or keywords and ATA chapters.
C. Trouble Shooting of Faults Reported on the PFR
The following general procedure describes trouble shooting of Upper ECAM DU warnings, ECAM STS
(Status) Maintenance messages or CFDS fault messages given on the PFR.
(1) Compare the ECAM warning or ECAM STS message with the CFDS fault message (if
applicable) on the PFR to obtain the fault symptom and the ATA chapter reference.

NOTE: A time difference of 1-3 minutes between the fault message and the warning message
may occur due to CFDIU internal behaviour.
(2) Use the Troubleshooting function to retrieve the fault symptom using Warnings/malfunctions or
the correlated CFDS messages and retrieve the associated fault isolation procedure.
D. Trouble Shooting of Faults not Reported on the PFR
The following general procedure describes troubleshooting of Inop System messages, Lower ECAM
DU flags/advisories, local warnings and crew or maintenance observations.
(1) Use the Trouble Shooting function to retrieve the fault symptom and correlate the CFDS
message (if any).
(2) The fault isolation procedure is displayed after identification of the relevant fault symptom.
E. Trouble Shooting of CFDS Fault Messages
The following general procedure describes troubleshooting of CFDS Fault Messages.
(1) Note the CFDS fault message ATA chapter reference.
Use the troubleshooting function to retrieve the CFDS message. The fault isolation procedure is
displayed when the CFDS message is identified.
F. Trouble Shooting Tips

JCP Title: swap © AIRBUS S.A.S. ALL RIGHTS RESERVED. Page 2 of 7

CONFIDENTIAL AND PROPRIETARY DOCUMENT. PRINT DATE: May 08/2022
 TSM - HIM - A318/A319/A320/A321 REV DATE: May 01/2022
Tail Number - MSN - FSN: ALL
8. Philosophy and Use
swap

(1) Fault symptoms

Fault Symptoms given in the TSM contain primary faults (identified as "Correlated with" in the
Troubleshooting function) and associated faults (identified as "Possible Warnings/Malfunctions"
in the Troubleshooting function).
(a) APU Fault Symptom Peculiarities
Whenever the operation of the APU may result in damage to the aircraft, or to the APU or
the Electronic Control Box (ECB) of the APU, the ECB shuts down the APU automatically.
The cause of the shutdown and the associated LRUs are stored in the ECB memory. This
information is available on the APU SHUTDOWNS menu page of the CFDS.
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.
i.e. ATA 494138
CLASS: 1
IGNITION EXCITER P12
However, during several operator conferences concerning the APU, it has been shown
that most operators prefer to enter the TSM via the information of the APU SHUTDOWNS
menu, which shows the same faulty LRU as the PFR but additionally the shutdown
reason.
It has been decided to follow the operators preference and to combine the PFR
maintenance message with the Shutdown cause in one Fault Symptom.
i.e. Source Message ATA Class
ECB NO FLAME ASD *
associated with
ECB IGNITION EXCITER P12 494138 1
(2) Fault isolation procedures
Ref. Fig. Computer Reset Flowchart
A computer reset may clear intermittent fault without correcting the cause. In some cases a
computer reset may hide failure conditions (i.e. in-flight condition no longer present on ground)
that may lead to unsafe conditions on the next flight.
The system reset guidelines detailed in the TSM provide a reset table and the system reset
restrictions to confirm intermittent faults or faults generated by electrical transient.
(a) Fault confirmation
1 Permanent fault
The fault is confirmed on the ground by performing the test given in the fault
confirmation paragraph. Consequently, the procedure must be applied to
troubleshoot the A/C.
2 Intermittent fault
The fault is not confirmed on the ground by performing the test given in the fault
confirmation paragraph. The CFDS for some systems, may display (INTM) when an
intermittent operation of the system is detected.
Example of message:
NO BSCU DATA (INTM)

JCP Title: swap © AIRBUS S.A.S. ALL RIGHTS RESERVED. Page 3 of 7

CONFIDENTIAL AND PROPRIETARY DOCUMENT. PRINT DATE: May 08/2022
 TSM - HIM - A318/A319/A320/A321 REV DATE: May 01/2022
Tail Number - MSN - FSN: ALL
8. Philosophy and Use
swap

If the confirmation test result is "TEST OK" or equivalent, the aircraft may be
dispatched providing recording in logbook and monitoring of the subject fault.

NOTE: When a fault is not confirmed on ground, AIRBUS recommends using the
Ground Scanning function of the related system in addition of the test
required in the Fault Confirmation paragraph. The ground Scanning
function is an additional mean to track intermittent faults and to confirm
faults on ground.
NOTE: When the Fault Confirmation paragraph contains the wording "Not
Applicable" (or equivalent), you must do the Fault Isolation step(s).
The TSM has been designed to isolate/troubleshoot permanent faults. However
depending on the airlines organization, the following can be applied for intermittent
fault indications:
- if the test result is "TEST OK" (fault not confirmed), dispatch the aircraft, then
monitor the reported symptom on the following flights by checking:
* the previous leg reports
* the PFR/Previous PFRs (if available)
* the logbook of the previous flights.
After three occurrences of the same fault indication, (even though the test is still
OK), the fault isolation procedure must be applied.
(3) Fault indications generated by Electrical Transients:
On ground, especially during power-up, engine/APU start, electrical transfer, etc, Warnings may
be generated by electrical transients without the related aircraft system being actually faulty.
Only in such situation if after a reset the fault indication disappear, the aircraft can be
dispatched.
If after a reset the fault is confirmed, apply the troubleshooting procedure, or MEL if applicable
for aircraft dispatch.
(4) Swapping policy
Swapping for trouble shooting purpose.
When a reported fault is not confirmed on the ground (all tests given in the fault confirmation
paragraph are done and the results are correct), it is possible to swap identical LRUs installed
on the same A/C for subsequent flights for data analysis and decrease the NFF rate.
When a fault is confirmed on the ground, it is not allowed to swap LRUs as a trouble shooting
step unless the TSM tells you to do so.
Swapping for aircraft dispatch purpose.
When there is a logbook entry (Flight Deck effect...), and the suspected LRU (e.g. LRU x) is a
NO GO as per MEL in its original position X (e.g. X=1) but less penalizing in another position Y
(e.g. Y=2).
At that stage, the mechanics are allowed to remove the faulty LRU X and swap it with the same P
/N LRU Y if and only if:
- the subject LRU is confirmed faulty by the applicable TSM fault isolation
- the specific TSM procedure does not forbid swapping
- no spare is available
- LRU X and Y are installed on the same A/C
- Swapping is not used to extend a dispatch under MEL condition

NOTE:

JCP Title: swap © AIRBUS S.A.S. ALL RIGHTS RESERVED. Page 4 of 7

CONFIDENTIAL AND PROPRIETARY DOCUMENT. PRINT DATE: May 08/2022
 TSM - HIM - A318/A319/A320/A321 REV DATE: May 01/2022
Tail Number - MSN - FSN: ALL
8. Philosophy and Use
swap

The maintenance must apply MEL procedures and limitations for LRU X in position Y.
Corrective maintenance must be applied as soon as possible and in any case before
the MEL time limit.
- LRU X and Y have dedicated C/Bs
- the faulty LRU X (installed after swapping in position Y) is de-energized.
In accordance with LRU Removal/Installation AMM procedures, a BITE test of LRU Y (installed
in position X) shall be performed after swapping.
CAUTION : BEFORE YOU SWAP LRU'S X AND Y, AND IF THERE WERE TRIPPED C/B'S OR
SMOKE WITH THE INITIAL FAILURE, BE VERY CAREFUL WHEN YOU DOTHE CHECK
OF THE CONDITION OF THE PLUGS (LRU AND AVIONICS RACK).
ALSO, FREQUENT DISCONNECTIONS AND CONNECTIONS WILL INCREASE THE RISK
OF DAMAGE TO PLUG AND CONNECTORS.
CAUTION : WHEN DOING FAULT ISOLATION ON ETOPS IMPORTANT SYSTEMS, IN
ACCORDANCE WITH THE TSM, IT MAY REQUIRE THE SWAPPING OF
LRUs. THE OPERATOR'S APPROVED MAINTENANCE PROCEDURES MUST
BE FOLLOWED TO KEEP THE ETOPS STATUS OF THE AIRCRAFT.
The TSM does not give the action to be taken if a suspect unit removed from the aircraft during
trouble shooting is found to be serviceable rather than failed. This is due to differing replacement
policies of airlines on such units (reinstall, or send to the workshop). If such a situation occurs
airline internal replacement policy shall be applied.
Continuity and isolation checks on LRUs and system wiring made on the equipment rack ARINC
600 connectors, should only be done with the use of a breakout box and test cables or
equivalent.
After a fault isolation procedure action has been completed a check must be done to make sure
that the reported fault has been corrected.
When an AMM LRU replacement procedure is referenced in the TSM, the AMM procedure
usually specifies a test. This AMM test is to make sure that the replacement unit is installed
correctly. It does not always confirm the correction of the fault symptom. In such a case the TSM
refers to the appropriate operational or system test procedure.
Warnings about static sensitive devices may have to be used to prevent damage to sensitive
devices.
On the ground, a tripped circuit breaker must not be engaged without trouble shooting of the
associated system.
G. Trouble Shooting Summary
Ref. Fig. Trouble Shooting Flow
The various possibilities for using the TSM are summarized in the flow chart in the following figure.

JCP Title: swap © AIRBUS S.A.S. ALL RIGHTS RESERVED. Page 5 of 7

CONFIDENTIAL AND PROPRIETARY DOCUMENT. PRINT DATE: May 08/2022
 TSM - HIM - A318/A319/A320/A321 REV DATE: May 01/2022
Tail Number - MSN - FSN: ALL
8. Philosophy and Use
swap

Figure 00-00-00-74000-00-A (SHEET 1) - Computer Reset Flowchart

** ON A/C FSN ALL

JCP Title: swap © AIRBUS S.A.S. ALL RIGHTS RESERVED. Page 6 of 7

CONFIDENTIAL AND PROPRIETARY DOCUMENT. PRINT DATE: May 08/2022
 TSM - HIM - A318/A319/A320/A321 REV DATE: May 01/2022
Tail Number - MSN - FSN: ALL
8. Philosophy and Use
swap

Figure 00-00-00-20100-00-A (SHEET 1) - Trouble Shooting Flow

** ON A/C FSN ALL

JCP Title: swap © AIRBUS S.A.S. ALL RIGHTS RESERVED. Page 7 of 7

CONFIDENTIAL AND PROPRIETARY DOCUMENT. PRINT DATE: May 08/2022