Compare and highlight differences

Compare / EASA/ Incorporated Amendments/ Compare & Highlight Differences

AMC3 ORA.FSTD.120 Equipment specification list

Available versions for ERULES-1963177438-24251

ED Decision 2026/006/R found in: Easy Access Rules for Aircrew (Oct 2026)

Version

Show details Hide details

##### AMC3 ORA.FSTD.120 Equipment specification list

*ED
Decision
2026/006/R*

**INSTRUCTIONS
FOR ESL COMPLETION**

(a) The ESL should include the following
information in each section as referred to in the table below.

*Table: Instructions for completion of ESL
per section*

<table align="left" bgcolor="#d9d9d9" cellpadding="7" cellspacing="0" hspace="12">
<col/>
<col/>
<tr valign="top">
<td bgcolor="#808080">
ESL
			section reference
</td>
<td bgcolor="#808080">
Content
			of the section
</td>
</tr>
<tr valign="top">
<td bgcolor="#808080" rowspan="2">
Section
			1 ‘Organisation operating the FSTD’
</td>
<td bgcolor="#d9d9d9">
Name
			of the organisation operating the FSTD and its principal place of
			business address
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
FSTD
			location address
</td>
</tr>
<tr valign="top">
<td bgcolor="#808080" rowspan="9">
Section
			2 ‘FSTD information’
</td>
<td bgcolor="#d9d9d9">
(i)	Indication
			of the FCS or assigned FCS for an FSTD with FCS or with assigned
			FCS; or

(ii)	FSTD
			type/level for a legacy FSTD.
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
FSTD
			serial number
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
FSTD
			identification number (ID)
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
Organisation’s
			FSTD ID
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
Primary
			reference document and additional refence documents, if applicable
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
FSTD
			manufacturer
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
Year
			of manufacture
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
Validation
			data roadmap (VDR) (number, VDR version/revision, date)
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
Indication
			whether the FSTD has a multi-crew cooperation (MCC) capability,
			when applicable
</td>
</tr>
<tr valign="top">
<td bgcolor="#808080" rowspan="5">
Section
			2

Feature
			1: Flight deck layout and structure (FDK)
