AIRWORTHINESS NOTICE

Transcription

1 GENERAL REQUIREMENTS FOR TECHNICAL PERFORMANCE & RELIABILITY PROGRAM OF AN OPERATOR AIRWORTHINESS NOTICE VERSION : 4.0 DATE OF IMPLEMENTATION : OFFICE OF PRIME INTEREST : AIRWORTHINESS DIRECTORATE 26/03/2010 AWNOT-066-AWXX-4.0

2 RELIABILITY PROGRAM OF AN OPERATOR 26/03/2010 AWNOT-066-AWXX-4.0

3 A. AUTHORITY: A1. This Airworthiness Notice has been issued under the authority vested in DG CAA vide rule 4 & 51 of Civil Aviation Rules B. PURPOSE: B1. The purpose of this Airworthiness Notice is to ensure compliance with requirements specified for reliability and technical performance program of an operator. C. SCOPE: C1. This Airworthiness Notice is applicable to all aviation operators related to aviation activities in Pakistan. C2. A reliability program shall be required in the following cases:- C2.1. The aircraft maintenance program is based upon MSG-3 logic or C2.2. The aircraft maintenance program includes condition monitor components; or C2.3. The aircraft maintenance program does not includes overhaul time periods for all significant systems or C2.4. When specified by the manufacturer's maintenance planning document or MRB D. DESCRIPTION: D1. DEFINITION: Nil D2. INTRODUCTION: D2.1 There are generally four general categories for operator's reliability programme (a) Systems (b) Components (c) Engines (d) Structures. All may be controlled by a composite programme or each may be handled individually. D2.2 The reliability programs constitute typically collection of data, analysis of the data, corrective actions, display and reporting. These programmes besides complying with airworthiness requirements, increase fleet reliability and reduce operations & maintenance cost. D2.3 This programme is mandatory for aircraft engaged in regular public transport. However, other operators are encouraged to follow this programme. D2.4 The operators are required to institute the performance reliability programme per this AW Notice and seek HQAW approval of the programme. PCAA shall overview its implementation, as appropriate. D3. DATA COLLECTION SYSTEM: D3.1 Typical sources of data collection by the operator, include the following: D3.1.1 D3.1.2 D3.1.3 D3.1.4 D3.1.5 Pilot reports (PIREPS) Unscheduled removals of components / engines. Confirmed failures Sampling inspections Shop findings 26/03/2010 Page 1 of 6 AWNOT-066-AWXX-4.0

4 D3.1.6 D3.1.7 D3.1.8 D3.1.9 Functional /Bench checks Defects Investigations Interruptions Summaries Other sources the operator considers appropriate D3.2 Not all of these sources may necessarily be covered in each and every programme. Adequate data should be used by the operator, to carryout reasonable analysis to obtain meaningful conclusion from its analysis. D3.3 Data collected should be accurate and factual to support a high degree of confidence for any derived conclusion. It should be obtained from units functioning under operational conditions and should relate directly to the established levels of performance. D3.4 For aircraft components, data collection should be established for all the critical components, which should be established by the operator. D4. DATA ANALYSIS: D4.1 The objective of data analysis is to recognize the need for corrective action, establish what corrective action is needed, and determine the effectiveness of that action. D4.2 The first step in analysis is to compare or measure data against acceptable performance levels. The standard may be a moving average, tabulation of removal rates for past periods, graphs or charts depicting a "norm". The analysis should be carried out through appropriately constituted Maintenance Review Board (MRB) for each type/fleet as applicable. D4.3 Aircraft systems (ATA 100): Aircraft systems reliability programme should use "Pilot reports per thousand Flying Hours" (or delays per 100 departures) as the parameter for reliability analysis. The operator should analyse data to identify characteristics indicating a need for programme adjustment, revising maintenance practices, improving (modifying) hardware etc. The operators should incorporate performance Levels (standards) as described in Statistical Performance Levels. 04 Digits ATA chapterization is to be used for purpose of data collection/analysis with in one year of issue of this notice. D4.4 Component Performance/Reliability Monitoring: The operator s component reliability programme should use the same performance criteria or the mathematical model as used for the systems reliability. For the components, rate of "Unscheduled removals per thousand Flying Hours" should be used as indicator of reliability monitoring. D4.5 Engine Trend / Health Monitoring: The operators are required to monitor Turbine Engine Trend / Health on the basis of recommendation of engine/aircraft Manufacturer. They should monitor condition of on-wing engines and utilize Computer Aided System for comparing in-flight engine parameters to detect potential failures & defects in early stages of development. The engine trend /health monitoring should constitute, as applicable: D4.5.1 D4.5.2 D4.5.3 D4.5.4 D4.5.5 Flight log Engine Cruise Data Monitoring Spectrometric oil analysis (SOAP Check), for internal health of engine. Boroscopic Inspection (BSI), at regular interval prescribed by MPD/ Manufacturer. Oil consumption of engine on regular interval (e.g Daily / Transit / Layover Check) Magnetic Chip Detection (MCD) Inspection at regular interval. D4.6 Performance Statistical data should also be compiled to assist in the day-to-day implementation of the maintenance programme. It may be used effectively as a basis for continuous mechanical performance analysis. (Interruption summaries, Removal rates, engine monitoring reports, incident reports, and engine and component analysis reports are examples of the types of suitable information). 26/03/2010 Page 2 of 6 AWNOT-066-AWXX-4.0

