In service Information

Ref: ISI 31.32.00069

Issue: January 2020

A320 Family
Centralised Fault
Display System
Troubleshooting Guidelines
 Guidelines for System
Troubleshooting
_
A320 Family
GUIDELINES FOR TROUBLESHOOTING USING
CENTRALISED FAULT DISPLAY SYSTEM (CFDS)

Note:
• These instructions do not amend or supersede any information contained in the Aircraft
Maintenance Manual (AMM).
• The AMM remains the main reference document.
• For additional information refer to: AMM 31-32-00.

003 A320 Family - Ref: ISI 31.32.00069 - Issue: January 2020

004 A320 Family - Ref: ISI 31.32.00069 - Issue: January 2020

Table
_ of content
Glossary 005

1. General Overview 007

1. CFDS Architecture 008
2. Component Location 010

2. Failure Classification & Indication 013

1. Failure Reporting per Flight Phase 014
2. Failure Classification 015
3. What are the cockpit effects associated with class 1 failures? 016
4. What are the cockpit effects associated with class 2 failures? 017

3. Access to CFDS Reports 019

1. Different types of CFDS Reports 020
2. How to access the different CFDS Reports 021
3. How to access the list of systems reporting to the CFDS? 022
4. What is the last (or current) leg Report? 023
5. What is the last (or current) leg ECAM Report? 024
6. What is the previous legs report? 025
7. What is the avionics status? 026
8. What is the post flight Report? 027

4. PFR Correlation Principle 029

1. What is the purpose of Correlation? 030
2. CFDIU New Standards Capabilities 030
3. How to correlate the different messages given by the PFR? 031

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

Troubleshooting 034
1. How to start with Trouble Shooting? 035
2. How to retrieve a TSM Task in AIRN@V From PFR data? 037
3. How to use the TSM for fault confirmation and isolation?
6. Additional means to optimise PFR data 039
1. In-Service Information (ISI) 45.00.00039 & 00.00.00228 040
2. Customised Maintenance Filter 041
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 Pow er Unit
ATA Air Transport Association
ATSU Air Traffic Service Unit
AUTO Automatic

BCL Battery Charge Limiter

BIT E 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

005 A320 Family - Ref: ISI 31.32.00069 - Issue: January 2020

006 A320 Family – Ref: ISI 31.32.00069 – Issue: January 2020

Glossary
FMGC Flight Management and Guidance Computer
FWC Flight Warning Computer
FWS Flight Warning System

GMT Greenw ich Mean Time

GND Ground
GPCU Ground Pow er Control Unit
GPSSU Global Positioning System Sensor Unit
GPWS Ground Proximity Warning System

IDENT Identifier
ILS Instrument Landing System
INIT Initialisation
INOP Inoperative
ISI In-Service Information

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. CFDS Architecture
2. Component Location
008 A320 Family - Ref: ISI 31.32.00069 - Issue: January 2020

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) w hich interfaces
w ith:
• 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 1SYSTEM TYPE 2SYSTEM TYPE 3SYSTEM

GENERAL PARAMETERS
CFDIU (FWC1 OR FWC2, FAC1,
CLOCK, FDIU, DMC1, etc.)

MCDU 1 MCDU 2

ACARS PORTABLE DISCRETE

MU or DATA PRINTER
ATSU LOADER OR ARINC 429 BUS
MDDU
OPTION
 1.
_ General
1.1. CFDS Architecture

Centralised Fault Display Interface Unit (CFDIU)

