A320 Family Centralised Fault Display SystemTroubleshooting Guidelines

In Service Informations
Ref: ISI 31.32.00069

Issue: August 2016
A320 Family
Centralised Fault
Display System
Troubleshooting Guidelines
Guidelines for System Troubleshooting
_
A320 Family
GUIDELINES FOR TROUBLESHOOTING USING
CENTRALISED FAULT DISPLAY SYSTEM (CFDS)
Note:
•T
hese instructions do not amend or supersede any information contained in the Aircraft
Maintenance Manual (AMM).
•T
he AMM remains the main reference document.
•F
or additional information refer to: AMM 31-32-00.
A320 Family - Ref: ISI 31.32.00069 - Issue: August 2016 003

Table of content
_
Glossary 005
1. General Overview 007

1.1. CFDS Architecture 008
1.2. Component Location 010
2. Failure Classification & Indication 013

2.1. Failure Reporting per Flight Phase 014
2.2. Failure Classification 015
2.3. What are the cockpit effects associated with class 1 failures? 016
2.4. What are the cockpit effects associated with class 2 failures? 017
3. Access to CFDS Reports 019

3.1. Different types of CFDS Reports 020
3.2. How to access the different CFDS Reports 021
3.3. How to access the list of systems reporting to the CFDS? 022
3.4. What is the last (or current) leg Report? 023
3.5. What is the last (or current) leg ECAM Report? 024
3.6. What is the previous legs report? 025
3.7. What is the avionics status? 026
3.8. What is the post flight Report? 027
4. PFR Correlation Principle 029

4.1. What is the purpose of Correlation? 030
4.2. CFDIU New Standards Capabilities 030
4.3. How to correlate the different messages given by the PFR? 031
5. Utilisation of the PFR and AirN@v Maintenance for Troubleshooting 033

5.1. How to start with Trouble Shooting? 034
5.2. How to retrieve a TSM Task in AIRN@V From PFR data? 035
5.3. How to use the TSM for fault confirmation and isolation? 037
6. Additional means to optimise PFR data 039

6.1. Service Information Letter (SIL) 00-028 CFDS Anomalies 040
6.2. Customised Maintenance Filter 041
6.3. Technical Follow-up (TFU) 042
Glossary
_
A/C Aircraft
ACARS Aircraft Communication Addressing and Reporting System
ADF Automatic Direction Finder
ADIRS Air Data/Inertial Reference System
ADIRU Air Data/Inertial Reference Unit
AIDS Aircraft Integrated Data System
AIRCOND Air Conditioning
AFS Automatic Flight System
AMM Aircraft Maintenance Manual
APU Auxiliary Power Unit
ATA Air Transport Association
ATSU Air Traffic Service Unit
AUTO Automatic
BCL Battery Charge Limiter

BITE Built-In Test Equipment
BSCU Braking/Steering Control Unit
CAPT Captain
CFDIU Central Fault Display Interface Unit
CFDS Central Fault Display System
COM Communication
CPU Central Processing Unit
DB/N Database Number

DMC Display Management Computer
DMU Data Management Unit
E/WD Engine / Warning Display

ECAM Electronic Centralised Aircraft Monitoring
ECU Engine Control Unit
EFIS Electronic Flight Instrument System
EIS Electronic Instrument System
ELAC Elevator Aileron Computer
ELEC Electrical
ENG Engine
F/CLT Flight Controls

FAC Flight Augmentation Computer
FDIU Flight Data Interface Unit
FIN Functional hem Number

Glossary
_
FMGC Flight Management and Guidance Computer
FWC Flight Warning Computer
FWS Flight Warning System
GMT Greenwich Mean Time

GND Ground
GPCU Ground Power Control Unit
GPSSU Global Positioning System Sensor Unit
GPWS Ground Proximity Warning System
IDENT Identifier
ILS Instrument Landing System
INIT Initialisation
INOP Inoperative
L/G Landing Gear

LGCIU Landing Gear Control and Interface Unit
LRU Line Replaceable Unit
MCDU Multipurpose Control and Display Unit

MDDU Multipurpose Disk Drive Unit
MEL Minimum Equipment List
MU Management Unit
NAV Navigation
PDL Portable Data Loader

PFD Primary Flight Display
PFR Post Flight Report
PH Phase
PHC Probe Heat Computer
REF Reference
SYS System
TAT Total Air Temperature

TFU Technical Follow-Up
TSM Trouble Shooting Manual
UTC Universal Time Coordinated
VHF Very High Frequency
WBS Weight and Balance System

