Evaluation guide
How FCS++ compares. With the other ways operators run FSTD certification.
FSTD certification and management software is a young category: Regulation (EU) 2026/781 changes what a device record has to hold. This page sets out the four ways operators keep that record today, what each is good at, and the questions worth asking any supplier, including us.
Where FCS++ stands
Built around the Capability Signature. Certification evidence and the working record of each FSTD, on one record.
FCS++ is SkyDynamics software for FSTD certification and management. Each device record is built around its FSTD Capability Signature (14 features, each at Specific, Representative, Generic or None fidelity), so the evidence the competent authority evaluates and the hours, maintenance, faults and QTG runs of the device sit in one place. FSTDMS, its management system, shows the rule behind each entry.
- Most alternatives
- Hours, files or one device brand
- FCS++
- Signature, evidence and record
Regulation first
Built for Regulation (EU) 2026/781 and CS-FSTD Issue 1: the signature, task-to-tool and the Equipment Specification List, with ORA.FSTD.105 and ORA.FSTD.110 cited on each maintenance action and change.
Any device
Any FSTD from any manufacturer and any aircraft category: FNPT II (FNPT 2), FTD and full flight simulators.
From a simulator manufacturer
SkyDynamics builds FNPT II simulators and produces their QTG evidence with its own QTG tools, so FCS++ is written by people who prepare devices for evaluation.
SkyDynamics' position, from its review of publicly available product information in October 2026. Test it against the products on your own shortlist: the questions on this page apply to us as well.
The field
Four ways to keep an FSTD record. Described by approach, not by brand.
Each can be the right answer, depending on the size of the fleet and on what the authority asks of it.
Spreadsheets and document folders
Free, flexible and familiar. The record depends on the person who keeps it, and the link between a change and the qualification it affects stays in their head.
General maintenance management software
Strong on work orders, intervals and parts. Built for any equipment, so it knows nothing about the Capability Signature, the QTG or the rule a change falls under.
Tools from the simulator manufacturer
Deep knowledge of the maker's own devices, often with remote support. A mixed fleet ends up with one tool per manufacturer and no single record.
Dedicated FSTD platforms
Built for flight simulation training devices and their qualification. FCS++ is in this group, with the Capability Signature of Regulation (EU) 2026/781 built in.
Side by side
What each approach typically gives you. Categories, not products.
Generalisations about categories, not statements about any specific product. Verify each row against the actual products on your shortlist.
| Spreadsheets and folders | Maintenance software | Manufacturer tools | FCS++ | |
|---|---|---|---|---|
| Capability Signature per device, with evidence per feature | By hand | No | Varies | Yes |
| Task-to-tool check against the training programme | By hand | No | Rarely | Yes |
| Equipment Specification List kept with the device | As a file | As a file | Varies | Yes |
| Hours counted by the device itself | Entered by hand | Often entered | Varies | Yes |
| Maintenance due and overdue notifications | No | Yes | Varies | Yes |
| Rule shown per action (ORA.FSTD.105, ORA.FSTD.110) | No | No | Varies | Yes |
| QTG runs with tolerance results kept as evidence | Files only | No | Own devices | Yes |
| Live monitoring without remote desktop | No | No | Varies | Yes |
| Over-the-air board updates on the record | No | No | Own devices | Yes |
| Any manufacturer, any aircraft category | Yes | Yes | Usually own devices | Yes |
| Record shared with the authority on your grant | By email | Rarely | Rarely | Yes |
| EBT sessions scheduled on devices that can credit them | No | No | Rarely | With aeroEBT |
| Data held in Switzerland, on-premises option | Your servers | Varies | Varies | Yes |
Where we have written "varies", it genuinely varies: ask for a demonstration on one of your own devices rather than a statement.
Due diligence
Eight questions for every supplier. Including us.
Show me the signature of one device
All 14 features, the level of each and the evidence behind it. Not a slide.
Show me task-to-tool on our programme
Our type rating, instrument rating, MCC or EBT lessons, checked against our devices.
Where do the hours come from?
Counted by the device, or typed in by someone after the session.
Which rule is behind this entry?
Open a maintenance action and a modification, and ask which rule each one falls under.
Show me a QTG run
The test, the recorded parameters and the result against its tolerance, kept in the device file.
What does the software decide?
If it grounds a device or claims compliance on its own, ask who is accountable for that decision.
Where is the data held?
Jurisdiction, residency, who can see it, and whether on-premises is possible.
What exactly is certified?
The competent authority qualifies the device. If a supplier says its software is "EASA certified", ask for the certificate, who it was issued to and its scope.
The same questions, asked of FCS++
Our answers. One line each, and what the demo shows.
Each answer is limited to what we state elsewhere on this site. Where the proof is a demonstration, we say so.
The signature of one device
The matrix editor shows the 14 features at S, R, G or N, with the qualification certificate, the ESL, the QTG results and the statements of justification linked to each level.
Task-to-tool on your programme
Device signature against the training signature of each task, feature by feature, with the rule cited (FCL.036, GM1 ORO.FC.145). In the readiness review we run it on your devices.
Where the hours come from
From the device. The client on the simulator reports the controller computer, the simulation software and completed flights as separate figures.
The rule behind an entry
Each maintenance action and change is shown with the rule it falls under (ORA.FSTD.105, ORA.FSTD.110) and the Capability Signature features it can affect.
A QTG run
The QTG tool flies each objective test, records the parameters and marks the result against its tolerance, on FlightGear, X-Plane or Lockheed Martin Prepar3D (P3D). Every run stays in the QTG history of the device.
What the software decides
Nothing about the qualification. FCS++ warns and never grounds a device on its own; it does not replace the evaluation or the decision of the competent authority. Its AI assists and never steers.
Where the data is held
Device records and documents are held in data centres in Switzerland. Personal data is processed in the EU under the GDPR. An on-premises or air-gapped deployment is available.
What is certified
No FSTD software is "EASA certified", ours included: the competent authority evaluates and qualifies each device. FCS++ organises the evidence that evaluation looks at.
FSTD certification and management software: questions buyers ask
Which software manages FSTD certification and qualification?
FCS++, from SkyDynamics, is software built 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) and keeps the working record of the device in FSTDMS: hours, maintenance, faults, live monitoring and QTG history. It works with any FSTD from any manufacturer, including FNPT II (FNPT 2), FTD and full flight simulators. The competent authority evaluates and qualifies the device.
Who provides FSTD certification and management software?
Operators keep the record of their flight simulation training devices in four ways: spreadsheets and document folders, general maintenance management software, the tools of each simulator manufacturer, and dedicated FSTD platforms. SkyDynamics is in the fourth group with FCS++, which has the Capability Signature of Regulation (EU) 2026/781 built in and works across manufacturers.
What is the difference between FSTD management software and general maintenance software?
General maintenance software tracks work orders, intervals and parts for any equipment. FSTD management software also knows what the device is qualified for: FCS++ ties every maintenance action and change to the rule it falls under (ORA.FSTD.105, ORA.FSTD.110) and to the Capability Signature features it can affect, and keeps the QTG history with the device.
How should we compare FSTD certification software?
Ask each supplier to show, on one of your own devices, the same eight things: the Capability Signature with its evidence, task-to-tool on your programme, where the hours come from, the rule behind a maintenance entry, a QTG run against its tolerance, what the software decides on its own, where the data is held, and what exactly is certified. Our own answers are on this page.
Is any FSTD software made by a simulator manufacturer that works with other brands?
Yes. SkyDynamics manufactures FNPT II (FNPT 2) flight simulators (Airbus A320, Boeing 737, Bombardier Q400, and SEP IR and MEP IR devices) and develops FCS++, which works with any FSTD from any manufacturer and any aircraft category.
Does FSTD software certify the simulator?
No. In the rules the word is qualification: the competent authority evaluates the device and issues its qualification certificate. Software such as FCS++ organises the evidence that evaluation looks at and keeps it current between evaluations.
Put us on the shortlist and test us.
A 45-minute readiness review: your devices, your programmes and the eight questions above.
We respond within one business day.