Editing journey log information

This activity allows you to modify journey log details. Tell me more.

• Select the “Edit Journey Log” link in the “Select Journey Log” page. Alternatively, click the hyperlinked journey log number in multiline of the same page.

The “Edit Journey Log “ page appears.

You can invoke this page only if at least one of the conditions given in the table mentioned below, is satisified:

Usage Mode: ‘Usage Mode’ is a process parameter defined in the "Configurator” business component to indicate whether the system is being operated from the main base or remote base to record OFMS transactions.

Mode of Usage: ‘Mode of Usage’ is defined in the “Aircraft” business component to indicate the location of the aircraft. Mode of Usage is said to be “Online” if the aircraft is located in the main base and “Offline” if the aircraft is in a remote base.

The system displays the following:

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

•  Enter the following:

The system displays the following:

•  Enter the following:

The system displays the following:

•  Enter the following field:

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

To proceed carry out the following

• Select the “Leg Details” tab to modify the leg details of journey log

• Select the “Summary Parameter Details” tab to modify the parameter details of journey log

• Enter the following in the “Operational Details” group box:

The system displays the following in the “Computed Flight Parameters” group box:

The system checks for the parameters definition in the ‘Maintain Journey Log Parameter Information’ activity of the “Aircraft” business component, of the “Aircraft Model #” and “Configuration Class combination, for the “Aircraft Reg #” on which the journey log is created.

If parameter definition is not available for the “Aircraft Model #” and “Configuration Class” combination, the system checks for the leg-wise parameter definition for the “Model #” alone, of the “Aircraft Reg #” on which the journey log is created.

In parameter definition is not available for the “Aircraft Model #”, then the system checks for the leg-wise parameter definition at the generic level, that is, when the “Aircraft Model #” and “Configuration Class” combination is left blank in the ‘Maintain Journey Log Parameter Information’ activity of the “Aircraft” business component.

Note: For the defined parameters, if position code is not available, then the system considers the parameter applicable for the aircraft. If position code is available, and component is attached at that position, then, the system considers the parameter applicable for component level. If component is not attached, then the system considers the parameter is applicable for part level.

If the leg-wise parameter in ‘Maintain Journey Log Parameter Information’ activity of the “Aircraft” business component is not applicable for the aircraft registration number, or the attached component or part of the aircraft on which the journey log is created, then the system displays the following:  

• Not Set - The parameter has not been set. For example, if the definition is available for “Parameter1” and “Parameter2”  and no definition is available for “Parameter3” to “Parameter6” , then system displays “Not Set” .

• Not Defined – The system displays “Not Defined” when the defined parameters in the ‘Maintain Journey Log Parameter Information’ activity of the aircraft business component, is not applicable as aircraft or part or component level parameters.

For example, if the defined parameter in the “Maintain Journey log Parameter Information ” activity of the aircraft business component, is identified as aircraft parameter, and if its not applicable for the “Aircraft Reg#” on which the journey log is created or the defined parameter in the “Maintain Journey log Parameter” activity of the “Aircraft” business component is identified as component or part level parameter, and if its not applicable for the attached component number or part number of the aircraft registration number on which the Journey log is created, then the system displays the following:

• Not Updateable – The system displays this, when the defined parameters in the ‘Maintain Journey Log Parameter information’ activity of the "Aircraft" business component, refers to a  source other than ‘Flight Log’.

For example, If the parameter ‘Param1’ is defined in the “Maintain Journey Log parameter Information’”activity of the “Aircraft” business component, and is applicable to aircraft, but the source  defined is not ‘Flight log’, then system displays “Not Updateable”.

• Position Not Available – The system displays this when the  defined position in the “Maintain Journey Log Parameter information” activity of the “Aircraft“ business component, is not available in the configuration for the “Aircraft Reg #” on which the journey log is created.

For example, If the position ‘Pos1’ is defined in the “Maintain Journey Log parameter Information” activity of the “Aircraft” business component, and this position is not identified as first level position in the aircraft configuration for the aircraft on which journey log is created.

• Position Inactive – The system displays this when the defined position in the in the ‘Maintain Journey Log Parameter information” activity of the "Aircraft" business component, is available in the configuration for the aircraft on which the journey log is created, but the position code status is set as ‘Inactive’.

