Test guides, not spreadsheets.
Define each test against its reference trace, with per-channel tolerances and the governing clause attached. Versioned in the platform, not emailed around as files.
Qualification testing for FSTDs
Qualify the simulator with the discipline of the cockpit it replicates.
Wasim QTG authors, runs, and reports Qualification Test Guides for full-flight simulators and FNPT IIs against EASA CS-FSTD(A), with Part 60-formatted exports. Easier than the legacy stack it replaces: live telemetry in, a generated evidence pack out. No spreadsheets. No unsourced number on the record.
- 20 Hz
- Live telemetry · per-test configurable
- ed25519
- Signed on-sim agent updates
- 42 + 24 tests
- Certified 2012 roster + Issue 2 additions
- SHA-256
- Digest on every evidence pack
Built againstEASA · CS-FSTD(A)FAA · Part 60-formatted exports
Run-time evidence
Capture the simulator's truth, sample by sample.
Every run records against approved reference data, with per-channel tolerances checked live as the trace comes in. Operators see the deviation as it happens; regulators see the evidence pack at the end. Pass and fail are computed at completion, server-side, over the whole run.
RUN 042 · A320 FFS · LIVE14:32 UTC
Lifecycle
One platform from first issue to recurrent cycle.
Telemetry at the test's own rate.
The on-sim agent captures live telemetry over UDP, 20 Hz by default, higher where a test needs it. Deviation shows live against the reference.
Evidence packs the authority can check.
Submission-ready packs: traces, tolerance results, discrepancy notes, and a SHA-256 digest. The append-only discrepancy history travels with the pack.
Every value, sourced.
Each reading links back to the run, the operator, the reference data set, and the simulator record. Nothing floats free of its origin.
Catch drift before it becomes a finding.
A rolling 12-month window of 4 to 12 blocks, judged against the MQTG as amended. Not against a VDR you no longer hold.
MQTG revisions with a supersession chain.
Initial issue, then amendments that re-test only what changed, with per-test provenance keyed to ORA.FSTD.110(b). The MQTG stays current without a full re-run.
Both sides of the table
Less work for your operators. Faster answers for your authority.
Initial qualification and every recurrent cycle after it run on the same records. Results post as runs complete and packs generate themselves. Nothing is re-keyed into a binder the week before an evaluation.
“When the authority asks where a number came from, the answer is a click, not a week.”
01 · PACKS
Evidence packs generate as sealed PDFs: traces, results, and the audit trail. Download any run, on any device, at any time.
02 · DOSSIER
The annual dossier assembles the whole cycle for the qualifying authority in one step: results, configuration changes, and notes.
03 · CONFIG LOG
Hardware and software changes are logged against the tests they affect, per GM3 ORA.FSTD.100(d). The retest question answers itself.
04 · ACCESS
Give the authority its own account, scoped to what it may see. Records are append-only and retained for the life of the device.
See it run
Run a full qualification before any hardware is connected.
Demo simulator mode drives the whole pipeline, from authoring to sealed evidence pack, with no simulator in the room. Bring a recent finding and see what the pack looks like.