Amending journey log details

This page allows you to amend the journey log details. Tell me more

Select the “Amend Journey Log” link in the “Select Journey Log For Amendment” page.

The “Amend Journey Log” page appears.

The system displays the following field:

Date & Time Format

The format in which the date fields are to be entered. 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 “Log Details” group box:

Journey Log #	The journey log number for which the details are to be amended.
Status	The status of the journey log, which could be "Under Amendment" or "Approved".
Flight Date	The date on which the flight is scheduled.
Reporting Time Zone	The time zone where the journey log is reported.

Enter the following:

Starting Station

The station from where the journey starts (Alphanumeric, 30).Mandatory.

Help facility available.

Ensure that the value entered here is a valid station in “Active” status as defined in the “Common Masters” business component, if the “Flight Details Validation Basis” is set as "Required" in the Set Options activity of the current business component.

Journey Log Category

Use the drop-down list box to select the category to which the journey log belongs. The system lists all the values defined for the quick code type “Journey Log Category” in the “Create Quick Code” activity.

The system displays the following:

Amendment#	The amendment number of the journey log.
Flight Status	The status of the flight, which could be ”On Schedule”, ”Delayed”, “Cancelled”, “Substituted”, “Air Turned Back”, “Ground Turned Back” “Diverted” or “Deleted”.

Enter the following fields:

Flight Ops. Type

Use the drop-down list box to modify the flight operation type. The system lists the following options:

“Regular” - Select this option if the flight is used for regular flight operations.
“Test Flight” – Select this option if the flight is used for test flight operations.
“Training”- Select this option, if the flight is used for training flight operations.
“Ferry”-Select this option, if the flight is used for ferrying flight operations.
“Positioning”- Select this option, if the flight is used for positioning flight operations.
“Others”- Select this option, if the flight is used for operations, other than the above flight operation types.

By default, the system sets the field to “Regular”.

Flight Category

Use the drop-down list to select the flight category. The system lists all values defined for the Flight Log/Occ.Rep Attribute Type “Flight category” in the “Create Flight Log / Occ.Rep Attributes” activity of the “Common Masters” business component.

By default, the system leaves the field blank.

Log #

The log number reference in the journey log. This number refers to the page number in the journey log. (Alphanumeric, 20).

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

Aircraft Reg#	The registration number of the aircraft.
Aircraft Model#	The model number of the aircraft.
Manufacturer Serial#	The manufacturer’s serial number given to the aircraft by the manufacturer at the time of production.
Configuration Class	The configuration class associated to the aircraft registration number.
Total Flight Hours	The total number hours spent on the journey.
Total Flying Cycles	The total number of flying cycles during the journey.
Last Journey Log #	A unique number generated by the system, to identify last journey log.
Last Journey Log Status	The status of last journey log of aircraft.
FH Log Mode	The mode of flight hours showing “Actual Flight Times” or “Hobbs Meter Reading”.
Hobbs Meter Reading	The Hobbs meter reading that shows for the aircraft.
Hobbs Re-set?	The reset of Hobs Meter Reading is identified using the option “Yes” or “No”.

To proceed, carry out the following:

Select the “Leg Details” tab to enter the details of the legs associated to the journey log.
Select the “Summary Parameter Details” tab to enter the details of the parameters mapped to the journey log.

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

Engine Bleed?

Use the drop-down list box to denote whether the engine bleed was “ON” or “OFF”, while recording the parameter value. Engine bleed is an air pressure tapping taken usually from the high-pressure compressor stage of a jet engine. It is utilized for various purposes including air-conditioning and engine compressor stability. The system lists the following options:

Yes – Select this option to indicate that the parameter value was recorded when the engine bleed was ”ON”.
No – Select this option to indicate that the parameter value was recorded when the engine bleed was ”OFF”.

The system leaves the field blank by default.

Pilot Special Report

Any observations reported by the pilot (Alphanumeric, 2000).

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

Flight Hours	The number of hours spent on the journey.
Block Hours	The difference between the departure time and the arrival time of the flight.
Flight Cycles	The number of times the flight takes off and lands, considering each take off and landing as one cycle.
Landing Cycles	The number of times the flight takes off and lands, considering each take off and landing as one cycle. This count will also include the touch-and-go landings.
Engine Hrs / Cycles	The number of times the engine was shut down and restarted, considering each shut down to each restart as one cycle.
Parameter 1	The first parameter of the leg.
Parameter 2	The second parameter of the leg.
Parameter 3	The third parameter of the leg.
Parameter 4	The fourth parameter of the leg.
Parameter 5	The fifth parameter of the leg.
Parameter 6	The sixth parameter of the leg.

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.

If 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, 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 not ‘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 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 ‘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 “Leg/Summary 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:

File Name

The name of the file attached to the journey log for reference (Alphanumeric, 50).

Help facility available.

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

Remarks

Any remarks pertaining to the file. (Alphanumeric,255).

To amend journey log

Click the “Amend Journey Log” pushbutton to amend journey log details.

