GM1 SIMD.200 Substantiation of the scope of the validation source
data
ED Decision 2014/033/R
(a) The substantiation of the scope of the validation source data (VSD) should be performed by:
(1) demonstrating that the applicant has developed and used a process that is acceptable to EASA (see point b of GM1 SIMD.100) to develop the scope of the VSD;
(2) using a list of parameters to be recorded for the different validation tests; the proposed validation data (VD) should be presented in a way that allows EASA to verify by analysis that that VD is suitable to fulfil the requirements of CS-FSTD(A) or (H):
(i) before initiating the VD gathering
campaign, the data providers should have suitable supporting documentation for
all necessary flight tests indicating aircraft configuration, flight
conditions, piloting techniques, associated CS-FSTD test requirements, etc.;
aspects such as data acquisition equipment type, installation, sampling rate,
etc., should also be described as part of the flight test data gathering
process; such documents should also constitute the basis for the data provider
processes to verify the quality and suitability of the collected data before
it is submitted to EASA;
(ii) whenever snapshot validation is
considered in the associated CS-FSTD objective test, the proposed snapshot
test points should be obtained during a continuous uninterrupted flight to
avoid unexpected changes in aircraft configuration (weight, CG, etc.) or
flight conditions such as wind; and
(iii) each data parameter should be
clearly described and labelled together with its unit; providing only software
or data acquisition variables is not acceptable;
(3) assessing the adequacy of the proposed VD and the associated validation data roadmap (VDR) by observing the first evaluation of the first type-specific FSTD (see GM3 SIMD.200); or
(4) alternatively, in any other way that may be proposed by the
applicant and agreed by EASA.
(b) An additional set of validation tests may
be specified to complement the minimum set of validation tests that are listed
in CS-FSTD(A) or (H) (‘Table of FSTD validation tests’).
A typical
illustration of such possible additional specifications may be the following:
the
behaviour of the aeroplane on ground at 95 % of maximum crosswind should
be simulated with the associated VD. In this example, the minimum would
normally be 60 % of the aeroplane flight manual (AFM) value.
(c) Based on the technical verification performed at the data provider and a theoretical compliance check of the presented VDR against the applicable regulations, EASA assesses the adequacy of the VDR and associated VD to establish if an initial evaluation can be envisaged. However, the result of the first evaluation of the first FSTD may lead to an update of the proposed VDR (see GM3 SIMD.200).
Subsequently, the updated VDR becomes the basis for the qualification of FSTDs for that type of aircraft.
[Issue No: SIMD/2]
To validate flight simulator data, applicants must demonstrate a process for defining validation scope, using parameter lists suitable for EASA verification. Flight test documentation, data quality checks, and clear parameter descriptions are crucial. EASA assesses the validation roadmap, potentially requiring updates after the initial simulator evaluation, establishing qualification standards.
* Summary by Aviation.Bot - Always consult the original document for the most accurate information.
Loading collections...