BLOG POSTS
Drone Compliance Is a System, Not One Document: The EU Operator's Stack
Last updated: 15 October 2026. Regulatory references checked against the EASA Easy Access Rules for UAS (June 2026 revision).
Short answer: drone compliance in the EU is not one document. Under Implementing Regulation (EU) 2019/947, a specific category operator needs a registered operator, a suitable aircraft, competent remote pilots, written procedures, the right approval route (STS, PDRA, SORA or LUC), insurance and records kept for three years. If one element is missing, the operation can be blocked.
Which document do I need to fly in the specific category?
No single document makes an operation legal. Operators often ask us for “the document” they are missing, as if compliance were a form to fill in. In practice, the competent authority looks at whether a set of controls exists, matches the real concept of operations (ConOps), and can be proven with records.
That is why two operators with the same drone and the same declaration can get very different results. One can fly next week. The other gets stuck on a pilot certificate, an expired declaration or a missing cross-border notification. If you are new to the framework, start with our guide to the specific category and the wider EU drone regulations explained.
What does a complete drone compliance stack include?
A complete stack has eight layers. Each one has its own legal basis and its own evidence that an inspector can ask for.
| Layer | What it covers | Legal reference | Evidence an inspector asks for |
|---|---|---|---|
| Operator | Registration of the UAS operator, registration number on every aircraft | Art. 14, Regulation (EU) 2019/947 | Registration certificate, number visible on each drone |
| Aircraft | Class label (C5 for STS-01, C6 for STS-02) or technical suitability for the operation, configuration control, maintenance | Delegated Regulation (EU) 2019/945; UAS.SPEC.050 | Class label documentation, maintenance records, fleet list |
| Approval route | STS declaration, PDRA or SORA operational authorisation, or LUC privileges | Art. 5(5), Art. 11, Art. 12 and Annex Part C, Regulation (EU) 2019/947 | Confirmation of receipt and completeness, operational authorisation or LUC |
| Procedures | Operations manual, normal and emergency procedures, security, privacy and noise procedures | UAS.SPEC.050 | Version-controlled manual, checklists actually in use |
| People | Remote pilot competence for the scenario, training of other personnel, list of designated pilots | UAS.SPEC.050; UAS.STS-01.020 and UAS.STS-02.020 | Pilot certificates, practical skills accreditation, training records |
| Insurance | Third-party liability cover where Union or national law requires it | Regulation (EC) 785/2004 (20 kg and above); national law below that | Valid policy matching the aircraft and operation |
| Coordination | Geographical zones, airspace coordination, cross-border notification, U-space where designated | Art. 13, Regulation (EU) 2019/947; Regulation (EU) 2021/664 | Coordination records, host-state acknowledgements |
| Evidence | Records of operations, occurrences, maintenance and personnel, plus occurrence reporting | UAS.SPEC.050; Art. 19(2), Regulation (EU) 2019/947; Regulation (EU) 376/2014 | Flight logs, occurrence reports, records kept for at least 3 years |
The full legal text is on EUR-Lex (Regulation (EU) 2019/947), and EASA keeps a consolidated version in its Easy Access Rules for UAS.
Does a class-labelled drone mean my operation is approved?
No. A class label proves that the aircraft meets the product requirements of Delegated Regulation (EU) 2019/945. It does not authorise a mission. In the specific category, the approval is driven by the operation: the environment, the ground and air risk, and the mitigations you apply.
The label still matters a lot. STS-01 requires a C5 drone (or a C3 fitted with its C5 accessory kit) and STS-02 requires a C6 drone. Without the right label, the standard scenario route is closed and you fall back to a PDRA or a full SORA. You can check which aircraft already carry a label in our list of certified drones. Manufacturers who need a label can start with class label certification from an official Notified Body (Drone Certification Lab).
STS, PDRA, SORA or LUC: which approval route fits my operation?
Choose the route from the operation, not from what feels fastest. The wrong first choice is the most common cause of rewrites and lost months.
| Route | When it fits | Aircraft | What you submit | What you get |
|---|---|---|---|---|
| STS-01 | VLOS, below 120 m, over a controlled ground area that can be in a populated environment, ground speed under 5 m/s | C5 (or C3 with C5 kit) | Declaration to the authority of your Member State of registration | Confirmation of receipt and completeness, valid 2 years |
| STS-02 | BVLOS with airspace observers over a controlled ground area in a sparsely populated environment, up to 2 km from the pilot (1 km without observers) | C6 | Declaration | Confirmation of receipt and completeness, valid 2 years |
| PDRA | Your ConOps matches one of the five EASA predefined risk assessments: PDRA-G01, G02, G03, S01 or S02 | No class label required | Application for an operational authorisation using the predefined assessment | Operational authorisation |
| SORA | Anything outside the standard scenarios and PDRAs, such as complex BVLOS, larger aircraft or higher-risk areas | Suited to the operation | Full risk assessment under SORA 2.5 (ED Decision 2025/018/R) | Operational authorisation |
| LUC | Recurring, multi-country specific category operations where waiting for each approval no longer makes sense | Fleet managed under your system | LUC application with a safety management system and LUC manual | Privilege to authorise your own operations (UAS.LUC.060) |
EASA adopted SORA 2.5 as acceptable means of compliance through ED Decision 2025/018/R, published on 29 September 2025. For each route in more depth, see STS-01 standard scenarios, STS-02 standard scenarios, what a PDRA is, SORA 2.5 and the Light UAS operator Certificate.
Not sure which route your operation needs, or whether your current documents would survive an inspection? We review the full stack against your ConOps and tell you the shortest path to approval.
How can one missing piece block an operation that is otherwise ready?
Because every layer is a precondition, not a bonus. These are typical situations we see when operators bring us their files:
- The pilot gap. The operator has a C6 drone and a complete STS-02 manual, but the pilot holds the STS theoretical knowledge certificate without the STS-02 practical skills accreditation. The declaration is fine, yet that pilot cannot fly the operation.
- The expired declaration. Declarations made under national standard scenarios ceased to be valid on 1 January 2026, under Regulation (EU) 2022/425. Operators still relying on them have no valid declaration at all.
- The border. An operator with a Spanish SORA authorisation wins a job in France. Cross-border operations under Article 13 require the host authority to be involved first, so the contract is ready but the flight is not.
- The new aircraft. The fleet changes, but the manual and the authorisation still describe the old model. Flying the new drone is operating outside the approved limits.
- The missing records. The procedures exist on paper, but no flight logs, maintenance records or training records were kept. In an inspection, an undocumented control is treated as a missing control.
None of these operators lacked “the document”. Each one lacked one layer of the system.
What evidence does an inspector expect to see?
Inspectors expect records, not intentions. UAS.SPEC.050 requires the operator to keep records of operations, occurrences and maintenance for at least 3 years, and personnel qualification and training records for at least 3 years after the person leaves the organisation. A practical evidence set includes:
- a version-controlled operations manual that matches the current fleet and ConOps;
- completed pre-flight and post-flight checklists;
- flight logs per aircraft and per pilot;
- maintenance and configuration records;
- pilot certificates, practical skills accreditations and recurrent training records;
- occurrence reports filed with the competent authority under Regulation (EU) 376/2014;
- insurance policies and coordination records for each operation.
If your system cannot produce this evidence on request, it cannot scale, and it will not hold up under inspection pressure. Insurance is a frequent blind spot: see drone insurance regulations for the rules by aircraft mass.
When does a LUC become the right layer to add?
A LUC makes sense when approvals, not aircraft or pilots, become your bottleneck. Under Annex Part C of Regulation (EU) 2019/947, a LUC holder must run a safety management system and keep a LUC manual, and the authority can grant the privilege to authorise its own operations without a new declaration or application each time.
A LUC does not replace the other layers. It sits on top of them, so it only works when the underlying stack is already real and auditable. Read advanced SORA operations for the step before, and see our LUC service if you are already there.
How do I audit my own drone compliance stack?
Answer these seven questions with a document or a record, not with “we do this”:
- Is the operator registered in the Member State of its principal place of business, and is the number on every aircraft?
- Does each aircraft in the fleet match the route: the right class label for STS, or a technical description that fits the PDRA or SORA?
- Is the approval route the right one for the real ConOps, and is the declaration or authorisation still valid?
- Does every designated pilot hold the competence the route requires, including practical skills for STS?
- Does the operations manual describe today’s fleet, crew and procedures?
- Is insurance in place for every aircraft and country you fly in?
- Can you show 3 years of operations, maintenance and occurrence records?
Any “no” is the piece that can block the operation.
Build the system once, then scale it
Drone compliance is an operating system made of people, aircraft, procedures, approvals, coordination and evidence, all aligned to the ConOps. Operators who treat it as a system get approved faster, pass inspections and can expand to new countries. Operators who chase single documents keep running into “one more requirement”.
Send us your one-page ConOps, your current manuals and procedures, and your operating profile (countries, environments, mission types). EU Drone Port reviews the stack end to end, from STS manuals and PDRAs to SORA and LUC, and recommends the shortest path to a repeatable setup.
Frequently Asked Questions
Is there one document that makes a drone operation compliant in the EU?
No. Compliance under Regulation (EU) 2019/947 combines operator registration, a suitable aircraft, competent pilots, procedures, an approval route, insurance and records. The declaration or authorisation is only one layer, and it depends on all the others being in place.
Why do drone approvals stall even when the paperwork looks complete?
Usually because the ConOps is unclear, the procedures do not match how the operator really flies, or evidence is missing, such as training records, logs or coordination steps. Authorities assess the whole system against the operation, not the length of the file.
Does a C5 or C6 drone mean I can fly STS without anything else?
No. The class label opens the standard scenario route, but you still need to register as an operator, submit a declaration, receive the confirmation of receipt and completeness, use pilots with the STS theoretical certificate and the practical skills accreditation, and follow your operations manual.
How long must a drone operator keep records in the specific category?
UAS.SPEC.050 requires records of operations, occurrences and maintenance for at least 3 years. Personnel qualification and training records must be kept for at least 3 years after the person leaves the organisation.
Is my STS declaration valid in other EASA countries?
It can be used across the 31 EASA countries, but not automatically. Under Article 13 of Regulation (EU) 2019/947, you must give the authority of the host country copies of the declaration and the confirmation of receipt and completeness before operating there.
When should a drone operator apply for a LUC?
When you run recurring, complex or multi-country specific category operations and waiting for each approval has become the bottleneck. A LUC requires a safety management system and a LUC manual, and it can give you the privilege to authorise your own operations.
What is the fastest way to improve drone compliance maturity?
Build the stack around one clear ConOps, then add traceable evidence: version-controlled manuals, training and maintenance records, and internal audits. An external review of the full stack is the quickest way to find the missing layer before an authority does.