Open a FlightTwin JSON report, Professional suite, ULog diagnostic or input manifest. Inspect declared outcomes and check source digests locally. Nothing is uploaded to a LOKSAN backend.
Export JSON from Engineering Reports or from Professional Studio, then inspect it below.
Sample output is computed from a bundled synthetic CSV. It is not a real aircraft record or a customer case study.
For ULog diagnostics, compare the original ULog bytes. For Professional manifests, select a CSV to compare its normalized seven-column FlightTwin representation.
Matching a digest only links bytes or normalized rows to a claimed hash. It does not prove source authenticity, executed software version or safe flight operation.
Select a FlightTwin JSON export or run the synthetic sample to see checks, sample coverage and the report's declared metrics.
The inspector checks supported JSON shapes and highlights inconsistent rule flags. Where a record contains a SHA-256 reference, you can compare a selected local input. No report is sent to LOKSAN.
JSON content can be edited, hashes are not signatures, and browser-local timestamps are not independently trusted. A matching file digest does not validate the flight, software build, regulatory compliance or third-party provenance.
See format reference and test rules, open the interactive demo or request a scoped technical evaluation.
