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.
Two people in the pilot seats of a SkyDynamics Airbus A320 FNPT II, flying over the sea in daylight

FCS++

FSTD Capability Signature · Regulation (EU) 2026/781

FCS++ maps every training task. To the FSTD that can credit it.

FCS++ records each simulator's Capability Signature, compares it with what your training programme requires and shows which lessons each device can credit. With FSTDMS it is also the FSTD management platform, under Regulation (EU) 2026/781. Your device data and documents are held in data centres in Switzerland.

  • Topproduct

  • Mostinnovative

  • Highassurance

In 60 seconds

Three questions. Answered for every device you operate.

  • What can this device do?

    Its Capability Signature: 14 features, each at a stated fidelity, with the evidence behind every level.

  • What does this lesson need?

    The fidelity each training task requires, feature by feature: the training signature. A type rating session, an instrument rating lesson and an MCC exercise each ask for something different.

  • Where is the gap?

    Device against task, before you schedule the session and before the authority asks.

Why FCS++

FSTD certification software. Built around the Capability Signature, not added to it.

FCS++ is SkyDynamics software for FSTD certification and management: the evidence the competent authority evaluates and the working record of each device, on one record, for any FSTD from any manufacturer.

How FCS++ comparesFour approaches to FSTD certification and management, and eight questions for any supplier.
  • The signature is the record

    Each device is described by its 14-feature Capability Signature, with the qualification certificate, the ESL, the QTG results and the statements of justification linked to every level.

  • Task-to-tool on every lesson

    The fidelity each training task needs is checked against each device before the session is scheduled, with the rule cited (FCL.036, GM1 ORO.FC.145).

  • A rule on every entry

    Each maintenance action and change is shown with the rule it falls under (ORA.FSTD.105, ORA.FSTD.110) and the features it can affect.

  • QTG runs kept as evidence

    The QTG tool runs the objective tests on FlightGear, X-Plane or Prepar3D (P3D) and keeps every result in the QTG history of the device.

  • Written by an FSTD manufacturer

    SkyDynamics builds FNPT II (FNPT 2) simulators for A320, B737, Q400, SEP IR and MEP IR training and prepares them for evaluation by the competent authority.

  • AI-assisted, never steering

    FCS++ documents and checks. The qualification decision stays with the competent authority and the people accountable for the device.

Regulation (EU) 2026/781

Four dates. From device levels to a Capability Signature per device.

FSTD qualification moves from device types and levels (FFS A to D, FTD, FNPT) to a Capability Signature per device. Legacy devices can keep their type and level, or opt in to an assigned or evaluated signature.

: the Regulation applies

  1. In force

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

  2. The Regulation applies

    New qualifications are issued with a Capability Signature.

  3. Equipment Specification List

    An Equipment Specification List (ESL) is submitted for every device, except BITDs.

  4. Certificates reissued

    Competent authorities have reissued all FSTD qualification certificates in the new format.

The signature, explained

14 features. Four fidelity levels. One rule. A device credits a task only when it meets every level the task needs.

A Capability Signature describes how faithfully a device reproduces each of 14 simulation features, at one of four levels: Specific (the type and variant), Representative (the type), Generic (the class) or None. A training task can be credited on a device only when the device meets or exceeds the required level on every feature that task needs.

  • Flight deck · Control forces · Control systems · Aircraft systems
  • Ground handling · In ground effect · Out of ground effect
  • Sound · Vibration · Motion · Visual
  • Navigation · Atmosphere and weather · Operating sites and terrain
  • Data caps the level: if validation data only supports Representative, the feature is Representative, whatever the hardware can do.
  • Generic is a higher bar than legacy FNPT II on several features. Existing FNPT II documentation needs a gap check, not a relabel.
Capability SignatureSRGNFDKCLHCLOSYSGNDIGEOGESNDVIBMTNVISNAVATMOSTEVIDENCEDevice 1FNPT IIMCCLegacyAssignedQualifiedEvidence behind each levelQTGValidation dataStatement of justificationAI-assisted review · you set the level
The Capability Signature matrix for one device.Illustrative

Task-to-tool

