EDDC Switzerland and EASA competence: what operators need to know
Professional drone work on EDDC Switzerland and EASA competence 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
- document operation type and category (open vs specific)
- align ConOps content with SMS logic
- verify crew qualification (A1/A2/A3, STS, LUC) and type rating
- clarify insurance, geo-zones and property rights
- schedule authority application or LUC privilege in time
- 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.