Insurance Replay Certificate
SAIL-Aware Replay and Risk Certificate
Drone insurance claims require verifiable, tamper-evident records of the exact conditions under which a mission flew. The HCDR-I engine (M222) replays mission telemetry against the EASA SORA Specific Assurance and Integrity Level (SAIL) framework, computes per-flight risk scores across ground and air exposure dimensions, and emits chain-hashed insurance certificates that are structurally verifiable without reliance on the platform operator's attestation alone.
Capability specification
- 01
EASA SORA SAIL I–VI classification per flight based on operational volume and population density
- 02
Per-flight risk score across ground exposure, air exposure, and collision risk dimensions
- 03
Chain-hashed insurance certificate with KSL signature for tamper evidence
- 04
Replay against recorded telemetry: certificate reflects actual flight conditions, not filed ConOps
- 05
61-test green suite covering SAIL boundary conditions, risk math, and certificate chain integrity
How it works
Telemetry Replay
Recorded mission telemetry is submitted for replay. The engine re-evaluates SAIL classification against the actual flight envelope — altitude, speed, operational volume, population density buffer — not the pre-filed ConOps.
Risk Scoring
Ground exposure risk (population density within operational volume) and air exposure risk (controlled airspace proximity, conflicting traffic) are computed and combined into a per-flight risk score.
Certificate Emission
A chain-hashed certificate record is written with the SAIL classification, risk score components, and KSL signature. The certificate is structured for direct consumption by underwriters and regulatory authorities.
Standards we follow
- STD-01
EASA SORA (Specific Operations Risk Assessment) — SAIL I–VI classification
- STD-02
NIST FIPS 180-4 — Secure Hash Standard (certificate chain hash)
Areas served
This capability is deployed across 14 operational regions. Regulatory alignment details vary by jurisdiction — consult engineering for jurisdiction-specific deployment guidance.
Frequently asked questions
Can the certificate be used directly by an insurance underwriter?
The certificate record is structured and chain-hashed for external consumption. Underwriters receive the SAIL class, per-dimension risk scores, and KSL signature. Whether a specific underwriter accepts it as the primary evidence artefact depends on that underwriter's claims process — Lydos Air produces the structured record; it does not operate as an insurance intermediary.
Talk to engineering
For capability evaluation, integration guidance, and deployment scoping, submit a brief to the engineering team.
Submit engineering brief