Task to tool. From the training objective to the device approved for it.

Qualification says a device meets a standard. Approval says this device is adequate for these tasks (GM1 ORO.FC.145). FCS++ keeps both on one screen.

  1. Training objective

    From your type rating, instrument rating, MCC, recurrent or EBT programme.

  2. Training task

    Each lesson item, flagged Training or Training-to-Proficiency.

  3. Required fidelity

    The features and level each task needs: the training signature.

  4. Compare

    Device signature against training signature, feature by feature, with the rule cited.

  5. Evidence

    Qualification certificate, ESL, QTG and statements of justification linked to each feature.

  6. Approval

    Device list for Operations Manual Part D, ready for authority acceptance.

Illustrative example

Can this device credit this lesson?

Pick a training task and a device to see the first-pass comparison FCS++ performs, feature by feature. These values are illustrative and are not a regulatory determination for any real device or task.

Every feature meets or exceeds what the task requires.

On a real device this is where the evidence behind each level (QTG, validation data and statements of justification) is checked before the task is credited.

Feature-by-feature comparison of FNPT II MCC, jet flight deck (illustrative) against MCC line-oriented flight training
FeatureTask needsDevice hasResult
Flight deck (FDK)RR Meets
Control forces (CLH)GG Meets
Control systems (CLO)GR Meets
Aircraft systems (SYS)RR Meets
Ground handling (GND)GG Meets
In ground effect (IGE)GG Meets
Out of ground effect (OGE)RR Meets
Sound (SND)GG Meets
Vibration (VIB)NN Not required
Motion (MTN)NN Not required
Visual (VIS)GR Meets
Navigation (NAV)RR Meets
Atmosphere & weather (ATM)RR Meets
Operating sites & terrain (OST)RR Meets

Order of fidelity: S (specific) > R (representative) > G (generic) > N (none). Run this on your own fleet in an FCS readiness review.

Connected to aeroEBT

Every EBT session. On a device that can credit it.

EBT modules run on FSTDs, and different scenarios ask different things of the device: upset recovery depends on motion and vibration cueing; a low-visibility approach depends on visual and operating-site fidelity. Connected to aeroEBT, FCS++ lets your programme schedule the evaluation phase, manoeuvres training and scenario-based training on devices whose signature supports them, with the device evidence already linked to the training record. A flight school asks the same question of its FNPT II before an instrument rating lesson or an MCC session.

  • Device signatures visible to the training programme, not just engineering
  • Mixed fleets: the right device for each syllabus segment
  • One record: session, device, signature and evidence
  • On the roadmap: required-fidelity tags on Scenario Builder scenarios, checked automatically against each device
Programme suitabilityDevice 1Device 2Device 3IFR proceduresEngine failure after V1Low-visibility operationsUpset recoveryType-specific systemsLegendCan creditConditionsGapNo FCS yetWhy amber?ESL dueExplains, never decides
Which device can credit which part of the programme.Illustrative

Who it serves

One platform, three roles. Built for everyone who signs off a simulator.

  • Simulator operators, ATOs and training centres

    FSTD register, document vault (certificate, ESL, QTG, evaluation reports), signature matrix, suitability against every programme and a change timeline per device.

  • Manufacturers, integrators and suppliers

    Type templates with a factory signature baseline, hand-over to operators by serial number, and service bulletins with their feature impact. Component suppliers declare the features their products support.

  • Authorities

    Oversight relationships, ESL review, evaluation checklists with the evidence attached, and read-only change history.

Configuration control

The simulator changes. You know which features it touches.

Every change is mapped to the features it can affect, so modification decisions (ORA.FSTD.110) start from evidence, not memory.

Pick a change to see the features it can affectIllustrative

Capability Signature: 14 features

FMS or avionics software update can affect 3 of 14 features: control systems, aircraft systems, navigation.

On the roadmap: desktop companion

Detects the simulation software on the host and records changes on the timeline automatically.

FSTD management

Also an FSTD management platform. Hours, maintenance, faults and sharing, on the device record.

The Capability Signature says what a device can credit. Running the device produces the rest of its record, and FCS++ keeps that too: one file per FSTD, held in Swiss data centres, for the operator, the manufacturer and the authority.