1. General
1.1. CFDS Architecture
1.2. Component Location
1. General
_
1.1. CFDS Architecture
The A320 Family maintenance concept is based on the use of the Centralised Fault Display
System (CFDS) and the Troubleshooting Manual (TSM).
The main purpose of the CFDS is to ease aircraft maintenance by compiling failure information
from system BITE (Built-In Test Equipment) and providing system BITE test capability from
the cockpit.
The CFDS is made of the Centralised Fault Display Interface Unit (CFDIU) which interfaces with:
• Built-In Test Equipment (BITE) of each connected Line Replaceable Unit (LRU)
• Multipurpose Control and Display Unit (MCDU)
• Multipurpose Disk Drive Unit (MDDU) or Portable Data Loader (PDL)
• Aircraft Communications Addressing and Reporting System (ACARS)
or Air Traffic Service Unit (ATSU)
• Printer
• Clock
TYPE 1 SYSTEM TYPE 2 SYSTEM TYPE 3 SYSTEM
GENERAL PARAMETERS
CFDIU (FWC1 OR FWC2, FAC1,
CLOCK, FDIU, DMC1, etc.)
MCDU 1 MCDU 2
ACARS PORTABLE DISCRETE

MU or DATA LOADER PRINTER
ATSU OR MDDU ARINC 429 BUS
OPTION
1. General
_
1.1. CFDS ARCHITECTURE
Centralised Fault Display Interface Unit (CFDIU)

The CFDIU receives failure messages from all aircraft systems with BITE capability.
The CFDIU memorises and manages system faults and compiles various maintenance reports.
Built-In Test Equipment (BITE)
The BITE is a function incorporated in the computers for fault detection, localisation and
recording. The system BITE reports to the CFDIU via an ARINC 429 input/output bus for
Type 1, discrete input and ARINC 429 output for Type 2 systems, and via an input/output
discrete for Type 3 systems.
Multipurpose Control and Display Unit (MCDU)
The MCDU is a display unit and a keyboard used by the CFDS to display and interrogate BITE
and to initiate system tests. Both MCDUs are connected to the CFDS. The CFDS can be used
on one MCDU at a time.
Multipurpose Disk Drive Unit (MDDU) or Portable Data Loader (PDL)
The MDDU or PDL is used to load a maintenance filter in the CFDIU.
Aircraft Communications Addressing and Reporting System Management Unit
(ACARS MU) or Air Traffic Service Unit (ATSU)
The ACARS MU or the ATSU permits exchanges of data between the aircraft and the ground.
The radio transmission/reception of messages is performed by the VHF 3 transceiver which
is controlled (in frequency and in transmission activation) by the ACARS MU or the ATSU if
installed. When the ATSU is connected, it fulfils all the functions provided by the ACARS MU.
Printer
The Printer is used for printing information automatically or on request.
Clock
The CFDIU permanently receives the Universal Time Coordinated (UTC) and the date from
the aircraft clock and then sends these two parameters to all type 1 systems. The UTC and
date are used by the system BITE as well as the CFDIU in the various maintenance reports.

1. General
_
The user interface items (MCDU and Printer) are located on the center pedestal in the cockpit.
CFDS filter data base loading is achieved with an MDDU or a PDL connector located on
the pedestal (117 VU Panel) or in overhead panel (52VU).
The CFDIU is located in the avionics bay.
PDF connector 52VU

2x MCDUs (alternative to 117VU), FIN 2TD
MCDU 3 (if installed)
Printer
MDDU (FIN 1TD)

or PDL connector
117VU (FIN 86LM)
TO MCDUs
AND PRINTER
AVIONICS BAY (80VU)
ACARS MU OR ATSU CFDIU AVIONICS SYSTEM BITE

(IF INSTALLED)
1. General
_
A (80VU)
B (CFDIU)

2. Failure Classification
& Indication
2.1. Failure Reporting per flight phase
2.2. Failure Classification
2.3. What are the cockpit effects associated
with class 1 failures?
2. Failure Classification & Indication

_
2.1. Failure Reporting per flight phase
A/C SPEED < 80 kts + 150s (FROM CFDIU Std 9B)

NUMBER ENTERED PRIOR TO 1 ENG START
NO NEW FLIGHT NUMBER ENTERED PRIOR

TO 1 ENG START + A/C SPEED > 80 kts
OR 30s FOR CFDIU STD 8 AND LOWER

1 ENG START + 3mn + NEW FLIGHT
EARLY PFR START CONDITION:
SECOND ENGINE SHUT DOWN

LATE PFR START CONDITION:
PER STOP CONDITION:

1 ENG START
TOUCH DOWN
5MN AFTER
POWER UP
< 80 KTS
LIFT OFF
1 2 3 4 5 6 7 8 9 10
POST FLIGHT
PREFLIGHT
APPROACH
TAKE OFF
TAXI OUT
LANDING
CRUISE
TAXI IN
CLIMB
Note:
•T
he CFDIU generates its flight/ground condition using some parameters transmitted by the
Flight Warning Computer (FWC), the Flight Augmentation Computer (FAC), the memorised
maintenance phases and a discrete signal from the Landing Gear Control and Interface Unit
(LGCIU).
• In normal operation, flight phase information is transmitted by the FWCs to the CFDIU and
when a new flight number is entered the information is given by the FAC.
• In downgraded mode, the discrete signal (nose landing gear shock absorber compressed)
from the LGCIU is used by the CFDIU as backup when the FWCs are inoperative.
_
2.2. Failure Classification
The maintenance message classification is based on fault consequences on flight operations:

