Appendix 2 to AMC1 FSTD(A).300 Validation data roadmap

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

Appendix 2 to AMC1 FSTD(A).300 Validation data roadmap ED Decision 2012/010/R (a) General (1) Aeroplane manufacturers or other sources of data should supply a validation data roadmap (VDR) document as part of the data package. A VDR document contains guidance material from the aeroplane validation data supplier recommending the best possible sources of data to be used as validation data in the QTG. A VDR is of special value in the cases of requests for ‘interim’ qualification, requests for qualification of simulations of aeroplanes certificated prior to 1992, and for qualification of alternate engine or avionics fits (see Appendices 3 and 4 of this AMC). A VDR should be submitted to the competent authority as early as possible in the planning stages for any FSTD planned for qualification to the standards contained herein. The respective Member State’s civil aviation authority is the final authority to approve the data to be used as validation material for the QTG. (2) The validation data roadmap should clearly identify (in matrix format) sources of data for all required tests. It should also provide guidance regarding the validity of these data for a specific engine type and thrust rating configuration and the revision levels of all avionics affecting aeroplane handling qualities and performance. The document should include rationale or explanation in cases where data or parameters are missing, engineering simulation data are to be used, flight test methods require explanation, etc., together with a brief narrative describing the cause/effect of any deviation from data requirements. Additionally, the document should make reference to other appropriate sources of validation data (e.g., sound and vibration data documents). (3) Table 1 below depicts a generic roadmap matrix identifying sources of validation data for an abbreviated list of tests. A complete matrix should address all test conditions. (4) Additionally, two examples of ‘rationale pages’ are presented in Appendix F of the IATA document *Flight Simulation Training Device Design & Performance Data Requirements, 7th edition*. These illustrate the type of aircraft and avionics configuration information and descriptive engineering rationale used to describe data anomalies, provide alternative data, or provide an acceptable basis to the competent authority for obtaining deviations from QTG validation requirements.  \*1 CCA mode shall be described for each test condition. \*2 If more than one aircraft type (e.g., derivative and baseline) are used as validation data more columns may be necessary. Table 1: generic roadmap matrix