FSTD Capability Signature · Regulation (EU) 2026/781
Map every training task to the device that can credit it.
FCS++ records each simulator's Capability Signature (14 features, each at Specific, Representative, Generic or None fidelity) compares it with what your training programme requires, and shows which lessons each device can credit before you schedule them. Built for FSTD operators, manufacturers and authorities moving to Regulation (EU) 2026/781.
In 60 seconds
Three questions FCS++ answers 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.
Where is the gap?
Device against task, before you schedule the session and before the authority asks.
Regulation (EU) 2026/781
What changes, and when
FSTD qualification moves from device types and levels (FFS A–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 signature, explained
14 features. Four fidelity levels. One rule.
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.
Task-to-tool
From training task to approved device
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, 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 | Task needs | Device has | Result |
|---|---|---|---|
| Flight deck (FDK) | R | R | Meets |
| Control forces (CLH) | G | G | Meets |
| Control systems (CLO) | G | R | Meets |
| Aircraft systems (SYS) | R | R | Meets |
| Ground handling (GND) | G | G | Meets |
| In ground effect (IGE) | G | G | Meets |
| Out of ground effect (OGE) | R | R | Meets |
| Sound (SND) | G | G | Meets |
| Vibration (VIB) | N | N | Not required |
| Motion (MTN) | N | N | Not required |
| Visual (VIS) | G | R | Meets |
| Navigation (NAV) | R | R | Meets |
| Atmosphere & weather (ATM) | R | R | Meets |
| Operating sites & terrain (OST) | R | R | 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.
- 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
The product
Four screens, one device file
From registering a device to sharing the evidence with your authority.
Register
Add the device with its current qualification, configuration and documents.
Step 1 of 4
Signature
Set or review the fidelity of each of the 14 features, with the evidence attached to each one.
Step 2 of 4
Compare
Check the device against what your training programme requires and see the gaps.
Step 3 of 4
Share
Produce the Equipment Specification List and share the evidence with your authority when you choose to.
Step 4 of 4
One platform, three roles
Built for everyone who signs off a simulator
Simulator operators & 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 & 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
When the simulator changes, you know what it touches
Every change is mapped to the features it can affect, so modification decisions (ORA.FSTD.110) start from evidence, not memory.
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.
Legacy devices
A transition path for every device you already operate
Adopting a Capability Signature is not forced on legacy devices. FCS++ shows the options for each one 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
FCS++ documents device capability and checks training suitability, citing the rule behind every comparison. 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.
Regulatory library
In-app citations and rules drawn from a maintained regulatory corpus. EASA leads; other frameworks are tracked as they converge on task-to-tool.
- EASAReg. (EU) 2026/781, CS-FSTD
- ICAODoc 9625
- FAA14 CFR Part 60
- UK CAA
- Transport Canada
- CASA
- GACA
- DGCA
- CAAC
Data security & residency
Your qualification evidence, under the law that protects it most
Company data in Switzerland
Stored in Swiss infrastructure under the revised Swiss Data Protection Act (revFADP).
Personal data under EU GDPR
Processed in Greece (EU), where the GDPR applies in full.
Access you control
Encrypted in transit and at rest, role-based access, and evidence shared with an authority only when you grant it.
On-premises option
For defence and regulated operators, an on-premises or air-gapped deployment keeps data inside your own perimeter.
FCS++: questions operators and authorities ask
Is my FNPT II still usable after 30 April 2028?
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.
What is the difference between an assigned and an evaluated signature?
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.
Does FCS++ qualify the device or submit to the authority for us?
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.
Can the Capability Signature be used for EBT recurrent training?
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.
Which simulators does it work with?
Any FSTD, any manufacturer. The signature describes the device, not the software it runs on.
Where is our data stored?
Company data in Switzerland under Swiss data-protection law; personal data in the EU (Greece) under the GDPR. On-premises deployment is available.
How do we start?
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.