Instructor operating station of a SkyDynamics Airbus A320 FNPT II: two screens behind the pilot seats, with the flight deck and the visual system beyond
FSTDMS: the FSTD management systemHours, maintenance, live monitoring, over-the-air updates and the rules behind each entry.

QTG tool

A QTG tool. For any aircraft category and any manufacturer.

The FCS++ QTG tool runs the objective tests of the Qualification Test Guide (QTG) on the device and keeps every result in the device file. It is compatible with any aircraft category and any manufacturer, on three simulation platforms: FlightGear, X-Plane and Lockheed Martin Prepar3D (P3D).

  • Test packs per aircraft type

    Tests, procedures, checkpoints, recorded parameters and tolerances for the aircraft the device represents, matched to the device and its platform before a run starts.

  • Automated runs

    The tool flies each test, records the parameters and marks the result against its tolerance: match or no match. One test or a queue of them.

  • Results kept as evidence

    Every run is stored in the QTG history of the device and linked to the feature it supports in the Capability Signature. A failed test raises a notification.

  • Evidence, not qualification

    QTG results support the evaluation. The competent authority evaluates and qualifies the device.

Data security and residency

Your FSTD data, held in Switzerland. Device records, documents and QTG results in Swiss data centres.

Everything FCS++ keeps for a device (the qualification certificate, the Equipment Specification List, QTG results, the maintenance history and the change timeline) is stored in data centres in Switzerland.

  • Company data is held under the revised Swiss Data Protection Act (revFADP). Personal data is processed in the EU, where the GDPR applies in full.

  • Device records and documents are stored in data centres in Switzerland, encrypted in transit and at rest.

  • For defence and regulated operators, an on-premises or air-gapped deployment keeps data inside your own perimeter.

  • Role-based access, and evidence shared with an authority only when you grant it.

Pick a point to mark it in the diagram.

Legacy devices

Stay legacy, or opt in. A transition path for every device you already operate.

Adopting a Capability Signature is not forced on legacy devices: an FNPT II used for instrument rating and MCC training can keep its type and level. Two things are required of every operator: an Equipment Specification List by 30 April 2029 (BITDs excepted) and the certificate reissued by 30 October 2029. FCS++ shows the options for each device and the evidence each needs.

  • Stay legacy

    Keep the current type and level, with no change to how the device is used for training.

  • Assigned signature, no evaluation

    Only for devices on a listed primary reference document, without limitation.

  • Assigned signature, after evaluation

    For devices that are not on those reference documents.

  • Evaluated signature

    A full evaluation determines the actual signature, often broader credit than the legacy level.

  • Dual-qualified devices

    Remain legacy, or opt in for one merged signature.

  • Exceptions

    FTD 1: evaluated signature only. BITD: out of scope, three-yearly recurrent evaluation retained.

What FCS++ is. And what it is not.

  • It documents and checks

    FCS++ documents device capability and checks training suitability, citing the rule behind every comparison.

  • It does not decide

    It does not replace your authority's evaluation or decision, and it does not claim automated CS-FSTD compliance. Engineering judgement, waivers and on-site evaluation stay with the people accountable for them.

Rules tracked in the product. A reference library, not a list of approvals.

In-app citations and rules are drawn from a maintained regulatory corpus. EASA leads; other frameworks are tracked as they converge on task-to-tool. Listing a rule set here implies no approval, recognition or endorsement of FCS++ by that authority.

  • EASAReg. (EU) 2026/781, CS-FSTD
  • ICAODoc 9625
  • FAA14 CFR Part 60
  • UK CAA
  • Transport Canada
  • CASA
  • GACA
  • DGCA
  • CAAC

FCS++: questions operators and authorities ask

FCS++, from SkyDynamics, is software for FSTD certification and management under Regulation (EU) 2026/781 and CS-FSTD Issue 1. It records the FSTD Capability Signature of each device with the evidence behind every level (qualification certificate, Equipment Specification List, QTG results, statements of justification), checks which training tasks each device can credit (task-to-tool), keeps QTG runs as evidence and, in FSTDMS, the working record of the device: hours, maintenance, faults and live monitoring. It works with any FSTD from any manufacturer: FNPT II (FNPT 2), FTD and full flight simulators. The competent authority evaluates and qualifies the device.