• Class 1 faults may have an operational consequence on flight
• Class 2 faults have no immediate operational consequence on flight
• Class 3 faults have no consequence on flight
FAILURE / FAULT
1 2 3
CLASSES
OPERATIONAL
CONSEQUENCES
YES NO NO
ON THE CURRENT
FLIGHT
YES
Automatically Displayed.
YES
INDICATION TO Warning or caution
Available on ECAM
messages on Engine NO
THE FLIGHT CREW status page.
Warning Display, local
Engines not running.
warning
Flag in the Flight Deck.
No need to refer to MEL.

DISPATCH Refer to MEL:
“GO” without condition.
May be “GO”, “GO IF”, MEL not applicable.
CONSEQUENCES Can be left uncorrected
“NO GO”.
for 10 days.
YES YES
INDICATION TO THE
Automatically printed out at the end of each flight: Available on request thru
MAINTENANCE TEAM Fault message on the CFDS Post Flight Report. System Report/Test.
Refer to Poster “A320 family maintenance concept”, AM409/06.


_
The Class 1 failures are indicated to the pilots on Primary Flight Display (PFD) and/or
the Engine / Warning Display (E/WD).
INSTRUMENT FLAGS ECAM WARNINGS / CAUTIONS
LOCAL WARNINGS
PFD (Primary Flight Display) Engine / Warning Display
LOCAL
indication
Note:
•O
nly the title of the warning or caution is reported in the CFDS “LAST LEG ECAM” report
(here “HYD B RSVR OVHT”).
•T
he ECAM action lines (here “BLUE ELEC PUMP OFF”) are not reported in the PFR.
•T
he aircraft configuration warning (ex: OVER SPEED VFE (VLE), L/G GEAR NOT DOWN,
CONFIG PARK BRK ON, etc.) are usually not reported in the PFR.
_
The cockpit effects associated to Class 2 failures are indicated to the cockpit crew on ground
by a maintenance status on the ECAM STATUS page after the engines shut down.
MAINTENANCE STATUS
MESSAGE ON THE “STATUS” PAGE
Engine / Warning Display Status Display
SYSTEMS IN WHICH
CLASS 2 FAILURES
ARE DETECTED
THE PRESENCE OF CLASS 2

FAILURES CAUSES THE “STS”
REMINDER TO APPEAR AND PRESS TO CALL STATUS PAGE
TO PULSE ON GROUND AFTER
ENGINE SHUT DOWN
Note:
•O
nly the name of the affected system is reported in the “LAST LEG ECAM” report
(here “ADR3” and “EIVMU2”).
• “ STS” displayed on the Status Display means there is a Maintenance Status accessible by
pressing the “STS” button to call up the “STATUS” page.

3. Access to CFDS
Reports
3.1. Different types of CFDS reports
3.2. How to access the different CFDS reports
3.3. How to access the list of systems reporting to the CFDS?
3.4. What is the last (or current) leg report?
3.5. What is the last (or current) leg ECAM report?
3.6. What is the previous legs report?
3.7. What is the avionics status?
3.8. What is the post flight report?
3. Access to CFDS Reports

_
3.1. Different types of CFDS reports
Several types of reports are established by the CFDS in flight or on ground. On ground, all
the reports are available. In flight, only CURRENT LEG ECAM REPORT and CURRENT LEG
REPORT are available.
• LAST (CURRENT) LEG ECAM REPORT:
ECAM Warnings / Caution messages seen by the crew during the last (current) flight leg.
• LAST (CURRENT) LEG REPORT:
Failures recorded during the last flight (current) leg.
• PREVIOUS LEGS REPORT:
Equivalent to LAST LEG REPORT but accessible for the last 64 flights.
• AVIONICS STATUS:
List in real time of the systems affected by at least one internal or external failure
(Class 1,2 or 3).
• POST FLIGHT REPORT:
Sum of the LAST LEG ECAM REPORT and LAST LEG REPORT.
Note:
•A
fter a flight when the aircraft is on ground, the CURRENT LEG (ECAM) REPORT is renamed
LAST LEG REPORT and stored in the PREVIOUS LEGS REPORT by the CFDS.
•C
lass 1 and 2 failures are displayed in the LAST (or CURRENT) LEG REPORT,
LAST (or CURRENT) LEG ECAM REPORT and the POST FLIGHT REPORT.
•A
VIONICS STATUS displays on ground and in real-time the name of the systems affected
by failures of any class.
_
3.2. How to access the different CFDS reports?
Pressing the “MCDU MENU” key and then selecting CFDS gives access to CFDS menu page
(ground or flight). All CFDS reports are accessible on ground.
MCDU MENU
<FMGC
<ACARS
<AIDS
<CFDS
RETURN>
SELECT DESIRED SYSTEM
CFDS
<LAST LEG REPORT
<LAST LEG ECAM REPORT
<PREVIOUS LEG REPORT
NORMAL OPERATION
<AVIONICS STATUS
<SYSTEM REPORT/TEST
<POST FLIGHT REPORT PRINT*
NEXT PAGE
CFDS
ITEM ONLY DISPLAYED <GMT/DATE INIT
IN CASE OF CLOCK FAULT
<AVIONICS CONFIGURATION REPORT
<REPORTS PROGRAMMING
<PFR FILTER PROGRAMM
<PASSWORD CHANGE


