UAS compliance built on certification experience

Launch compliant drones faster while avoiding unnecessary testing, redesigns and certification delays.

i 3 Table of contents

The compliance gap in UAS sector

Most drones on the European market do not have proper CE marking evidence

The UAS sector is still young. Most manufacturers are small and medium-sized enterprises building innovative products with limited regulatory budgets. They know CE marking matters, but the combination of a complex regulatory framework, expensive laboratory testing, and a shortage of specialised guidance creates a barrier that many cannot cross alone.

Achieving compliance under Regulation 2019/945 does not have to be prohibitively expensive. The cost depends almost entirely on how the process is structured. Knowing which requirements apply to your specific class, which evidence you can produce internally without third-party testing, and how to avoid failed test campaigns before they happen makes the difference between a viable compliance investment and an uncontrolled one.

Typical reasons why manufacturers overspend on compliance

  • Wrong UAS class selected
  • Testing started before reviewing the design
  • External laboratories used for evidence that could be generated internally
  • Non-conformities discovered only during testing
  • Poor coordination with laboratories and the Notified Body

01

UAS Regulatory Roadmap

02

Pre-Test Design Review

03

Test Campaign Support

04

Specific Category Advisory

EU regulatory framework for UAS

How EU drone regulation works

EU drone regulation follows an operation-centric approach. Implementing Regulation 2019/947 establishes three categories of UAS operations, each corresponding to a different risk level:

open

lowest risk, no prior authorisation required

specific

medium risk, requires operational authorisation or declaration

certified

highest risk, subject to EASA certification

For manufacturers placing UAS on the European market, the central regulation is Delegated Regulation 2019/945. It defines the technical requirements for each class of UAS and the conformity assessment procedures available to demonstrate compliance. The class assigned to a product is directly linked to its intended operating environment, its weight, and its capabilities, and it determines both the regulatory requirements the manufacturer must meet and the operational permissions available to the end user.

Identifying the correct class is the foundation of the entire compliance process and drives every decision that follows: which requirements apply, which conformity assessment module is available and whether a Notified Body must be involved.

Class identification labels — C0 through C6

Regulation 2019/945 defines seven classes of UAS besides the DRI Add-on. Classes C0 through C4 correspond to operations in the open category. Classes C5 and C6 are designed for standard scenarios in the specific category under declaration.

The class determines the full scope of product requirements: maximum take-off mass limits, speed restrictions, geo-awareness, safety features, noise emission limits, and more. Higher classes generally carry more complex requirements, but the relationship is not always linear.

Class

MTOM

Open subcategory/STS

Notified Body required?

Class

C0

MTOM

<250 g

Open subcategory/STS

A1

over people, not assemblies

Notified Body required?

No

Module A available

Class

C1

MTOM

<900 g

Open subcategory/STS

A1

sobre personas, no aglomeraciones

Notified Body required?

Sí

Module B+C or H

Class

C2

MTOM

<4 kg

Open subcategory/STS

A2

close to people, with restrictions

Notified Body required?

Sí

Module B+C or H

Class

C3

MTOM

<25 kg

Open subcategory/STS

A3

far from people

Notified Body required?

Sí

Module B+C or H

Class

C4

MTOM

<25 kg

Open subcategory/STS

A3

model aircraft

Notified Body required?

No

Module A available

Class

C5

MTOM

<25 kg

Open subcategory/STS

STS-01

VLOS, populated area

Notified Body required?

No

Módulo A disponible

Class

C6

MTOM

<25 kg

Open subcategory/STS

STS-02

BVLOS, sparsely populated

Notified Body required?

No

Module A available

EN 4709 standards and conformity assessment procedures

The harmonised standards supporting Regulation 2019/945 form the EN 4709 series. These standards provide technical specifications and verification methods that give manufacturers a presumption of conformity when applied correctly.

