Actual data formats, rule limits, analysis boundaries and an honest implementation status. Review the specification, download synthetic fixtures and evaluate on non-sensitive data first.
All bundled flights are synthetic and are not evidence of a real aircraft flight or customer deployment.
02 — TELEMETRY CONTRACT
Required CSV fields
At least 2 data rows. UTF-8 CSV; comma, semicolon and tab separation accepted. Maximum 5 MiB / 50,000 samples. Timestamps strictly increase.
Field
Units / expected values
Interpretation
timestamp_s
seconds ≥ 0
Monotonic time base
altitude_m
metres
Reported altitude
speed_mps
m/s
Reported ground speed
battery_pct
0–100%
Available battery percentage
gps_satellites
integer 0–64
Tracked satellites
gps_fix
1/0, true/false
Reported GPS fix
telemetry_ok
1/0, true/false
Reported communication health
These fields are an explicit input contract, not standardized airworthiness measurements. Values must be interpreted with the source vehicle and logger.
03 — PX4 SUPPORT
ULog reader — partial support
The in-browser PX4 reader accepts ULog `.ulg` files up to 32 MiB and maps selected vehicle position, GPS and battery topics into FlightTwin's analysis model. Missing or invalid data is reported as unavailable. Recording gaps are not equivalent to proven RF-link dropouts.
Currently available
Selected uORB topic mapping, available data coverage, timestamp alignment, local SHA-256 diagnostic report, explicit `INCOMPLETE` and `NOT EVALUATED` rule states.
Defaults below are implementation values—not universal vehicle limits or official flight safety standards. Adjust for the aircraft and test plan.
Threshold
Default
Configurable range
Loading local engine rules…
FlightTwin evaluates nine rule families: altitude, speed, battery, GPS satellites, GPS continuity, reported telemetry status, timestamp gaps, absolute climb rate and battery drain. A missing measurement is not a pass.
05 — EVIDENCE OUTPUTS
Engineering exports, not certification
Flight report
JSON per-rule statuses, observed metrics and anomaly groups. JUnit XML for compatible automated test viewers.
Professional suite
Test run summaries, regression gates, CSV and JUnit; optional hash manifest computed over canonical seven-column CSV.
ULog diagnostics
Original input SHA-256 and data-coverage record, which can be compared locally in Evidence Inspector.
Integrity limitations
No digital signature, trusted timestamp, independent data authentication or certified airworthiness evaluation.
Does FlightTwin upload my selected telemetry files?
Current browser analysis has no flight upload backend. Uploaded files are processed locally. The browser and device remain within your own security boundary.
Is FlightTwin AI currently powered by a learned model?
Not for the existing verification results. Current core checks are explicit, deterministic engineering rules; AI-assisted explanations are planned.
Can the test results authorize a flight?
No. Results are exploratory software-engineering indicators and cannot replace qualified engineering review, applicable certification or operational authorization.
Can I import all PX4 ULog formats?
No. The importer supports selected topic variants. Unsupported or absent measurements are marked incomplete or not evaluated. Diverse real-log validation is pending.
What does Enterprise currently include?
Only browser-local workspaces, encrypted export and a local hash audit. Shared accounts, SSO, RBAC, managed on-premises deployments and cloud services have not been delivered.
Does the sales form send my message automatically?
No. It opens Gmail or another mail application with a draft. You must review and press Send. No unannounced form submission occurs.
What does a matching source hash mean?
A matching SHA-256 compares exact ULog bytes or canonical CSV rows to the corresponding manifest. It does not authenticate a pilot, aircraft, date or software build.
Can I use this for sensitive defence data?
Do not upload or share confidential, classified, export-controlled or restricted data without a separate approved data-handling and security assessment.
Verification limits & offline CI
Baseline / Candidate: New firmware is only reviewable against a declared, matching mission, airframe and test-conditions ID. These are operator-provided labels, not independently authenticated measurements. Missing or inconsistent context returns REVIEW, never PASS.
PX4: Selected PX4 ULog topics can be analyzed up to 32 MiB. Large-log byte integrity preflight is available in the source CLI as a separate streaming hash command. It does not parse or validate flight telemetry.
Example comparison context JSON requires matching missionId, airframeId and testConditionsId fields under baseline and candidate. Real PX4 cross-version validation and ArduPilot DataFlash support are not complete.
Rather than trusting a single baseline/candidate pair, evaluate at least five operator-matched independent trials with local quality checks, uncertainty intervals and CI artifacts. Not a safety certificate.
FlightTwin 2.11 adds a local-only, deterministic rule-wiring smoke test for canonical CSV. It injects eight controlled faults into cloned samples and checks whether the relevant rules detect newly aligned violations. A valid clean control is mandatory; incomplete evidence returns REVIEW. This is not proof of real-world defect recall, sensor calibration, or flight safety.
Release Drift Intelligence (v2.14, CLI-only): Re-evaluate ordered, passport-matched CSV cohorts against a common baseline to identify the first observed FAIL among supplied releases. A REVIEW gap prevents an adjacent transition claim. This is an experimental engineering tool, not firmware causality or release approval. See the source package documentation docs/RELEASE-DRIFT-TR.md and the bundled synthetic example samples/cohort/drift-releases.json.
Signal Provenance (v2.13): Cohort reports can reference source CSV columns and exact sample/time windows that contribute to the GPS outage, telemetry status, battery consumption and sampling gap metrics. Browser trace and Markdown export are available in Cohort Gate. This is a calculation trace, not an authenticated recording or certified audit.