Note: The system verifies that no other journey log is entered for the same period of time for the aircraft registration number.

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

The system performs the following while amending the journey log:

Does not allows you to modify any of the leg details in the multine, if the flight status is set to “Deleted”.
Updates the parameters to the position codes.
Sets the status of the journey log to “Under Amendment”.
Allows Journey Log Amendment in Main Base for Online / Offline aircraft.

Note: The system does not allow the following:

Amendment of Journey Logs in “Under Amendment” status with 'Source' as "Offline", from Main Base.
Amendment of Journey Logs with ‘Source’ as “Online”, from Offline Base.
Amendment of Journey Logs in “Approved” status with ‘Source’ as “Offline”, from Offline Base, if the data has been transferred to Main Base.

On amendment of Journey Log, the system updates the 'Source' as "Online" / "Offline" based on the value set in 'Usage Mode' parameter in the “Configurator” business component.
Increments the amendment number of the journey log by one. For example if the amendment number of the journey log is ‘000’, then it is incremented to ‘001’.

A journey log in the “Under Amendment” status can be edited any number of times before clicking the “Approve Amendment” pushbutton. In such a situation, the system will not update the amendment number on click of the “Amend Journey Log” pushbutton.

When an already-recorded summary leg 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: 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 "Flight Assignment" in the Set Options activity of the current business component.

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 preceding leg as the Departure Date and Departure Time for current record.

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”.

Note: The system does not calculate the “Delay on Departure” and “Delay on Arrival” values, if the “Flight Status” of the selected row is set as “Air Turned Back”, “Ground Turned Back”, “Diverted”, “Cancelled” or “Deleted”

The system performs the following on clicking the “Amend Journey 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/or (b)The difference between the Schedule Arrival Time and the Actual Arrival Time, is less than the 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/or (b) The difference between the Schedule Arrival Time and the Actual Arrival Time, is greater than the 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.

Computation of NSD / NSV based on ‘Change Type’:

If the ‘Change Type’ is set as “Correction”, on modification of interval or correction of complied value from ‘Compliance History’ or modification of journey Log, NSV is recomputed based on:

- Threshold value or Repeat Interval if task is not complied at least once.
- ‘Update Basis’ (Time Window, Schedule or Actual Completion) set in the last instance of compliance.

If the ‘Change Type’ is set as “Correction”, on modification of interval or correction of Complied Date and Time from ‘Compliance History’, NSD is recomputed based on:

- "Reference Basis" (Induction or Operational date) if task is not complied at least once.
- ‘Update Basis’ (Time Window, Schedule or Actual Completion) set in the last instance of compliance.

If the ‘Change Type’ is set as “Re-baseline”, on modification of interval:
- On re-baseline of LPD / LPV, NSD / NSV, on change of Journey log, NSD / NSV must not be recomputed.

Note: If any open escalation exists for tasks in aircraft program, on modification of Journey Log, the system recomputes the Next Due Value, and the new due value is updated in escalation records.

Update of computation basis controls - Post Compliance

To approve journey log

Click the “Approve Amendment” pushbutton to approve amended 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 carries out the following:

Sets the status of the previously approved journey log to “Amended”. For example if the amendment number of the journey log is ‘001’ and it’s previous value was ‘000’, then the status of the journey log with amendment number as ‘000’ is set as “Amended”.
Sets the status of the journey log with it’s current amendment number to “Approved”.
Updates the flight details, interruption details and delay summary details recorded in the “Report Operational Interruption Details” page to the “Regularize Operational Interruption Details” page.

The system re-computes the Last Performed Value of the work units by the amended values of 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. If a journey log that was already created on 14th Dec 2004, is amended by increasing one flight hour, then the ‘Last Performed Value’ will be recomputed as 111and the ‘Next Schedule Value’ will be recomputed as 161.

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

The system performs the following on clicking the “Approve Amendment” 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.

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:

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 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:

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 preceding leg as the Departure Date and Departure Time for current record.

Note: For all the rows in the “Leg Details” multiline for which “Flight Status” is “Deleted”, no further amendments are possible once “Approve Amendment” is done.

If the “Flight Status” of a journey log is modified to 'Deleted”, the system back updates all the parameter values such as “Aircraft Reg #”, “Component #”, “Part #”, and “Position #” against the deleted leg irrespective of the “FH Log Mode” set in the “Aircraft” business component, using the following steps:

Deletes the existing history of the parameter value
Recomputes and updates the values for the specific parameters, for all the maintenance objects.

Example: A “Journey Log" with 5 FH and 1FC is “Deleted”, for which the current parameter values are 1450FH and 620FC. The system recomputes the parameter values as follows: 1445FH (1450FH - 5FH) and 619FC (620FC - 1FC).

Note: The system modifies the Hobbs Meter parameter value (mapped for Hobbs Meter) that is identified as “Inherited Parameter” as defined in the “Set Base Parameter” activity of the “Aircraft” business component. This update will happen based on the following logic: The system identifies the “Hobbs-Out” value for the journey log with latest Leg # having flight status other than “Cancelled” or “Deleted”, and updates the “Hobbs Out” as the “Hobs Meter” parameter value in the Aircraft PV update history.