The series covers product requirements for:

  • $
    Open category (EN 4709-001)
  • $
    Direct remote identification (EN 4709-002)
  • $
    Geo-awareness (EN 4709-003)
  • $
    Lighting (EN 4709-004)
  • $
    Geo-caging (EN 4709-005)
  • $
    Flight termination systems (EN 4709-006)
  • $
    General requirements for C5 and C6 classes (EN 4709-007)
  • $
    C5 accessories kits (EN 4709-008)

For classes where Module A is available, applying the relevant EN 4709 standards allows the manufacturer to self-declare conformity without Notified Body involvement. For classes C1, C2, and C3, third-party assessment is mandatory: the manufacturer must use Module B+C (EU-type examination followed by internal production control) or Module H (full quality assurance system), both of which require a Notified Body.

Beyond Regulation 2019/945, UAS manufacturers must comply with all other applicable EU harmonisation legislation. This typically includes the Radio Equipment Directive (RED), the Machinery Directive, RoHS, and the Cyber Resilience Act (CRA). Compliance with 2019/945 alone is not sufficient for CE marking, and do not forget additionally to testing, the manufacturer shall carry out production control.

The support gap for UAS manufacturers

Why existing providers leave drone manufacturers underserved

Drone manufacturers looking for compliance support typically encounter four types of providers, each with structural limitations.

Testing laboratories perform the measurements and tests, but their role ends there. They are not incentivised to optimise the manufacturer's overall strategy, and they rarely flag design issues that could cause a test failure before the campaign begins. A failed test means a repeat booking, and the cost falls on the manufacturer.

Notified Bodies evaluate conformity; they assess, they do not advise. A Notified Body cannot guide a manufacturer on how to meet a requirement. This boundary exists for good reason, but it means manufacturers often enter the certification process without the preparation they need

Generalist CE marking consultancies cover broad product categories but rarely have deep experience with UAS-specific regulation. Drone compliance sits at the intersection of product safety legislation and aviation regulation, with its own class system, its own harmonised standards, and its own conformity assessment logic.

Independent consultants working in the drone sector sometimes bring relevant domain knowledge, but in practice they often rely on personal interpretations that diverge from what the regulation actually requires. The result can be a compliance approach that feels logical but does not align with how a Notified Body or market surveillance authority will evaluate the product.

The manufacturer needs someone who understands the regulation, the evaluation process, and the testing landscape well enough to build a strategy that works before the first lab booking is made.

Background

The experience behind the advisory

I led the development of the UAS testing capabilities of the first Notified Body designated under Regulation 2019/945 in Europe. From that position, I evaluated the conformity of UAS across multiple classes, working through the full range of requirements.

That work involved close cooperation with EASA and the European Commission on the practical implementation of the regulation, and I was part of the consortium behind the Support Study for the European Trusted Drone Label, a flagship initiative under the European Drone Strategy 2.0 and referenced in the European Action Plan on Drone and Counter Drone Security.

This is not theoretical knowledge applied from outside. It is operational experience built through years of testing drones, reviewing technical documentation, identifying non-conformities, and making certification decisions. That perspective now works for the manufacturers.

The objective is simple:

Help manufacturers reach conformity with the minimum necessary cost, time and regulatory risk.

UAS compliance services

Four services designed to cover the complete compliance lifecycle

Every UAS compliance project starts from a different position.

Some manufacturers need to understand what applies to their product before committing to anything. Others are mid-development and need someone to catch problems before they reach the lab.

Others are already in the testing phase and need technical coordination. The services below are structured to address each of these stages.

1
1

UAS Regulatory Roadmap

The compliance map before the first lab booking

2
2

Pre-Test Design Review

Catch the gaps before the laboratory does

3
3

Test Campaign Support

Expert presence throughout the EN 4709 test campaign

4
4

Specific Category Advisory

Technical support for PDRA, SORA, and design verification

01

UAS Regulatory Roadmap

The compliance map before the first lab booking

Before spending a single euro on laboratory testing, know exactly what your drone needs to comply with. This service determines whether Regulation 2019/945 applies, identifies the most appropriate class given the intended operational environment, and works through every applicable requirement down to the individual technical specification level.

