Delays by Week-ATA-Dispatch Reliability by Station Report

This report displays information on delays and the dispatch reliability for a reliability report group/ reliability fleet, reported during a month.

The report displays information on reliability report group or reliability fleet based on the Reporting Level attribute of the Set Options activity. If this attribute is set to “Reliability Report Group”, the delay information would pertain to all the fleets in the reliability report group. For information on reliability fleet, you must specify “Reliability Fleet” as the Reporting Level.

This report is an Excel sheet and consists of four work sheets,

Delay by Week

Delay by System ATA

 Delay by Major System ATA

Delay by Station

For in-depth information, see Retrieval of delays for the report and Example

Delay by Week

This worksheet lists delays against each week of the reported month, for a reliability report group or a reliability fleet. If the “Reliability Analysis Level” attribute in the Set Options is set as,

• “Reliability Reporting group level”, the weekly delays are listed for all the reliability fleets associated to the selected ‘Reliability Report Group’.

• ”Reliability Fleet level”, the weekly delays are listed for the selected reliability fleet

Delay by System ATA

This worksheet lists the System ATA-wise count of delays against each week of the reported month for a reliability report group or a reliability fleet. If the “Reliability Analysis Level” attribute in the Set Options is set as,

• “Reliability Reporting group level”, the System ATA-wise weekly delays are listed for all the reliability fleets associated to the selected ‘Reliability Report Group’.

• ”Reliability Fleet level”, the System ATA-wise weekly delays are listed for the selected reliability fleet

Note: Delays against only those System ATAs defined for a reliability fleet in the ‘Set ATA Reporting Levels’ page would be listed.

Delay by Major System ATA

This worksheet lists the Major System-ATA wise count of delays against each week of the reported month, for a reliability report group or a reliability fleet. If the “Reliability Analysis Level” attribute in the Set Options is set as,

• “Reliability Reporting group level”, the Major System ATA-wise weekly delays are listed for all the reliability fleets associated to the selected ‘Reliability Report Group’.

• ”Reliability Fleet level”, the Major System ATA-wise weekly delays are listed for the selected reliability fleet

Note: Delays against only those Major System ATAs defined for a reliability fleet in the ‘Set ATA Reporting Levels’ page would be listed.

Delay by Station

This worksheet provides departure delays recorded in all the stations and station–wise dispatch reliability for a reliability report group/ reliability fleet.

• “Reliability Reporting group level”, the station-wise delays are listed for all the reliability fleets associated to the selected ‘Reliability Report Group’.

• ”Reliability Fleet level”, the station-wise delays are listed for the selected reliability fleet

Note: Only the stations against which at least one revenue departure has happened for the reported month would be listed.  

A graph depicting the dispatch reliability for departure stations is also available in this worksheet.

Prerequisites

• Journey logs must be created and processed in the Flight Log component.

• System ATAs and Major System ATAs must be created for a reliability fleet and their attributes defined in the ”Set ATA Reporting Levels” page of the Set Reliability Fleet activity in the Reliability Analysis component.

• Interruption codes must be created in the Create Interruption Code activity of the Common Masters component.

Retrieval of delays 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,

• Journey log Status is “Approved”

• The Flight Date must occur in the reported month

• Journey log legs ‘Flight Status’ as “Delayed’, with delay duration between the ‘Reportable Delay’ and ‘Delay Limit’ specified in the Setup Reliability Fleet activity.

• The “Flight Status” specified as part of the leg details of the journey log must be “Delay”.

• ‘Flight Ops. Type’ flagged as ‘To be considered for Reliability Analysis’in the Set Options activity alone would be considered for delay count.

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

Set Options table

Reliability Fleet table

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

• For Aircraft Reg # A1, for Journey Log # “JL-000050”, Leg # “1” 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 # A2 for Journey Log # “JL-000050”, Leg # “1” 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 # A1, for Journey Log # “JL-000050”, Leg # “1” with Flight Ops Type “Regular”, delay reported for 20 minutes.

• 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 # A1, for Journey Log # “JL-000050”, Leg # “1” 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.