How to handle different class fault messages

ATA: 45-00 FIN: Ref: 45.00.00028

A/C Type: A318 A/C Serie: Topic: First Issue 09-JUL-2010
A319 Date:
A320
A321
A330
A340
A340-500
A340-600
Part Number: Last Publication 27-SEP-2016
Date:
Supplier:
Linked Linked
Articles: Documentation:

Old Wise Ref:

engsup-13961

Engineering Support
First Issue Date: 09-JUL-2010
Model: Last Publication Date: 27-SEP-2016
Manufacturer:

Applicability

References

Description

How to handle different class fault messages

Solution

1. Airbus suggestion on how to treat the PFR messages

More in particular, WHEN taking the Maintenance Action following Class I, Class II or Class III fault
message.
Conditional maintenance operations are carried out in response to the observations made by the flight
crew in the LOG BOOK.
This information represents a cockpit effect defined below. If no log book entry, no maintenance action
is due during turn around. PFR items associated to a logbook entry may be differed under MEL.
Correction interval is defined in the MEL.

2. Reminder on the failure message classification on A320/A330/A340 fam A/C

a. CLASS I (CLASS 1):

We remind that a CLASS 1 fault message should be associated to:

- a cockpit effect:
ECAM warning
a local warning
a flag
any invalid function such as a missing audio signal, amber crosses on a system page,
etc...
The COCKPIT EFFECT should be reported by the pilot in the LOGBOOK.

- or to a cabin effect:
message displayed in the cabin on the Forward Attendant Panel (FAP),
caution lights,
chimes, etc

b. CLASS II (CLASS 2):

We remind that a CLASS 2 fault message should be associated to a Maintenance Status.

c. CLASS III (CLASS 3):

We remind that a CLASS 3 fault message is not recorded in the PFR.

CLASS 3 messages are recorded in the memory of each SYSTEM BITE and can be
displayed:
- via the CLASS 3 REPORT of each system BITE
- via the CMS CLASS 3 report (A330/A340 only)
- via the CFDS AVIONICS STATUS report (A320 only).

However, there are deviation cases to these items. There are documented, when identified as
deviation, in following ISIs:

3. Management of fault messages

The management of the fault messages mainly depends on the maintenance level:

a. 1st Level:LINE MAINTENANCE

No Log-Book complaint No Maintenance Action required

Log-Book complaint (Class 1) PFR + System Report / Test +
LRU Level only Ref to MMEL

b. 2nd Level:BASE MAINTENANCE / NIGHT STOP

Maintenance status PFR (Class 2) +

LRU Level System Report / Test

c. 3rd Level:SCHEDULED CHECKS

Class 3 faults General Class 3 Report +

LRU level System Report / Test

d. 4th Level:SHOP MAINTENANCE

LRU removal Trouble Shooting Data +

 SRU Level BITE Shop Memory

4. More in particular, how to treat a PFR Message (whichever category) if no Pilot Report has
been made on the Technical Log Book

a. Regarding CLASS 1 messages associated to a cockpit effect or to a cabin effect:

As stated above, the troubleshooting philosophy is that no maintenance action is due during
turn around if no logbook entry.

It is pilot's duty to correctly enter items in the logbook.

If no entry in the logbook is made for a CLASS 1 messages linked to a cockpit effect, the
maintenance may take the opportunity of an A/C stop to address it.

b. Regarding CLASS 2 messages associated to a Maintenance Status:

MAINTENANCE STATUS messages displayed on ECAM STATUS page are for maintenance
purpose only. Dispatch with MAINTENANCE STATUS messages displayed on ECAM
STATUS page is allowed without condition.

Management of these messages is handled by the Trouble Shooting Manual (TSM) and
should be rectified within the timescale defined in the TSM, i.e. no later that 800 F/H for
A330/A340 fam A/C and no later than 10 days for A320 fam A/C.

Maintenance Status is displayed on the ECAM on ground after all engines shut down only.
Maintenance Status remains displayed on the ECAM as long as it is present and no
engine is turned on. Maintenance Status should be logged in the logbook, at least to
initiate the countdown for correction. It is left to Operator to define the role devoted to
flight crew and/or maintenance personnel in this procedure.

c. Regarding CLASS 3 messages:

These messages are not associated to any cockpit nor cabin effect and are not part of the
PFR. It is therefore very unlikely that they are reported by the PILOT in the logbook.
On A320, CLASS 3 faults should be checked on a regular basis as part of a MPD task.
However, there is no obligation for correction.

On A330/A340, there is no obligation to check CLASS 3 faults. There is an unlimited time for
correction.

However, these CLASS 3 faults may have an economical effect.

Additional Note

Airbus SAS, 2016. All rights reserved. Confidential and proprietary document.The technical information
provided in this article is for convenience and information purposes only. It shall in no case replace the
official Airbus technical or Flight Operations data which shall remain the sole basis for aircraft
maintenance and operation. These recommendations and information do not constitute a contractual
commitment, warranty or guarantee whatsoever. They shall not supersede the Airbus technical nor
operational documentation; should any deviation appear between this article and the Airbus or airline's
official manuals, the operator must ensure to cover it with the appropriate document such as TA, FCD,
RAS. Access to WISE is supplied by Airbus under the express condition that Airbus hereby disclaims any
and all liability for the use made by the user of the information contained in WISE. It shall be used for
the user's own purposes only and shall not be reproduced or disclosed to any third party without the
prior consent of Airbus.