Академический Документы
Профессиональный Документы
Культура Документы
AIRBUS S.A.S.
31707 BLAGNAC CEDEX, FRANCE
CONCEPT DESIGN GDC
REFERENCE GDCOD-S298/03
NOVEMBER 2003
PRINTED IN FRANCE
AIRBUS S.A.S. 2003
ALL RIGHTS RESERVED
NFF
AN EADS JOINT COMPANY
WITH BAE SYSTEMS No Fault Found policy
The statements made herein do not
constitute an offer. They are based on
A320 Family and A330/A340 Family
the assumptions shown and are
expressed in good faith. Where the
supporting grounds for these
statements are not shown, the Company
will be pleased to explain the basis
thereof. This document is the property
of Airbus and is supplied on the express
condition that it is to be treated as
confidential. No use of reproduction
may be made thereof other than that
expressely authorised.
Customer Services
This is the fourth issue of the Airbus No Fault Found (NFF) Policy
1
No Fault Found policy
Aims and benefits to be achieved from
implementing this policy
2
No Fault Found policy
The success of the policy is dependent on each party fulfilling the
specific requirements in terms of reporting and tracking the relevant
information as defined below.
Suppliers responsibility
The supplier is responsible for keeping historic data by serial number of all
units. These files should not only contain data on a LRU warranty aspects
but also on the total repair history, reasons for removal, testing, NFF,
modification standard and all the work performed on the LRU.
Operators responsibility
The operator will provide the minimum data for removal substantiation.
The removal data are:
This policy presupposes that the Airbus operational - Flight Crew Operating
Manual (FCOM) including Operation Engineering bulletins (OEBs) -
and maintenance recommendations are followed.
3
No Fault Found policy
NFF charges
When no LRU defect is found to be the origin of a fault message, the cause
will be clarified between the supplier and Airbus. The supplier will open a
specific file for these cases.
Airbus and the suppliers will not support NFF cases where clear TSM
procedures, in relation to a PFR warning message, provide for correct
system trouble shooting.
The operator shall not be deemed responsible where it is shown that the LRU
test specification is incomplete or incorrect.
4
Aircraft Return to service
YES PASS
AIRMAN Log entry book Operator test Dump BITE memory
ATE test
bench capability before reset
PFR
NO FAIL
or Keep BITE data
on record for
TSM analysis by supplier
No Fault Found policy
if LRU becomes
Unit sent to Repair at rogue
repair station operators
BITE test required shop
by TSM Constitute
supporting data
PASS if no TSD available
5
Test NFF
NO Fault confirmed YES FAIL
BITE
by BITE
Retrieve print-out
Procedure - NFF Policy flow chart
YES
YES
Supporting
TSD Operator supplies
print-out Unscheduled data substantiates
supporting data
sent with unit removal YES removal NO
unit NO
Procedure on aircraft
All entries are made by the flight crew (PIREP) or maintenance personnel
(MAREP) into the aircraft log.
BITE test
In this case the supporting data is the PFR (coming from the
aircraft or from AIRMAN) and/or the logbook and the BITE test
results (where applicable).
6
No Fault Found policy
The LRU is removed in accordance with the TSM and dispatched to the
suppliers authorised repair station with the supportive data.
In this case the supporting data is the PFR and TSD.
The LRU is returned to supplier repair station together with the ATE failure
report. In this case the supporting data is the PFR and the ATE report.
If the PFR plus the BITE Test Results or TSD as applicable or the ATE failure
results are included and demonstrate (in conjunction with TSM) that the
removal is justified, then no testing charges will apply in case of NFF.
If the above data confirm aircraft system fault and if no Airbus Operational or
Maintenance procedure exists to prevent LRU removal, Airbus will warrant
that the aircraft system responsible party supports test charges.
7
No Fault Found policy
Definition of terms
AIRCRAFT MALFUNCTION
UNSCHEDULED REMOVAL
Known or suspected
malfunction
No failure which
substantiates Failure found
the reason for removal even substantiating
though another failure the reason for removal
may be found
Applicability
It has been found that such cases are impossible to adjudicate as far as
assessing the responsibility within the standard maintenance practices.
8
No Fault Found policy
Equipment list
A320 Family
9
No Fault Found policy
FCD Full Colour Display or DU Thales Avionics
FCDC Flight Control Data Concentrator Litef
FCU Flight Control Unit Thales Avionics
FDU Fire Detection Unit LHotellier
FDIU Flight Data Interface Unit SFIM
FLSCU Fuel Level Sensing Control Unit BFG Fuel
FMGC Flight Mngt. and Guidance Computer Thales Avionics
FQIC Fuel Quantity Indication Computer Smiths/BFG Fuel
FWC Flight Warning Computer Airbus Avionics
A330/A340 Family
11
No Fault Found policy
FMGEC Flight Mngt. Guidance/Envelope Computer Thales Avionics
FWC Fight Warning Computer Airbus Avionics
AIRBUS S.A.S.
31707 BLAGNAC CEDEX, FRANCE
CONCEPT DESIGN GDC
REFERENCE GDCOS-S298/03
NOVEMBER 2003
PRINTED IN FRANCE
AIRBUS S.A.S. 2003
ALL RIGHTS RESERVED
NFF
AN EADS JOINT COMPANY
WITH BAE SYSTEMS No Fault Found policy
The statements made herein do not
constitute an offer. They are based on
A320 Family and A330 & A340 Family
the assumptions shown and are
expressed in good faith. Where the
supporting grounds for these
statements are not shown, the Company
will be pleased to explain the basis
thereof. This document is the property
of Airbus and is supplied on the express
condition that it is to be treated as
confidential. No use of reproduction
may be made thereof other than that
expressely authorised.
Customer Services