News · LUC Gateway

LUC gateway: your path to the operator certificate

GDDC LUC gateway: people and missions in an approved framework. Practical tips and authorisation path for your drone operations. More at GDDC.

  • Partner onboarding into ConOps / LUC
  • Training through to remote pilot certificate
  • Dock, FlyCart, BVLOS in scope
  • EU-valid within the approved framework
Book a gateway callExplain LUC service
  • First LUC in Germany
  • EU 2019/947 · LBA
  • SMS & compliance
  • On- & offshore ConOps
  • Partner onboarding

  • 1 day+

    Typical onboarding blocks

  • SMS

    Safety compliance core

  • EU

    Scope usable across EU

  • LBA

    Privileges in the certificate

News · GDDC Editorial · 30. Juni 2026 · 8 Min. Lesezeit

LUC gateway: your path to the operator certificate

Professional drone work on LUC gateway needs clear competence, auditable processes and an authorisation path that scales with your mission. This article targets decision-makers, critical-infrastructure operators and partners crossing open-category limits — without liability or insurance gaps.

Legal framework in DE, CH and EU

The open category (EU 2019/947) fits standard visual-line tasks. For BVLOS, heavy systems (>25 kg), altitudes above 120 m, dock operations or sensitive airspace, specific category rules apply. You need a concept of operations (ConOps), often a SORA risk assessment and authority clearance — or LUC privileges within the reviewed scope.

Who decides what?

EASA harmonises EU requirements. LBA (Germany) and FOCA/BAZL (Switzerland) implement them: registration, geo-zones, insurance evidence and approvals. A German LUC does not replace Swiss clearance and vice versa. Plan early which state leads your operation and which data or crews cross borders.

Typical corporate mistakes

  • applying open rules to BVLOS or dock missions
  • late insurance and operator registration
  • thermal imaging over third-party property without legal basis
  • seeking authorisation only after serial ops or tender binding
  • cross-border work without a second authority and insurance path
  • treating ConOps as marketing instead of an auditable document

Practical delivery with GDDC

GDDC combines Academy (qualification), LUC gateway (partner onboarding), operational flight service and regulatory hub DE/CH. You receive documented processes: intake → ConOps/SORA → clearance → flight → archive. Recurring missions in energy, critical infrastructure, construction or perimeter especially benefit because KPIs and compliance run in parallel.

Planning checklist

  1. document operation type and category (open vs specific)
  2. align ConOps content with SMS logic
  3. verify crew qualification (A1/A2/A3, STS, LUC) and type rating
  4. clarify insurance, geo-zones and property rights
  5. schedule authority application or LUC privilege in time
  6. consider privacy for image/thermal data

Short FAQ

Do I always need an LUC? No — limited one-offs can use case-by-case approval. As operations scale, LUC becomes more economical.

What is the first step? A structured intake: mission, corridor, sensors, repeat rate.

Does GDDC support authority applications? Yes — ConOps, SORA and guidance on the specific category path.

Next step

Operating authorisation · LUC service · Contact · All news

Partner value

Four levers that cut waiting time

  • Onboard instead of rebuild

    People and hardware into the approved framework — instead of organisation, SMS and a first application from scratch.

  • Ride along safety compliance

    You operate under a proven safety/compliance system — the core of every LUC and the trust base for authorities.

  • Unlock the specific category

    BVLOS, dock, heavy lift, altitude — within approved scope, with the right qualifications and limits.

  • European reach

    Authorisations under the LUC framework apply in the released EU states — not only locally improvised.

Typical gateway ops

Where partners need the framework now

Process

How partner onboarding works

  1. Clarify need & scope

    Mission type, aircraft, BVLOS/dock, height, airspace. We check whether gateway or own ConOps/LUC is the shorter path.

  2. Training & qualification

    Modular: A2 / STS / specific category, then specialised modules (dock, FlyCart, thermo, offshore …) per approved operations.

  3. Release people & tech

    Aircraft records, maintenance (ConOps part M), remote pilot certificate, release to operation — documented and auditable.

  4. Operate & optional own LUC

    You fly in the framework. As volume grows, we support privilege expansion or the jump to your own LUC.

Concrete next steps

FAQ

FAQ on the LUC gateway

  • What is the LUC gateway?

    A structured path to onboard people and hardware under GDDC’s approved LUC/ConOps framework — instead of building a full operator certificate from scratch first. Goal: a faster, documented start in the specific category.

  • What do partners save versus owning a LUC?

    Time and cost for organisation, SMS setup and the first application. Typical: onboard a pilot and e.g. a dock into the existing framework (training, type rating, aircraft records) in short planned blocks. Your own LUC remains optional for later scale.

  • Which operations does the framework cover?

    Specific category: BVLOS/dock, >25 kg (e.g. FlyCart), >120 m, special airspace, recurring industrial/energy missions — always within the approved scope and with required qualifications.

  • Who remains responsible?

    You do for day-to-day operations and on-site compliance. GDDC provides the approved framework, training path and documentation. Privileges and limits are defined in the certificate/ConOps — not in marketing claims.

Ready for the faster path?

Gateway callUnderstand LUC →All news →