Automating the SORA authorisation file
- The context
- A French drone (UAS) operator, required to follow the SORA 2.5 risk-assessment methodology for its operational authorisation applications. Every flight scenario, with its area, its aircraft and its risk level, opens a new file.
- The problem
- Every application requires a complete file: ConOps, risk assessment, compliance matrix and annexes. That is several days of repetitive drafting per application. These documents constantly cite the flight, maintenance and operations manuals: each time a manual is revised or amended, every cited reference has to be checked one by one, at the risk of letting one slip through.
- The approach
- The automated workflow ingests every available input: GIS data for the area, manuals and supplementary scenario information. A hybrid processing stage first applies the SORA 2.5 methodology deterministically, ground and air risk calculations, SAIL and ARC classes, then a language model drafts the documents, contextualising every element and justification with a systematic citation of its source reference.

The result
-75%
less drafting time
Drafting drops from several days to a few hours. And cited references keep themselves current: when a manual is amended, the file regenerates instead of being re-read line by line. The risk of error is gone.