Yes. The FCS++ QTG tool runs the objective tests of the Qualification Test Guide (QTG) on the device, records the parameters, marks each result against its tolerance and keeps every run in the QTG history of the device, linked to the Capability Signature feature it supports. It works for any aircraft category and any manufacturer on FlightGear, X-Plane and Lockheed Martin Prepar3D (P3D). QTG results support the evaluation; the competent authority qualifies the device.

The competent authority evaluates the FNPT II (FNPT 2) and issues its qualification certificate. An existing FNPT II can keep its type and level, or opt in to an assigned or evaluated Capability Signature. Every operator submits an Equipment Specification List by 30 April 2029, and certificates are reissued in the new format by 30 October 2029. FCS++ shows the path for each device and the evidence it needs; how SkyDynamics prepares its own FNPT II devices for evaluation is on https://skydynamics.aero/flight-simulators

Spreadsheets and general maintenance software track hours, intervals and files. FCS++ also knows what each device is qualified for: the Capability Signature, task-to-tool, the rule behind each maintenance action and change, and the QTG history. The comparison guide sets four approaches side by side and lists eight questions to ask any supplier: https://skydynamics.aero/fcs/how-fcs-compares

Yes. FCS++, from SkyDynamics, is software built around the FSTD Capability Signature of Regulation (EU) 2026/781. It records the signature of each device (14 features, each at a stated fidelity, with the evidence behind every level), compares it with the fidelity each training task requires (task-to-tool) and shows the gap before a session is scheduled. It works with any FSTD from any manufacturer, and it also keeps the working record of the device: hours, maintenance, documents and QTG history.

People use it for the qualification of a flight simulation training device under the FSTD Capability Signature. In the rules the word is qualification: the competent authority evaluates the device and issues its qualification certificate, and from 30 April 2028 new qualifications are issued with a Capability Signature. FCS++ organises what that evaluation looks at: the signature feature by feature, the qualification certificate, the Equipment Specification List (ESL), the QTG results and the statements of justification.

Yes. Legacy devices can keep their type and level. Operators can also opt in to an assigned or evaluated Capability Signature; FCS++ shows which path fits each device and what evidence it needs.

An assigned signature comes from the equivalence tables for legacy devices, with or without an evaluation depending on the device. An evaluated signature is determined by a full evaluation of the device and can give broader training credit.

No. The competent authority evaluates and qualifies the device. FCS++ organises the signature, the evidence and the suitability check, and can share them with the authority when you grant access.

A device we describe as FCS ready has its capability documented feature by feature, with the evidence behind each fidelity level (qualification certificate, ESL, QTG and statements of justification) linked to it. It describes the state of the documentation. It is not a qualification status: the competent authority evaluates and qualifies the device.

The primary use case is type-rating training. Operator recurrent training can use it where the operator applies the framework (GM1 ORO.FC.145). Connected to aeroEBT, the programme sees which devices support each EBT module.

Any FSTD, any manufacturer. The signature describes the device, not the software it runs on. The QTG tool runs on FlightGear, X-Plane and Lockheed Martin Prepar3D (P3D), for any aircraft category.

Yes. Next to the Capability Signature, FCS++ keeps the working record of each device: hours tracked automatically, maintenance intervals with due and overdue notifications, fault and configuration logs, the document vault, licences and the QTG history. The operator can share that record with the manufacturer and with the competent authority. The management system is called FSTDMS and has its own page.

In data centres in Switzerland. Device records and documents (the qualification certificate, ESL, QTG results and maintenance history) are held there under Swiss data-protection law; personal data is processed in the EU under the GDPR. On-premises deployment is available.

A 45-minute readiness review: we go through your devices, their current qualification and your programmes, and show the transition path for each device.

Know which lessons each of your devices can credit, before 2028.

In a 45-minute readiness review we map your devices and programmes to the Capability Signature and show the transition path for each device.

We respond within one business day.