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 T roubleshooting 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.

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

003

004


Table of content _

Glossary

005

1. General Overview 1.1. CFDS Architecture 1.2. Component Location

007 008 010

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.4. What are the cockpit effects associated with class 2 failures?

013 014 015 016 017

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?

019 020 021 022 023 024 025 026 027

4.

PFR 4.1. 4.2. 4.3.

029 030 030 031

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 Task in AIRN@V From PFR data? 5.3. How to use the TSM for fault confirmation and isolation?

033 034 035 037

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)

039 040 041 042

Correlation Principle What is the purpose of Correlation? CFDIU New Standards Capabilities How to correlate the different messages given by the PFR?

Glossary _

A/C ACARS ADF ADIRS ADIRU AIDS AIRCOND AFS AMM APU ATA ATSU AUTO

Aircraft Aircraft Communication Addressing and Reporting System Automatic Direction Finder Air Data/Inertial Reference System Air Data/Inertial Reference Unit Aircraft Integrated Data System Air Conditioning Automatic Flight System Aircraft Maintenance Manual Auxiliary Power Unit Air Transport Association Air Traffic Service Unit Automatic

BCL BITE BSCU

Battery Charge Limiter Built-In Test Equipment Braking/Steering Control Unit

CAPT CFDIU CFDS COM CPU

Captain Central Fault Display Interface Unit Central Fault Display System Communication Central Processing Unit

DB/N DMC DMU

Database Number Display Management Computer Data Management Unit

E/WD ECAM ECU EFIS EIS ELAC ELEC ENG

Engine / Warning Display Electronic Centralised Aircraft Monitoring Engine Control Unit Electronic Flight Instrument System Electronic Instrument System Elevator Aileron Computer Electrical Engine

F/CLT FAC FDIU FIN

Flight Controls Flight Augmentation Computer Flight Data Interface Unit Functional hem Number


005


Glossary _

FMGC FWC FWS

Flight Management and Guidance Computer Flight Warning Computer Flight Warning System

GMT GND GPCU GPSSU GPWS

Greenwich Mean Time Ground Ground Power Control Unit Global Positioning System Sensor Unit Ground Proximity Warning System

IDENT ILS INIT INOP

Identifier Instrument Landing System Initialisation Inoperative

L/G LGCIU LRU

Landing Gear Landing Gear Control and Interface Unit Line Replaceable Unit

MCDU MDDU MEL MU

Multipurpose Control and Display Unit Multipurpose Disk Drive Unit Minimum Equipment List Management Unit

NAV

Navigation

PDL PFD PFR PH PHC

Portable Data Loader Primary Flight Display Post Flight Report Phase Probe Heat Computer

REF

Reference

SYS

System

TAT TFU TSM

Total Air Temperature Technical Follow-Up Trouble Shooting Manual

UTC

Universal Time Coordinated

VHF

Very High Frequency

WBS

Weight and Balance System

006

1. General 1.1. CFDS Architecture 1.2. Component Location

008


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 (FWC1 OR FWC2, FAC1, CLOCK, FDIU, DMC1, etc.)

CFDIU

MCDU 1 ACARS MU or ATSU

PORTABLE DATA LOADER OR MDDU

MCDU 2 DISCRETE PRINTER 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.


009

010


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 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 (alternative to 117VU), FIN 2TD

2x MCDUs

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 (IF INSTALLED)

CFDIU

AVIONICS SYSTEM BITE

1. General 1.2. Component Location _

A

A (80VU) B (CFDIU)

B


011


012

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.4. What are the cockpit effects associated with class 2 failures?

014


2. Failure Classification & Indication 2.1. Failure Reporting per flight phase _

T R A T P S U R G E N W E O P 1

1 T H G I L F E R P

T R A T S T G H N G I E L : F 1 N W O O I E T N T I R D + O N I R O n P C m 3 D T E R + R A T E T T S R A N R T E F S R P G E Y B L N R E M A U E 1 N

2

T U O I X A T

R O t I s R k P 0 D 8 E > R E D E : T E N N P E O S I R T I E C / D B N M A O U + C N T T T R R H A T A G T I S S L G R F N F F W E F P E O E N 1 T T O A O F I L N T L

3

4