</td>
<td bgcolor="#d9d9d9">
In
			the cell that contains the instruction ‘[Indicate
			the fidelity level (S, R, G or N) (or leave blank for a legacy
			FSTD]’, for the ‘FDK’
			feature:

(i)	indication
			of the applicable fidelity level (S, R, G, N) for an FSTD with FCS
			or with assigned FCS; or

(ii)	to
			be left blank for a legacy FSTD.
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
Summary
			of the following:

			— FSTD;

			— simulated
			aircraft type, variant (make, model, series) or group of aircraft;

			— arrangement
			of equipment, covering the entire flight deck (e.g. enclosure,
			windows, lighting, seating); and
— aircraft
			system interfaces (e.g. panels, switches, buttons)
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
Description
			of the flight deck including, in cases it is applicable, elements
			which are touchscreen representations of flight deck equipment or
			interfaces
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
For
			an FSTD with FCS, where the flight deck has differences in
			fidelity levels across flight deck representation or aircraft
			system interfaces (e.g. panels, switches, buttons), identification
			of:

(i)	any
			omitted system interfaces, or any non-interactive representations
			used in place of functional elements used; and

(ii)	any
			fidelity differences across cockpit panels and consoles.
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
Maximum
			take-off weight (MTOW), maximum landing weight (MLW), in cases it
			is applicable
</td>
</tr>
<tr valign="top">
<td bgcolor="#808080" rowspan="5">
Section
			2

Feature
			2: Flight control forces and hardware (CLH)
</td>
<td bgcolor="#d9d9d9">
In
			the cell that contains the instruction ‘[Indicate
			the fidelity level (S, R, G or N) or leave blank for a legacy
			FSTD]’, for the ‘CLH’
			feature:

(i)	indication
			of the applicable fidelity level (S, R, G, N) for an FSTD with FCS
			or with assigned FCS; or

(ii)	to
			be left blank for a legacy FSTD.

Note:
			If the feature CLH reflects flight controls at different fidelity
			levels, the highest fidelity level is entered for the feature CLH
			and marked with an asterisk (*). A remark should be added that not
			all flight control forces and hardware are simulated and/or at the
			same fidelity level.
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
In
			cases it is applicable, identification of each flight control not
			meeting the highest fidelity level of the feature CLH and
			description of the actual fidelity level of such flight control

Note:
			For FSTDs with assigned FCS, list with identification of flight
			control forces and hardware which are type-specific and generic
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9"><a name="_Hlk219212856"></a>
List
			and description of the installed primary flight controls, e.g.
			whether their forces change with flight conditions such as
			configuration or airspeed, and, at a generic level, whether they
			are reversible or irreversible.
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
List
			and description of the installed flight controls other than the
			primary ones, e.g. which of them use hardware or touchscreens
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
Information
			about aircraft make/model/series, version/revision of the
			equipment, as applicable
</td>
</tr>
<tr valign="top">
<td bgcolor="#808080" rowspan="2">
Section
			2

Feature
			3: Flight control systems operation (CLO)
</td>
<td bgcolor="#d9d9d9">
In
			the cell that contains the instruction ‘[Indicate
			the fidelity level (S, R, G or N) or leave blank for a legacy
			FSTD]’, for the ‘CLO’
			feature:

(i)	indication
			of the applicable fidelity level (S, R, G, N) for an FSTD with FCS
			or with assigned FCS; or

(ii)	to
			be left blank for legacy FSTD.
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
Description
			of the flight control system operation, including a high-level
			overview (e.g. for type-specific: the simulated aircraft variant
			and flight control data revision; for generic: whether the system
			is conventional or fly-by-wire) and what is simulated (e.g. for
			type-specific: the flight control data revision; for generic
			fly-by-wire systems: details on simulated system operation modes
			and flight and manoeuvre envelope protection functions).
</td>
</tr>
<tr valign="top">
<td bgcolor="#808080" rowspan="6">
Section
			2

Feature
			4: Aircraft systems (SYS)
</td>
<td bgcolor="#d9d9d9">
In
			the cell that contains the instruction ‘[Indicate
			the fidelity level (S, R, G or N) or leave blank for a legacy
			FSTD]’, for the ‘SYS’
			feature:

(i)	indication
			of the applicable fidelity level (S, R, G, N) for an FSTD with FCS
			or with assigned FCS; or

(ii)	to
			be left blank for a legacy FSTD.

Note:
			In cases the feature SYS reflects aircraft systems that are at
			different fidelity levels or may be not installed at all, the
			highest fidelity level is entered for the feature SYS and marked
			with an asterisk (*). A remark should be added that not all
			aircraft systems are simulated and/or at the same fidelity level.
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
A
			list of all installed aircraft systems

The
			information can be structured according to the applicable Air
			Transport Association (ATA) chapters if deemed beneficial.
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
Where
			applicable, identification of each aircraft system not meeting the
			highest fidelity level of the feature SYS and description of the
			actual fidelity level of such system

Note:
			For FSTDs with assigned FCS, list with identification of aircraft
			systems which are type-specific and generic
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
Summary
			of avionics system versions and the fidelity level

For
			the generic aircraft systems, adequate information should be
			provided on the simulated characteristics and capabilities (e.g.
			modes of an autopilot system).

For
			the aircraft systems simulating a certain aircraft type, part or
			system version, the simulated system should be identified by
			using, for example, ‘part number’ or ‘revision’. The
			provided information should enable users to verify whether the
			simulated system configuration corresponds to a particular
			aircraft standard or modification state (e.g. as required by an
			airworthiness directive or service bulletin), as identified by the
			relevant revision or part number.
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
Identification
			of the OEM reference documentation (e.g. AFM, RFM, pilot’s
			operating handbook, FCOM, etc.), including the applicable
			revision, for any modelled aircraft system based on such
			documentation. This is particularly necessary where the simulated
			aircraft is based upon a specific tail number or does not
			correspond to the latest revision of the OEM documentation
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
Identification
			of approach capabilities

(i)	If
			an approach capability has lowered minima declared, due to the use
			of some special equipment, that equipment should also be specified
			in support of the declaration (e.g. CAT III RVR 75m - No DH
			because of HUD/HUGS/PVD/EVS, etc.)

(ii)	If
			any approach capability is limited to a particular
			airport/approach, that limitation should be included, e.g. RNP AR
			APCH ‘Limited to VNKT RNP Z RWY 02 (AR)’.

(iii)	If
			an approach capability is declared without any known limitation,
			it is assumed that the capability can be demonstrated and used at
			all operating sites without limitation. This should be
			substantiated by appropriate sample testing described in the
			organisation’s management system.

(iv)	Any
			additional PBN capabilities can be mentioned (e.g. ‘Oceanic L1
			RNP 4’) if supporting features and equipment have been validated
			to support those capabilities.
</td>
</tr>
<tr valign="top">
<td bgcolor="#808080" rowspan="2">
Section
			2

Feature
			5: Performance and handling on ground (GND)
</td>
<td bgcolor="#d9d9d9">
In
			the cell that contains the instruction ‘[Indicate
			the fidelity level (S, R, G or N) or leave blank for a legacy
			FSTD]’, for the ‘GND’
			feature:

(i)	indication
			of the applicable fidelity level (S, R, G, N) for an FSTD with FCS
			or with assigned FCS; or

(ii)	to
			be left blank for a legacy FSTD.
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
Description
			of the simulated aircraft and model (type and variant, type or
			group of aircraft), including any applicable limitations (e.g.
			differences, having an impact on training, testing or checking,
			between the simulation and the simulated aircraft)
</td>
</tr>
<tr valign="top">
<td bgcolor="#808080" rowspan="2">
Section
			2

Feature
			6: Performance and handling in-ground effect (IGE)
</td>
<td bgcolor="#d9d9d9">
In
			the cell that contains the instruction ‘[Indicate
			the fidelity level (S, R, G or N) or leave blank for a legacy
			FSTD]’, for the ‘IGE’
			feature:

(i)	indication
			of the applicable fidelity level (S, R, G, N) for an FSTD with FCS
			or with assigned FCS; or

(ii)	to
			be left blank for a legacy FSTD.
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
Description
			of the simulated aircraft and model (type and variant, type or
			group of aircraft), including any applicable limitations (e.g.
			differences, having an impact on training, testing or checking,
			between the simulation and the simulated aircraft)
</td>
</tr>
<tr valign="top">
<td bgcolor="#808080" rowspan="3">
Section
			2

Feature
			7: Performance and handling out-of-ground effect (OGE)
</td>
<td bgcolor="#d9d9d9">
In
			the cell that contains the instruction ‘[Indicate
			the fidelity level (S, R, G or N) or leave blank for a legacy
			FSTD]’, for the ‘OGE’
			feature:

(i)	indication
			of the applicable fidelity level (S, R, G, N) for an FSTD with FCS
			or with assigned FCS; or

(ii)	to
			be left blank for a legacy FSTD.
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
Description
			of the simulated aircraft and model (type and variant, type or
			group of aircraft), including any applicable limitations (e.g.
			differences, having an impact on training, testing or checking,
			between the simulation and the simulated aircraft)
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
Identification
			whether the FSTD is approved for approach to stall or full/post
			stall and any information or limitations relating to UPRT
			specifics
</td>
</tr>
<tr valign="top">
<td bgcolor="#808080" rowspan="2">
section
			2

Feature
			8: Sound cueing (SND)
</td>
<td bgcolor="#d9d9d9">
In
			the cell that contains the instruction ‘[Indicate
			the fidelity level (S, R, G or N) or leave blank for a legacy
			FSTD]’, for the ‘SND’
			feature:

(i)	indication
			of the applicable fidelity level (S, R, G, N) for an FSTD with FCS
			or with assigned FCS; or

(ii)	to
			be left blank for a legacy FSTD.
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
Source
			of the simulation model (simulated aircraft type, variant or group
			of aircraft), data/revision where applicable and a basic hardware
			description
</td>
</tr>
<tr valign="top">
<td bgcolor="#808080" rowspan="2">
Section
			2

Feature
			9: Vibration cueing (VIB)
</td>
<td bgcolor="#d9d9d9">
In
			the cell that contains the instruction ‘[Indicate
			the fidelity level (S, R, G or N) or leave blank for a legacy
			FSTD]’, for the ‘VIB’
			feature:

(i)	indication
			of the applicable fidelity level (S, R, G, N) for an FSTD with FCS
			or with assigned FCS; or

(ii)	to
			be left blank for a legacy FSTD.
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
Source
			of the simulation model (simulated aircraft type, variant or group
			of aircraft), data/revision and degrees of freedom if a separate
			vibration platform/seat is installed
</td>
</tr>
<tr valign="top">
<td bgcolor="#808080" rowspan="2">
Section
			2

Feature
			10: Motion cueing (MTN)
</td>
<td bgcolor="#d9d9d9">
In
			the cell that contains the instruction ‘[Indicate
			the fidelity level (S, R, G or N) or leave blank for a legacy
			FSTD]’, for the ‘MTN’
			feature:

(i)	indication
			of the applicable fidelity level (S, R, G, N) for an FSTD with FCS
			or with assigned FCS; or

(ii)	to
			be left blank for a legacy FSTD.
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
Technology
			used, the revision of the model data, degrees of freedom, motion
			type and stroke length, as applicable
</td>
</tr>
<tr valign="top">
<td bgcolor="#808080" rowspan="2">
Section
			2

Feature
			11: Visual cueing (VIS)
</td>
<td bgcolor="#d9d9d9">
In
			the cell that contains the instruction ‘[Indicate
			the fidelity level (S, R, G or N) or leave blank for a legacy
			FSTD]’, for the ‘VIS’
			feature:

(i)	indication
			of the applicable fidelity level (S, R, G, N) for an FSTD with FCS
			or with assigned FCS; or

(ii)	to
			be left blank for a legacy FSTD.
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
Display
			type (e.g. collimated film, collimated mirror, 10 ft Dome, etc.),
			field of view, projector technology, and any other attributes of
			the visual system or specific capabilities

Note:
			The contents of the visual databases/models should not be included
			under this feature (See feature OST below).
</td>
</tr>
<tr valign="top">
<td bgcolor="#808080" rowspan="2">
Section
			2

Feature
			12: Navigation (NAV)
</td>
<td bgcolor="#d9d9d9">
In
			the cell that contains the instruction ‘[Indicate
			the fidelity level (S, R, G or N) or leave blank for a legacy
			FSTD]’, for the ‘NAV’
			feature:

(i)	indication
			of the applicable fidelity level (S, R, G, N) for an FSTD with FCS
			or with assigned FCS; or

(ii)	to
			be left blank for a legacy FSTD.
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
Coverage
			of geographical areas where navigation aids are simulated;

List
			of simulated navigation aids (e.g. GNSS, SBAS, VOR, DME);

Update
			frequency along with any known limitations to the use of the FSTD
			(e.g. ‘Navaid coverage only accurate within 25 nm of
			specified airport model’)
</td>
</tr>
<tr valign="top">
<td bgcolor="#808080" rowspan="4">
Section
			2

Feature
			13: Atmosphere and weather (ATM)
</td>
<td bgcolor="#d9d9d9">
In
			the cell that contains the instruction ‘[Indicate
			the fidelity level (S, R, G or N) or leave blank for a legacy
			FSTD]’, for the ‘ATM’
			feature:

(i)	indication
			of the applicable fidelity level (S, R, G, N) for an FSTD with FCS
			or with assigned FCS; or

(ii)	to
			be left blank for a legacy FSTD.
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
All
			environment-related capabilities of the device, useful to the
			users of the device, paying attention to any peculiarities of the
			FSTD
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
Summary
			regarding the icing model, based on the statement of
			justification/statement of compliance, described in the MQTG
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
Runway
			contaminants, if applicable
</td>
</tr>
<tr valign="top">
<td bgcolor="#808080" rowspan="2">
Section
			2

Feature
			14: Operating sites and terrain (OST)
</td>
<td bgcolor="#d9d9d9">
In
			the cell that contains the instruction ‘[Indicate
			the fidelity level (S, R, G or N) or leave blank for a legacy
			FSTD]’, for the ‘OST’
			feature:

(i)	indication
			of the applicable fidelity level (S, R, G, N) for an FSTD with FCS
			or with assigned FCS; or

(ii)	to
			be left blank for a legacy FSTD.
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
List
			of installed visual databases including specific capabilities

Visual
			database revision numbers should not be included on the ESL. The
			ESL should not require a new revision when a visual database is
			replaced or removed.

The
			addition of a new visual database or a visual model should only
			warrant an update to the ESL if a new or amended capability is
			being declared. This would generally be visual databases which
			would be used to support a specific training scenario.
</td>
</tr>
<tr valign="top">
<td bgcolor="#808080">
Section
			3 ‘Miscellaneous’
</td>
<td bgcolor="#d9d9d9">
Any
			other information useful to the users of the device which is not
			tied to any of the above features.

Such
			information may include but is not limited to:

(i)	the
			‘Malfunction document’ revision should be specified to ensure
			that all users use the most up-to-date document. If a system is in
			place for update of the malfunction document and this necessitates
			regular updates of the ESL, such updates of the ESL can be
			omitted, but an alternative method of keeping all users informed
			should be employed. A similar approach could be taken to the
			instructor operating station (IOS) user manuals or other relevant
			documents;

(ii)	any
			additional capabilities (e.g. debriefing tools, lesson plan
			tools);

(iii)	SATCE
			and its available real-time exercise scenarios, if such capability
			is simulated on the FSTD. The capability and equipment, supporting
			the SATCE may be listed in the ESL provided that it is indicated
			as additional equipment as referred to point <a href="#_DxCrossRefBm2072462880">ORA.FSTD.120</a>(d)
			outside the scope of the FSTD qualification.
</td>
</tr>
</table>

(b) For each capability entered in the ESL, the
organisation operating the FSTD should specify, for each affected
FSTD feature, the equipment and systems that support the validation
of that capability. For readability of the ESL, these may be
summarised as a single entry under the feature that is most
appropriate for the capability.

A capability should only be entered in the ESL,
when all elements required to support that capability have been
validated by the organisation operating the FSTD. Entering a
capability in the ESL is a declaration that its validation has been
completed.

Example 1: Simulation of an RNP AR APCH is
supported by the FSTD features ‘Operating sites and Terrain’ for
the visual scene and terrain modelling, ‘Aircraft systems’ for
the aircraft’s approach and navigation capabilities, ‘Navigation’
for the simulation of navigation aids, and ‘Visual cueing’ for
the image display qualities. To enter an RNP AR APCH in the ESL, all
of these elements should be validated and referenced in the ESL
entry.

Example 2: Simulation of runway contaminant
(e.g. snow on the runway) is supported by the FSTD features
‘Atmosphere and weather’ for the environmental controls,
‘Performance and handling on ground’ for the stopping and
directional performance and handling characteristics, ‘Operating
sites and Terrain’ for the visual presentation of the runway
contaminant, and ‘Visual cueing’ for the image display qualities.
To enter runway contaminant in the ESL, all of these elements should
be validated and referenced in the ESL entry.

(c) Information about aircraft make/model,
version/revision of the equipment under each feature should be
included, if relevant for the applicable feature.

(d) Where the ESL refers to a group of
aircraft, it should specify the group with sufficient detail (e.g.
jet aeroplanes with swept wings) to facilitate understanding of the
expected performance and handling qualities. This is of particular
importance for the FSTD features ‘GND’, ‘IGE’ and ‘OGE’.

(e) If the feature is not installed, functional
or available, the feature is considered to have fidelity level ‘N’
and it is not necessary for the ESL to provide information for that
feature.

(f) The ESL should only include entries for
capabilities which exist in the FSTD. It is not necessary to enter a
capability, followed by the word – ‘No’ or ‘N/A’.

(g) Equipment as referred to point
ORA.FSTD.120(d) may be listed in the ESL provided that it is clearly
indicated as additional equipment outside the scope of the FSTD
qualification.

(h) The ESL should be signed by the person of
the organisation operating the FSTD nominated in accordance with
point [ORA.GEN.210](#_DxCrossRefBm2072463002)(b)
or his or her delegate.

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