mmir

1. MMIR & Event Reporting www.mmir.com

3. What is MMIR? • Industry’s pre-eminent parts failure database • 2+ decades in service • Conceived by HAI • Eliminates redundancy, reduces workload • Meets SDR reporting requirements • Sharing information is positive for safety

4. Before MMIR, operators had to submit same information to different places; • Time consuming • Costly Manufacturers and HAI Technical Committee devised 4-copy form

5. Why use MMIR today? • Enhance aviation safety • Reduce operating costs • Find out which parts may fail BEFORE they fail SHARING INFORMATION ABOUT PARTS MALFUNCTIONS IS GOOD FOR SAFETY

6. Why use MMIR today? • Access via Internet (www.mmir.com) • Fulfills FAA SDR requirements (FARs) • Easy to file voluntary SDRs (AC 20-109) • Submit warranty claims & customer orders • Comply with MIS requirements (FARs) • Reduce paperwork & workload • Records are permanent & secure • FREE access to collective database

7. MMIR Success Stories

8. Common Sad Story • Aircraft crash • Investigation: part failure was cause • Conversations reveal part has failed previously on other aircraft; replaced before catastrophe • Research into SDRs; reports of part failures exist but nothing done with information

9. Success! • MMIR instant reporting; for example: • Crack found in tail boom • Operator submits MMIR report; receives e-mail about several other boom cracks on same model • FAA and manufacturer electronically notified • Part was fixed BEFORE catastrophic event • SDR information being used actively; potential failures identified

10. Parts Reliability Concerns • Run MMIR analysis report of all parts for a specific helicopter model • Minimum, maximum, average hours for each part • High-count reports for parts are identified • Detailed report available on any part • MMIR report can include ALL parts, including OEM and PMA parts

11. Success! • Reliability engineer at airframe manufacturer impressed with reports • Operators had been purchasing PMA fuel control valve for lower price • Had no idea about problem with PMA valve • MMIR provided data to airframe manufacturer that otherwise they would not know

12. Aircraft Design • Manufacturer working on new aircraft • Planned to use existing tail rotor design from previous model • One engineer expressed concerns about problems with existing tail rotor design • Engineer ran MMIR reports on the tail rotor assembly

13. Success! • Engineer presented MMIR reports as evidence of concerns • Management convinced; agreed with engineer • Tail rotor design modified

14. Resource Management • One large operator devoted 2 full-time positions: • Submit and file warranty claims • Submit SDRs • Same information passed around

15. Success! • Company started using MMIR • Consolidated work • Less than 1 full-time position handled both tasks • Resources freed to productive tasks

16. Operator Benefits • Warranty & SDR reports consolidated • Electronic submission to FAA • Lookup of prior reports with ease • Find similar problems on other aircraft • Always up-to-date information • No extra equipment; no extra cost

18. Report Types • Warranty Claim / Customer Order • Service Difficulty Report • Warranty Claim plus SDR • Mechanical Interruption Summary • MMIR for information purposes* • Company Internal • Event Report *Highly encouraged - SHARING INFO IS GOOD FOR SAFETY

19. Choose your report type

20. MMIR Form (all fields) Submitter info pre-completed “Submit To” pull-down list from your customizable address book Warranty claim / order info Aircraft & Engine info SDR or MIS options (pull-down lists) Defective part(s) info Optional Major Assembly section (aids MMIR & SDR searches) Replacement part(s) info Narrative fields

21. Find your reports easily

22. Analysis Queries • By part number • By aircraft model or model series • Available to all access levels • Full (submit reports) • Read (analysis only) • Manufacturer (receive warranty claims)

27. Event Reporting

29. Safety Management System What is it? “…a formal framework for integrating safety into day to day operation and includes safety goals and performance targets, risk assessments, responsibilities and authorities, rules and procedures, and monitoring and evaluation processes.” - Curt Lewis, P.E., CSP Flight Safety Information Quarterly Journal

30. 5 Key Elements of an effective SMS • Clear policies • Effective organization • Systematic planning • Performance measurement • Audit and review process - Curt Lewis, P.E., CSP Flight Safety Information Quarterly Journal

31. Safety Management System • Does your operation have a program in place? • Is it being used? • Really? • What will you be able to say in court? HAI’s Event Reporting can be the basis of your SMS or a useful addition to your existing program

32. Event ReportingClosed-Loop System New report initiated Investigation findings documented Document solution Report acknowledged Documentation reviewed Close or Rescind report Continue investigation? Event investigated Notify initiator No Yes

34. Company, initiator, status, users Rating information, dates Broad, multiple categories User-customizable topics Aircraft, engine, SDR, MIS fields (if applicable) Check for related reports Narrative boxes (text) Part(s) information Once report is “Open,” Manager Level can “Close” report when resolved and documented

35. Event Reporting Access Levels • Administrator • Controls all company users’ level of authorization • Manager • Controls dispensation of company Event Reports (i.e., Closed, Rescinded) • Write • Can initiate and edit Event Reports • Read • Can only view existing reports

36. Use this to VIEW both Company and External Reports Shared External Reports originate outside your company Company Reports are viewable and editable by authorized company users The company originating the Event Report decides whether or not to “share” it with external users. Sharing is good for safety.

38. EXAMPLE ONLY

39. Event Reporting • To fix a problem, you must identify it • Big problems usually begin with small issues, or a series of little problems • Don’t wait until you have a big problem! • Track issues that affect your operation; identify potential problems • Resolve little problems before they become !! TROUBLE !!