_
3.3. How to access the list of systems reporting to the CFDS?
The SYSTEM REPORT/TEST function is available on the ground only. It enables an interactive
dialogue between the CFDS and one particular system.
Pressing the line key adjacent to a system name enables access to the menu of the system,
generally made up of below items (Systems of Type 1):
• LAST LEG REPORT
• PREVIOUS LEGS REPORT
• LRU IDENTIFICATION
For some systems, the following optional functions may be available:
• TROUBLE SHOOTING DATA (TSD)
• CLASS 3 FAULTS
• TEST
• GROUND SCANNING
MCDU MENU
<FMGC
<ACARS
<AIDS
<CFDS
RETURN>
SELECT DESIRED SYSTEM
CFDS
<LAST LEG REPORT
<PREVIOUS LEG REPORT
<AVIONICS STATUS
<SYSTEM REPORT/TEST
<POST FLIGHT REPORT PRINT*
SYSTEM REPORT/TEST SYSTEM REPORT/TEST INST

<AIRCOND F/CTL> <ECAM 1 CFDIU>
<AF3 FUEL> <ECAM 2 EIS 1>
<COM ICE & RAIN> <FDIU EIS 2>
<ELEC INST> <WBS 1 EIS 3>
<FIRE PROT L/G> <WBS 2 DMU>
<RETURN NAV> <RETURN
_
3.4. What is the last (or current) leg report?
The LAST (OR CURRENT) LEG REPORT displays the failures (Class 1 and 2 only) detected by
the system BITE during the last flight leg. The CFDS can store up to 40 failures over this period.
Pressing the line key adjacent to an item, the SOURCE/IDENTIFIERS page comes in to view.
This page provides for a given failure its “Source” and the “Identifiers”.
CFDS MENU
• Concerns all systems connected to CFDS
TIME AT WHICH THE CFDS
RECEIVES THE FAULT but only for faults recorded from phase 02
to 09 for type 1 and 3 systems and 05 to 07
LAST LEG REPORT FEB 23 for type 2 systems.
Phases ground faults avail “GND scanning”
<GMT1245 PH04 ATA362200 system report.
CHECK R WING LOOP A
<GMT1302 PH06 ATA282100 •D isplays “Class1” and “Class2” failures
FUEL L TK PUMP 1QM
<GMT1315 PH06 ATA220000 received by CDFS during last flight leg.
FMGC 1
<GMT1317 PH06 ATA261200
ENG1 LOOP A FAULT
<GMT1317 PH06 ATA220000
ATS DISCONNECT
<RETURN PRINT*
A/C IDENT DATE GMT FLTN CITYPAIR

XY-ABCO FEB23 2350 XY-1234 LFBO/LFPO
<GMT1315 PH06 ATA220000 LAST LEG REPORT FEB23

FMGC 1
OR
NEXT PAGE <GMT1245 PH04 ATA362200
SOURCE FMGC1 CHECK R WING LOOP A
IDENTIFIERS <GMT1302 PH06 ATA282100
FCDC 1
FCDC 2 FUEL L TK PUMP 1QM
CFDIU <GMT1315 PH06 ATA220000
FMGC 1
<RETURN PRINT*
<GMT1317 PH06 ATA261200
ENG1 LOOP A FAULT
<GMT1317 PH06 ATA220000
ATS DISCONNECT
<GMT1320 PH06 ATA220000
LAST LEG REPORT FEB 23 LAND 3 INOP
<GMT1325 PH06 ATA270000
<GMT1320 PH06 ATA220000 SFCC1 FAULT
LAND 3 INOP
<GMT1325 PH06 ATA220000
SFCC1 FAULT ONE PRINT ACTION CAUSES
PRINTING OF TOTAL REPORT
<RETURN PRINT*