F F O E K A T

) B 9 d t S U I D F R C E M W O O R L F D ( s N 0 A 5 8 : 1 D N + T S O I s t T k U I I D 0 D F N 8 C O < C R O P D E F S O T T E s K S P 0 S 3 0 R 8 E C / R < P A O

N W O D H C U O T

5

B M I L C

6

E S I U R C

7 H C A O R P P A

8

G N I D N A L

9

N I I X A T

N W O D T U H S E N I G N E D N O C E S

R E T F A N M 5

10 T H G I L F T S O P

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 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 CLASSES

OPERATIONAL CONSEQUENCES ON THE CURRENT FLIGHT

INDICATION TO THE FLIGHT CREW

DISPATCH CONSEQUENCES

INDICATION TO THE MAINTENANCE TEAM

1

2

3

YES

NO

NO

YES Automatically Displayed. Warning or caution messages on Engine Warning Display, local warning Flag in the Flight Deck.

YES Available on ECAM status page. Engines not running.

NO

Refer to MEL: May be “GO”, “GO IF”, “NO GO”.

No need to refer to MEL. “GO” without condition. Can be left uncorrected for 10 days.

MEL not applicable.

YES Automatically printed out at the end of each flight: Fault message on the CFDS Post Flight Report.

YES Available on request thru System Report/Test.

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


015

016


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 FLAGS

ECAM WARNINGS / CAUTIONS

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 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 TO PULSE ON GROUND AFTER ENGINE SHUT DOWN

PRESS

TO CALL STATUS PAGE

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


018

3. Access to CFDS Reports 3.1. 3.2. 3.3. 3.4. 3.5. 3.6. 3.7. 3.8.

Different types of CFDS reports How to access the different CFDS reports How to access the list of systems reporting to the CFDS? What is the last (or current) leg report? What is the last (or current) leg ECAM report? What is the previous legs report? What is the avionics status? 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:

• 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.

020

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.

MCDU MENU

RETURN> SELECT DESIRED SYSTEM

CFDS

PRINT*

NEXT PAGE

CFDS

ITEM ONLY DISPLAYED IN CASE OF CLOCK FAULT


021

022


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

RETURN> SELECT DESIRED SYSTEM

CFDS

PRINT*

SYSTEM REPORT/TEST

SYSTEM REPORT/TEST INST

F/CTL>

CFDIU>

FUEL>

EIS 1>

EIS 2>

ICE & RAIN>

INST>

EIS 3>

L/G>

DMU>

NAV>

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”.

CFDS MENU

• Concerns all systems connected to CFDS but only for faults recorded from phase 02 to 09 for type 1 and 3 systems and 05 to 07 for type 2 systems. Phases ground faults avail “GND scanning” system report.

TIME AT WHICH THE CFDS RECEIVES THE FAULT LAST LEG REPORT FEB 23

• Displays “Class1” and “Class2” failures received by CDFS during last flight leg.

PRINT*

A/C IDENT DATE GMT FLTN CITYPAIR XY-ABCO FEB23 2350 XY-1234 LFBO/LFPO
LAST LEG REPORT FEB23 NEXT PAGE

SOURCE FMGC1 IDENTIFIERS FCDC 1 FCDC 2 CFDIU PRINT*

LAST LEG REPORT FEB 23


OR

PRINT*

023

024


3. Access to CFDS Reports 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

FLIGHT PHASE DEFINED INSIDE THE ECAM SYSTEM

PRINT*

A/C IDENT DATE GMT FLTN CITYPAIR XY-ABCD FEB23 2352 XY-1234 LFBO/LFPO NEXT PAGE 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 GMT: 0933 PH: 05 ATA: 26-12 ENG1 LOOP A FAULT GMT: 0904 PH: 06 ATA: 22-00 LAND 3 INOP GMT: 1012 PH: 06 ATA: 27-00 SFCC 1 FAULT

LAST LEG ECAM REP DATE: FEB23


PRINT*

ONE PRINT ACTION CAUSES 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 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

INTERMITTENT FAILURE RUNS FROM 00 (FIRST LEG BEFORE LAST LEG) TO 63

LEG DATE GMT <00 FEB27 1315 FMGC1 <01 FEB24 1328 N2 SENSOR ENG1 <01 FEB24 1318 NO FAC DATA (INTM) <01 FEB24 0928 CHECK ADIRU 1 STATIC PHC INTERFACE

PH 06

ATA 220000

06

770000

06

220000

06

346700

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 <00 FEB27 1315 06 FMGC1 <01 FEB24 1328 06 N2 SENSOR ENG 1 <01 FEB24 1318 06 NO FAC DATA (INTM) <01 FEB24 0928 06 CHECK ADIRU 1 STATIC PHC INTERFACE


LEG DATE GMT <02 FEB23 1915 CHECK LGCIU#PHC 2 INTERFACE

PH 06

ATA 261200

<02 FEB23 1915 06 CHECK LGCIU#PHC 2 INTERFACE

ATA 220000 770000 220000 346700

261200

A PRINT ACTION CAUSES PRINTING OF THE DISPLAYED PAGE ONLY.
PRINT*


025

026


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.

CFDS MENU

AVIONICS STATUS

NO GPCU DAIA ADF1 (CLASS 3) FMGC VHF AIDS
PRINT*

A/C IDENT DATE GMT FLTN CITYPAIR 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 DETECTED IN DMC

FMGC VHF

AVIONICS STATUS

OMU NOILS DATA DMC (CLASS 3)

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

DATE AT THE TIME OF THE PRINT

PRINT>

A/C ID DATE GMT FLTN CITY PAIR F-WWJH 01JAN 0700 ITAF9877 LFPG LFMN MAINTENANCE POST FLIGHT REPORT

DATE AT THE TIME OF THE FLIGHT

0656: 1 ENG START + 3MN OR 80 KTS IF NEW FLIGHT NUMBER NOT ENTERED

A/C ID DATE GMT FLTN CITY PAIR F-WWJH 01JAN 0656/0700 ITAF9877 LFPG LFMN

0700: A/C SPEED < 80 KTS + 150 SEC(30 SEC for CFDIU Std 8 or lower)

GMT PH ATA 1353 05 30-31 ANTI ICE F/O TAT

WARNING/MAINT. STATUS MESSAGES FAULT MESSAGE ON TWO LINES MAXI

FAILURE MESSAGES GMT PH ATA 0657 06 23-24-34 AAA 0657 06 31-38-22 NO MDDU DATA

SOURCE IDENT. GPSSU 1 CFDS

LIST OF SOURCE AND IDENTIFIERS (SYSTEM SOURCE ON TOP LIST)

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


028

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?

030


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

PRINT>

CORRELATED WARNING ASSOCIATED TO THE FAULT “CHECK R WING LOOP A ”

LAST LEGT REPORT FEB23

CORRELATED WARNING DATE FEB23

>

PRINT*

>

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, 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

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/CTL

1744

06

32-00

WHEEL TYRE LO PR (2)

FAILURE MESSAGES GMT

PH

ATA

SOURCE

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

IDENT.

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. A320 Family - Ref: ISI 31.32.00069 - Issue: August 2016

031


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

• Case 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.

• Case 3: No Correlation For those items (failure or warning) not correlated, they are input individually in the TSM.

032

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 REPORT (PFR)

LOGBOOK

Post Flight Report (PFR) A/C ID XY-ABCD | |

DATE 01FEB

GMT 1634

NON CORRELATED POST FLIGHT REPORT

A/C ID XY-ABCD

DATE 01FEB

GMT 1634

FLTN XY-1234 | |

CITY PAIR LFBO LFPO

DB/N XXXXXXXXXXXXXXX FLTN XY-1234

CITY PAIR LFBO LFPO

WARNING / MAINT. STATUS MESSAGES GMT 1411

PH 02

ATA 24-00

ELEC BCL 1 FAULT

FAILURE MESSAGES GMT 1411

PH 02

ATA 24-38-34

SDCA1: NO DATA FROM BCL1

SOURCE ECAM1

IDENT. 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”.

034

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


DATE 01FEB

GMT 1634


A/C ID XY-ABCD

DATE 01FEB

FLTN XY-1234 | |

GMT 1634

CITY PAIR LFBO LFPO


CITY PAIR LFBO LFPO


PH 02

ATA 24-00

ELEC BCL 1 FAULT


PH 02

ATA 24-38-34


SOURCE ECAM1

IDENT. ECAM2

**ON AC/ ALL

24-00 ELEC BCL 1 FAULT

ELEC BCL 1 FAULT ECAM WARNING MESSAGE SELECTED IN THE WARNING/MALFUNCTIONS LIST


035

036


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


DATE 01FEB

GMT 1634


A/C ID XY-ABCD

DATE 01FEB

GMT 1634

FLTN XY-1234 | |

CITY PAIR LFBO LFPO


CITY PAIR LFBO LFPO


PH 02

ATA 24-00

ELEC BCL 1 FAULT


PH 02

ATA 24-38-34


SOURCE ECAM1

IDENT. 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


038

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:

• 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.

040

6. Additional means to optimise PFR data 6.2. Customised Maintenance Filter _

SIL 00-028 ZIP PACKAGE CONTENTS - SIL00-028 PDF File - SIL00-028.csv - FILENVXX.320

FILENVXX.320

ENVELOPE FILTER

FOR CUSTOMISATION OF THE ENVELOPE FILTER FILE, REFER TO MAINTENANCE FILTER TOOL (MFT) THROUGH ISI 31.32.00062

MFT CFDIU Printer

CUSTOMISED MAINTENANCE FILTER DATABASE

“ON GROUND”

PDL or MDDU

“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:

• 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


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 information, until the technical solution is finalised.

042

Notes _

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________


043


Notes _

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

_____________________________________________________________________________________________________________

044

A320 Family Centralised Fault Display SystemTroubleshooting Guidelines

Recommend Documents