The system performs the following on clicking the “Approve Amendment” 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/or (b)The difference between the Schedule Arrival Time and the Actual Arrival Time, is less than the 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/or (b) The difference between the Schedule Arrival Time and the Actual Arrival Time, is greater than the Delay Duration.

If the Flight Status for the last leg of any of the journey log is set as “Deleted”, then the system considers the Hobbs-In value of the immediate preceding leg whose flight status is other than “Deleted” or “Cancelled”, as the latest Hobbs meter reading for the parameter that is mapped to the Aircraft Reg #. This is applicable only if the parameter is classified as “Hobbs Meter Reading” in the “Aircraft” business component.

In the above mentioned examples, the latest Hobbs Meter Reading in the first example is 1030 as the flight status for all the legs is On-Schedule. Where as in the second example the Hobbs meter reading is 1025 as the flight status for the third leg i.e. Leg # 3 is set as “Deleted”. In the second case the system considers the Hobbs-In value of the preceding leg as the latest Hobbs Meter reading.

On approval of amendment 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. If the value identified as Date for Flight Day update (Flight Date / Departure Date / Takeoff Date / Arrival Date) in the Set Options activity of the current business component, has been modified in the Journey log /leg, then

a. The system checks whether Flight Day parameter has been already updated for the modified date. If no, then updates the value as 1 for the modified date. Else, the system does not update any value.

b. The system checks whether any eligible (with Flight Status and Flight Operations Type included in Set Options) journey log is available in approved status for the Date identified before the amendment.

i. If available, then updates the next eligible Journey log / leg as the reference document for Flight Day update. Do not decrement the Flight Day value for the date.

ii. If there are no other Journey Logs available in Approved status for the Date identified for Flight Days Update in Set Options activity of the current business component, then the Parameter Flight days will be decremented by 1 for that date for the Aircraft and the document reference will be deleted from the Parameter value details in the interactive Configuration business component.

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

S.No	Parameter	Value set
1	Date for Flight Date Update	Departure Date
2	Flight Status – On Schedule	Include
3.	Flight Ops. Type – Regular	Include

For amending a journey log, let there be a new journey log JL1 created for Aircraft Reg #: A1. The Journey log – leg details be as follows:

Before Amendment:

Leg#	Departure Date	Arrival Date	Flight Operations Type	Flight Status
1	01/01/2009	02/01/2009	Regular	On Schedule

Flight Day parameter got updated for the Journey Log – Leg # for the date 01/01/2009.

After Amendment:

Leg#	Departure Date	Arrival Date	Flight Operations Type	Flight Status
1	02/01/2009	03/01/2009	Regular	On Schedule

Departure Date has been modified as 02/02/2009.

Following updates will be executed on approval of the amendment:

1. Based on the above given options settings, If there are no Journey logs available in Approved status for the Departure Date 01/01/2009, with Flight Status and Flight operations type included for Flight Day update from option settings, then system deducts the Flight Day by ‘1’ for the date 01/01/2009.

2. If there is a Journey Log – leg (Ex: JL2-Leg1) in approved status for the Departure Date 01/01/2009, with Flight Status and Flight operations type included for Flight Day update from option settings, then system retains the Flight Day for the date 01/01/2009.

3. If there is no update for Flight Day parameter for the Date 02/01/2009, system updates the values as “1” for 02/01/2009 and reference document as JL1 – Leg1.

4. If there exists an entry for Flight Day parameter for the Date 02/01/2009, no update will happened due to the amended Journey log JL1-Leg1.

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. Eligibility of Journey log means, if the Flight Operations Type and Flight Status selected for the Journey Log - leg is identified as "Include" in the Journey Log recording options of the current business component.

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 “Record Operational Interruption Details” link to update interruption and/or delay information of the flight recorded for the journey log.
Click the “Record Pilot Reported Discrepancies” link to update pilot reported discrepancies.
Click the “View Pilot Reported Discrepancy” link to view pilot reported discrepancies.
Click the “Report Cabin Crew Details” link to enter the cabin crew details.
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.)

Select the “Report In-Flight Shut Down Hours” link to update engine parameters subsequent to engine failure during flight for journey logs in “Under Amendment” status.

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

Created by	The login ID of the user, who created the journey log.
Created Date	The date on which the journey log was created.
Last Modified by	The name of the user who last modified the journey log.
Last Modified Date	The date on which the journey log was last modified.
Approved by	The name of the user who approved the journey log.
Approved Date	The date on which the journey log was approved.

Enter the following:

Amendment Remarks

Any remarks pertaining to the amendment of the journey log (Alphanumeric, 255).

Amending journey log details – An overview

In this page, you can modify the journey log details that are in the “Confirmed” status. Details such as station where the journey starts, journey log category and flight category can be amended. Parameter values for the leg of the journey and the parameter value for the part in the position code can be modified. Details such as the documents attached to the journey log and remarks about the amendment of the journey log can be mentioned.