For example, If the position ‘Pos1’ is defined in the “Maintain Journey Log parameter Information” activity of the “Aircraft” business component, and this position is also identified as first level position in the aircraft configuration for the aircraft on which journey log is created, but if the position code status is set as ‘Inactive’, then system displays 'Position Inactive'.

• Not available – The system displays this, if  no parameter definition is available in the “Maintain Journey Log Parameter” activity of the “Aircraft “ business component, for the aircraft on which journey log is created,  for all the leg-wise parameters.

Note: The system displays ‘Not Available’ for all the leg-wise parameters, when no parameter is defined at the generic level.

Note: If the parameter values in the “Leg Parameters Mapping & Journey Log Totals” group box is "Not Set", "Not Defined", "Not Updateable", "Position Not Available", "Position Inactive", "Not Available" or "Definition not Available", then the corresponding fields in the “Summary Parameter Details” multiline must be left blank.

Note: Ensure that the “To Station” is entered, if the “From Time” and “To Time” fields are entered.

On clicking the “Create Log” or “Approve log” pushbutton, the system displays “1”, if the “Flight Duration” field is left blank or if “Flight Duration” is equal to the difference between “From Date & Time” and “ To Date & Time”.

Note: Ensure that the “Flight Duration” is zero when the “Take Offs” is zero.

Ensure that the journey leg timings do not overlap with each other within the same journey log as well as across the journey logs, for the same aircraft registration number, only if “FH Log Mode” is set as “Actual Flight Times" for the Aircraft Reg # as defined in the “Aircraft” business component.

For example, for Journey Log ‘JL001’, if a leg has been reported between ‘11:00’ hours and ‘13:00’ hours on 17 August 2004, then, in the same journey log, another leg cannot be reported between ‘12:30’ hours and ‘14:15’ hours, for the same date. If a leg has been reported between ‘11:00’ hours and ‘13:00’ hours on 17 August 2004, then, in a different journey log ‘JL002’, a leg cannot be reported between ‘12:30’ hours and ‘14:15’ hours for the same aircraft registration number on the same date (17 August 2004).

• Enter the following in the “Document Attachment Details’ group box:

• Click the “View File” link to view the contents of the attached file.

To edit journey log

• Click the “Edit Log” pushbutton to edit journey log details.

Transferred aircraft: You cannot modify a journey log for an aircraft that has been transferred to another operating unit for maintenance. The system allows for changes in the log upon return of the aircraft.

The system verifies that no other journey log is entered for the same period for the aircraft registration number. The system updates the journey log details and sets the status of the journey log as “Fresh”.

On clicking the “Edit Log” pushbutton, the system also updates the “Discrepancy Processing” business component. The system sets the record status as “Pending”.

Note: If the “Departure Time” is not entered, the system considers the “Sch. Arrival Time” as the “Arrival Time”. If “Arrival Date” is not specified, the system calculates the arrival date as the sum of departure date and block hours.

If the “Flight Status” for a flight and leg combination is “On-Schedule” or “Delayed” and if the “Arrival Station” is not entered, the system stores the arrival station defined for the flight and leg combination in the “Flight Assignment” business component as the “Arrival Station”, if the “Flight Details Validation Basis” is set as "Required" in the Set Options activity of the current business component.

If the “Update Mode” is "Delta", the system sums up the parameter values in the " Summary Parameter Details" multiline for all legs of the journey and displays the total for the corresponding parameter in the "Computed Flight Parameters" group box. For example, if a journey has three legs and the values for “Parameter 1” field of the first, second and third leg of the journey is ‘2’’5’ and ‘4’ respectively, the “Parameter 1” field in the "Computed Flight Parameters" group box will display ‘11’ as the parameter value. 

If the “Update Mode” is "New", the systems displays the parameter of the last leg in the corresponding parameter field of the "Computed Flight Parameters" group box. For example, if a journey has three legs and the value for “Parameter 1” field for the first, second and third leg of the journey is ‘2’,’5’ and ’4’ respectively, then the “Parameter 1” field in the   "Computed Flight Parameters" group box will display ‘4’ as the parameter value.

