BLOG POSTS
How to Choose the Right Drone Approval Path: STS, PDRA, SORA or LUC
If you have ever asked “Do we need STS, a PDRA, a SORA, or a LUC?”, you are not alone. Many drone operators lose weeks, sometimes months, because they start writing documents before they pick the right regulatory path.
This guide is a practical decision framework across:
-
STS operations manuals (declaration path for EU standard scenarios)
-
Airspace coordination and pre-coordination (often required on top of the chosen path)
-
PDRAs (Predefined Risk Assessments that simplify SORA documentation)
-
Operational authorisation via SORA (the standard route for complex Specific operations)
-
LUC (Light UAS Operator Certificate, when you need repeatable approval privileges)
It is written for operators who want the shortest compliant path, not the “most paperwork” path.
Step 0: Confirm You Are Not Already in the Open Category
Before you look at STS, PDRA, SORA, or LUC, ask one question:
Can you fly the mission in Open Category and without needing authority approval?
Open Category is designed for low-risk operations and comes with strict boundaries. When the mission’s risk profile or environment pushes outside those boundaries, you are in Specific Category, and then you need to choose your path.
Common signals you are outgrowing Open:
- You want to fly BVLOS in a way that Open does not allow.
- You plan to fly near people or in environments where you cannot guarantee separation.
- You plan to fly with UAS models that are not permitted in any open subcategory.
- You need to fly repeatedly in locations and conditions that require formal operational procedures and documented mitigations.
If any of those apply, keep reading.
Step 1: Does the Mission Fit an EU Standard Scenario (STS)?
If there is one rule of thumb that saves the most time, it is this:
If your ConOps fits in an STS, do that first.
EASA’s Standard Scenarios (STS) are designed as a fast lane for specific operations that match a predefined envelope. Instead of applying for an operational authorisation, you generally file a declaration, and then you fly within the scenario limitations.
Two common STS families are:
- STS-01: VLOS in urban areas, with a C5 drone.
- STS-02: BVLOS in sparsely populated environments, with a C6 drones.
What you still need even in STS:
- A compliant Operations Manual for the STS you declare under.
- STS Pilot competence training (both theoretical & practical)
- Often airspace coordination when the mission intersects controlled airspace, FIZ, airport environments, or special-use airspace.
Practical “yes” indicators for STS:
- Your mission profile is repeatable and stays within the exact STS operational envelope.
- You can operate with the required aircraft class and equipment expectations.
- The environment and overflight rules match the STS constraints.
Practical “no” indicators for STS:
- You need flexibility, such as higher altitude, longer range, different types of areas, or a mix of urban and rural profiles in one project.
- You want to do something that is “close” to STS, but not quite, and you cannot accept the limitations.
- You foresee that you will quickly add complexity (multiple aircraft, multi-site, controlled airspace, unusual environments).
If STS is your path, start by making your documentation robust. Here are two useful references:
And if you want the fastest implementation route, EU Drone Port provides ready-to-adapt manuals:
Step 2: If STS Does Not Fit, Can a PDRA Simplify the Approval Path?
If your operation is in Specific Category but it does not fit STS, the next question is:
Is there a PDRA that matches our operation closely enough to reduce the work?
PDRA stands for Predefined Risk Assessment. Think of it as a standardised risk assessment “starting point” published for certain operation types. When a PDRA fits, it can reduce the amount of custom work in a full SORA, because some assumptions and safety objectives are already structured.
Important: PDRAs are not the same as STS. In many cases, you still need to produce documentation and obtain approval before operating, but the risk assessment and safety objectives are less open-ended.
Operator-friendly signs a PDRA may be relevant:
- Your operation resembles a known pattern (for example, a published PDRA family).
- You want a route that is more structured than “blank page SORA”.
- You accept that approvals and documentation still apply, but you want clarity about what to produce.
Two useful starting points:
If you suspect PDRA is your shortest path, you can also start here:
Step 3: When Do You Need a Full SORA Operational Authorisation?
When an operation does not fit STS, and a PDRA does not fully match, the standard professional route in Specific Category is:
Apply for an operational authorisation using SORA.
SORA, the Specific Operations Risk Assessment, is the methodology that classifies the risk of your intended operation and defines the mitigations and safety objectives your operation must meet. EASA describes it here.
When SORA is usually required (plain-language signals):
- You are planning BVLOS operations that exceed STS constraints.
- You are flying dronw swarms
- You are flying with a drone-in-a-box solution, or drone dock.
- You operate near people or in complex environments where ground risk is non-trivial.
- Your operation relies on multiple layers of mitigation (procedures, training, aircraft features, operational limitations).
- You need a defensible package that can survive authority review without endless rework.
What operators often underestimate:
- A ConOps is not optional. It is the foundation, and it should be specific.
- “We will be careful” is not a mitigation. Authorities look for systematic mitigations and evidence.
- Airspace is frequently the hidden blocker. Your chosen path might be correct, but coordination requirements can still shape the ConOps and timeline.
- Your documentation has to match your actual operation. Many rejections happen because the paperwork describes an operation that does not match the reality on the ground.
If you want a deeper look at what “complex SORA” preparation looks like:
what complex SORA preparation looks like
And if you want the service route where EU Drone Port prepares the package end-to-end:
Step 4: When Should You Consider a LUC (Light UAS Operator Certificate)?
An operational authorisation can be perfect for a specific project, but some operators grow into a bigger challenge:
We need to run many different missions, in many places, with consistent safety and compliance, without starting from scratch each time.
That is where a LUC can become relevant. A Light UAS Operator Certificate can grant operational privileges, depending on what the authority accepts, and it typically requires a higher level of organisational maturity.
LUC is worth considering when:
- You have recurring operations, not a one-off project.
- You have an internal safety management structure, or you are ready to build it.
- You want a framework that scales: consistent training, maintenance, procedures, audit readiness.
- You want reduced friction over time, even if the initial setup is more demanding.
If you are not sure whether you are “big enough” for LUC, a good heuristic is:
If your biggest bottleneck is that approvals and documentation cycles are slowing down the business model, you should evaluate LUC.
Coordination, Pre-Coordination, and Dispatching: The Operational Layer Many Operators Miss
Operators often treat “approval path” as the full problem. In reality, many flights are delayed not by the regulatory category, but by airspace and local coordination requirements.
Even if you are:
- in Open Category, or
- operating under an STS declaration, or
- covered by a PDRA/SORA operational authorisation,
you may still need to coordinate with relevant airspace stakeholders depending on location and context.
Practical signs you should plan coordination early:
- Near an aerodrome environment or controlled airspace
- Within areas with special use airspace constraints
- In scenarios where other stakeholders must be informed or procedures must be followed
This is why a good decision process starts with the ConOps and includes airspace constraints upfront, not as an afterthought.
A Simple Decision Checklist
Use this quick checklist to get unstuck:
- Where will we fly? (urban, rural, industrial site, near aerodrome, controlled airspace)
- How will we fly? (VLOS, EVLOS, BVLOS, multi-drone, observers)
- Who or what is below? (people, traffic, critical infrastructure, controlled premises)
- What aircraft and class label do we have? (or plan to use)
- Is the operation a one-off or repeatable? (one project vs operational program)
- Can we fit a standard scenario without “bending the rules”?
- If not STS, is there a PDRA that matches closely?
- If not, do we need a full SORA authorisation?
- Are we building long-term capability that points toward a LUC?
If you answer these in one page, the approval path usually becomes obvious.
Send Your ConOps and Find the Shortest Compliant Path
If you want us to quickly recommend the shortest compliant route, send:
- A short ConOps (one page is enough)
- Your aircraft model and key specs
- The countries you want to operate in
- Whether you need repeatable operations or a one-off project
EU Drone Port can advise whether you should start with STS manuals, a PDRA-based package, a full SORA operational authorisation, or a LUC roadmap.
Is STS always the fastest route?
Often, yes, when the mission truly fits the STS envelope. But if you need flexibility or your ConOps exceeds the constraints, forcing an STS approach can waste time and still lead to rework later.
Do PDRAs remove the need for authority approval?
Not necessarily. PDRAs are designed to simplify the risk assessment and structure the safety objectives, but many PDRA-based operations still require producing documentation and obtaining approval before operating.
When should I assume I need SORA?
When the operation does not fit STS, and you cannot map it cleanly onto a PDRA, SORA is the standard method to justify mitigations and obtain operational authorisation for complex Specific operations.
What is the difference between operational authorisation and a LUC?
Operational authorisation is typically granted per operation or operation set. A LUC is a certificate that can grant defined operational privileges to an operator who demonstrates a higher level of organisational maturity and safety management.
What is the most common reason approvals get delayed?
Unclear or inconsistent ConOps, and “late discovery” of airspace or coordination constraints. The fastest path is usually the one that matches your actual operation and is documented clearly from the start.
Can EU Drone Port help even if we do not know our path yet?
Yes. If you share your ConOps and constraints, EU Drone Port can recommend the shortest compliant path and produce the documentation package aligned to that path.