ECAST Meeting - 04 Jun 2013 - Reliability Data Sharing

739 views

Published on

Published in: Technology, Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
739
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
16
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

ECAST Meeting - 04 Jun 2013 - Reliability Data Sharing

  1. 1. Everything I will say and all information included in this presentation is either cited material from other sources or my personal opinion and may or may not reflect any of the organisations I am associated with.
  2. 2. The regulatory requirements and industry standards (Part M, Part 21 & IOSA) Reliability Data Sharing – Can it be replicated in other disciplines? MONITORING REPLACEMENT OF PARTS & COMPONENTS OPERATOR’s RELIABILITY PROGRAMME TO DISSEMINATE INFORMATION ABOUT RECURRENT FAILURES TC/STC holders’ responsibilities & programmes TRADITIONAL AIRCRAFT TYPES DATA COLLECTED MANUALLY NEW TECHNOLOGY (ON-BOARD HEALTH MONITORING SYSTEMS) vs
  3. 3. 21.A.3A Failures, malfunctions and defects (a) System for Collection, Investigation and Analysis of Data The holder of a TC, RTC, STC, ETSO holder shall have a system for collecting, investigating and analysing reports of and information related to failures, malfunctions, defects or other occurrences which cause or might cause adverse effects on the continuing airworthiness of the product, part or appliance covered by the TC, RTC, STC, ETSO authorisation. Information about this system shall be made available to all known operators of the product, part or appliance and, on request, to any person authorised under other associated implementing Regulations.
  4. 4. 21.A.3A Failures, malfunctions and defects (b) Reporting to the Agency 1. The holder of a TC, RTC, STC, ETSO authorisation shall report to the Agency any failure, malfunction, defect or other occurrence of which it is aware related to a product, part, or appliance covered by the TC, RTC, STC, ETSO authorisation, and which has resulted in or may result in an unsafe condition. 2. These reports shall be made in a form and manner established by the Agency, as soon as practicable and in any case dispatched not later than 72 hours after the identification of the possible unsafe condition, unless exceptional circumstances prevent this.
  5. 5. AMC M.A.202 (a) Occurrence reporting Accountable persons or organisations should ensure that the type certificate (TC) holder receives adequate reports of occurrences for that aircraft type, to enable it to issue appropriate service instructions and recommendations to all owners or operators. Liaison with the TC holder is recommended to establish whether published or proposed service information will resolve the problem or to obtain a solution to a particular problem. An approved continuing airworthiness management or maintenance organisation should assign responsibility for co-ordinating action on airworthiness occurrences and for initiating any necessary further investigation and follow-up activity to a suitably qualified person with clearly defined authority and status. In respect of maintenance, reporting a condition that could seriously hazard the aircraft is normally limited to: • serious cracks, permanent deformation, burning or serious corrosion of structure found during scheduled maintenance of the aircraft or component. • failure of any emergency system during scheduled testing.
  6. 6. 2.12 Reporting to the Authority MNT 2.12.1 The Operator shall have a procedure to provide the Authority, for aircraft over 5,700 (12,566 lb) kg maximum certificated takeoff mass, with in-service information as prescribed by the Authority. Guidance Guidance may be found in ICAO Annex 8, Part II, 4.2.4. Each Contracting State shall establish, in respect of aeroplanes over 5 700 kg and helicopters over 3 175 kg maximum certificated take-off mass, the type of service information that is to be reported to its airworthiness authority by operators, organizations responsible for type design and maintenance organizations. Procedures for reporting this information shall also be established. MNT 2.12.2 The Operator shall have a procedure for reporting to the Authority and, if applicable, the Type Certificate Holder, defects or un-airworthy conditions in accordance with requirements contained in Table 4.4. MNT 2.12.3 – 2.12.6 (Intentionally open) MNT 2.12.7 The Operator shall have a procedure to transmit to the Type Certificate Holder information on faults, malfunctions, defects and other occurrences which could affect the continuing airworthiness of aircraft of over 5,700 kg (12,566 lb) maximum certificated takeoff mass.
  7. 7. • RELIABILITY: The probability that an item will perform a required function, under stated conditions, for a stated period of time. AVAILABILITY SAFETY • Important aspect of System Safety Assessment for Certification. i.e. CS 25.1309 • From commercial / operational point of view, it is absolutely crucial for AVAILABILITY.
  8. 8. Source: ARP 4754 - Guidelines for development of civil aircraft systems
  9. 9. Source: Reliability, Maintainability & Risk, David J. Smith, 2001
  10. 10. Generator • Design (Inherent) • Production standards • Installation • Component + System Reliability • Preventive + Predictive Maintenance Trailing Edge Flaps • Design (Redundancy) • Components • Operation (Usage)
  11. 11. Source: VIVACE 1.6/3/EADS-CRC-F/T/05018-2.0 Report on Aircraft Maintenance Programme 2005 Reliability Program
  12. 12. http://www.flightglobal.com/articles/2009/04/28/325753/turkish-737-altimeter-fault-occurred-on-several-flights-prior-to.html CASE STUDY – REPETITIVE DEFECTS MANAGING RELIABILITY & RISK
  13. 13. Source: http://www.readigroup.org/background.html
  14. 14. Source: http://www.spec2000.com/10.html
  15. 15. Source: http://www.spec2000.com/44.html
  16. 16. Source: http://www.boeing.com/commercial/aeromagazine/articles/qtr_1_08/AERO_Q108.pdf Source:http://www.ataebiz.org/forum/2010_ata_ebiz_forum/Reliability_Yakubowsky_2010.pdf
  17. 17. TRADITIONAL AIRCRAFT TYPES DATA COLLECTED MANUALLY NEW TECHNOLOGY (ON-BOARD HEALTH MONITORING SYSTEMS) vs
  18. 18. Reliability Data Analysis - Data Mining/Machine Learning The goal of this research is to develop and implement a statistically based alerting system for reliability events, for mature aircraft programs, allowing an easier identification of problems by analysing the historical in-service event data.
  19. 19. CAN SOME OF THE RELIABILITY DATA ANALYSIS & SHARING PRACTICES BE REPLICATED FOR FLIGHT SAFETY OR FDM DATA?

×