5 D5. PERFORMANCE LEVELS (STANDARDS): The operators should establish Statistical Performance Levels System as given below: D5.1 Aircraft Systems (ATA 100) D5.1.1 Pilot report rate per thousand Flying Hours (PIREP/1000 FH) should be calculated every month for each fleet type as parameter for reliability analysis. D5.1.2 Twelve-month "Running Average" of the PIREP RATE should be established as Good Performance Level (GPL). D5.1.3 Alert Level should be established as GPL plus two standard deviation of these 12 months PIREP RATE. D5.1.4 Green Alert Status: If current month's PIREP RATE is less than or equal to GPL then the Alert Status remains Green. D5.1.5 Amber Alert Status: If three month running average exceeds GPL then the Alert Level should change to Amber. D5.1.6 Red Alert Status: If three month running average exceeds the GPL & Alert Levels then the Alert status should become Red. D5.2 Aircraft Components D5.2.1 "Unscheduled Components Removal rate per thousand component Flying Hours " should be calculated every month for each critical component as parameter for reliability analysis. D5.2.2 Twelve-month "Running Average" of the "Unscheduled Components Removal rate per thousand component Flying Hours " should be established as Good Performance Level (GPL). D5.2.3 Alert Level should be established as GPL plus two standard deviation of this 12 months "Unscheduled Components Removal rate per thousand component Flying Hours" rate. D5.2.4 Green Alert Status: If current month's "Unscheduled Components Removal rate per thousand component Flying Hours" is less than or equal to GPL then the Alert Status remains Green. D5.2.5 Amber Alert Status: If three month running average exceeds GPL then the Alert Level should change to Amber. D5.2.6 Red Alert Status: If three month running average exceeds the GPL & Alert Levels then the Alert status should become Red. D5.3 The following factors may also be considered for establishing or revising reliability programmes performance levels, with prior approval of PCAA: D5.3.1 D5.3.2 D5.3.3 Note: Past and present individual operator and industry experience. Performance analysis of similar equipment currently in service Aircraft or equipment manufacturers' reliability engineering analysis The Reliability programme should cater for monitoring new aircraft until sufficient operating experience is available to compute performance standards, normally one year. 26/03/2010 Page 3 of 6 AWNOT-066-AWXX-4.0

6 D6. RELIABILITY REVIEW /MONITORING BOARDS: D6.1 Maintenance Review Board (MRB): Each operator should establish a Maintenance Review Board. Function of MRB is to review the effectiveness of the Performance & Reliability Programme. MRB should also review the functioning of Aircraft Systems & Component Reliability Boards. MRB should consist of 3-4 members headed by Chief of the Quality organization. Other relevant mangers/ chief engineer's should be members of the board. One PCAA Field office inspector shall participate in the MRB meetings as PCAA representative. MRB should meet quarterly to review preceding quarter's performance. The minutes of the meetings should be prepared and a copy of the same should be forwarded to concerned Airworthiness Field office. D6.2 Aircraft Systems Reliability Boards: Functions of Aircraft Systems Reliability Boards are to review the preceding month's performance on the basis of weak areas identified ATA wise. It should review Red and Amber status and suggest corrective measures for improvement of the performance. Each operator should establish two (one aerospace & one avionics) "Aircraft Systems" reliability boards for its fleet. These boards should consist of 3-4 members, headed by concerned trade's Development Engineering manager or equivalent. Other relevant engineers/managers should be members. PCAA Field office Airworthiness Inspectors (Aerospace/Avionics, as applicable) shall participate in the aircraft system Reliability Board meeting. These Boards should meet each month. The minutes of the meetings should be prepared and a copy of the same should be forwarded to concerned Airworthiness Field office. D6.3 Component Reliability Boards: Functions of Aircraft Component Reliability Boards are to review the preceding month's performance. It should review Red and Amber status and suggest corrective measures for improvement of the performance of those components. Each operator should establish appropriate number of Aircraft Components" reliability boards to adequately cover components of its fleet. These boards should consist of 3-4 members, headed by concerned shop's Quality manager (or equivalent). Other relevant engineers/managers should be members. PCAA Field office Airworthiness Inspectors (Aerospace/Avionics) shall participate in the aircraft system Reliability Board meeting. These Boards should meet bi-monthly to review the preceding month's component performance. The minutes of the meetings should be prepared and a copy of the same should be forwarded to concerned Airworthiness Field office. D7. DISPLAYS, CORRECTIVE ACTION AND REPORTING: D7.1 Corrective actions are to be recommended by Maintenance Review Board, Aircraft Systems Reliability Boards and Component Reliability Boards, as appropriate. Corrective action should be positive enough to restore performance effectively to an acceptable level within a reasonable time. D7.2 The corrective action system should include notification to the concerned section / organization responsible for taking the action. The concerned section should monitor the performance until it reaches an acceptable level. D7.3 Critical failures in which loss of function or the secondary effects of failure could affect the airworthiness of the aircraft should be monitored by the MRB and concerned System/component reliability Board. D7.4 Data Display and Reporting System: D7.4.1 Aircraft Systems Performance & Reliability: Operators should develop monthly reports with appropriate data displays summarizing the previous month's activity. This report should include the following: D Performance of all aircraft systems controlled by the programme in sufficient depth to enable the PCAA and other recipients to evaluate the effectiveness of the total maintenance programme. 26/03/2010 Page 4 of 6 AWNOT-066-AWXX-4.0

