Discrepancy Report in ETOP Aircraft

This report displays discrepancy-related details pertaining to ETOP certified aircraft of a reliability fleet, for the month of the report.

See Discrepancy retrieval for reliability report for more information.

Report input: You must select the month and year and, the reliability fleet for the report in the Generate Reliability Report page. For further information, see the “Generate Reliability Report” topic.

Report output: This report is an Excel sheet and consists of a single work sheet - ETOP report.

ETOP report worksheet: Helps to analyze discrepancies of ETOP aircraft with reference to ATAs. Both, PIREP and MIREP types of discrepancies are taken into consideration for generating the report. The below-listed details are available in the report,

Aircraft Reg #	The identification number of the aircraft.
Flight #	The identification number of the flight.
Reported Date	The flight date of the aircraft, as recorded in the journey log.
ATA #	The ATA against which the discrepancy is recorded.
System ATA #	The System ATA to which the ATA is mapped.
Major System ATA #	The Major System ATA to which the System ATA is mapped.
Discrepancy #	The identification number of the discrepancy.
Discrepancy Description	The short name or description of the discrepancy.
Remedial Action	The action undertaken to resolve the discrepancy.
Resolved Date	The date on which the discrepancy is resolved.

Prerequisites

System ATAs and Major System ATAs must be created and their attributes defined in the ”Set ATA Reporting Levels” page of the Set Reliability Fleet activity in the Reliability Analysis component. Prior to this, reliability fleets must be defined in the same activity.
Discrepancies recorded in the Discrepancy Processing component.

Discrepancy retrieval for reliability report

For generating the discrepancy information, the system retrieves discrepancies of type “PIREP” and “MIREP” reported against all the aircraft in the fleet, from Discrepancy Processing. However, the aircraft must be mapped to a configuration class that is flagged for “ETOP”. Further, the discrepancies must also satisfy the following conditions for inclusion in the report,

The record status must not be “Fresh, “No Fault Found” or “Cancelled”.
The discrepancy applicability must be “Aircraft”.
The Analysis Required attribute of the ATA against which the discrepancy is reported must be flagged for reliability analysis in the Set ATA Reporting Levels page of the Setup Reliability Fleet activity.
The discrepancy must be reported in the month of the report.
The Reliability Analysis attribute of the discrepancy must be set to “Include”, in the Analyze Discrepancy/MR Details” activity.

Note: A discrepancy is not considered for reporting, if it does not possess an ATA #.