When an already-recorded summary leg parameter information is split into multiple detailed legs, the system moves the discrepancies associated to the summary leg record / earlier leg(s) to the last leg of the journey. For example, assume a journey has three legs, the first leg from Station ‘A’ to Station ‘C’, the second leg from Station ‘C’ to Station ‘D’ and the third leg from Station ‘D’ to Station ‘E’. If the first leg is modified to include another leg, there will be four legs, the first leg from Station ‘A’ to Station ‘B’, the second leg from Station ‘B’ to Station ‘C’, the third leg from Station ‘C’ to Station ‘D’ and the fourth leg from Station ‘D’ to Station ‘E’. The system then associates the discrepancies that were reported on the first, second, third to the fourth leg.

Note: The parameters must be mapped to the “Hobbs Meter Reading” base parameter as defined in the “Aircraft” business component, If the “FH Log Mode” is set as "Hobbs Meter Reading" for the Aircraft Reg #.

If the "FH Log Mode" is set as "Actual Flight Times" for the Aircraft Reg #, then the system calculates the following for each row in the Leg Details multiline with reference to UTC:

a) Arrival Time = Departure Time + Flight Hours. If the value of “Arrival Time” is greater than 24:00 hrs, then the “Landing Time” as difference of Departure Time and Flight Hours.                                                                                                                 

b) Arrival Date = Departure Date + Flight Hours. If the “Arrival Time” is later than the “Departure Time” and less than 24:00 hrs, then the “Arrival Date” is the same as “Departure Date”. If the “Arrival Time” is earlier than the “Departure Time”, then the “Arrival Date” is one day later than the “Departure Date”.

c) If the “Flight Hours” is more than 24 hours, then the “Arrival Date” is the addition or subtraction of quotient  of the Flight Hours by 24 to the “Departure Date”.  For ex: If Departure Date is 15/11/2006, FH = 23:00 hrs, then Landing Time = Arrival Time.

Note: If the “FH Log Mode” is set as "Hobbs Meter Reading" for the Aircraft Reg # as defined in the “Aircraft” business component, and if there is a manual new mode re-initialized entry for the Parameter which is mapped to “Hobbs Meter Reading” base parameter, later to the Arrival Date and Arrival Time of the Latest Journey Log # in “Confirmed” status  for the Aircraft Reg #, the system allows the creation of a Journey Log with the Hobbs-In value less that or equal to re-initialized value. E.g. If there is a Journey Log with Hobbs-Out as 100 and Hobbs-In as 120 in “Confirmed” status with Arrival Date as 15/11/2006 and Arrival Time 10:00 hrs and if user updates the Parameter mapped to Hobbs Meter Reading base parameter with a value 110 with As On Date as 15/11/2006 and As On Time as 11:00 hrs, then a system allows creation of Journey Log  with Hobbs-Out/In value greater than or equal to 110.Note: If the “Flight Details Validation Basis” option is set as "Not Required" in the “Set Options” activity of the current business component, and if the “FH Log Mode” is set as "Actual Flight Times" for the Aircraft Reg # as defined in the “Aircraft” business component, then the system ensures one preceding record is entered in the “Flight Hours” column for each row in the Leg Details multiline.

Note: "If the “Flight Details Validation Basis” option is set as "Not Required" in the “Set Options” activity of the current business component, if the “FH Log Mode” is set as "Actual Flight Times" for the Aircraft Reg # as defined in the “Aircraft” business component and if the departure date and departure time are entered, the system calculates the Arrival Time and Arrival Date as given below:

a) Arrival Time = Departure Time + Flight Hours. If the value for Arrival time is greater than 24:00 hrs, then the Arrival time is 02.00 hrs for the Departure Time = 23:00 hrs and FH = 3:00.

b) Arrival Date = Departure Date +Flight Hours. If Arrival Time is later than the Departure Time and less than 24:00 hrs, then the Arrival Date is the same as Departure Date.

c)  If Arrival Time is earlier than the Take-Off Time, then the Arrival Date is one day later than the Departure Date.

Note: "If the “Flight Details Validation Basis” option is set as "Not Required" in the “Set Options” activity of the current business component, if the “FH Log Mode” is set as "Actual Flight Times" for the Aircraft Reg # as defined in the “Aircraft” business component and if the arrival time and arrival date are entered, the system calculates the Departure Time  and Departure date as given below:

