How to scope a complex UAS compliance case before SORA

Complex UAS projects often begin with a mission description that sounds settled: inspect a corridor, survey a site or fly beyond visual line of sight. For compliance planning, that is not enough. The route, aircraft, people exposed on the ground, airspace context and operating limits can change the questions that need answering.

An initial scoping session is a working meeting to make those variables visible before a team commits to a SORA or a SORA-adjacent application. It is not a shortcut to an approval, and it should not presume which regulatory route applies. The useful outcome is a shared description of the operation, a register of open questions and a short plan for resolving them.

Prepare the operation, not the presentation

Ask the project lead to bring a plain-language mission description and the material already available. Useful inputs include the intended aircraft and configuration, proposed operating area, route or representative mission, planned altitude, operating hours, crew roles, control arrangements and any known airspace constraints. Include the mission’s purpose and the conditions under which it must stop or change.

Do not fill gaps with optimistic assumptions. If the route is preliminary, mark it preliminary. If the aircraft configuration is not fixed, list the alternatives. Separate what the team has verified from what it believes will be possible. A map can help, but it should show the proposed operation and its uncertainties, not create a false impression of precision.

Use the session to answer five questions

1. What exactly will happen? Define the task, aircraft, launch and recovery arrangements, crew responsibilities, operating area and expected frequency. Identify whether the proposal covers one site or several operating environments.
2. Where and when will it happen? Describe the route or area, altitude range, duration, operating hours and relevant ground conditions. Note nearby settlements, roads, facilities or other places where people could be present. Record seasonal or weather limits if they are part of the concept.
3. What else shares the environment? Identify known airspace users, airspace structures and site-specific constraints. Ask who can verify those details and whether the operation depends on coordination with an air traffic service or other local parties. Do not treat an initial map review as confirmation that access is available.
4. What could make the operation unsafe or non-compliant? Discuss credible ways the aircraft could leave the intended area, lose control or encounter people or other airspace users. Record existing controls, proposed mitigations and the evidence needed to show that each control can work in the actual operation.
5. Which regulatory questions remain open? Identify the possible EASA framework and national or local requirements that need competent review. The right route depends on the operation and its circumstances. Avoid assigning a category, risk outcome or authorization pathway merely to keep a project plan moving.

Keep a three-column working record

For each issue, record the fact, the assumption and the decision or evidence needed. For example: the route crosses an area where people may be present; the team assumes access can be restricted; the next step is to confirm whether that restriction is feasible and what evidence could support it.

This simple discipline prevents a proposal from quietly turning into a risk assessment built on untested premises. It also makes ownership clear. Assign each open item to a person, give it a due point in the project schedule and state what decision it affects. If a change to route, aircraft or operating hours would alter the analysis, note that dependency now.

Keep the risk discussion tied to the operation. A generic hazard list may be useful as a prompt, but it cannot replace analysis of the actual site, exposure and operating concept. Teams handling a broader risk register may also find the distinction between a current, traceable picture and a static record in this discussion of aviation risk monitoring relevant.

Close with decisions and owners

Reserve the final part of the session to read back the agreed operation description. Confirm what is fixed, what remains provisional and what change would trigger another review. Then produce four outputs: a concise operational concept; a list of applicable-rule questions for review; an evidence and information gap list; and an action log with owners and next steps.

Those outputs are more useful than a premature conclusion about whether a SORA is required or what result it will produce. They give the project team a defensible starting point for a drone operational risk assessment and make later changes easier to spot. Where the case spans countries or intersects with local airspace arrangements, keep those jurisdictional questions explicit rather than assuming one answer covers every site.

For a complex operation, involve regulatory and operational specialists early enough to challenge the concept while it can still change. North Sky Aviation Consultancy offers aviation advisory services across Norway, Sweden, Denmark and the broader European region, including drone operations and compliance consulting. An initial review can help frame the questions; the operator remains responsible for the accuracy of its operational details and for following the applicable authorization process.