Compliance & SORA
Written to survive an authority audit.
The EASA Specific Operations Risk Assessment implemented as a working calculator, wired into the mission it belongs to and stored as a permanent record.
What the engine actually computes
Step 01
OPEN eligibility
Screen the operation before assuming it is Specific at all.
Step 02
STS / PDRA match
Match the mission to a standard scenario where one exists.
Step 03
GRC & ARC
Ground and Air Risk Class computed from the operational volume.
Step 04
SAIL & OSOs
SAIL determination and the full Operational Safety Objective checklist.
Gates, not reminders
A mission cannot be marked complete until every required signature is in place. A grounded aircraft cannot be dispatched. A pilot's device can only write to missions assigned to that pilot — enforced in PostgreSQL by Row-Level Security, not by application logic that a future change could quietly bypass.
Every create, update and delete across the system is captured centrally, attributed to the user who made it. That audit trail is structural: it is also the mechanism that carries a pilot's offline work back to the office.
Status vocabulary
The same three states are used everywhere, and nowhere decoratively. If a screen shows amber, something operationally needs attention.
Governance suite
Controlled documents
Authored, versioned and sectioned in-app with per-section audit history and direct EASA-reference linking.
Internal audit programme
Tracked findings that feed straight into the same corrective-action register the SMS uses.
Application builder
Assemble authorisation and certification submission packages from records you already hold.