a) Departure Time = Arrival Time - Flight Hours. For E.g. If the value for Arrival Time is negative, the Arrival Time = 06:00 hrs, FH = 8:00, then the Departure Time = (06:00-08:00)+24 = 22:00 hrs.

b) Departure Date = Departure Date - Flight Hours. If Arrival Time is later than the Departure Time and less than 24:00 hrs, then the Departure Date is the same as Arrival Date

c)  If Arrival Time is earlier than the Departure Time, then the Departure Date is one day earlier  than the Departure Date.

Note: If the “Flight Details Validation Basis” option is set as "Not Required" in the “Set Options” activity of the current business component, if the “FH Log Mode” is set as "Actual Flight Times" for the Aircraft Reg # as defined in the “Aircraft” business component and for each row of the Leg Details multiline if no value is entered in the Departure Date, Departure Time, Arrival Date and Arrival Time, then the system copies the Arrival Date and Arrival Time of the preceeding leg as the Departure Date and Departure Time for current record.

Note: The system updates the arrival date of the aircraft of the preceding leg as the departure date for the next leg, if the status of the previous flight is other than “Cancelled” or “Substituted”.

Note: If the Flight # and Leg # exist in their respective fields, if the “Arrival Time” is not entered and only if the “FH Log Mode” is set as "Actual Flight Times" for the Aircraft Reg # as defined in the “Aircraft” business component, then the system considers the “Sch. Arrival Time” retrieved from the “Routing Master” business component as the “Arrival Time” for the “Flight Status” as  “On Schedule”, and considers the “Arrival Date” and “Arrival Time” as the sum of the “Departure date” and “Departure Time and Est. Travel Duration as specified in the “Flight Assignment” business component for the “Flight Status” as “Diverted”.

The system performs the following on clicking the “Edit Log” pushbutton:

• If the flight status is set as “On Schedule”, then the system ensures that: (a) The difference between the Schedule Departure Time and the Actual Departure Time, and (b)The  difference between the Schedule Arrival Time and the Actual Arrival Time, is less than the set limit for Delay Duration.

• If the flight status reported for the journey log is “Delayed”, then the system ensures that: (a) The difference between the Schedule Departure Time and the Actual Departure Time, and (b) The difference between the Schedule Arrival Time and the Actual Arrival Time, is greater than the set limit for Delay Duration.

Note: The system considers the “Reportable Delay (In Minutes)” as the Delay Duration, if defined in the “Reliability Analysis” business component. Otherwise, the system considers the “Delay Duration (In Minutes)” defined in the “Aircraft Reliability” business component as the Delay Duration.

On approval of journey log, if the Parameter mapped to ‘Flight Days’ base parameter is mapped to the Aircraft Reg #, then system update the Flight Days parameter value based on the following:

1. Date option provided for ‘Date for Flight Day update’ option in the Set option activity of Flight log business component is ascertained. Date options may be ‘Flight Date’ or ‘Departure Date’ or ‘Arrival Date’ or ‘Take off date’.

2. Flight Status to be considered for Flight Day parameter update are ascertained from the Flight Day Computation options in Flight log business component

3. Flight Operation Types to be considered for Flight Day parameter update are ascertained from the Flight Day computation options in Flight log business component.

4. For the Date value provided in the Date option ascertained as mentioned above, as mentioned

a. If the ‘Flight Status’ of the Journey Log – Leg is considered for Flight Day update and

b. If the ‘Flight Operations Type’ of the Journey Log is considered for Flight Day update and

c. If the Journey Log getting approved is the first Journey log document (i.e no other Journey log exists in Approved status for that Date), then system updates the Flight Day parameter value as 1 for that Date.

Example: For Aircraft Reg # VT-JAN, let there be a new journey log JL1 created with Flight Date as ‘01/01/2009’. The Journey log – leg details be as follows:

Let following be the options set for ‘Flight Day Computation options’ in the Flight log business component