_
3.5. What is the last (or current) leg ECAM report?
The LAST (OR CURRENT) LEG ECAM REPORT displays the warning messages sent
to the CFDIU by the Flight Warning System (FWS) flight leg. The CFDS can store up
to 40 warnings over the last flight leg.
CFDS MENU
TIME WHEN THE CFDS
RECEIVES THE FAULT
LAST LEG ECAM REP

DATE: FEB 23
<GMT: 0904 PH :04 ATA: 36-22 FLIGHT PHASE
BLEED LOOP DEFINED INSIDE
<GMT: 0915 PH: 04 ATA: 28-21 THE ECAM SYSTEM
FUEL L TK PUMP 1LO PR
<GMT: 0922 PH: 05 ATA: 22-00
ATS DISCONNECT
<GMT: 0933 PH: 05 ATA: 26-12
ENG1 LOOP A FAULT
<RETURN PRINT*

XY-ABCD FEB23 2352 XY-1234 LFBO/LFPO
NEXT PAGE
LAST LEG ECAM REP
OR DATE: FEB23
GMT: 0904 PH: 04 ATA: 36-22

BLEED LOOP
GMT: 0915 PH: 04 ATA: 28-21
FUEL L TK PUMP 1LO PR
LAST LEG ECAM REP GMT: 0922 PH: 05 ATA: 22-00
DATE: FEB23 ATS DISCONNECT
<GMT: 0904 PH :06 ATA: 22-00 GMT: 0933 PH: 05 ATA: 26-12
LAND 3 INOP
<GMT: 1012 PH :06 ATA: 27-00 ENG1 LOOP A FAULT
SFCC 1 FAULT GMT: 0904 PH: 06 ATA: 22-00
LAND 3 INOP
GMT: 1012 PH: 06 ATA: 27-00
SFCC 1 FAULT
<RETURN PRINT*
ONE PRINT ACTION CAUSES PRINTING
OF TOTAL REPORT
_
3.6. What is the previous legs report?
At each new flight the content of the LAST LEG REPORT is transferred into the PREVIOUS
LEGS REPORT. The CFDS can store up to 200 failures over the last 64 flight legs.
The PREVIOUS LEGS REPORT is displayed only on ground. It displays the failure message
history.
CFDS MENU
AIRCRAFT IDENT
PREV LEGS REP XY-ABCD

LEG DATE GMT PH ATA
<00 FEB27 1315 06 220000
FMGC1
<01 FEB24 1328 06 770000
INTERMITTENT N2 SENSOR ENG1
FAILURE <01 FEB24 1318 06 220000
NO FAC DATA (INTM)
RUNS FROM 00 <01 FEB24 0928 06 346700
(FIRST LEG BEFORE CHECK ADIRU 1 STATIC
LAST LEG) TO 63 PHC INTERFACE
<RETURN PRINT*

XY-ABCD FEB23 2352 XY-1234 LFBO/LFPO
NEXT PAGE
PREV LEGS REPXY-ABCD
LEG DATE GMT PH ATA
<00 FEB27 1315 06 220000
FMGC1
<01 FEB24 1328 06 770000
N2 SENSOR ENG 1
<01 FEB24 1318 06 220000
NO FAC DATA (INTM)
<01 FEB24 0928 06 346700
LAST LEG ECAM REP CHECK ADIRU 1 STATIC
DATE: FEB23 PHC INTERFACE
LEG DATE GMT PH ATA
<02 FEB23 1915 06 261200 <02 FEB23 1915 06 261200
CHECK LGCIU#PHC 2 CHECK LGCIU#PHC 2
INTERFACE INTERFACE
A PRINT ACTION CAUSES PRINTING

OF THE DISPLAYED PAGE ONLY.
<RETURN PRINT*


_
3.7. What is the avionics status?
The AVIONICS STATUS displays the name of systems currently affected by a failure regardless
of the classification. This function is only available on ground and in real-time. The information
presented is permanently updated but not stored.
CFDS MENU
AVIONICS STATUS
NO GPCU DAIA
ADF1 (CLASS 3)
FMGC
VHF
AIDS
<RETURN PRINT*

LAB-620 AUG23 1505 ADCD1989 TLSE/LYON
NEXT PAGE
/AVIONICS STATUS/
OR
NO GPCU DAIA
ADF1 (CLASS3)
INDICATES THAT
A CLASS 3 FAULT HAS BEEN FMGC
DETECTED IN DMC
VHF
AVIONICS STATUS
OMU
NOILS DATA
DMC (CLASS 3)
<RETURN PRINT*
_
3.8. What is the post flight report?
The PFR is available on ground to present Warnings/Maintenance status and failure messages
(Class 1 and 2) of the last flight leg. The PFR is only available on the printer after a flight or on
the ground via ACARS by using manual or automatic transmission.
CFDS
<LAST LEG REPORT

