Operational Interruptions Details-System ATA

Operational Interruptions Details – System ATA

This report displays month-wise information on operational interruptions with reference to System ATAs for a reliability fleet.

The number of System ATAs included in the report is determined by the “Count of Top ATA # determiners of Delay” specified in the Set Options activity. For example, if this attribute is set to 5, the report will provide details of the five System ATAs with the most number of interruptions reported against them.

Operational interruptions include events such as, Delays, Cancellations, Air Turn backs, Substitutions, Ground Turn backs and Diversions reported against all aircraft in the reliability fleet during the month of the report.

The months for which information is displayed in this report is based on the ‘Analysis Period’ attribute in the Set Options activity. For example, the March 2008 report with the ‘Analysis Period’ set to ‘12’ would show data beginning April, 2007 to March, 2008.

Report input: You must select the month and year and, the reliability fleet for the report in the Generate Reliability Report page. For further information, see the “Generate Reliability Report” topic.

Report output: This report is an Excel sheet and consists of six work sheets,

For in-depth information, see Retrieval of interruptions for the report, Delay computation, and Cancellation count.

Delays per System ATA

This worksheet provides the month-wise count of delays and the delay duration for each System ATA associated to the reliability fleet.

System ATA #	The System ATA against which delays are reported for a reliability fleet.
System ATA Description	The chapter description of System ATA.
Major System ATA #	The Major System ATA against which delays are reported for a reliability fleet.
Major System ATA Description	The chapter description of Major System ATA.
No. of delays	Monthly count of delays recorded against the system ATA.
Total Time	Monthly total delay duration against the system ATA

Cancellations per System ATA

In this worksheet, you can find the month-wise breakup of cancellations based on System ATAs for a reliability fleet.

ATA #	The ATA against which the delay is reported.
Operational Interruption	The name of the System ATA to which the ATA is mapped.
Recorded Date	The flight date of the interruption.
Fleet	The identification code of the reliability flight.
Aircraft	The registration number of the aircraft.
Journey Log #	The identification number of the journey log in which the delay is recorded.
Line #	The line number of the multiline in the Leg Details tab of the “Create Journey Log “ page, where the delay details are recorded.
Flight #	The identification number of the flight associated with the journey log.
Leg #	The identification number of the leg of the journey in which the delay occurred.
Station	The code of the departure station where the delay occurred.
Reason	The reason as recorded against the delay.
Action Taken	Any remedial action undertaken to resolve the delay.
Remarks	Any comments or additional information on the delay.

Delays and Cancellations

This worksheet provides the month-wise count of delays and cancellations for each System ATA of the reliability fleet.

Other than Delay and Cancellations

This worksheet provides the month-wise count of all operational interruptions for each System ATA of the reliability fleet.

Graph-Delay by System ATA

This worksheet displays graph that depicts delays reported against each System ATA for the reliability fleet.

X-Axis

The System ATAs for the reliability fleet.

Y-Axis

The count of delays for each of the System ATA.

The count would include the delays reported against each of the ATAs mapped to the System ATA.

Graph-Delay by Major System ATA

This worksheet displays graph that depicts cancellations reported against each Major System ATA for the reliability fleet.

X-Axis

The Major System ATAs for the reliability fleet.

Y-Axis

The count of cancellations for each System ATA.

The count would include the cancellations reported against each of the ATAs mapped to the System ATA.

Prerequisites

Journey logs must be created and processed in the Flight Log component.
System ATAs and Major System ATAs must be created and their attributes defined in the ”Set ATA Reporting Levels” page of the Set Reliability Fleet activity in the Reliability Analysis component.
Flight Delay codes must be created in the Create Flight Delay Code activity of the Common Masters component.

Retrieval of interruptions for the report

For creating the Operational Interruptions report, the system retrieves information from the journey logs created in the Flight Log component. Only the journey logs satisfying the following conditions are considered for reporting,

The “Flight Status” specified as part of the leg details of the journey log must be ”Diversions”, “Air Turn Back”, “Ground Turn Back”, “Delay”, “Cancellation” and Substitutions
The Flight Ops Type of the journey log checked in the Set Options activity is considered for Reliability Analysis. For example, journey logs of Flight Ops Type “Training” and “Positioning” may not require reporting, whereas reliability reports for journey logs of Flight Ops Type “Regular” may be mandatory.
The status of the journey log must be “Approved”.
The “Analysis Required” attribute for the ATA of the interruption must be set to “Yes” in the Set ATA Reporting Levels” page of the Setup Reliability Fleet activity. For example, if this attribute is set to “No” , any interruptions reported against the ATA will not be considered for reporting by the system.
The flight date of the interruption must occur in the month of the report.
The count of interruptions other than delays and cancellations for a flight would be the number of interruption codes that satisfy the above-explained conditions.