7 D Identification of Systems that exceeded the established Good Performance Level (GPL) and discussion on factors responsible for deterioration and actions taken or planned for improvement. D The progress on corrective action plan D7.4.2 The Aircraft Systems Performance & Reliability report should also include following information for each type: D Fleet Cumulative Landings and Airframe Hours. D Aircraft Operational Summary including aircraft in service, fleet utilization, and technical delays over 3 Hours etc. D Technical Incidents including Rejected take off, In-flight Engine Shut downs, Air turn backs, Diversions, In-flight Fire warnings, FOD etc. D Interruption Summary reports D7.4.3 Aircraft Components Reliability: Operators should develop monthly reports with appropriate data displays summarizing the previous month's activity. This report should be prepared by the last date of the following month (i.e. Report of January is due by end of February). This report should include the following: D Performance of all aircraft components controlled by the programme to enable the PCAA and other recipients to review overall performance trend. D Identification of components that exceeded the established Good Performance Level (GPL) and discussion on factors responsible for deterioration and actions taken or planned for improvement. D Summaries of the actions taken or planned on amber and red, as appropriate. D7.4.4 The programme should include a procedure for revision, which should be compatible with PCAA approvals. The procedures should identify organizational elements involved in the revision process and the authority. The programme areas requiring formal PCAA approval include any changes to the programme that involve the following: D D D Monitoring). D Procedures relating to reliability measurement/ performance standards. Data analysis methods and application to the total maintenance programme. Process/task changes (from Hard Time to On Condition, On Condition to Condition Adding or deleting components/systems. D8. INTERVAL ADJUSTMENTS AND PROCESS CHANGES: D8.1 The programme should include procedures for the classification of maintenance processes and/or tasks and for changing from one process and/or task to another. It should include the authority (PCAA, MRB, Chief of Quality) and procedures for changing maintenance specifications to reflect the interval adjustment or processes and/or task changes. D9. APPROVAL /MONITORING BY PCAA. D9.1 The operators shall institute the Reliability programme and seek PCAA HQ AW approval through respective Field Office. 26/03/2010 Page 5 of 6 AWNOT-066-AWXX-4.0

8 D9.2 The operators, after the formal PCAA approval, shall control the Reliability programme. D9.3 PCAA Field Offices shall monitor the programme implementation by the operators regularly. E. EVIDENCES (ACRONYMS / RECORDS / REFERENCES): E1. ACRONYMS: ATA AIR TRANSPORT ASSOCIATION BSI BOROSCOPE INSPECTION GPL GOOD PERFORMANCE LEVEL HQAW HEADQUARTERS AIRWORTHINESS MCD MAGNETIC CHIP DETECTION MPD MAINTENANCE PROGRAMME DOCUMENT MRB MAINTENANCE REVIEW BOARD PCAA PAKISTAN CIVIL AVIATION AUTHORITY PIREPS PILOT REPORTS SOAP SPECTROMETRIC OIL ANALYSIS PROGRAM E2. RECORDS: Nil E3. REFERENCES Nil IMPLEMENTATION: This Airworthiness Notice cancels / supersedes Airworthiness Notice No. 65, Issue-03 dated 19 th May, 2007 and shall be implemented with effect from 26 th March, /03/2010 Page 6 of 6 AWNOT-066-AWXX-4.0