Recording discrepancies

This activity allows you to record the discrepancies that are identified during the execution of line maintenance activities on the aircraft. Tell me more.

Select the “Record Discrepancies” link at the bottom of the “Plan Gate Maintenance” page.

The “Record Discrepancies” page appears.

The system displays the following field:

Date Format

The format in which the date fields are displayed. This format is displayed from the "User Preferences" business component based on the login user ID. In case the format is not defined, the system displays the date format from the “Enterprise Modeling” business component by default.

The system displays the following fields in the “Aircraft Details” group box:

Aircraft Reg #	The registration number of the aircraft.
Plan Date	The date on which the flight schedule is planned.
Flight #	The number identifying the first flight that is scheduled for the plan date.
Leg #	The number identifying the leg in the journey.
Station #	The station for which the line maintenance activities are planned.
Work Plan Status	The status of the line package, which could be “Package Created”, Tech. Log Created” or “Not Planned”.

Enter the following in the “Default Details” group box:

Reported by

The code identifying the employee who recorded the discrepancy (Alphanumeric, 20). The number entered here must be a valid employee number as identified in the “Employee Information” business component and should be in “Active” status.

Reported Date

The default date on which the employee has recorded the discrepancy (Date Format). The date entered here should not be later than the current system date.

The system displays the following in the “Discrepancy Details” group box:

Discrepancy #

A unique number generated by the system to identify the discrepancy. The number is generated based on the numbering type selected in the ”Set Options” activity.

Enter the following fields in the “Discrepancy Details” multiline:

Discrepancy Description

The textual description of the discrepancy (Alphanumeric, 80). Mandatory.

Help facility available.

ATA #

The ATA chapter on which the discrepancy is reported (Alphanumeric, 16). Ensure that the value entered here is a valid ATA chapter number in the “Active” status, as defined in the “Aircraft” business component.

Help facility available.

Fault #

The code identifying the fault in the aircraft (Alphanumeric, 25). This fault code should have already been defined in the “Create Fault Codes” activity of the “Fault Isolation Manual” business component and the status of the fault code must be “Active”. Also, the fault code must be a valid fault code for the ATA chapter entered in the “ATA #” field.

Help facility available.

Note: Ensure that “ATA #” is entered, if “Fault #” is specified.

Tracking Status	Use the drop-down list box to select the tracking status of the discrepancy or the maintenance report. The system displays all the values for the attribute “Tracking Status” as defined in the “Maintain Discrepancy Attributes” activity of the “Common Masters” business component. The system leaves the field blank by default.
Discrepancy Category	Use the drop-down list box to select the discrepancy category of the journey log for which the discrepancy details are reported. The system lists all the discrepancy categories as defined in the “Maintain Discrepancy Attributes” activity of the “Common Masters” business component. By default, the system leaves the field blank.
Discrepancy Type	The type of discrepancy, which can be “PIREP” or “MIREP”. PIREP - Indicates that the discrepancy has been reported by the pilot while recording the journey log. MIREP - Indicates that the discrepancy has been reported by the mechanic while raising a technical log. By default, the system sets this field to “PIREP”.
Action	Use the drop-down list box to change the status of the discrepancy or the maintenance report. Mandatory. The system lists the following options: To Process – Select this option to process the discrepancy. Cancel – Select this option to cancel the discrepancy. No Fault Found – Select this option to indicate that no fault is found in the component. Close - Select this option if the discrepancy is closed. The system leaves this field blank by default.
Reported By	The code identifying the employee who recorded the discrepancy (Alphanumeric, 20). If this field is left blank, the system considers the value specified in the “Reported by” field in the “Default Details” group box.
Reported Date	The date on which the discrepancy was reported (Date Format). If this field is left blank, the system considers the “Reported Date” field in the “Default Details” group box. The date entered here should not be later than the current system date.

The system displays the following in the “Discrepancy Details” multiline:

Record Status

The record status of the discrepancy or the maintenance report, which could be “Fresh”, “Under Resolution” or Pending”.

Note: Ensure that at least one record exists in the multiline.

Click the “Record Discrepancies” pushbutton, to record the discrepancies.

The system generates a unique discrepancy number, based on the numbering type selected in the ”Set Options” activity, and assigns the “Fresh” status for the created discrepancies.

If the work plan status is "Not Planned", the system updates the discrepancy information to the "Discrepancy Processing" business component in “Pending” status. If the work plan status is “Package Created”, the system updates the discrepancy information to the corresponding line package for the flight number, leg number and plan date. If the work plan status is “Tech Log Created” and if the technical log is not in “Confirmed” status, the system adds the discrepancy details directly to the “Tech Log #” for the flight number, leg number and plan date. Also, the system changes the status of the discrepancy to “Under Resolution”.

Recording discrepancies – An overview

This page allows you to record the pilot-reported discrepancies and mechanic reported discrepancies, along with the details of the employee who recorded the discrepancy. The recorded discrepancy details can be updated to the "Discrepancy Processing" business component or line package or to the technical log based on the work plan status of the line package.