Reporting a Flight Log—Exercises

Main Exercise

Purpose: The purpose of this lesson is to learn how to enter data in a flight log for an aircraft. The main content of a flight log includes:

Report Flight Information on a Flight Log - Generated Operational Plan ID

Purpose: The purpose of this exercise is to learn how to report information for a flight log and flights in general. In this exercise, the operational plan ID (flight number) is generated automatically.

If you want to use predefined operational plans to define the operational plan ID (flight number), perform the steps described in the Report Flight Information on a Flight Log - Using predefined Operational Plans exercise.

Prerequisites: Before starting on this exercise, you must have completed the exercises in Flight Log Reporting - Basic Data and Requirements Exercises. In addition, you must have completed the Create Serial Structure - 3 exercise and the Set a Structure In Operation exercise. The serial you created in Create Serial Structure - 3 must have the owner organization FANTASY AIRLINES. The owner organization for the serial can be set up in the Part Serial window, if not already done.

Windows:
Flight Log
Flight Log /Flight Info /General

  1. Open the Flight Log window and create a new record (F5).
  2. In the Part Number field, enter the nX747-900 part number and the * Part Rev of your vehicle. You can also use the List of Values to select the value.
  3. In the Serial Number field, enter the nX30000 serial of your vehicle. You can use the List of Values to select the correct serial number.
  4. In the Flight Log Number field, enter 50.
  5. In the Flight Log Date field, keep the suggested date which is the system date.
  6. Save the information (F12).
  7. Click the Flight Info tab and then click the General sub tab.
  8. Create a new record (F5).
  9. Leave the Operational Plan ID field empty. The operational plan ID will then be generated automatically for the flight when you save the record. Since you have defined and operator designator for the owner organization of the vehicle (in basic data), the operator designator will be used to define the auto-generated value.
  10. In the Oper. Plan Desc. field, enter a description of the operational plan, for example, Oslo - New York.
  11. In the Departure Location field, enter OSL. If needed, you can use the List of Values to find the departure location.
  12. In the Arrival Location field, enter JFK as the arrival location of the flight. Use the List of Values to find the arrival location.
  13. In the Block Off field, enter the time and date the vehicle was released from the blocks. A block as referred to here is the block that is placed under the wheels of a vehicle to keep it from rolling. The date and time you enter in this field cannot be any date/time prior to the flight log date.
  14. In the Take Off field, enter the time and date the vehicle is to take off. 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 and before the block on time.
  15. In the Touchdown field, enter the time and date of the vehicle's touchdown. 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.
  16. In the Block On field, enter the time and date the blocks were put back on the vehicle (placed under an aircraft's wheel after the flight). The date and time you enter in this field cannot be any date/time prior to the flight log date and it must be later than the touchdown time.
  17. In the Remark field, you can enter additional information about the flight.
  18. Save the information (F12).
  19. Create several operational plans (flights) by repeating the steps 8 to 18.

Define Deviation and Delay Reasons

Purpose: When entering information about a vehicle in a flight log, it can be that the vehicle has arrived at a different location than planned or is delayed and arrives later than planned. The purpose of this exercise is to learn how to report such operational disruptions for a flight on a flight log.

Prerequisites: Before starting on this exercise you must have completed the above exercise.

Windows:
Flight Log /Flight Info /Operational Disruptions

  1. Open the Flight Log window and query (F3) for the flight log number 50, part number nX747-900 and serial number nX30000.
  2. Click the Operational Disruptions tab.
  3. Select an operational plan (flight) in the Operational Plan ID field.
  4. In the Delay Reason field, enter TRAFFIC. You can use the List of Values to find the value.
  5. In the Disruption Info field, enter additional information on the delay.
  6. Save the information (F12).

Report Operational Logging

Purpose: The purpose of this exercise is to learn how to report operational loggings (utilization) for a flight on a flight log.

Prerequisites: Before starting on this exercise you must have completed the Report Flight Information on a Flight Log - Generated Operational Plan ID exercise.

Windows:
Flight Log /Flight Info /General

  1. Open the Flight Log window and query (F3) for the flight log number 50, part number nX747-900 and serial number nX30000.
  2. Click the Flight Info tab and then click the General sub tab.
  3. Select an operational plan (flight) in the Operational Plan ID field and click on the table in the tab.
  4. Enter the new Accumulated Value or an Add on Value. If this is an operational parameter logging time, enter a value in the Time Difference field instead.
  5. If there are no changes to an operational parameter value, you do not need to enter any value for the parameter.
  6. Save the information (F12).
  7. The operational loggings you have just entered for the flight will be added and spread to the vehicle and its structure when the flight log is closed.

Report Crew Information

Purpose: The purpose of this exercise is to learn how to report information about the crew that worked the flights recorded on a flight log.

Prerequisites: Before starting on this exercise you must have completed the Report Flight Information on a Flight Log - Generated Operational Plan ID exercise. In addition, you must have completed the exercises in Flight Log Reporting - Basic Data and Requirements Exercises.

Windows:
Flight Log /Crew
Flight Log /Crew /Operational Tasks
Flight Log /Crew /Crew Time Specification

  1. Open the Flight Log window and query (F3) for the flight log number 50, part number nX747-900 and serial number nX30000.
  2. Click the Crew tab and select an operational plan (flight) in the Operational Plan ID field.
  3. Create a new record (F5) in the table (Crew Members).
  4. In the Person ID field, enter 101004 (Keith Franklin). Use the List of Value to find the value.
  5. In the Person Category field, enter PILOT. Use the List of Values to find the value.
  6. In the Training Level field, enter PILOT.
  7. In the Remark field, enter any applicable information for the crew member.
  8. Save the information (F12).
  9. Select the crew member you just recorded and then click the Operational Tasks sub tab.
  10. Create a new record (F5).
  11. In the Operational Task Type field, select the value 01 (Unspecified Flying) by using the List of Values.
  12. In the Elapsed Time field, enter the time the pilot spent on the operational task.
  13. If the default Time Unit is incorrect, use the List of Values to change to a valid time unit.
  14. Save the information (F12).
  15. Click the Crew Time Specification sub tab and create a new record (F5).
  16. In the Crew Time Type field, enter INSTRUMENT. You can use the List of Values to find the value.
  17. In the Elapsed Time field, enter how much of the total time the pilot spent on flying by instruments.
  18. If the default Time Unit is incorrect, use the List of Values to change to a valid time unit.
  19. Create another record (F5) and enter the value Manual in the Crew Time Type field.
  20. In the Elapsed Time field, enter how much of the total time the pilot spent on flying the aircraft manually.
  21. Enter the correct time unit in the Time Unit field and save the two record (F12).

Report Fault Information

Purpose: The purpose of this exercise is to learn how to report faults found during the flight or as a part of line maintenance activities. In addition, you will learn how to report actions performed against faults without having to plan the activities beforehand. This is used to record actions taken to close off the fault without creating a work order of any kind.

Prerequisites: Before starting on this exercise you must have completed the Report Flight Information on a Flight Log - Generated Operational Plan ID exercise.

Windows:
Flight Log /Fault

  1. Open the Flight Log window and query (F3) for the flight log number 50, part number nX747-900 and serial number nX30000.
  2. Click the Fault tab and create a new record (F5).
  3. In the Fault Description field, enter a short description of the fault.
  4. In the Functional Number field, enter 3224 (Tyre) by using the List of Values.
  5. In the Fault Code, field enter DAM by using the List of Values.
  6. In the Flight Oper Plan ID field, enter the operational plan (flight) on which the fault was reported. Use the List of Values to select a valid value.
  7. Use the List of Values to fine the value MECHENG (Mechanical Engineer) in the Person Category field.
  8. Save the information (F12).
  9. Click on the table in the tab and create a new record (F5).
  10. In the Action Taken field, enter a description of the action taken for the vehicle to fly without the fault being signed off.
  11. In the Action Date field, enter the date and time the action was taken. The system date is displayed automatically but can be changed. Note that the action date must be higher than the fault date.
  12. Enter the value 101001 (Igor Stravinsky) to identify the technician that performed the action.
  13. Select the Fault Cleared check box to indicate that necessary actions have been taken for the vehicle to fly without the fault being signed off.
  14. Save the information (F12).
  15. To enter more faults and fault actions on the flight log, repeat steps 2 to 14.

Report Condition Measurements

Purpose: The purpose of this exercise is to learn how to report measurement results from any monitoring activities related to daily operations in a flight log.

Prerequisites: Before starting on this exercise you must have completed the Report Flight Information on a Flight Log - Generated Operational Plan ID exercise.

Windows:
Flight Log /Condition Meas.

  1. Open the Flight Log window and query (F3) for the flight log number 50, part number nX747-900 and serial number nX30000.
  2. Click the Condition Meas. tab and select the record for part number X32WHE7002.
  3. In the Measure Value field, enter 12.
  4. Save the information (F12). You should get a message that a condition task has being generated.

Report Flight Servicing Activities

Purpose: The purpose of this exercise is to learn how to report activities performed prior to or after a flight. These kind of activities are called pre- and post-flight activities and need to be entered in the flight log.

Prerequisites: Before starting on this exercise you must have completed the Report Flight Information on a Flight Log - Generated Operational Plan ID exercise. In addition, you must have completed the exercises in Flight Log Reporting - Basic Data and Requirements Exercises.

Windows:
Flight Log /Flight Servicing

  1. Open the Flight Log window and query (F3) for the flight log number 50, part number nX747-900 and serial number nX30000.
  2. Click the Flight Servicing tab and create a new record (F5).
  3. If the flight servicing activity was performed against an operational plan (flight), enter the ID of the operational plan in the Operational Plan ID field. Use the List of Values to select a valid value. If you do not enter a value in this field, the servicing activity will be defined against the flight log in general.
  4. In the Flight Servicing Type field, enter DE-ICING. Use the List of Values to find the value.
  5. In the Remark field, enter a brief description of the flight servicing activity.
  6. In the Technician ID field, enter 101002 (Julie McPhersson) to identify the technician who performed the flight servicing activity.
  7. In the Flight Servicing Completed field, enter the date and time the flight servicing activity was completed.
  8. Save the information (F12).

Void Flight

Purpose: The purpose of this exercise is to learn how to void a flight which has been entered incorrectly on a flight log. It is not valid to delete a flight for documentation purposes so it has to be set to void instead.

Prerequisites: Before starting on this exercise you must have completed the Report Flight Information on a Flight Log - Generated Operational Plan ID exercise and entered more than one operational plan (flight).

Windows:
Flight Log /Flight Info /General
Flight Log /General

  1. Open the Flight Log window and query (F3) for the flight log number 50, part number nX747-900 and serial number nX30000.
  2. Click the Flight Info tab and then click the General sub tab.
  3. Select an operational plan (flight) in the Operational Plan ID field, right-click and then click Void Flight. The Void Flight dialog box opens.
  4. In the Voiding Information field, enter the reason for voiding the flight.
  5. Click OK.
  6. Click the General tab. Verify that the Voided check box is selected and the information you entered when voiding the flight is displayed in the Voiding Information field.
  7. When a flight has been voided, it is no longer considered to be a valid flight.

Report Flight Information on a Flight Log - Using Predefined Operational Plans

Purpose: The purpose of this exercise is to learn how to report information for a flight log and flights in general by using predefined operational plans.

Prerequisites: Before starting on this exercise you must have completed the exercises in Flight Log Reporting - Basic Data and Requirements Exercises. In addition, you must have completed the Operational Planning exercise in order to define the operational plan that will be used in this exercise. Make sure that the operational plan is defined for the serial number nX30000 with part number nX747-900. If an open flight log exists for the part and serial, complete the Close Flight Log exercise before continuing with this exercise.

Windows:
Flight Log
Flight Log /Flight Info /General

  1. Open the Flight Log window and create a new record (F5).
  2. In the Part Number field, enter the nX747-900 part number and the * Part Rev of your vehicle. You can also use the List of Values to select the value.
  3. In the Serial Number field, enter the nX30000 of your vehicle. You can use the List of Values to select the correct serial number.
  4. In the Flight Log Number field, enter 100.
  5. In the Flight Log Date field, the date entered must correspond with the date defined on the predefined operational plans that are to be used.
  6. Save the information (F12).
  7. Click the Flight Info tab and then click the General sub tab.
  8. Create a new record (F5).
  9. In the Operational Plan ID field, use the List of Values to select a predefined operational plan ID having a valid operational event which is connected to the serial defined on the flight log.
  10. In the Remark field, you can enter additional information on the flight.
  11. Save the information (F12).
  12. Enter additional information to this flight log by performing exercises such as Report Operational Logging, Report Crew Information, Report Fault Information as described above.