The result is a structured test plan that covers every requirement, identifies what can be evidenced without external testing, and ranks the laboratories that can cover the rest. Everything that can be self-declared without a third party reduces your testing budget. That optimisation is built into the plan from the start.

Outcomes

  • Full regulatory scope identification
  • Class determination and conformity assessment route
  • Structured test plan
  • Internal vs. external testing optimization
  • Laboratory ranking and quotes
  • Notified Body identification (if required)

€1,500 Fixed Fee · Delivered in 5 – 7 working days

02

Pre-Test Design Review

Catch the gaps before the laboratory does

Most non-conformities found during EU-type examination or laboratory testing could have been identified weeks earlier from the design documentation. A failed test means delays, additional laboratory costs, and in some cases a design change that cascades across documentation already produced.

This service is a structured review of the drone's design against the applicable requirements of Regulation 2019/945 and the EN 4709 series before the test campaign begins. The output is a formal gap report with specific corrective actions and their priority. Issues found here cost a fraction of the same issues found in the laboratory.

Outcomes

  • Design review against 2019/945 and EN 4709
  • Compliance gap identification
  • Documentation analysis
  • Formal gap report with prioritised corrective actions
  • Risk assessment of likely test failures

€2,000 Fixed fee · Delivered in 7 – 10 working days

03

Test Campaign Support

Expert presence throughout the EN 4709 test campaign

Depending on the conformity assessment procedure, the test requirements can be validated in two ways: requirements where I participate directly in the test plan at the manufacturers facilities, and requirements where laboratory involvement is genuinely necessary. Where I execute tests alongside the manufacturers team, I design the test protocol against the applicable EN 4709 specification, direct the measurement process, and validate the results.

Where laboratory testing is required, I select the appropriate facility, prepare the product and documentation for submission, and remain the technical point of contact throughout.

Outcomes

  • Test protocol design per EN 4709 specification
  • Direct test execution at your facilities
  • Laboratory selection and coordination
  • Notified Body preparation and liaison
  • Complete test report and records

Custom pricing · Depends on UAS class and conformity assessment procedure

04

Specific Category Advisory

Technical support for PDRA, SORA and design verification

Manufacturers developing UAS for commercial operations beyond the open category face a compliance challenge at the intersection of product design and operational approval. The SORA methodology defines the safety case, PDRAs offer a streamlined route for defined scenarios, and for SAIL IV operations, a Design Verification Report issued by EASA is required.

Design-related operational safety objectives (OSOs) must be supported by evidence linking the products design characteristics to the claimed level of robustness. This service covers regulatory analysis of the intended operation, identification of the applicable SORA pathway, technical support for OSO evidence preparation, and advisory throughout the operational authorisation process.

Outcomes

  • Regulatory analysis of intended operation
  • SORA pathway identification
  • Design-related OSO evidence preparation
  • PDRA applicability assessment
  • Support throughout national authority process

Hourly advisory · Scoped after initial consultation

Also relevant for UAS manufacturers

Turnkey Technical File

Complete technical documentation for Regulation 2019/945 and all other applicable directives

External Compliance Manager

Regulation 2019/945 has been amended multiple times since its adoption and further changes are in preparation. The External Compliance Manager keeps your documentation current as the framework evolves

faqs

Frequently asked questions

Does my drone need CE marking to be sold in Europe?

Yes—unless your drone is to undergo EASA type certification—it must comply with directives such as the RED or RoHS (and soon the CRA), making the CE mark mandatory in all cases. Furthermore, if it is intended for operation in the "open" category or under a standard scenario within the "specific" category, it must comply with Delegated Regulation 2019/945 and bear the appropriate class identification label. Drones manufactured commercially and placed on the market from January 2024 onwards must meet these requirements.

Can a drone with a class identification label use a DRI Add-on to meet its direct remote identification requirement?

