Report Flight Information

Explanation

This activity is used to report information about a flight such as the take off and landing times, deviations and utilization (operational loggings) once the flight is completed. This information is usually entered by a pilot on a flight log that is defined for the vehicle. The flight log can contain information on one or more flights, where a single record is defined for each flight on the vehicle. For more information on how to report a flight log, refer the Report Flight Log activity.

On the flight log an operational plan ID must be entered to define which flight the vehicle has completed. This value can be entered manually or by using the operational plans predefined in IFS/Vehicle Information Management. If the field is left blank when saving, the system will automatically generate an operational plan ID which serves as an identifier for the flight. If an operator designator is defined in basic data, this value will be used when auto-generating the operational plan ID.

If predefined operational plans are used, the OPER_LOG_SEV_EVENTS object property will be used to validate if the same operational event can be entered several times for one operational plan ID (flight). The following settings are available for this object property:

• No Requirements - The same operational event can be entered several times for an operational plan ID as long as the dates do not overlap.
• Warning - The same operational event can be entered several times for an operational plan ID as long as the dates do not overlap. A warning will be displayed.
• Not Allowed - The same operational event cannot be entered several times for the same operational plan ID. An error message will be displayed.

Prerequisites

• The flight log for the vehicle must exist in the Open status.
• If an existing operational plan is to be connected to the flight, the operational plan must have been defined for the serial defined on the flight log.
• If the operational plan ID is to be generated automatically prefix with an operator designator, the operator designator must have been predefined in basic data.
• If deviations or delays are to be reported, the deviation reason must have been defined in basic data.
• If a flight is to be cancelled, a valid cancellation cause must have been defined in basic data.

System Effects

As a result of this activity, information pertaining to the flights operated within a day will be reported in the flight log. Operational loggings (utilization) can be reported on the flight.

Window

Flight Log

Related Window Descriptions

Flight Log
Flight Log/Flight Info
Flight Log/Flight Info/General
Flight Log/Flight Info/Operational Disruptions

Procedure

• Entering general information for a flight
• Entering any operational disruptions that occurred during the flight

Use this procedure to enter general information on a flight:

1. Open the Flight Log window and query (F3) for your flight log number and/or vehicle ID.
2. Click the Flight Info tab and then click the General tab.
3. Create a new record (F5).
4. In the Operational Plan ID field, enter the operational plan ID for the operational event completed by the vehicle. Entering a value in this field is required and cannot be updated. There are several ways in which this value can be defined:

• Use the List of Values to select an operational plan ID having a valid operational event which is connected to the serial defined on the flight log.
• Manually enter an operational plan ID (e.g., flight number).
• The operational plan ID will be generated automatically for the flight when you leave this field blank and save the record. Note that if an operator designator has been predefined in basic data, the operator designator will be used to define the auto-generated value.

5. If a new operational plan ID is entered manually or auto-generated, you need to manually enter a description of the operational plan in the Oper. Plan Desc. field. If entered manually, the value can be changed as long as the flight log is open.
6. In the Oper. Event Desc. field, enter a valid operational event for the selected operational plan ID, if the required value is not already defaulted in this field. Use the List of Values to select a valid value. Once saved this value cannot be changed. If an operational plan ID is to be generated automatically, it is possible to select a valid ad hoc event from the List of Values. If an operational plan ID is entered manually that is not predefined in the application, a value cannot be entered in this field.
7. In the Departure Location field, enter the departure location of the flight. If a valid operational plan ID is connected, the departure location on the operational plan is displayed in this field. If a valid operational plan ID is not connected, the current location of the vehicle will be displayed in this field. Use the List of Values to change to a different location, if needed.
8. In the Arrival Location field, enter the arrival location of the flight. If a valid operational plan ID is connected, the arrival location on the operational plan is displayed in this field. If a valid operational plan ID is not connected, the arrival location must be entered manually. Use the List of Values to select or change the arrival location.
9. In the Block Off field, enter the time and date the vehicle was released from the blocks. A block referred to here is the block that is placed under the wheels of a vehicle to keep it from rolling. Entering a value in this field is optional. The value can be changed as long as the flight log is open. Observe the following behavior/rules:

• If a valid operational plan ID and operational event are connected to the flight, the planned start date of the operational event will be defaulted in this field.
• If only an operational plan ID has been connected, the start date of the operational plan will be defaulted in this field.
• If a valid operational plan ID is not connected, the block off date and time must be entered manually.
• The date and time you enter in this field cannot be any date/time prior to the flight log date.
• The date and time you enter in this field cannot be prior to the date/time entered on the previously closed flights for the same vehicle.

10. In the Take Off field, enter the time and date the vehicle is to take off. The flight log date will be defaulted in this field and will need to be changed to the correct time. The time and date you enter in this field cannot be prior to the flight log date, and must be later than the block off time (if entered). Furthermore, the take off date/time cannot be prior to the date/time entered on the previously closed flight log for the same vehicle. The value in this field can be changed as long as the flight log is open.
11. In the Touchdown field, enter the time and date of the vehicle's touchdown. The flight log date will be defaulted in this field and will need to be changed to the correct time. The time and date you enter in this field cannot be prior to the flight log date, and must be later than the take off time and before the block on time (if entered). Furthermore, the touchdown date/time cannot be prior to the date/time entered on the previously closed flight log for the same vehicle. Entering a value in this field is required. This value can be changed as long as the flight log is open.
12. In the Block On field, enter the time and date the blocks were put back on the vehicle (e.g., placed under a aircraft's wheel after the flight). Entering a value in this field is optional. The value can be changed as long as the flight log is open. Observe the following behavior/rules:

• If a valid operational plan ID and operational event are connected to the flight, the planned finish date of the operational event will be defaulted in this field.
• If only an operational plan ID has been connected, the end date of the operational plan will be defaulted in this field.
• If a valid operational plan ID is not connected, the block on date and time must be entered manually.
• The date and time you enter in this field cannot be any date/time prior to the flight log date.
• The date and time you enter in this field must be later than the touchdown time.
• The date and time you enter in this field cannot be prior to the date/time entered on the previously closed flights for the same vehicle.

12. In the Remark field, you can enter additional information on the flight. If an operational event is connected to the flight, any remark entered on the operational event will be defaulted in this field. If not, you need to enter the information manually. Entering a value in this field is optional and can be changed, if needed.
13. Save the information (F12).
14. In the table you can view and report the actual usage of the serial. For more information, refer the activity Report Operational Logging.

Use this procedure to report any operational disruptions on the flight:

1. Open the Flight Log window and query (F3) for your flight log number and/or vehicle ID.
2. Click the Flight Info tab and then click the Operational Disruptions tab.
3. Verify that the correct operational plan ID is selected in the Operational Plan ID field. If not select from one of the defined values.
4. If a deviation of the route occurred, enter the reason for this deviation in the Deviation Reason field. Use the List of Values to select a valid value.
5. If a delay occurred, enter the reason for the delay in the Delay Reason field. Use the List of Values to select a valid value.
6. In the Disruption Info field, enter any additional information on the deviation or delay.
7. If the flight was cancelled, enter a reason for the cancellation in the Cancel Cause field. Use the List of Values to select a valid value.
8. In the Cancellation Info field, enter any additional information on the flight cancellation.
9. Save the information (F12).