|
|
|
This report displays information on APU starts for all the aircraft in the reliability fleet.
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 one work sheet: APU Starts Report.
The following information is available for each month in the APU Starts Report worksheet. The months for which information is displayed 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.
|
Aircraft Reg. # |
The aircraft against which APU starts are recorded in the journey log. |
|
Date |
The flight date of journey logs in which APU starts are recorded. |
|
Journey Log # |
The journey logs in which APU starts are recorded. |
|
Component |
The identification number of the component that recorded APU starts. |
|
Part # |
The part number of the component. |
|
Serial # |
The serial number of the component. |
|
APU Starts |
The APU cycles recorded by the component in the journey log. |
Reliability fleets must be defined in the Setup Reliability Fleet activity.
Journey logs must be recorded and approved for the aircraft in the fleet in the Flight Log component.
The APU Starts report enables you to analyze the APU starts of all aircraft in a specified reliability fleet. The report displays the APU starts for all the flights pertaining to an aircraft during the month.
The APU starts refer to the APU cycles recorded against components of an aircraft with the following attributes
Position Code = “First Level”
Position Type = “APU”
Note: All APU cycles are recorded using a parameter mapped to the base parameter APU Cycles.
This information is retrieved from journey logs recorded in the Flight Log component. The following conditions must be true for journey logs for reporting,
The Flight Ops Type must be flagged for reliability reporting in the Set Options activity of the Reliability Analysis component.
The journey log status must be “Approved”.
For computing the APU cycles, the system makes the following additional checks,
If any Component Replacement History record exists for the component, the system considers the APU cycles recorded against the removed APU as well as the incoming/new APU
If any Component Parameter Update History record exists, the system considers the parameter update of the parameter mapped to the base parameter APU Cycles for retrieving the APU starts.
The report generates this information for all aircraft mapped to the reliability fleet during the month of the report and/or during the previous months. This implies aircraft not attached to the reliability fleet during the month of the report but mapped during the previous months are also considered for reliability analysis.
Aircraft remain attached to the fleet during the period between the Effective From and Effective To dates specified in the “Associate Aircraft to Fleet” page of the Setup Reliability Fleet in the Reliability Analysis component.