<PREVIOUS LEGS REPORT
<AVIONICS STATUS
<SYSTEM REPORT/TEST
<POST FLIGHT REPORT PRINT>
DATE AT THE TIME A/C ID DATE GMT FLTN CITY PAIR

OF THE PRINT F-WWJH 01JAN 0700 ITAF9877 LFPG LFMN
MAINTENANCE
POST FLIGHT REPORT DATE AT THE TIME
OF THE FLIGHT
0656: A/C ID DATE GMT FLTN CITY PAIR
1 ENG START + 3MN F-WWJH 01JAN 0656/0700 ITAF9877 LFPG LFMN
OR 80 KTS IF NEW FLIGHT
NUMBER NOT ENTERED
WARNING/MAINT. STATUS MESSAGES
0700: GMT PH ATA FAULT MESSAGE
A/C SPEED < 80 KTS ON TWO LINES MAXI
1353 05 30-31 ANTI ICE F/O TAT
+ 150 SEC(30 SEC
for CFDIU Std 8 or lower)
FAILURE MESSAGES
GMT PH ATA SOURCE IDENT. LIST OF SOURCE AND
IDENTIFIERS (SYSTEM
0657 06 23-24-34 AAA GPSSU 1 SOURCE ON TOP LIST)
0657 06 31-38-22 NO MDDU DATA CFDS
Note:
•T
he PFR displays both LAST LEG ECAM REPORT and LAST LEG REPORT in one single
report.
•T
he logbook is the first entry point for troubleshooting. Associated to the logbook, the PFR
is the means to input the TSM.

4. PFR Correlation
Principle
4.1. What is the purpose of correlation?
4.2. CFDIU New Standards Capabilities
4.3. How to correlate the different messages given by the PFR?
4. PFR Correlation Principle

_
4.1. What is the purpose of correlation?
The purpose of the correlation is to define the fault symptoms from Logbook entries, and input
the relevant TSM tasks required to isolate and fix the faults reported by the crew.
The fault symptom is the result of a manual warning/failure correlation: it consists in associating
each cockpit effect (logbook entries) to the relevant failure message(s) (PFR or result of
the system BITE test).
4.2. CFDIU New Standards Capabilities

From the CFDIU standard 10A, warning/failure correlation is possible on MCDU through
the CFDS main page, from the LAST LEG (ECAM) REPORT.
If a warning is correlated to a fault, a prompt (“>”) is added on the right of corresponding fault.
CFDS
<LAST LEG REPORT

<PREVIOUS LEGS REPORT
<AVIONICS STATUS
<SYSTEM REPORT/TEST
<POST FLIGHT REPORT PRINT>
CORRELATED WARNING
ASSOCIATED TO THE FAULT
“CHECK R WING LOOP A”
LAST LEGT REPORT FEB23 CORRELATED WARNING DATE FEB23
<GMT1245 PH04 ATA 362200 > <GMT1245 PH04 ATA 3622 >
CHECK R WING LOOP A BLEED LOOP
<RETURN PRINT* <RETURN PRINT*
Note:
The correlation information is available on the MCDU only, not in the printed PFR.
_
4.3. How to correlate the different messages
given by the PFR?
The correlation consists in comparing the time/occurrence and ATA number of

Warning/Maintenance Status messages, with these of failure messages and identifier(s) if any.
A/C ID DATE GMT FLTN CITY PAIR

D-WWFT 29JAN 2304 AIB001 LFBO LFPG
| MAINTENANCE | DB/N
| POST FLIGHT REPORT | XXXXXXXXXXXXXXX

D-WWFT 29JAN 1507/1935 AIB001 LFBO LFPG
WARNING / MAINT. STATUS MESSAGES
GMT PH ATA
1511 04 36-21 AIR ENG1 BLEED FAULT
1527 06 34-00 NAV ADR3 FAULT
1527 06 27-00 F/CTL
1744 06 32-00 WHEEL TYRE LO PR (2)
FAILURE MESSAGES
GMT PH ATA SOURCE IDENT.

1511 04 36-11-52 PRESS REG-V 4001HA1 BMC1
1511 04 34-43-00 DMC1: NO TCAS DATA EIS1 EIS3/EIS2
1527 06 34-11-17 ADM 19FP3 ADR3 EFCS1/AFS
EFCS2
1743 06 31-61-12 DMC2: NO ECP DATA EIS2
1744 06 32-41-13 CHECK TIRES 1/2 PRESS TPIS
1921 07 34-55-31 DMC3: NO VOR1 DATA EIS3 EIS2/EIS1
AFS
The first step is to select one Warning / Maintenance Status message as an entry point,
and then to identify the associated failure message(s) or Identifier(s).
The exercise is to repeat until either all Warning / Maintenance Status are correlated
or no correlation is possible.