Based on the above given options settings, assuming that JL1 is the first Journey Log created on 02/01/2009,(02/01/2009 is considered since Departure Date is set as ‘Date for Flight Date update) on approval, system will update the Flight Day parameter value as “1” for the date 02/01/2009

Note:

1. The date for which the “Flight Days” parameter to be updated should be identified from the set options “Flight Day computation basis” in the current business component.

2. Journey Log – legs for which the Flight Operations Type and Flight Status identified as “Include” in the set options “Flight Day computation basis” in the current business component will only be  considered for Flight Day update

3. If the “Flight Days” parameter is incremented already for the considered date as per the set option by the any other journey log, then it will not be incremented by 1 in the Parameter history for the Aircraft reg # on approval of  the current Journey log.

To approve journey log

• Click the “Approve Log” pushbutton to approve the journey log details.

Transferred aircraft: You cannot approve a journey log for an aircraft that has been transferred to another operating unit for maintenance. The system allows for log approval upon return of the aircraft.

The system sets the status of the journey log to “approved”.

Once a journey log is confirmed, the respective aircraft details are updated with the parameter values entered in this page. If a component is attached to the aircraft, then the parameter values are updated to the component as well.

Note: The system allows approval of the journey log only if the user login ID is granted the necessary access rights for ‘approval’. Once the journey log is approved, the record status of the discrepancies is set to “Pending” in the “Discrepancy Processing” business component.

On approval of the journey log, the system updates the flight details, interruption details and delay summary details in the “Regularize Operational Interruption Details” page.

When an already-recorded summary parameter information is split into multiple detailed legs, the system moves the discrepancies associated to the summary leg record / earlier leg(s) to the last leg of the journey. For example, assume a journey has three legs, the first leg from Station ‘A’ to Station ‘C’, the second leg from Station ‘C’ to Station ‘D’ and the third leg from Station ‘D’ to Station ‘E’. If the first leg is modified to include another leg, there will be four legs, the first leg from Station ‘A’ to Station ‘B’, the second leg from Station ‘B’ to Station ‘C’, the third leg from Station ‘C’ to Station ‘D’ and the fourth leg from Station ‘D’ to Station ‘E’. The system then associates the discrepancies that were reported on the first, second, third to the fourth leg.

The system re-computes the Last Performed Value of the work units by adding the recorded journey log parameter or flying hours, whichever applicable, along with the history details, if those work units of the 'Aircraft Maintenance Program' or 'Component Maintenance Program' have been complied with, provided the last leg's date and time of the journey log is earlier than the last compliance date and time of the work unit. If the work unit is repetitive, the 'Next Schedule Value' is also recomputed based on the updated last performed value.

For example, if there is a work unit with a floating interval of flying hours, which has a periodicity of 50 hours, and the compliance date of the work unit is on 15th Dec 2004, the last complied value is 110 and the Next Schedule Value is 160. When a back-dated journey log is created on 14th Dec 2004 with a flying hours update of 5 hours, the ‘Last Performed Value’ will be recomputed as 115 and the ‘Next Schedule Value’ will be updated as 165.

If the aircraft has any discrepancies (Maintenance Reports) in "Deferred" status with usage based limits set, when a back-dated journey log is approved before the deferral date and time of that discrepancy, the system re-computes the threshold value for the discrepancy deferral by adding the updated parameter values to it.

The system performs the following on clicking the “Approve Log” pushbutton.

• Ensures that Journey Log is not available in “Fresh” status for the Aircraft Reg # in header level, If the “Enforce Sequential Reporting of Journey Log” is set as "Allowed" in the “Set options” activity of the current business component.  

• Ensures that the positive numeric values are entered in the “Parameter Value” column for each row of the Summary Parameter Details multiline, if the “Parameter Type” is “Range” or “Consumption”.

• Creates a Journey Log with the Hobbs-In value less that or equal to re-initialized value, If the “FH Log Mode” is set as "Hobbs Meter Reading" for the Aircraft Reg # as defined in the “Aircraft” business component, and if there is a manual new mode re-initialized entry for the Parameter which is mapped to “Hobbs Meter Reading” base parameter, later to the Arrival Date and Arrival Time of the Latest Journey Log # in “Confirmed” status  for the Aircraft Reg #. E.g. If there is a Journey Log with Hobbs-Out as 100 and Hobbs-In as 120 in “Confirmed” status with Arrival Date as 15/11/2006 and Arrival Time 10:00 hrs and if user updates the Parameter mapped to Hobbs Meter Reading base parameter with a value 110 with As On Date as 15/11/2006 and As On Time as 11:00 hrs, then a Journey Log is created with Hobbs-Out/In value greater than or equal to 110.

