Field at the edge of a village
Terrain survey of a field, a few farms nearby.
- GRC
- 3
- ARC
- ARC-b
- SAIL
- II
Reference for the comparison
With a generic SORA, you don't apply for your operational authorisation for a single flight area, but for all areas with the same or a lower risk. wingman checks whether your sample flight plans match, guides you through the SORA and, once you have the authorisation, checks every new flight area against the authorised risk.
This video is only loaded after consent. It is embedded from YouTube, which requires your consent to the “Marketing & Media” category.
SORA applications created with wingman have already been successfully submitted to the LBA and Austro Control. A selection of the drone operators planning with wingman.



With a precise SORA, your authorisation applies exactly to the area you applied for. For every new location you need an amendment or a new application, and with changing jobs you keep waiting for the authority. A generic SORA assesses the risk of your operation based on several sample flight plans with the same risk. Every area that matches this risk or lies below it is then authorised.
| Precise SORA | Generic SORA | |
|---|---|---|
| Flight area | one specific area, usually a single location | at least three sample flight plans with the same risk |
| Authorised for | exactly this area | all areas with the same or lower risk within the authority's jurisdiction |
| Mitigations and procedures | described for this location | apply to every declared area |
| New location | amendment of the authorisation or new application | flight declaration: you check and document it yourself |
| Suitable for | fixed sites and higher risks | similar operations at changing locations, up to SAIL II |
A generic SORA is not a shortcut: the risk assessment follows the same method, and before every flight you check yourself whether the area fits. In return, you fly at new locations without applying for an authorisation each time.
Generic SORA
Precise SORA
Not sure which route suits your operation? Our SORA consulting supports you.
wingman supports you from your first sample flight plan to operating at a new location.
You create a main flight plan and add at least two more flight plans from your day-to-day operations, uploaded or drawn in the risk map.
three sample areaswingman calculates the initial GRC, ARC and SAIL for each flight plan and compares every additional flight plan with the main flight plan.
same riskYou go through the SORA as usual. Every mitigation and every procedure applies to all areas.
SORA reportYou apply to fly in all areas with the same or a lower risk.
generic authorisationFor every new location you create a flight declaration. wingman checks it, including your mitigations, against the authorised risk.
checked and documentedA surveying company flies within visual line of sight with a multicopter under 1 m, up to 120 m altitude. The main flight plan and a second flight plan are set, there are several candidates for the third. Swap it and see what wingman reports when comparing it with the main flight plan.
Flight plan 3:
Terrain survey of a field, a few farms nearby.
Reference for the comparison
Volume measurement in the extraction area, a country road along the edge.
matches the main flight plan
Inventory of a storage yard, a forester's house nearby.
matches the main flight plan
Comparable
Both additional flight plans have the same risk as the main flight plan: GRC 3, ARC-b and SAIL II. All three are suitable as samples for your application.
Simplified example. wingman compares the initial risk, i.e. before mitigations. wingman calculates the actual risk of your areas from your flight plans, the population density and the airspace.
With the generic authorisation, you check yourself whether a new area fits within the authorised limits. In wingman, you create a flight declaration for this. wingman checks the area, including your mitigations, against the authorised risk. Choose an area and see the result.
Your authorisation
New flight area:
Flight declaration: Storage yard of a sawmill
Example · checked against your authorisation
Within the authorised limits
The risk matches your authorisation. You can fly there.
Check and result saved in wingman, ready at hand for an audit.
Simplified example. As a rule, you don't send a flight declaration to the authority in advance, but it can request it during an inspection. What your authorisation requires in detail is stated in your notice of authorisation.
You bring flight plans from your day-to-day operations. wingman matches them, calculates and keeps track of all areas.

You upload your main flight plan and the additional sample flight plans or draw them in the risk map, which you also use to plan any other SORA in wingman. For each flight plan, wingman shows you ground risk, air risk and the SAIL.
wingman compares every additional flight plan with the main flight plan, value by value. If one doesn't match, you swap it before you spend time on the SORA.
wingman then guides you through the complete SORA as usual, from the concept of operations to the Comprehensive Safety Portfolio. You define mitigations and procedures once, and they apply to all declared flight areas.
At the end you have a SORA report for your application. wingman also fills in the application form and the compliance matrix from the same details.


Your flight declarations stay saved in wingman with your generic SORA, each with its result. You can see at any time which areas you have already checked.
If the authority asks during an audit, you show it which areas you checked and with what result. You don't have to gather any evidence for that.
Done by hand, a generic SORA is mostly matching work: finding sample areas with the same risk, thinking through mitigations for every area and later checking and documenting every new location yourself.
| by hand | with wingman | |
|---|---|---|
Finding sample flight plans | determining and comparing GRC, ARC and SAIL individually for every candidate | upload flight plans, wingman compares each one right away with the main flight planlearn more -> |
Risk assessment | determining ground and air risk by hand for every sample area | GRC, ARC and SAIL for all areas, automatically from route and dronelearn more -> |
Mitigations and procedures | thinking through and describing every measure for every area individually | define them once, wingman applies them to all declared areaslearn more -> |
New location | checking population density, airspace and mitigations on site and comparing them with the notice | create a flight declaration, wingman checks flight plan and mitigations against the authorised risk |
Evidence | documenting every check yourself and filing it for an audit | every flight declaration saved with its result and available instantly |
Result | a lot of matching work before the application and before every new operation | matching sample flight plans, one SORA for all areas and every new location documented |
Start for free and try all features. Here you can see what each plan includes.
Your question isn't listed? Write to us using the contact form or book a demo.
In the demo, Niko walks you through how to match your sample flight plans and create flight declarations in wingman. And if you have a question later, you won't be writing to an anonymous support desk but to a person who knows the tool and SORA.
You also use these features for the generic SORA, for every declared area.