GM1 ORA.FSTD.110 Modifications

EXAMPLES OF MAJOR MODIFICATIONS

The following are examples of modifications that should be considered as major. This list is not exhaustive and modifications need to be classified on a case-by-case basis:

(a) any change that affects the QTG;

(b) introduction of new standards of equipment such as flight management and guidance computer (FMGC) and updated aerodynamic data packages;

(c) re-hosting of the FSTD software;

(d) introduction of features that model new training scenarios; e.g. airborne collision avoidance system (ACAS), EGPWS;

(e) aircraft modifications that could affect the FSTD qualification; and

(f) FSTD hardware or software modifications that could affect the handling qualities, performance or system representation.

[applicable until 29 April 2028 — ED Decision ED Decision 2012/007/R]

GM1 ORA.FSTD.110 Management of modifications

(a) EXAMPLES OF MAJOR MODIFICATIONS

The following are examples of modifications that should be considered as major. This list is not exhaustive and modifications need to be classified on a case-by-case basis:

(1) any change affecting the FCS or assigned FCS;

(2) any modifications to the software or hardware that impact the flight or ground handling characteristics;

(3) any modification to the motion, visual, sound or control loading software or hardware that is intended to impact the FSTD performance and handling;

(4) any re-baselining of MQTG tests as a result of points (2) and (3) above;

(5) any modifications of the visual system which may affect the QTG results, such as the display hardware, mounting bracketry, replacement mylar or mirrors, projector model changes or image generator hardware/software changes;

(6) new design features on the aircraft (e.g. installation of a head-up display (HUD));

(7) new avionics features;

(8) additional options for a different engine (types/ratings);

(9) updated validation data roadmap (VDR);

(10) any change in the ESL which affects training, testing and checking;

(11) additional functionality on the aircraft or aircraft operations that require additional validation of the source data (e.g. auto-brakes with RTO; going from no auto-land capability to an auto-land capability);

(12) new equipment (e.g. use of EVS, NVG);

(13) an extension of the training envelope that requires new validation source data, or extension of its scope (e.g. UPRT, stall training, helicopter external sling load operations);

(14) integration of new host computer(s);

(15) IOS hardware/software updates;

(16) integration of new technology in the visual, motion, controls or vibration systems;

(17) relocation and any de-activation/re-activation of an FSTD.

(b) EXAMPLES OF NON-MAJOR MODIFICATIONS

The following are examples of modifications that should be considered as non-major. This list is not exhaustive and modifications need to be classified on a case-by-case basis:

(1) navigation databases (including FMS, ground station, RDB, GPS Almanac);

(2) terrain and obstacle databases;

(3) update, addition or removal of visual models;

(4) control loading tuning, when necessary to comply with the MQTG baseline;

(5) motion and vibration tuning, when necessary to comply with the MQTG baseline;

(6) cosmetic/text changes to the MQTG;

(7) lesson plans;

(8) debriefing stations.

[applicable from 30 April 2028 — ED Decision 2026/006/R]