The CFDIU receives failure messages from all aircraft systems w ith BITE capability.
The CFDIU memorises and manages system faults and compiles various maintenance reports.
Built-In Test Equipm ent (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 A RINC 429 input/output bus for
Type 1, discrete input and A RINC 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 Comm unications Addressing and Reporting System Managem ent Unit
(ACARS MU) or Air Traffic Service Unit (ATSU)
The ACARS MU or the ATSU permits exchanges of data betw een the aircraft and the ground.
The radio trans mission/reception of messages is performed by the V HF 3 transceiver w hich is
controlled (in frequency and in trans mission 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 per manently receives the Universal Time Coordinated ( UTC) and the date from
the aircraft clock and then sends these tw o parameters to all type 1 systems. The UTC and
date are used by the system BITE as w ell as the CFDIU in the various maintenance reports.

009 A320 Family - Ref: ISI 31.32.00069 - Issue: January 2020

010 A320 Family - Ref: ISI 31.32.00069 - Issue: January 2020

1.
_ General
1.2. Component Location

The user interface items (MCDU and Printer) are located on the center pedestal in the cockpit.
CFDS filter data base loading is achieved w ith 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 (alternativ e 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 SY STEM BITE

(IF INSTALLED)
 1.
_ General
1.2. Component Location

A (80VU)

B (CFDIU)

011 A320 Family - Ref: ISI 31.32.00069 - Issue: January 2020

2. Failure Classification
& Indication
1. Failure Reporting per flight phase
2. Failure Classification
3. What are the cockpit effectsassociated
with class 1 failures?
4. What are the cockpit effectsassociated
with class 2 failures?
014 A320 Family - Ref: ISI 31.32.00069 - Issue: January 2020

2.
_ Failure Classification & Indication
2.1. Failure Reporting per flight phase
1 ENG START + 3mn + NEW FLIGHT NUMBER

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

NO NEW FLIGHT NUMBER ENTERED PRIOR

9B) OR 30s FOR CFDIU STD 8 AND LOWER

TO 1 ENG START + A/C SPEED > 80 kts
ENTERED PRIOR TO 1 ENG START
EARLY PFR START CONDITION:

LATE PFR START CONDITION:

PER STOP CONDITION:

SECOND ENGINE SHUT

1 ENG START

TOUCH DOWN

5MN AFTER
POWER UP

< 80 KTS
LIFT OFF

DOWN
1 2 3 4 5 6 7 8 9 10
APPROACH
PREFLIGHT

TAKE OFF
TAXI OUT

LANDING
CRUISE

TAXI IN

FLIGHT
CLIMB

POST

Note:
• The 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.
_ Failure Classification & Indication
2.2. Failure Classification

The maintenance message classification is based on fault consequences on flightoperations:

• 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
Y ES NO NO
ON THE CURRENT
FLIGHT

Y ES
Automatically
Displayed. Warning or Y ES
INDICATION TO caution messages on Av ailable on ECAM NO
THE FLIGHT CREW Engine Warning status page.
Display, local warning Engines not running.
Flag in the Flight Deck.

No need to ref er to MEL.

Ref er to MEL: “GO” without condition.
DISPATCH May be “GO”, “GO MEL not applicable.
Can be lef t uncorrected
CONSEQUENCES IF”, “NO GO”. f or 10 days.

Y ES
INDICATION TO THE Y ES Av ailable on request thru
Automatically printed out
t at the end of each flight: Sy stem Report/Test.
MAINTENANCE TEAM Fault message on the CFDS Post Flight Report.

Refer to Poster “A320 family maintenance concept”, ISI 31.30.00011.

015 A320 Family – Ref: ISI 31.32.00069 - Issue: January 2020

016 A320 Family - Ref: ISI 31.32.00069 - Issue: January 2020

2.
_ Failure Classification & Indication
2.3. What are the cockpit effects associated with
class 1 failures?

The Class 1 failures are indicated to the pilots on Primary Flight Display (PFD) and/or
the Engine / Warning Display (E/WD).

INSTRUMENT ECAM WARNINGS / CAUTIONS

FLAGS

LOCAL WARNINGS

PFD (Primary Flight Display) Engine / Warning Display

LOCAL
indication

Note:
• Only the title of the warning or caution is reported in the CFDS “LAST LEG ECAM” report
(here “HYD B RSVR OVHT”).
• The ECAM action lines (here “BLUE ELEC PUMP OFF”) are not reported in the PFR.
• The 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.
 2.
_ Failure Classification & Indication
2.4. What are the cockpit effects associated with class
2 failures?

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 dow n.

MAINTENANCE STATUS
MESSAGE ON THE “STATUS” PAGE

Engine / Warning Display StatusDisplay

SYSTEMS IN WHICH
CLASS 2 FAILURES
ARE DETECTED

THE PRESENCE OF CLASS 2

FAILURES CAUSES THE “STS”
REMINDER TO APPEAR AND TO PRESS TO CALL STATUS PAGE
PULSE ON GROUND AFTER
ENGINE SHUT DOWN

Note:
• Only 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.

017 A320 Family – Ref: ISI 31.32.00069- Issue: January 2020

3. Access to CFDS
Reports
1. Different types of CFDS reports
2. How to access the different CFDS reports
3. How to access the list of systems reporting to the CFDS?
4. What is the last (or current) leg report?
5. What is the last (or current) leg ECAM report?
6. What is the previous legsreport?
7. What is the avionicsstatus?
8. What is the post flight report?
020 A320 Family - Ref: ISI 31.32.00069 - Issue: January 2020

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:
• After 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.
• Class 1 and 2 failures are displayed in the LAST (or CURRENT) LEG REPORT,
LAST (or CURRENT) LEG ECAM REPORT and the POST FLIGHT REPORT.
• AVIONICS STATUS displays on ground and in real-time the name of the systems affected
by failures of any class.
 3.
_ Access to CFDS Reports
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.

MCDUMENU

<FMGC
<ACARS
<AIDS
<CFDS

RETURN>
SELECT DESIRED SYSTEM

CFDS

<LAST LEG REPORT

<LAST LEG ECAM REPORT
<PREVIOUS LEGREPORT
NORMALOPERATION
<AVIONICSSTATUS

<SYSTEM REPORT/TEST
<POST FLIGHT REPORT PRINT*

NEXT PAGE

CFDS
ITEM ONLYDISPLAYED
<GMT/DATE INIT
IN CASE OF CLOCKFAULT
<AVIONICS CONFIGURATIONREPORT
<REPORTSPROGRAMMING
<PFR FILTER PROGRAMM
<PASSWORD CHANGE

021 A320 Family - Ref: ISI 31.32.00069 – Issue: January 2020

022 A320 Family - Ref: ISI 31.32.00069 - Issue: January 2020

3.
_ Access to CFDS Reports
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 betw een 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 follow ing optional functions may beavailable:
• TROUBLE SHOOTING DATA (TSD)
• CLASS 3 FAULTS
• TEST
• GROUND SCANNING
MCDUMENU

<FMGC
<ACARS
<AIDS
<CFDS

RETURN>
SELECT DESIRED SYSTEM

CFDS
<LAST LEGREPORT
<LAST LEG ECAM REPORT
<PREVIOUS LEGREPORT
<AVIONICSSTATUS

<SYSTEM REPORT/TEST
<POST FLIGHT REPORT PRINT*

SYSTEMREPORT/TEST SYSTEM REPORT/TESTINST

<AIRCOND F/CTL> <ECAM 1 CFDIU>
<AF3 FUEL> <ECAM 2 EIS1>
<COM ICE &RAIN> <FDIU EIS2>
<ELEC INST> <WBS1 EIS3>
<FIREPROT L/G> <WBS2 DMU>
<RETURN NAV> <RETURN
 3. Access to CFDS Reports
_
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”.

CFDSMENU
• Concerns all systems connected to CFDS
TIME AT WHICH THE CFDS but only for faults recorded from phase 02
RECEIVES THEFAULT
to 09 for type 1 and 3 systems and 05 to
LAST LEG REPORT 07 for type 2 systems.
FEB23 Phases ground faults avail “GND
<GMT1245 PH04ATA362200 scanning” system report.
CHECK R WING LOOPA
<GMT1302 PH06ATA282100 • Displays“Class1” and “Class2” failures
FUEL L TK PUMP1QM received by CDFS during last flightleg.
<GMT1315 PH06ATA220000
FMGC 1
<GMT1317 PH06ATA261200
ENG1 LOOPA FAULT
<GMT1317 PH06ATA220000
ATSDISCONNECT
<RETURN PRINT*

A/C IDENT DATE GMT FLTN CITYPAIR

XY-ABCO FEB23 2350 XY-1234 LFBO/LFPO

<GMT1315 PH06 LAST LEG REPORTFEB23

ATA220000 FMGC 1
OR <GMT1245 PH04ATA362200
NEXT PAGE
SOURCEFMGC1 CHECK R WING LOOPA
IDENTIFIERS <GMT1302 PH06ATA282100
FCDC 1 FUEL LTK PUMP 1QM
FCDC 2
<GMT1315 PH06ATA220000
CFDIU
FMGC 1
<RETURN PRINT* <GMT1317 PH06ATA261200
ENG1 LOOP AFAULT
<GMT1317 PH06ATA220000
ATSDISCONNECT
<GMT1320 PH06ATA220000
LAND 3INOP
LAST LEG REPORT <GMT1325 PH06ATA270000
FEB23 SFCC1FAULT
<GMT1320 PH06ATA220000
LAND 3INOP
<GMT1325 PH06ATA220000
SFCC1FAULT ONE PRINT ACTION CAUSES
PRINTING OF TOTALREPORT

<RETURN PRINT*

023 A320 Family - Ref: ISI 31.32.00069 - Issue: January 2020

024 A320 Family - Ref: ISI 31.32.00069 - Issue: January 2020

3. Access to CFDS Reports

3.5. What is the last (or current) leg ECAM report?

The LAST ( OR CURRENT) LEG ECA M REPORT displays the w arning messages sent
to the CFDIU by the Flight Warning System (FWS) flight leg. The CFDS can store up to
40 w arnings over the last flight leg.

CFDS MENU
TIMEWHEN THE CFDS
RECEIVES THEFAULT

LAST LEG ECAM REP

DATE: FEB23
<GMT: 0904 PH :04 ATA: 36-22 FLIGHT PHASE DEFINED
INSIDE THE ECAM SYSTEM
BLEED LOOP
<GMT: 0915 PH: 04 ATA: 28-21
FUEL L TK PUMP 1LOPR
<GMT: 0922 PH: 05 ATA: 22-00 ATS
DISCONNECT
<GMT: 0933 PH: 05 ATA: 26-12
ENG1 LOOPA FAULT

<RETURN PRINT*

A/C IDENT DATE GMT FLTN

CITY PAIR
XY -ABCD FEB23 2352 XY -1234
LFBO/LFPO

NEXT PAGE
LAST LEG ECAM REP
DATE: FEB23
OR GMT: 0904 PH: 04 ATA: 36-22
BLEED LOOP
GMT: 0915 PH: 04 ATA: 28-21
FUEL L TK PUMP 1LO PR
GMT: 0922 PH: 05 ATA: 22-00
ATS DISCONNECT
LAST LEG ECAM REP
GMT: 0933 PH: 05 ATA: 26-12
DATE:FEB23
ENG1 LOOP A FAULT
<GMT: 0904 PH :06 ATA: 22-00
LAND 3INOP GMT: 0904 PH: 06 ATA: 22-00
<GMT: 1012 PH :06 ATA: 27-00 LAND 3 INOP
SFCC 1FAULT GMT: 1012 PH: 06 ATA: 27-00
SFCC 1 FAULT

ONE PRINTACTION CAUSES

<RETURN PRINT* PRINTING OF TOTAL REPORT
 3.
_ Access to CFDS Reports
3.6. What is the previous legs report?

At each new flight the content of the LAST LEG REPORT is transferred into the PREV IOUS
LEGS REPORT. The CFDS can store up to 200 failures over the last 64 flight legs.
The PREV IOUS LEGS REPORT is displayed only on ground. It displays the failure message
history.

CFDSMENU

AIRCRAFT IDENT

RUNS FROM 00 PREV LEGS REPXY-ABCD

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

A/C IDENT DATE GMT FLTN CITYPAIR

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
PREV LEGS REP XY-ABCD
CHECK ADIRU 1 STATIC
LEG DATE GMTPH ATA PHC INTERFACE
<02 FEB23 1915 06 261200
CHECK LGCIU#PHC 2 <02 FEB23 1915 06 261200
INTERFACE CHECK LGCIU#PHC 2
INTERFACE

A PRINTACTION CAUSES PRINTING OF

THE DISPLAYED PAGEONLY.

<RETURN PRINT*

025 A320 Family - Ref: ISI 31.32.00069 - Issue: January 2020

 026 A320 Family - Ref: ISI 31.32.00069 - Issue: January 2020

3. Access to CFDS Reports

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.

CFDSMENU

AVIONICSSTATUS
NO GPCU DAIA

ADF1 (CLASS3)

FMGC
VHF
AIDS
<RETURN PRINT*

A/C IDENT DATE GMT FLTN CITYPAIR

LAB-620 AUG23 1505 ADCD1989 TLSE/LYON
NEXT PAGE
/AVIONICS STATUS/
OR
NO GPCU DAIA
INDICATESTHAT ADF1 (CLASS3)
A CLASS 3 FAULT HASBEEN FMGC
DETECTED IN DMC
VHF
AVIONICSSTATUS
OMU
NO ILSDATA

DMC (CLASS3)

<RETURN PRINT*
 3. Access to CFDS Reports
_
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

<LAST LEG ECAM REPORT
<PREVIOUS LEGS REPORT
<AVIONICSSTATUS
<SYSTEM REPORT/TEST

<POST FLIGHT REPORT PRINT>

DATEAT THETIME A/C ID DATE GMT FLTN CITY PAIR

OF THEPRINT F-WWJH 01JAN 0700 ITAF9877 LFPG LFMN

MAINTENANCE
POST FLIGHTREPORT
0656:
1 ENG START + 3MN A/C ID DATE GMT FLTN CITY PAIR DATEAT THETIME
OR 80 KTS IF NEWFLIGHT F-WWJH 01JAN 0656/0700 ITAF9877 LFPG LFMN OF THEFLIGHT
NUMBER NOT ENTERED
0700: WARNING/MAINT. STATUSMESSAGES
A/C SPEED < 80KTS
+ 150 SEC(30SEC GMT PH ATA FAULT MESSAGE
for CFDIU Std 8 or lower) ON TWO LINESMAXI
1353 05 30-31 ANTI ICE F/O TAT
FAILURE MESSAGES
LIST OF SOURCEAND
GMT PH ATA SOURCE IDENT.
IDENTIFIERS (SYSTEM
0657 06 23-24-34 AAA GPSSU 1 SOURCE ON TOP LIST)
0657 06 31-38-22 NO MDDUDATA CFDS

Note:
• The PFR displays both LAST LEG ECAM REPORT and LAST LEG REPORT in one single
report.
• The logbook is the first entry point for troubleshooting. Associated to the logbook, the PFR is
the means to input the TSM.

027 A320 Family – Ref: ISI 31.32.00069 - Issue: January 2020

4. PFR Correlation
Principle
1. What is the purpose of correlation?
2. CFDIU New StandardsCapabilities
3. How to correlate the different messages given by the PFR?
030 A320 Family - Ref: ISI 31.32.00069 – Issue: January 2020

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 w arning/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, w arning/failure correlation is possible on MCDU through
the CFDS main page, from the LAST LEG (ECAM) REPORT.
If a w arning is correlated to a fault, a prompt (“>”) is added on the right of corresponding fault.

CFDS

<LAST LEG REPORT

<LAST LEG ECAM REPORT
<PREVIOUS LEGS REPORT
<AVIONICSSTATUS

<SYSTEM REPORT/TEST
<POST FLIGHT REPORT PRINT>

CORRELATED WARNING
ASSOCIATED TOTHE FAULT
“CHECK R WING LOOP A”

LASTLEGT REPORTFEB23 CORRELATEDWARNINGDATEFEB23

<GMT1245 PH04 ATA362200 > <GMT1245 PH04 ATA3622 >

CHECK R WING LOOPA BLEED LOOP

<RETURN PRINT* <RETURN PRINT*

Note:
The correlation information is available on the MCDU only, not in the printed PFR.
 4.
_ PFR Correlation Principle
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, w ith 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 | XXXXXXXXXXXXXX
_________REPORT

A/C ID DATE GMT FLTN CITY PAIR

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/CT
1744 06 32-00 L
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.

031 A320 Family - Ref: ISI 31.32.00069 - Issue: January 2020

032 A320 Family - Ref: ISI 31.32.00069 - Issue: January 2020

_
4. PFR Correlation Principle
4.3. How to correlate the different messages
given by the PFR?

• Case 1: Correlation between Warning / Maintenance Status and failure m essages

The selection of items is achieved according to the tw o follow ing criterion:
1- GMT ±2 minutes (may be consolidated by flight phase).
2- ATA number (first tw o digits) of messages.
Demonstration: Red, Green and Blue scheme.

• Case 2: Correlation between Warning / Maintenance Status and Identifiers

The selection of items is achieved according to the tw o follow ing criterion:
1- GMT ±2 minutes (may be consolidated by flight phase).
2- ATA number (first tw o digits) of the Identifier..
Demonstration: Black scheme.

• Case 3: No Correlation
For those items (failure or w arning) not correlated, they are input individually in the TSM.
5. Utilisation of the PFR
and AirN@v Maintenance
for Troubleshooting
1. How to start with Trouble Shooting?
2. How to retrieve a TSM Task in AIRN@V from PFR data?
3. How to use the TSM for fault confirmation and isolation?
034 A320 Family - Ref: ISI 31.32.00069 - Issue: January 2020

5.
_ Utilisation of the PFR and AirN@v
Maintenance for Troubleshooting
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 follow s:
• A cockpit effect (ECA M/Engine/EFIS/Local Warning or Maintenance status
or Crew /Maintenance observation) alone
• A cockpit effect correlated w ith a failure message
• A failure message alone

POST FLIGHT
LOGBOOK REPORT (PFR)

POST FLIGHT REPORT (PFR)

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”.
 5.
_ Utilisation of the PFR and AirN@v
Maintenance for Troubleshooting
5.2. How to retrieve a TSM Task in AIRN@V from PFR data?

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 w arnings/malfunctions, and then you select
the related fault message.

Post Flight Report (PFR)

**ON AC/ALL
24-00 ELEC BCL 1FAULT

ELEC BCL 1 FAULT

ECAM WARNING MESSAGE SELECTED
IN THE WARNING/MALFUNCTIONS LIST

035 A320 Family - Ref: ISI 31.32.00069 - Issue: January 2020

036 A320 Family - Ref: ISI 31.32.00069 - Issue: January 2020

_5. Utilisation of the PFR and AirN@v

Maintenance for Troubleshooting
5.2. How to retrieve a TSM Task in AIRN@V from PFR data?
A cockpit effect correlated w ith 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.

Post Flight Report (PFR)

A/C ID DATE GMT FLTN CITY PAIR
XY-ABCD 01FEB 1634 XY-1234 LFBO LFPO

|NON CORRELATED | DB/N

|POST FLIGHT REPORT| XXXXXXXXXXXXXXX

A/C ID DATE GMT FLTN CITY PAIR

XY-ABCD 01FEB 1634 XY-1234 LFBO LFPO

WARNING / MAINT. STATUS MESSAGES

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

FAILUREMESSAGES
GMT PH ATA
1411 02 24-38-34 SDCA1: NO DATA FROM BCL1 SOURCE IDENT.
ECAM1 ECAM2

**ON AC/ ALL

24-38-34 SDAC2: NO DATA FROM BCL1 ECAM1 1

TSM TASK 24-30-00-810-805-AIS DISPLAYED

 5.
_ Utilisation of the PFR and AirN@v
Maintenance for Troubleshooting
5.3. How to use the TSM for fault confirmation and isolation?

The relevant trouble shooting task in the TSM provides:

• Possible root causes of the fault symptom.
• Instruction for fault confirmation
• Fault isolation procedure
• Correction procedure
LAST LEG
REPORT

SYSTEM/
REPORT TEST

GROUND
SCANNING

TROUBLE
SHOOTING
DATA

037 A320 Family - Ref: ISI 31.32.00069 – Issue: January 2020

6. Additional means
to optimise PFR data
1. In-Service Information (ISI) 45.00.00039 & 00.00.00228
2. Customised Maintenance Filter
3. Technical Follow-up (TFU)
040 A320 Family - Ref: ISI 31.32.00069 – Issue: January 2020

6. Additional means to optimise PFR data

6.1. In-Service Information (ISI) 45.00.00039 & 00.00.00228
ISI 45.00.00039 - "SA Centralized Fault Display System ( CFDS) Filter Envelope content"
contains all the know n A/C BITE failure messages and effects (Warning / maintenance status)
w hich AIRBUS recommends to filter out.

ISI 00.00.00228 - "Centralized Fault Display System ( CFDS) anomalies" identifies know n A/C
BITE failure messages and effects (Warning / maintenance status) that are spurious, but w hich
can not be filtered out. This ISI article is intended to be used by maintenance engineering as a
synthetic document, providing a short description of each deviation, as w ell as the affected part
and the corrective action, w ith a cross-reference to the relevant TFU/TSM procedure if
applicable.

The fault messages/w arnings or behaviours that should be know n by line maintenance teams
are covered by the TSM.

Note:
• Some spurious fault messages can affect a PFR.
• Spurious messages can be deleted from the PFR. For that, a customised filter must be
created, uploaded and then activated through the CFDS menu.
 6. Additional means to optimise PFR data
_.2. Customised Maintenance Filter
6

ISI 45.00.00039 ZIP PACKAGECONTENTS

- ISI-45.00.00039 PDF File
- ISI-45.00.00039.csv
- FILENVXX.320

ENVELOPE FILTER
FILENVXX.320

FOR CUSTOMISATION OF THE ENVELOPE

FILTER FILE,REFER TOMAINTENANCE FILTER
TOOL (MFT)THROUGH ISI 31.32.00062

MFT
CFDIU

Printer

PDL or
MDDU
CUSTOMISED MAINTENANCE
FILTER DATABASE

“ONGROUND” “ONA/C”

The customisation of the maintenance filter is achieved from envelop filter delivered w ith
ISI 45.00.00039 and using Maintenance Filter Tool (MFT) available through 31.32.00062.
The loading of the customised maintenance filter is performed using a PDL or the MDDU.

Note:
• The filtering function is effective on the PFR only (no effect on the memorised faults in
the system BITE).
• The 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.

041 A320 Family - Ref: ISI 31.32.00069 - Issue: January 2020

042 A320 Family – Ref: ISI 31.32.00069 - Issue: January 2020

6. Additional means to optimise PFR data

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 infor mation, until the technical
solution is finalised.
 Notes
_

043 A320 Family - Ref: ISI 31.32.00069 – Issue: January 2020

044 A320 Family - Ref: 31.32.00069 - Issue: January 2020

_
Notes
AIRBUS S.A.S. 31707 Blagnac Cedex,France
© AIRBUS S.A.S. 2016 - All rights reserved,
Airbus, its logo and theproduct names are
registeredtrademarks.
Concept design by Airbus Multi Media Support
20160263. Photos byAirbus:P.Masclet.
Printed in FrancebyAirbus Print Centre.