Skip to main content
Instructor operating station of a SkyDynamics Airbus A320 FNPT II: two screens behind the pilot seats with the flight deck and visual system beyond.
Overhead panel of a SkyDynamics Airbus A320 FNPT II flight simulator

FSTD transition hub

Regulation (EU) 2026/781, the EASA FSTD rule. What every FSTD operator must do before 2029.

Commission Implementing Regulation (EU) 2026/781 adds the FSTD Capability Signature for new qualifications from 30 April 2028. Legacy devices can keep their type and level. Here are the dates, the obligations by operator type and a readiness checklist.

The dates that matter

Four dates. April 2026 to October 2029.

: the Regulation applies

  1. In force

    Regulation (EU) 2026/781 enters into force, with CS-FSTD Issue 1 and the related AMC and GM (ED Decision 2026/006/R).

  2. The Regulation applies

    New qualifications are issued with a Capability Signature, and the task-to-tool method applies to type-rating and operator recurrent training.

  3. Equipment Specification List

    An Equipment Specification List has been submitted for every device except BITDs.

  4. Certificates reissued

    Competent authorities have reissued every FSTD qualification certificate in the new template.

The dates are those of Commission Implementing Regulation (EU) 2026/781 and ED Decision 2026/006/R, listed under the sources on this page.

What changes

From level to capability. The question is no longer what level a simulator is, but which training tasks it can credit.

New qualifications from 30 April 2028 carry a Capability Signature. Legacy devices can keep their type and level.

  • Tool-to-task becomes task-to-tool

    Training tasks determine the fidelity a device must provide, instead of the device level determining what may be trained on it.

  • 14 features, four fidelity levels

    Each device is described feature by feature at Specific, Representative, Generic or None fidelity.

  • Assigned signatures for legacy devices

    Existing devices can keep their type and level, or take an assigned or evaluated signature through the equivalence route.

  • The Equipment Specification List

    The ESL becomes the central document describing the device configuration, maintained by the operator.

Who must act

This reaches you. If you operate, build or oversee an FSTD.

  • Airline FSTD operators

    Full flight simulators and FTDs used for type rating and recurrent training: ESL, configuration control and certificate reissue.

  • ATOs with FNPT II and MCC devices

    Decide per device whether to stay legacy or opt in, and check which training your device can credit either way.

  • FSTD manufacturers and integrators

    Deliver devices with a defensible feature profile and the engineering evidence behind each fidelity level.

  • Competent authorities

    Evaluate, assign or reissue signatures and process ESL submissions across the fleet they oversee.

For flight schools

Buying an FNPT II before 2028. What happens to it when the Regulation applies.

An FNPT II qualified before 30 April 2028 is an existing device on the day the Regulation applies. This is what this page says about existing devices. Confirm the route for your own device with your competent authority.

  • It is qualified by type and level

    New qualifications are issued with a Capability Signature from 30 April 2028, the date the Regulation applies.

  • It can keep its type and level

    Adopting a Capability Signature is not forced on legacy devices. An existing device can keep its type and level, or opt in to an assigned or evaluated signature.

  • Two obligations still apply

    An Equipment Specification List by 30 April 2029, and the qualification certificate reissued by 30 October 2029.

  • Check what it can credit

    Either way, check which training the device can credit. Existing FNPT II documentation needs a gap check, not a relabel.

Readiness

Six steps. A practical sequence to be ready before 2029.

Every EU FSTD operator works to the same 2029 dates, and a device that opts in after an evaluation needs time with its authority. An early start leaves room to plan it.

  1. Inventory

    List every device, its current qualification, its configuration and its planned life.

  2. Feature gap

    Describe each device feature by feature and note where the evidence is thin.

  3. Data and QTG review

    Check which validation data supports which fidelity level: data caps the level you can claim.

  4. Draft the signature and ESL

    Produce a draft signature and the Equipment Specification List for each device.

  5. Authority dialogue

    Agree the route per device with your authority: stay legacy, assigned or evaluated.

  6. Reissue and maintain

    Complete the certificate reissue and keep the signature current as the device changes.

Readiness self-check

Where does your fleet stand?

Eight statements. Answer honestly for the fleet as a whole. Your answers stay in this browser: nothing is sent, stored or shared.

  1. We have a current inventory of every FSTD we operate, with its qualification status.
  2. We know, per device, whether we will stay legacy or opt in to a Capability Signature.
  3. We can describe each device feature by feature, not only by its type and level.
  4. We know which validation data supports which fidelity level for each feature.
  5. Our QTG and MQTG documentation is current and retrievable per device.
  6. We have started, or scheduled, the Equipment Specification List for each device.
  7. We have discussed the transition route per device with our competent authority.
  8. We know which training tasks each device is used for, and which it must be able to credit.
0 of 8 answered

Regulation (EU) 2026/781: questions operators ask

The FSTD Capability Signature (FCS) is how Regulation (EU) 2026/781 describes what a flight simulation training device can do. A device is no longer summed up by one type and level (FFS A to D, FTD, FNPT): it is described by 14 simulation features, each at Specific, Representative, Generic or None fidelity. A training task is credited on a device only when the device meets the fidelity that task needs, which is the task-to-tool method. New qualifications are issued with a Capability Signature from 30 April 2028; legacy devices can keep their type and level.

Yes. Adopting a Capability Signature is not forced on legacy devices: they can keep their existing type and level. What every operator must do is submit an Equipment Specification List by 30 April 2029 (BITDs excepted) and have the certificate reissued by 30 October 2029.

It is the signature a legacy device receives from the equivalence tables rather than from a full evaluation. Devices listed on a primary reference document without limitation can take it without an evaluation; others need one first.

Not automatically. The question is whether your existing validation data supports the fidelity level you want to claim for each feature, because the data caps the level. A gap analysis comes before any new testing.

The Regulation binds EU operators and devices. It matters elsewhere because ICAO Doc 9625 introduced the same task-to-tool approach and other authorities are moving in the same direction, and because training for EU licences is affected.

They can remain legacy or opt in for one merged signature. FTD 1 devices can only take an evaluated signature, and BITDs stay outside the framework with their three-yearly recurrent evaluation.

With an inventory and a feature-by-feature gap check per device. FCS++ does this and keeps the result current; a 45-minute readiness review shows where each device stands.

Find out where each of your devices stands.

A 45-minute readiness review covers your devices, their current qualification and the transition path for each one.

We respond within one business day.