Note: An interruption is not considered for reporting, if an interruption code is not specified for an interruption in the journey log.

Delay computation

The count of delays for a flight would be the delay codes that satisfy the conditions explained under the sub-head “Retrieval of interruptions for the report” as well as the below-mentioned.

4 If a delay duration is greater than the Delay Limit defined in the Setup Reliability Fleet page, the delay becomes a cancellation for reporting. See Example, for better understanding.

The system determines a delay in the following way,

Adds the delay duration reported against delay codes individually for departures as well as arrivals for a flight. If the total delay duration for a departure or arrival is less than the Reportable Delay defined in the Setup Reliability Fleet page, the delay is not considered for reporting. The delay is counted for reporting, if the duration exceeds the predefined Reportable Delay Limit. On the contrary, if the total delay duration is more than the Delay Limit defined in the same page, the delay is considered as a cancellation and not a delay for reporting.

Example

The following illustration shows how the system picks up data for generating the delay report.

Let us assume the following data is available in the database for generating the report.

Delay Master table

Delay Category	Interruption Code	Consider for Reliability Analysis
Technical & Aircraft Equipment	Landing Gear Malfunction	Yes
Technical & Aircraft Equipment	MEL item not available	Yes
Weather	Bad Weather	No

Set Options table

Flight Ops. Type	Consider for Reliability Analysis
Regular	Yes
Test Flight	No
Ferry	No

Reliability Fleet table

Limits	Value	Remarks
Reportable Delay (Min)	15 Min	Total Delay Duration>=15Minutes = Delay
Delay Limit (Min)	30 Min	Total Delay Duration>30Minutes = Cancellation

Scenario 1: The duration of delay is less than Reportable Delay

For Aircraft Reg # N1000 for Journey Log # “JL-000050”, Leg # “Auckland-Singapore” with Flight Ops Type “Regular”, delay reported for 10 minutes due to “Landing Gear Malfunction”.

This delay is not considered for the report since the duration of the delay is under the Reportable Delay, i.e. 15 minutes.

Scenario 2: The duration of a delay is greater than Reportable Delay

For Aircraft Reg # N1000 for Journey Log # “JL-000050”, Leg # “Auckland-Singapore” with Flight Ops Type “Regular”, delay reported for 20 minutes due to “MEL item not available””.

This delay is counted for the report as the duration of the delay is above the Reportable Delay, i.e. 15 minutes.

Scenario 3: The delay at leg level is reported against two different delay codes.

For Aircraft Reg # N1000 for Journey Log # “JL-000050”, Leg # “Auckland-Singapore” with Flight Ops Type “Regular”, delay reported for 20 minutes.

4 A delay of 10 minutes each reported against “Landing Gear Malfunction” and “Bad Weather”.

As the Interruption code “Bad Weather” is not flagged for reliability analysis, the total delay duration would be only 10 minutes; therefore this interruption would not be considered as a delay.

Scenario 4: The delay at leg level is converted to cancellation.

For Aircraft Reg # N1000 for Journey Log # “JL-000050”, Leg # “Auckland-Singapore” with Flight Ops Type “Regular”, delay reported for 40 minutes.

This delay is considered as a cancellation since the duration of the delay is above the Delay Limit, i.e. 30 minutes.

Cancellation count

The count of cancellations for a flight would be the cancellation codes that satisfy the conditions explained under the sub-head “Retrieval of interruptions for the report” as well as the below-mentioned scenario.

4 If a delay duration is greater than the Delay Limit defined in the Setup Reliability Fleet page, the delay becomes a cancellation for reporting. For example, For Aircraft Reg # N1000 for Journey Log # “JL-000050”, Leg # “Auckland-Singapore” with Flight Ops Type “Regular”, delay reported for 40 minutes. Assuming a predefined Delay Limit of 30 minutes, this delay is converted to a cancellation as the duration exceeds the Delay Limit by 10 minutes.