Recording pilot reported discrepancies in journey log
|
|
|
|
|
This activity allows you to enter the discrepancies reported by the pilot for the journey log. Tell me more.
Select the “Record Pilot Reported Discrepancies” link at the bottom of the “Create Journey Log” or "Edit Journey Log"page.
The “Record Pilot Reported Discrepancies” page appears.
The system displays the following field:
|
Date & Time 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 time is displayed as HH:MM or HHMM, in 24 hour format. For example 11:00pm is displayed as 23:00 and 10:45am is displayed as 10:45 . |
The system displays the following fields in the “Flight Details” group box:
|
Journey Log # |
The journey log number for which the snag details are to be entered. |
|
Amendment# |
The number identifying the amended journey log. |
|
Aircraft Reg # |
The registration number of the aircraft. |
|
Aircraft Model# |
The model to which the aircraft belongs. |
|
Status |
The status of the journey log, which could be “Fresh” or “Under Amendment”. |
Enter the following:
|
Line # |
Use the drop-down list box to select the line number of the journey log. The system lists all the line numbers identified for the journey log, if the “Main Execution?” field in the Leg Details multiline in the Create Journey Log page is set as “Yes”.. The system sets the latest value of Line # by default, if the hidden control is null and sets the hidden control value by default, If the hidden control value is available. |
Click the “Get Details” pushbutton to retrieve the flight details pertaining to the leg number.
The system displays the following:
|
Form Station |
The station at which the leg of the journey starts. |
|
To Station |
The station at which the leg of the journey ends. |
|
From Date & Time |
The date and time on which the leg of the journey starts. |
|
To Date & Time |
The date and time on which the leg of the journey ends. |
Enter the following in the “Default details” group box:
|
Reported By |
The number identifying the employee who reported the discrepancy.(Alphanumeric,20) Help facility available. |
|
Reported Date & Time |
The date and time on which the discrepancy was reported. (Date &Time Format). |
The system displays the following in the “Discrepancy Details" multiline:
The system retrieves the pending discrepancies if any, which are created or associated to the line package by the line planner control, on clicking the “Get Details” pushbutton.
|
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 |
The textual description of the discrepancy (Alphanumeric, 125). Mandatory. Help facility available. |
|
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 Master” business component. By default, the system leaves the field blank. |
|
Defer ? |
Use the drop-down list box and select “Yes” if the discrepancy must be deferred. Otherwise select “No”. By default, the system sets the field to “No". |
|
Deferral Remarks |
Any additional remarks pertaining to the deferral of the discrepancy (Alphanumeric, 255). |
|
Action |
Use the drop-down list box to set the action for the discrepancy as “Cancel”. By default, the system leaves the field blank. |
|
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. Data entry in this field is mandatory if the fault number is entered. 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. |
|
Reference # |
The reference document number, which contains the discrepancy details (Alphanumeric, 25). Ensure that the reference number is unique for a journey log. |
The system displays the following:
|
Reported Date & Time |
The date and time on which the journey log was reported. |
Enter the following:
|
Reported By |
The code identifying the employee who reported the discrepancy (Alphanumeric, 20). The employee code should have already been defined in the “Employee Information“ business component, and must be in “Active” status. Help facility available |
The system displays the following:
|
Reporting Employee |
The name of the employee who reports the discrepancy. |
|
Chapter Description |
A textual description of the ATA chapter. |
Enter the following field:
|
File Name |
The name of the file attached to the pilot defect report, for reference (Alphanumeric, 50). Help facility available. |
|
Occurrence Report# |
The number identifying the occurrence report in which a PIREP type discrepancy is reported and associated to the current journey log. (Alphanumeric, 40). Ensure that the occurrence report number is defined in the “Occurrence Reporting” business component and is associated to the “Discrepancy #”. . |
|
Note: Ensure that the date and time of the occurrence report is not later than the “To Date” and “To Time” of the leg of the journey log with which it is associated. Note: Ensure that the “Occurrence Report#” has been created for the aircraft registration number in the “Flight Details” group box. The system displays the following: |
|
|
Occ. Reporting Exe. Unit |
The execution unit where the occurrence is reported. |
Check the box in the “Select” column of multiline to mark the discrepancy for deletion.
Click the Delete icon in the tool bar above multiline, to delete the discrepancies selected in multiline.
Enter the following field in the “Pilot Remarks” group box:
|
Remarks |
Any information pertaining to the discrepancies (Alphanumeric, 2000). |
Click the “Record Discrepancies” pushbutton to record the discrepancies.
The system generates a unique discrepancy number depending upon the numbering type selected in the ”Set Options” activity, and assigns the “Fresh” status for the created discrepancies.
The system also updates the discrepancy code and other details in the “Discrepancy Processing” business component. The system saves the record status as “Fresh”, discrepancy type as “PIREP”, applicability as “Aircraft”, source document as “Journey Log” and source document number as the journey log number.
The system also updates the discrepancies or MRs that are retrieved from the “Line Planning and Control” business component, in the current journey log.
Note: The system does not allow modification of discrepancies whose record status is pending and journey log status is “Under amendment”.
Note: Pilot reported discrepancies cannot be recorded for a journey log which is in the “Cancelled” or “approved” status.
Recording pilot reported discrepancies in journey log – An overview
Discrepancies, or snags, are typically the symptoms of the problem, which are observed by the operation crew, such as the pilot, first officer, flight engineer or the cabin crew. In this page, you can add or modify the discrepancy details. You must enter the description of the discrepancy observed. The category for the discrepancy, the action taken to solve the discrepancy, the fault number and the code of the employee who reported the fault can also be entered.
The system generates the discrepancy number based on the numbering type selected. The discrepancies reported in the journey log are processed in the “Discrepancy Processing” business component, once this journey log is confirmed.
The system updates the discrepancy details and sets the “Last Modified By” and “Last Modified Date” fields to the name of the currently logged in user and current server date, respectively.
Specify the discrepancy category and the action
Specify the discrepancy category and the action
Use the “Discrepancy Category” drop-down list box to select the category of the discrepancy.
Use the “Action” drop-down list box to specify the action taken against the discrepancy.