_
4.3. How to correlate the different messages
given by the PFR?
•C
ase 1: Correlation between Warning / Maintenance Status and failure messages
The selection of items is achieved according to the two following criterion:
1- GMT ±2 minutes (may be consolidated by flight phase).
2- ATA number (first two digits) of messages.
Demonstration: Red, Green and Blue scheme.
•C
ase 2: Correlation between Warning / Maintenance Status and Identifiers
The selection of items is achieved according to the two following criterion:
1- GMT ±2 minutes (may be consolidated by flight phase).
2- ATA number (first two digits) of the Identifier..
Demonstration: Black scheme.
•C
ase 3: No Correlation
For those items (failure or warning) not correlated, they are input individually in the TSM.
5. Utilisation of the PFR
and AirN@v Maintenance
for Troubleshooting
5.1. How to start with Trouble Shooting?
5.2. How to retrieve a TSM Task in AIRN@V from PFR data?
5.3. How to use the TSM for fault confirmation and isolation?
5. Utilisation of the PFR and AirN@v

Maintenance for Troubleshooting
_
5.1. How to start with Troubleshooting?
After a malfunction, the crew reports the cockpit effect in the Log Book. Once correlated,
the Log book and the PFR provide the fault symptoms relative to the cockpit effect which can
be as follows:
• A cockpit effect (ECAM/Engine/EFIS/Local Warning or Maintenance status
or Crew/Maintenance observation) alone
• A cockpit effect correlated with a failure message
• A failure message alone
POST FLIGHT
LOGBOOK REPORT (PFR)
Post Flight Report (PFR)

XY-ABCD 01FEB 1634 XY-1234 LFBO LFPO
| NON CORRELATED | DB/N


GMT PH ATA
1411 02 24-00 ELEC BCL 1 FAULT
FAILURE MESSAGES

1411 02 24-38-34 SDCA1: NO DATA FROM BCL1 ECAM1 ECAM2
In order to find the troubleshooting task (fault confirmation and isolation) corresponding to each
fault symptom, AirNav offers a dynamic trouble shooting tool.
The path for it is: “AirNav Maintenance/Home page/Advanced tools/Start troubleshooting”.
_
To find out the reported problem (“ELEC BCL 1 FAULT” in this example), you have to select
“ECAM Warning” (or Maintenance Status for Class 2 failures) and enter the name of the fault
message reported on the logbook.
You can also enter the ATA chapter to have a list of warnings/malfunctions, and then you select
the related fault message.



GMT PH ATA
FAILURE MESSAGES

**ON AC/ ALL

24-00 ELEC BCL 1 FAULT
ELEC BCL 1 FAULT

ECAM WARNING MESSAGE SELECTED
IN THE WARNING/MALFUNCTIONS LIST


_
A cockpit effect correlated with a failure message can lead to several trouble shooting tasks.
Therefore, it is necessary to select the failure message data relevant to the ones given in
the PFR for the same message.
Once the selection of the fault symptom is completed, AirN@v provides access to the relevant
TSM task.



GMT PH ATA
FAILURE MESSAGES

**ON AC/ ALL

24-38-34 SDAC2: NO DATA FROM BCL1 ECAM1 1
TSM TASK 24-30-00-810-805-AIS DISPLAYED

_
5.3. How to use the TSM for fault confirmation and isolation?
The relevant trouble shooting task in the TSM provides:

•P
ossible root causes of the fault symptom.
• Instruction for fault confirmation
•F
ault isolation procedure
•C
orrection procedure
LAST LEG
REPORT
SYSTEM/
REPORT TEST
GROUND
SCANNING
TROUBLE
SHOOTING
DATA

6. Additional means
to optimise PFR data
6.1. Service Information Letter (SIL) 00-028 CFDS Anomalies
6.2. Customised Maintenance Filter
6.3. Technical Follow-up (TFU)
6. Additional means to optimise PFR data

_
6.1. Service Information Letter (SIL) 00-028 CFDS Anomalies
SIL 00-028 identifies all the known CFDS anomalies and BITE deviations. It is intended
to be used by maintenance engineering as a synthetic document, providing a short description
of each deviation, as well as the affected part and the corrective action, with a cross-reference
to the relevant TFU/TSM procedure if applicable.
The fault messages/warnings or behaviours that should be known by line maintenance teams
are covered by the TSM.
Note:
•S
ome spurious fault messages can affect a PFR.
•S
purious messages can be deleted from the PFR. For that, a customised filter must be
created, uploaded and then activated through the CFDS menu.
_
6.2. Customised Maintenance Filter
SIL 00-028 ZIP PACKAGE CONTENTS

- SIL00-028 PDF File
- SIL00-028.csv
- FILENVXX.320
ENVELOPE FILTER
FILENVXX.320
FOR CUSTOMISATION OF THE ENVELOPE

