Every claim, traced to the rule it answers.
Hespoire checks every claim and mitigation against the current EASA rules and flags gaps before the authority does.
Evidence over promises
Each check in Hespoire traces back to the rule it enforces. When a check passes, you can see which requirement it satisfied and why. When it fails, you can see what is missing. The rule model is owned by our regulatory co-founder, so that legal text and software do not drift apart.
A question instead of a rejection
A gap comes back as a specific question. "You claim M1(B) at medium robustness. How is access to the flight area restricted, and who enforces it?" is something an operator can answer in a minute. A general letter a few months later is not.
Nothing leaves until it passes
A file reaches the authority only once every rule check passes. That makes the application cleaner, but it does not replace the authority: the ILT, or your national authority, still decides. Hespoire is built so that it decides on a complete, consistent file.
Goes in
- Your drafted or imported file
- Current AMC and GM to Regulation (EU) 2019/947
- SORA 2.5 method and its annexes
- Authority-specific requirements
Comes out
- Pass or gap, per requirement
- Traceable link from claim to rule
- Specific questions for the operator
- An authority-ready file once every check passes