FALCON SERVICE ADVISORY

Transcription

1 A Inspection Interval Extension June 27, 2016 Classification: Maintenance F10 F20 F200 F50 F900 F2000 F7X EX - EX EASy DX LX - EX EASy DX LX S LXS X REASON Dassault Aviation is moving forward on extending the interval between Falcon 7X A checks to 12 months. The extended interval 12M or 800FH will be included in Revision 16 of the Falcon 7X Maintenance Planning Document (MPD - Chapter 5), to be released beginning of September This new program will improve operational availability by: - Reducing the number of scheduled maintenance stops - Improving the synchronization with 5-20 component scheduled maintenance - Scheduling annual maintenance stop within a preferred calendar period The purpose of this FSA is to describe the extension details prior to MPD release and assist operators with transitioning to the new program. INFORMATION In order to substantiate the extension, significant feedback from in-service fleet was required. This requirement has limited the scope of the extension to lower interval inspections: 1A/1A* and 2A/2A* Inspections. The intervals of 3A, 3A*, 4A and 6A inspections are re-aligned with the new 12M or 800FH interval. Page 1 / 6

2 On the above illustration, green arrows show extended intervals, orange arrows show realigned intervals, and black arrow shows unchanged intervals. Task intervals have been adapted (either extended or re-aligned) to match the new framework and limit the impact on maintenance downtime. To avoid any confusion with current intervals, new extended inspections will refer to their specific interval (i.e. 12M or 800FH, 800FH, 24M or 1600FH ), not A/A*, with the following rules: - First limit reached, 12 months or 800 flight hours for 12M or 800FH, - FH interval inspections can still be performed independently from other inspections, - Tolerances: 1 month for calendar / 50FH for FH interval ; all non-cumulative B and C Inspection intervals will remain unchanged. Note 1: Some of the existing tasks will remain at 600FH; another FSA will be available to provide details on the non-extended tasks at the MPD Rev16 release. Note 2: Many FSA/FSN/SB referring to current A/A* inspections and multiple have not been updated to take the new intervals into account yet. In the meantime, please consider that the new intervals apply to these documents (i.e. 12M or 800FH instead of 1A, 24M or 1600FH instead of 2A and 3A ) Additional MPD Rev16 Information In addition to the above, an effort has been made to group inspections within a similar zone and interval, to increase efficiency and organization. In Revision 16, Falcon 7X MPD (Chapter 5) tables will be edited without magenta in FIELD 5. However, to ease the update of your Operator Maintenance Program, Chapter 5 will be available on the Falcon Portal (Excel format) to track all changes between the last and the current MPD revision. Example of changes description display on Excel chapter 5 MPD Rev16 also contains 5-40 Rev5, related to: - Falcon 8X specificities - Impact of extensions on Life limit extensions of landing gear component and sub-components Transition As this MPD provides operational availability improvements, Dassault Aviation recommends moving to the new MPD as soon as possible. However, as there is no stipulated time, operators may transition to the new MPD with 12M or 800FH interval at their convenience, it can be done in between 2 visits. Page 2 / 6

3 Transition Help Software The transition will depend on aircraft progress in the maintenance cycle. An Excel-based software program has been developed to calculate future next due inspection dates based on last performed of each inspections (1A, 2A ): Request Form of Transition Help software The purpose of the transition help software is to display the following information customized per aircraft: o o The next due of new inspections ( 12M or 800FH, 800FH, 24M or 1600FH ) The next due of a specific transition package, when applicable The displayed next due are the maximum based on what was extended; new inspections may need to be performed earlier once to then synchronize all upcoming inspections. Page 3 / 6

4 For aircraft with FalconCare, the following transition actions will be covered: - Transition package, when applicable - New inspections anticipation for synchronization purpose (anticipation limited to former interval). For further details, refer to the tutorial available with the transition help software on the Maintenance Documentation/Technical Information page of Customer Portal: NOTES: CAMP analysts and OCIP administrators have been trained to help you transitioning to this program. How to prepare the transition before MPD Rev 16 release? The following workflow provides some guidelines for the transition to the new maintenance program to be implemented at the earliest convenience. It will help to: - Synchronize the aircraft schedule with the new program - Plan the maintenance slots for end of year and beyond Suggested Workflow: 1. Estimate the date of the transition: it is when you have taken into account the changes related to MPD Rev16 (i.e. when you agreed with your CAMP analyst on the Revision Summary Change Form, or the date of approval of your Operator Maintenance Program based on MPD Rev16) Note: Transition date is the date the new inspections based on Rev16 are initialized in the maintenance management program (i.e. CAMP). 2. Estimate TSN (Time Since New in FH) at the date of transition based on aircraft flight activity Page 4 / 6

5 3. Estimate the last performed (= last complied with date and FH) of each A/A* inspection at the transition date. (If no A Inspection is scheduled between now and this date, it may be the same as last performed today) 4. Run those estimated data in the transition help software and check the result. Note: Appendix 1 provides guidance to check the results of the Transition Help software. 5. Synchronize the aircraft schedule with the new program To ensure scheduled maintenance inspections are aligned within the new program, indicate all last performed inspections and next due inspection dates on a timeline (as illustrated in the Transition Help software tutorial, found on the Customer Portal). This will determine inspections that can be performed earlier to synchronize the new program. Note: if you are interested to position the future yearly maintenance stop in a preferred calendar period, please contact your Customer Service Manager, Field Service Representative or the Command Center. For aircraft managed by CAMP, contact your CAMP analyst to review the next due inspections and synchronization adjustments in order to prepare future implementation in the CAMP system. At this point, you may also want to take the opportunity to align 5-20 components scheduled maintenance with your 12M stops. 6. Plan the maintenance slots for end of year and beyond An e-forum will be held in July 2016 to detail the transition and to answer customer questions. In the meantime, please contact your Customer Service Manager, Field Service Representative or Command Center for any questions related to this FSA. Page 5 / 6

6 APPENDIX 1: CHECKING THE TRANSITION HELP SOFTWARE 1. Next due calculation of new packages T0 means maintenance date of origin. 12M or 800FH Inspection = due 12M or 800FH after last 1A (or T0 if never performed), whichever occurs first. 800FH Inspection is due 800FH after last 1A* (or T0 if never performed) 24M or 1600FH Inspection = due 24M or 1600FH after last 2A (or T0 if never performed), whichever occurs first 1600FH Inspection = due 1600FH after last 2A* (or T0 if never performed) 36M or 2400FH Inspection = due 36M or 2400FH after last 4A (or T0 if never performed), whichever occurs first 48M or 3200FH Inspection = due 48M or 3200FH after last 6A (or T0 if never performed) Note: If aircraft is too close to the 48M or 3200FH Inspection, former interval (54M or 3600FH) can be used one last time. 2. Necessity, Content and next due calculation of transition package Transition package is related to reduced periodicity. Using the Excel Chapter 5 available on the Falcon Portal at MPD Rev16 release, all cases of reduced periodicity can be identified. For each type of reduced periodicity: Check that the new next due is not after the former next due If it is, then perform all operations with this type of reduced periodicity no later than the former next due Example: 3A (27M or 1800FH) becomes 24M or 1600FH. If next due of 24M or 1600FH Inspection is after next due of former 3A Perform all tasks with this type of interval reduction (3A to 24M or 1600FH ) no later than 27M or 1800FH after last 3A. Note: To simplify the transition process, Transition Help software combines all applicable operations subjected to be overdone on an aircraft within the new program and consolidates them in a unique Transition Package. Page 6 / 6