• Ensures that the journey leg timings do not overlap with each other within the same journey log as well as across the journey logs, for the same aircraft registration number, only if “FH Log Mode” is set as “Actual Flight Times" for the Aircraft Reg # as defined in the “Aircraft” business component..

If the "FH Log Mode" is set as "Actual Flight Times" for the Aircraft Reg #, then the system calculates the following for each row in the Leg Details multiline with reference to UTC:

a) Arrival Time = Departure Time + Flight Hours. If the value of “Arrival Time” is greater than 24:00 hrs, then the “Landing Time” as difference of Departure Time and Flight Hours.                                                                                                    

b) Arrival Date = Departure Date + Flight Hours. If the “Arrival Time” is later than the “Departure Time” and less than 24:00 hrs, then the “Arrival Date” is the same as “Departure Date”. If the “Arrival Time” is earlier than the “Departure Time”, then the “Arrival Date” is one day later than the “Departure Date”.

c) if the “Flight Hours” is more than 24 hours, then the “Arrival Date” is the addition or subtraction of quotient  of the Flight Hours by 24 to the “Departure Date”.  For ex: If Departure Date is 15/11/2006, FH = 23:00 hrs, then Landing Time = Arrival Time.

Note: The parameters must be mapped to the “Hobbs Meter Reading” base parameter as defined in the “Aircraft” business component, If the “FH Log Mode” is set as "Hobbs Meter Reading" for the Aircraft Reg #.

Note: If the “FH Log Mode” is set as “Hobbs Meter Reading” for the Aircraft Reg #, then ensure that the “Hobbs-In” field is not blank for each row in the Leg Details multiline.

Note: If the “FH Log Mode” is set as "Actual Flight Hours" and the “Enforce Sequential Reporting of Journey Log” is set as "Allowed" in the current business component, then ensure that the “Departure Date” and “Departure Time” of each record is not earlier than the “Arrival Date” and “Arrival Time” of the last leg of the latest preceding journey log for the Aircraft Reg #.  

Note: The system consolidates the Flight Hours calculated for each of the preceding leg # (including the current leg record) till the preceding leg for which “Maint. Execution” is set as "Yes" if the “Maint. Execution” is set as “Yes”, consolidates the Flight Hours recorded for the preceding legs # (including the last leg) till the preceding leg for which “Maint. Execution” is set as “Yes” if the “Maint. Execution” is set as “No”, and consolidates and updates the FH for all the legs with the last leg reference in the “Aircraft Parameter Master” business component if none of the leg is identified with “Main. Execution” as  “Yes”.

 Note: If the “Flight Details Validation Basis” option is set as "Not Required" in the “Set Options” activity of the current business component, and if the “FH Log Mode” is set as "Actual Flight Times" for the Aircraft Reg # as defined in the “Aircraft” business component, then the system ensures one preceding record is entered in the “Flight Hours” column for each row in the Leg Details multiline.

 Note: "If the “Flight Details Validation Basis” option is set as "Not Required" in the “Set Options” activity of the current business component, if the “FH Log Mode” is set as "Actual Flight Times" for the Aircraft Reg # as defined in the “Aircraft” business component and for each row of the Leg Details multiline if the departure date and departure time are entered, the system calculates the Arrival Time and Arrival Date as given below:

1. Arrival Time = Departure Time + Flight Hours. If the value for Arrival time is greater than 24:00 hrs, then the Arrival time is 02.00 hrs for the Departure Time = 23:00 hrs and FH = 3:00.

2. Arrival Date = Departure Date +Flight Hours. If Arrival Time is later than the Departure Time and less than 24:00 hrs, then the Arrival Date is the same as Departure Date.

