C-DRONE GUIDE · 5 AUGUST 2026
LUC certificate (Light UAS Operator Certificate): which drone operators need it, how to get it, price
An operator who runs many missions in the specific category — recurring industrial inspections, BVLOS flights, jobs over populated areas — eventually hits the same bottleneck: every operation that falls slightly outside the ordinary needs a prior declaration or authorisation, each with its own processing time. The LUC certificate (Light UAS Operator Certificate) answers exactly that problem: it hands the operator itself the ability to assess and authorise its own operations, without going through the DGAC every time. It is not a universal pass — obtaining it means demonstrating a solid safety management system — but for certain organisations, particularly those bringing a drone team in-house, it radically changes operational agility. Here is who it makes sense for, how to obtain it, and what it costs in 2026.
Published on 5 August 2026, reviewed on 10 August 2026 — regulations in force as of August 2026.
Four ways to fly in the specific category — where the LUC fits
The specific category covers everything the open category does not allow: flying over dense populated areas, exceeding the height or mass ceilings, or flying beyond visual line of sight (BVLOS). To operate there legally, an operator has four routes, from the most supervised to the most autonomous:
- Declaration under a standard scenario (STS-01, STS-02): the operator applies a framework predefined by the EU regulation and simply files a declaration on AlphaTango, with a template operations manual (MANEX) — no individual review by the DGAC.
- Authorisation based on a predefined risk assessment (PDRA): a risk scenario already validated at national or European level, with a simplified authorisation request compared with a bespoke assessment.
- Authorisation based on an individual SORA assessment: when no standard scenario or PDRA fits the mission, the operator must conduct its own Specific Operations Risk Assessment and submit it to the DGAC, which reviews it before granting — or refusing — the authorisation.
- The LUC certificate: instead of getting each mission validated one by one, the operator gets its organisational capability to assess and authorise its own operations validated once, within the privileges recorded on its certificate.
The LUC therefore does not replace SORA or the standard scenarios: it changes who applies them. Once certified, it is the operator — not the DGAC — who checks that each new mission fits the framework for which it obtained that privilege.
Who the LUC is for: when self-authorisation pays off
The LUC can only be issued to a legal entity, never to an individual pilot: it is an organisational certification, not a pilot one. It is primarily aimed at organisations that repeat specific-category operations at a sustained pace — several BVLOS or populated-area missions a month — for whom the processing time of an individual authorisation becomes a recurring commercial or operational bottleneck. In practice, three profiles find real value in it:
- High-volume drone service providers: companies specialised in industrial inspection, mapping or professional audiovisual work that run similar missions across different sites, where each individual authorisation would carry a disproportionate management cost.
- Companies that have brought a drone team in-house: utilities, infrastructure managers, large industrial groups that operate their own fleet for recurring needs and want to control their schedule without depending on an external processing time.
- Operators aiming at large-scale BVLOS: the most advanced scenarios — including u-space — rely on operators able to demonstrate enough safety-management maturity to operate without systematic external validation.
Conversely, an operator running only a handful of specific-category missions a year — even complex ones — generally has no interest in investing in a LUC: the cost of setting up the safety management system far exceeds the savings made on a small number of one-off declarations or authorisations. The calculation mirrors the one detailed in our in-house drone or outsource guide: it is the recurrence of the need, not the complexity of a single mission, that justifies the organisational investment.
The operations manual and the procedure with the DSAC
Obtaining a LUC means demonstrating to the DSAC (Direction de la sécurité de l'aviation civile, part of the DGAC) that the organisation runs a genuine safety management system, formalised in a LUC operations manual. This document must cover, at minimum: a safety policy and its objectives, the roles and responsibilities of every function involved in drone operations, documented procedures — including emergency procedures — and an incident-reporting mechanism that tracks occurrences and turns them into corrective actions. This is not a purely administrative exercise: the DSAC assesses how closely what the manual describes actually matches how the operator runs its missions, a point on which organisations that already have a trained pilot and a registered operator start with a head start.
The procedure unfolds in several steps: filing the application with the DSAC, a documentary review, then most often an on-site audit or in-depth exchanges to verify the concrete implementation of the described system. Once issued, the certificate spells out the exact privileges granted — a LUC can cover only the standard scenarios, or extend to self-authorising PDRAs, even to internal SORA assessments depending on the maturity demonstrated. A 2025 study by Schnüriger, Schreiber, Widmer and Lenhart published in Drone Systems and Applications notes the complexity operators perceive in the specific-category risk-assessment process, which motivated the development of dedicated digital tools to make application files more reliable and faster to build (see the study on Google Scholar) — a reminder that the documentary rigour expected for a LUC goes well beyond that of a simple STS declaration.
Price, timeline and alternative: is the LUC worth the cost for your activity?
There is no single public fee schedule for obtaining a LUC: the cost mainly depends on the internal time — or the specialised aviation-regulation consulting — needed to draft the operations manual, structure the safety management system and prepare for the DSAC audit. For an SME with an already structured drone team (existing procedures, qualified pilots, a documented mission history), support typically costs a few thousand to a few tens of thousands of euros depending on the scope of privileges sought; for an organisation starting from scratch, the investment — time and consulting combined — climbs noticeably, on top of a processing time measured in months rather than weeks. On top of that comes a recurring cost: maintaining the safety management system (internal audits, manual updates, ongoing training) does not stop once the certificate is issued.
For the vast majority of operators — including those who regularly fly in the specific category via standard scenarios or PDRAs — filing an STS declaration or a standard authorisation request remains the simplest and cheapest route: it is the one followed by almost every provider on the market, including for supervised BVLOS. The LUC only becomes worthwhile once the mission volume makes the sum of individual processing times more costly, in lost commercial time, than the investment in the safety management system. Making that calculation requires knowing precisely one's pace of specific-category missions — an exercise to run before consulting a specialist, not after. For any one-off mission over a populated area or beyond visual line of sight, requesting a quote from a provider that already holds the necessary authorisations remains, in the vast majority of cases, the fastest and cheapest solution.