No. A class-marked UAS must implement direct remote identification as an integral part of the aircraft's design. The regulation requires the system to broadcast specific information tied to the UA itself: the serial number of the unmanned aircraft and its emergency status. DRI Add-ons transmit their own serial number and do not broadcast emergency status.
Add-ons were introduced as a solution for legacy drones that were placed on the market before remote identification requirements came into force, allowing them to continue operating in certain scenarios. Drones designed to be operated in the specific category, out of the STS, can also rely on DRI Add-ons to comply with this requirement. For any other new UAS, remote identification must be built in, not attach on.

What is a legacy drone, and does the concept affect new units of an existing model?

A legacy drone is one that was placed on the market before the UAS regulation came into force. Legacy drones can still be used under specific conditions, but with more restricted access to certain categories and scenarios.

The critical point is what "placed on the market" actually means. It refers to each individual unit made available for the first time, not to the product model as a whole. A drone model that existed before the regulation came into force is not automatically legacy in perpetuity. Every new unit of that model placed on the market today must comply with the regulations applicable at that moment.

In practice, this means that any drone sold today without a class identification label can only be operated in the specific category, subject to prior authorisation from the competent national aviation authority.

Where can a privately-built drone be flown?

A privately-built UAS (manufactured for the builder's own use, excluding ready-to-assemble kits) falls outside the scope of Delegated Regulation 2019/945. It does not need to meet class requirements and does not require carrying a class identification label. Its operational access under Implementing Regulation 2019/947 is determined directly by its mass.
A privately-built UAS with a MTOM below 250 g may operate in subcategory A1. A privately-built UAS with a MTOM below 25 kg may operate in subcategory A3. Subcategory A2 is not accessible to privately-built UAS under any conditions. For aircraft above 25 kg, or for any operation that goes beyond the open category, the specific category is the only path, which requires an operational authorisation from the competent national aviation authority.

How do I know which class my drone belongs to?

Class assignment under Regulation 2019/945 follows from the characteristics of the product and its intended operational environment, not from a free choice by the manufacturer. Maximum take-off mass is the starting point, but other factors matter.

Getting the class wrong has direct consequences: it affects which requirements apply, which conformity assessment procedure is available, and whether a Notified Body is required.

Do I need a Notified Body for my drone?

It depends on the class. Classes C1, C2, and C3 require mandatory third-party assessment under Module B+C or Module H, both of which involve a Notified Body. Classes C0, C4, C5, and C6 have access to Module A, which allows self-declaration, provided all applicable harmonised standards have been fully applied.

What are the EN 4709 standards and do I need to use them?

The EN 4709 series is the set of harmonised standards for the Regulation 2019/945. They translate the regulation's technical requirements into test methods and acceptance criteria. Using an EN 4709 standard published in the EU Official Journal gives the manufacturer a presumption of conformity for the requirements it covers, which significantly simplifies the conformity assessment.

What is the SORA and does it affect my product as a manufacturer?

The SORA (Specific Operations Risk Assessment) is the methodology defined by EASA for operators seeking authorisation to conduct UAS operations. While it is primarily an operator responsibility, it has direct implications for manufacturers: the SORA includes design-related operational safety objectives (OSOs) that the manufacturer's technical documentation must be able to support. For SAIL IV operations, a Design Verification Report issued by EASA is required, which means the product must meet a defined level of design assurance.
Manufacturers developing UAS for the professional specific category market benefit from understanding this dependency early in the design process.

Is EU drone compliance useful if I also want to sell in the UK?

Yes, and pursuing both simultaneously is the most efficient approach. The UK has introduced its own class marking system (UK0 to UK6) that closely mirrors the EU structure. A drone compliant with EU Regulation 2019/945 under a given class is recognised as the equivalent UK class until the end of 2027, after which explicit UKCA class marking is required for products placed on the UK market. Manufacturers targeting both markets can coordinate the UK class marking process in parallel with EU compliance, reusing most of the technical work and avoiding a separate compliance project. For more info see Blog article EU vs UK drone compliance

Drone compliance is one of the most technically demanding conformity assessment processes in the EU harmonisation framework. It does not have to be the most expensive one.