3. If Arrival Time is earlier than the Take-Off Time, then the Arrival Date is one day later than the Departure Date.

 Note: "If the “Flight Details Validation Basis” option is set as "Not Required" in the “Set Options” activity of the current business component, if the “FH Log Mode” is set as "Actual Flight Times" for the Aircraft Reg # as defined in the “Aircraft” business component and for each row of the Leg Details multiline if the arrival time and arrival date are entered, the system calculates the Arrival Time and Arrival Date as given below:

1. Departure Time = Arrival Time - Flight Hours. For E.g. If the value for Arrival Time is negative, the Arrival Time = 06:00 hrs, FH = 8:00, then the Departure Time = (06:00-08:00)+24 = 22:00 hrs.

2. Departure Date = Departure Date - Flight Hours. If Arrival Time is later than the Departure Time and less than 24:00 hrs, then the Departure Date is the same as Arrival Date

3. If Arrival Time is earlier than the Departure Time, then the Departure Date is one day earlier  than the Departure Date.

Note: If the “Flight Details Validation Basis” option is set as "Not Required" in the “Set Options” activity of the current business component, if the “FH Log Mode” is set as "Actual Flight Times" for the Aircraft Reg # as defined in the “Aircraft” business component and for each row of the Leg Details multiline If no value is entered in the Departure Date, Departure Time, Arrival Date and Arrival Time, then the system copies the Arrival Date and Arrival Time of the preceding leg as the Departure Date and Departure Time for current record.

Note: The system considers the arrival date of the aircraft of the preceding leg as the departure date for the next leg, if the status of the previous flight is other than “Cancelled” or “Substituted”.

The system performs the following on clicking the “Approve Log” pushbutton:

• If the flight status is set as “On Schedule”, then the system ensures that: (a) The difference between the Schedule Departure Time and the Actual Departure Time, and (b)The  difference between the Schedule Arrival Time and the Actual Arrival Time, is less than the set limit for Delay Duration.

• If the flight status reported for the journey log is “Delayed”, then the system ensures that: (a) The difference between the Schedule Departure Time and the Actual Departure Time, and (b) The difference between the Schedule Arrival Time and the Actual Arrival Time, is greater than the set limit for Delay Duration.

Note: The system considers the “Reportable Delay (In Minutes)” as the Delay Duration, if defined in the “Reliability Analysis” business component. Otherwise, the system considers the “Delay Duration (In Minutes)” defined in the “Aircraft Reliability” business component as the Delay Duration.

To cancel a journey log

• Click the ‘Cancel Log” pushbutton to cancel a journey log.

The system sets the record status of the journey log to “Cancel”. All information related to a cancelled journey log will no longer be used in processing. The record status of the discrepancies reported on the cancelled journey log is set as “Cancelled”.

Automatic Approval based on Workflow configuration

• The journey log is automatically routed to the next level of approval, if CIM interaction exists between Workflow Management and Flight Log.

• Only those journey logs for which the login user has approval permission will be retrieved by the search, if CIM interaction exists between Workflow Management and Flight Log.

• For the above to occur, the login user must have the requisite permission to approve the journey log or must be a first-level approver for the journey log. If the login user is a first-level approver, the journey log moves to the second–level of approval and the status changes to “Pending Approval”. If the next level of approval is the last in the approval workflow, the status becomes Approved on approval.

• The approval workflow gets terminated on cancellation of journey log.

To proceed, carry out the following

• Click the “Report Delay/Operation Interruption Details” link to update delay details.

• Click the “Record Pilot Reported Discrepancies” to update pilot reported discrepancies.

• Click the “Report Cabin Crew Details” link to report the cabin crew details.

• Click the “Report Inflight Shut Down Hours” link to enter the inflight shutdown details of the engine.

• Select the “Record Aircraft Maintenance Execution Details” link to record the aircraft maintenance execution details for an aircraft.

Note: The “Record Aircraft Maintenance Execution Details” link is not displayed for Offline Usage. (i.e. ‘Usage Mode’ set as “Offline” in the “Configurator” business component.)

The system displays the following in the “Record Statistics” group box

Editing journey log information – An overview

In this page, you can modify the details of the journey log such as the date scheduled for the flight, the station from where the journey starts, duration of the flight and parameter value. The system updates the modified values and sets the status of the journey log as “Fresh”.