Appendix 4 to AMC1 FSTD(A).300 Data requirements for alternate avionics (flight-related computers & controllers) - approval guidelines

• ED Decision 2012/010/R found in: CS-FSTD(A) Issue 2 - Aeroplane Flight Simulation Training Devices (May 2018)

Appendix 4 to AMC1 FSTD(A).300 Data requirements for alternate avionics (flight-related computers & controllers) – approval guidelines ED Decision 2012/010/R (a) Background (1) For a new aeroplane type, the majority of flight validation data is collected on the first aeroplane configuration with a baseline flight-related avionics ship-set (see (b)(2) below). These data are then used to validate all FSTDs representing that aeroplane type. (2) In the case of FSTDs representing an aeroplane with avionics of a different hardware design than the baseline, or a different software revision than that of previously validated configurations, additional validation data may be required. (3) When an FSTD with additional and/or alternate avionics configurations is to be qualified, the qualification test guide (QTG) should contain tests against validation data for selected cases where avionics differences are expected to be significant. (b) Approval guidelines for validating alternate avionics (1) The following guidelines apply to FSTDs representing aeroplanes with a revised, or more than one, avionics configuration. (2) The aeroplane avionics should be segmented into those systems or components that can significantly affect the QTG results and those that cannot. The following avionics are examples of those for which hardware design changes or software revision updates may lead to significant differences relative to the baseline avionics configuration: flight control computers and controllers for engines, autopilot, braking system, nose wheel steering system, high lift system, and landing gear system. Related avionics such as stall warning and augmentation systems should also be considered. The aeroplane manufacturer should identify for each validation test which avionics systems, if changed, could affect test results. (3) The baseline validation data should be based on flight test data, except where other data are specifically allowed (see [AMC7 FSTD(A).300](#_DxCrossRefBm1310592841) and [AMC8 FSTD(A).300](#_DxCrossRefBm1310592842)). (4) For changes to an avionics system or component that cannot affect master QTG (MQTG) validation test results, the QTG test can be based on validation data from the previously validated avionics configuration. (5) For changes to an avionics system or component that could affect a QTG validation test, but where that test is not affected by this particular change (e.g., the avionics change is a built-in test equipment (BITE) update or a modification in a different flight phase), the QTG test can be based on validation data from the previously-validated avionics configuration. The aeroplane manufacturer should clearly state that this avionics change does not affect the test. (6) For an avionics change which affects some tests in the QTG, but where no new functionality is added and the impact of the avionics change on aeroplane response is a small, well-understood effect, the QTG may be based on validation data from the previously validated avionics configuration. This should be supplemented with avionics-specific validation data from the aeroplane manufacturer’s engineering simulation, generated with the revised avionics configuration. In such cases, the aeroplane manufacturer should provide a rationale explaining the nature of the change and its effect on the aeroplane response. (7) For an avionics change that significantly affects some tests in the QTG, especially where new functionality is added, the QTG should be based on validation data from the previously validated avionics configuration and supplemental avionics-specific flight test data sufficient to validate the alternate avionics revision. However, additional flight validation data may not be needed if the avionics changes were certified without need for testing with a comprehensive flight instrumentation package. The aeroplane manufacturer should coordinate FSTD data requirements in this situation, in advance, with the competent authority. (8) A matrix or roadmap should be provided with the QTG indicating the appropriate validation data source for each test (see [Appendix 2 to AMC1 FSTD(A).300](#_DxCrossRefBm1310592837)).