FILTER FILE, REFER TO MAINTENANCE FILTER
TOOL (MFT) THROUGH ISI 31.32.00062
MFT
CFDIU
Printer
PDL or
CUSTOMISED MAINTENANCE MDDU
FILTER DATABASE
“ON GROUND” “ON A/C”
The customisation of the maintenance filter is achieved from envelop filter delivered
with SIL 00-028 and using Maintenance Filter Tool (MFT) available through SIL 00-088.
The loading of the customised maintenance filter is performed using a PDL or the MDDU.
Note:
•T
he filtering function is effective on the PFR only (no effect on the memorised faults
in the system BITE).
•T
he version of the filter database number loaded into the CFDIU is checked up with
the CFDIU LRU IDENTIFICATION function (Data base number: DB/N) or with an automatic
printing of the Filter content.


_
6.3. Technical Follow-up (TFU)
The TFU describes in-service issues affecting a system and its maintenance. It is produced
whenever the resolution is ongoing or not. It provides advanced information, until the technical
solution is finalised.
Notes
_
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��

Notes
_
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
��
AIRBUS S.A.S. 31707 Blagnac Cedex, France
© AIRBUS S.A.S. 2017 - All rights reserved, Airbus, its
logo and the product names are registered trademarks.
Concept design by Airbus Multi Media Support 20172315.
Photos by Airbus: P. Masclet.
Printed in France by Airbus Print Centre.

A320 Family Centralised Fault Display SystemTroubleshooting Guidelines

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

A320 Family Centralised Fault Display SystemTroubleshooting Guidelines

Transféré par

Droits d'auteur :

Formats disponibles

In Service Informations

Ref: ISI 31.32.00069

A320 Family - Ref: ISI 31.32.00069 - Issue: August 2016 003

1. General Overview 007

2. Failure Classification & Indication 013

3. Access to CFDS Reports 019

4. PFR Correlation Principle 029

5. Utilisation of the PFR and AirN@v Maintenance for Troubleshooting 033

6. Additional means to optimise PFR data 039

BCL Battery Charge Limiter

DB/N Database Number

E/WD Engine / Warning Display

F/CLT Flight Controls

A320 Family - Ref: ISI 31.32.00069 - Issue: August 2016 005

GMT Greenwich Mean Time

L/G Landing Gear

MCDU Multipurpose Control and Display Unit

PDL Portable Data Loader

TAT Total Air Temperature

UTC Universal Time Coordinated

VHF Very High Frequency

WBS Weight and Balance System

TYPE 1 SYSTEM TYPE 2 SYSTEM TYPE 3 SYSTEM

ACARS PORTABLE DISCRETE

Centralised Fault Display Interface Unit (CFDIU)

A320 Family - Ref: ISI 31.32.00069 - Issue: August 2016 009

PDF connector 52VU

MCDU 3 (if installed)

MDDU (FIN 1TD)

AVIONICS BAY (80VU)

ACARS MU OR ATSU CFDIU AVIONICS SYSTEM BITE

A320 Family - Ref: ISI 31.32.00069 - Issue: August 2016 011

2. Failure Classification & Indication

A/C SPEED < 80 kts + 150s (FROM CFDIU Std 9B)

NO NEW FLIGHT NUMBER ENTERED PRIOR

OR 30s FOR CFDIU STD 8 AND LOWER

SECOND ENGINE SHUT DOWN

PER STOP CONDITION:

The maintenance message classification is based on fault consequences on flight operations:

No need to refer to MEL.

Refer to Poster “A320 family maintenance concept”, AM409/06.

A320 Family - Ref: ISI 31.32.00069 - Issue: August 2016 015

2. Failure Classification & Indication

INSTRUMENT FLAGS ECAM WARNINGS / CAUTIONS

PFD (Primary Flight Display) Engine / Warning Display

Engine / Warning Display Status Display

THE PRESENCE OF CLASS 2

A320 Family - Ref: ISI 31.32.00069 - Issue: August 2016 017

3. Access to CFDS Reports

A320 Family - Ref: ISI 31.32.00069 - Issue: August 2016 021

3. Access to CFDS Reports

SYSTEM REPORT/TEST SYSTEM REPORT/TEST INST

A/C IDENT DATE GMT FLTN CITYPAIR

<GMT1315 PH06 ATA220000 LAST LEG REPORT FEB23

A320 Family - Ref: ISI 31.32.00069 - Issue: August 2016 023

3. Access to CFDS Reports

LAST LEG ECAM REP

A/C IDENT DATE GMT FLTN CITYPAIR

GMT: 0904 PH: 04 ATA: 36-22

PREV LEGS REP XY-ABCD

A/C IDENT DATE GMT FLTN CITYPAIR

A PRINT ACTION CAUSES PRINTING

A320 Family - Ref: ISI 31.32.00069 - Issue: August 2016 025

3. Access to CFDS Reports