Main/Temporary/Drone Regulation Overview.md

---
title: Drone Regulation Overview
created_date: 2025-09-15
updated_date: 2025-09-15
aliases:
tags:
---
# Drone Regulation Overview
## Drone Compliance & Airspace Technology — Engineer’s Primer (Swiss/EASA Focus)
*Version: 2025-09-11*

> Purpose: Give engineers who build sub‑4 kg autonomous drones a **clear, technical** understanding of the regulatory landscape (Swiss/EASA-first, FAA side-notes) and the **enabling technologies** (ADS‑B, FLARM, Remote ID, U‑space, class standards, categories, pilot certs, SORA). Each chapter ends with **references** to authoritative sources.

---

### 1) Executive Overview — What matters for an engineer
- **Regime:** In Switzerland the rules **mirror EASA** (EU) via FOCA. Operations are grouped by risk: **Open**, **Specific**, **Certified**. Most BVLOS delivery work sits in **Specific** with **SORA**-based authorization (or **STS‑02** where applicable). citeturn0search8  
- **Identification:** **Direct/Broadcast Remote ID** is mandatory (EU/CH: since **2024‑01‑01** for Specific and class‑marked Open; US: RID required since **2024‑03‑16** outside FRIAs). citeturn0search8turn0search4  
- **Conspicuity & DAA:** **ADS‑B Out** is generally **not for small UAS** in EU and **prohibited** under FAA **Part 107** unless authorized. **ADS‑B In** and **FLARM** receivers are **useful mitigations** but not broadly mandated. citeturn0search13  
- **Airspace:** Default drone ceiling **120 m AGL** in EU Open; controlled airspace/geo‑zones require authorization. **U‑space** introduces **digital services** (network ID, flight authorizations, traffic info) inside designated volumes. citeturn0search8turn0search6  
- **Design classes:** **C0–C6** CE classes tie **hardware features** (Remote ID, geo‑awareness, low‑speed, termination systems) to **where/how** the drone may legally fly. STS‑01/02 rely on **C5/C6**. citeturn0search9

---

### 2) Airspace & Regulatory Landscape (Swiss/EASA-first)

#### 2.1 Airspace basics (engineer’s view)
- **Uncontrolled (Class G):** Where most small UAS operate; still bound by geo‑zones and 120 m AGL (Open). Specific authorizations may approve higher altitudes.  
- **Controlled:** CTR/TMZ etc. near airports — **pre‑authorization** and coordination needed; often handled via national portals; in Open category generally **not allowed** without procedures.  
- **Geo‑zones:** States publish **UAS geographical zones** (no‑fly/restricted/conditional). You must **consume these data** into your planner/geo‑fence. citeturn0search8

**U‑space (EU/CH):** Reg. **(EU) 2021/664** creates **designated low‑altitude volumes** where operations require using **USSP** services: **Network RID**, **Flight Authorization**, **Geo‑awareness info**, **Traffic Information/Strategic deconfliction**. Expect API‑based plan filing, conformance monitoring, and tactical advisories. citeturn0search6turn0search14

**FAA side‑note:** No nationwide “U‑space” yet; **LAANC** provides digital authorizations in controlled airspace; broader UTM is evolving via FAA/NASA. RID broadcast is required nationally. citeturn0search4

---

### 3) EASA Operational Categories & Where BVLOS Fits
- **Open (A1/A2/A3):** Low‑risk, **VLOS only**, ≤120 m, no prior approval; subcategories control proximity to people (A1 over people *incidentally*, A2 close, A3 far). citeturn0search8
- **Specific:** For anything beyond Open (e.g., **BVLOS**, urban delivery). Access via **Standard Scenarios** (STS‑01 VLOS in populated controlled area; **STS‑02 BVLOS** w/ observers in sparsely populated area) **or** via **SORA** operational authorization (custom/PDRA). citeturn0search8
- **Certified:** High‑risk (large UAS, over assemblies, passenger/cargo) — aircraft & operator certification akin to manned aviation.

**FAA side‑note:** **Part 107** (VLOS) + **waivers/exemptions** for advanced ops; RID mandatory; ADS‑B Out **prohibited** under Part 107 unless authorized. citeturn0search5turn0search13

---

### 4) EASA Design Classes (C0–C6) — What to build into the aircraft
**Why it matters:** The **class mark** constrains legal use (Open subcategory) and, for STS, is **required** (C5/C6). As designers, you must meet **EN/CE** feature sets.

- **C0 (<250 g):** No RID/geo‑awareness required; A1 use.  
- **C1 (<900 g):** **Direct RID & geo‑awareness required**; A1.  
- **C2 (<4 kg):** **Direct RID & geo‑awareness**, **low‑speed mode ≤3 m/s**; A2.  
- **C3 (<25 kg):** **Direct RID & geo‑awareness**; A3.  
- **C4 (<25 kg):** “Model” (no automation), no RID requirement; A3.  
- **C5 (STS‑01) / C6 (STS‑02):** **Direct RID**, **flight termination** (e.g., parachute/kill), **geographical containment** (C6), speed caps (C5 ≤5 m/s, C6 ≤50 m/s). citeturn0search9

**Engineer’s checklist (C2/C5/C6 highlights):**
- **Direct RID** radio (Wi‑Fi/BLE) per 2019/945 & harmonized standards.  
- **Geo‑awareness** (consume national geo‑zone datasets; onboard inhibit/warning).  
- **Low‑speed mode** (C2/C5) with deterministic entry/exit.  
- **Termination system** (C5/C6): independent power/logic; validated opening altitude/energy.  
- **Containment** (C6): hard fences in nav stack + RF/gnss integrity checks.

**FAA side‑note:** No CE class marks. Instead, **operations‑over‑people** categories impose **injury energy** limits (Cat 2/3) or require **airworthiness** (Cat 4). Manufacturers can seek Means of Compliance acceptance to unlock those ops. citeturn0search5

---

### 5) Technology Deep‑Dives

#### 5.1 ADS‑B (In/Out)
**What it is:** Cooperative surveillance; aircraft compute GNSS position & **broadcast** periodically.  
- **Links:** **1090 ES** (global) and **978 UAT** (US‑only <FL180). **ADS‑B Out** = transmit; **ADS‑B In** = receive (incl. **TIS‑B** traffic, **FIS‑B** weather on UAT). citeturn2search1turn2search5turn2search12  
- **Why small UAS don’t TX ADS‑B:** 1090 MHz saturation & address space; EU doesn’t mandate; **FAA Part 107 forbids ADS‑B Out** unless authorized. Use **Remote ID** for ID instead. citeturn0search13

**Implementation notes (In on a drone):**
- **RF front‑end** @ 1090 MHz; demod 1090ES DF17/DF18; parse ICAO address, position, velocity.  
- **Sensor fusion:** Use ADS‑B In as **cooperative DAA** cue with geofence & tactical loiters.  
- **Limitations:** Not all manned aircraft emit ADS‑B (legacy, exemptions); don’t rely on it as sole DAA.

**References:** FAA ADS‑B overview; equipage & links; pilot apps (TIS‑B/FIS‑B). citeturn2search4turn2search1turn2search5

**FAA side‑note:** ADS‑B Out mandated for manned aircraft in most controlled airspace; **dual‑link** specifics and service nuances documented by FAA. citeturn2search0

---

#### 5.2 FLARM
**What it is:** **Short‑range, predictive** collision‑warning system popular in gliders/GA; uses **868/915 MHz ISM/SRD** to exchange **ownship state + predicted 3D path** and raises **selective alerts** only on collision risk. Typical **>3–10 km** range (PowerFLARM). citeturn1search0turn1search1turn1search10

**Why it’s relevant to drones:** Light, low‑power **electronic conspicuity**; improves mutual awareness with gliders/helos at low altitude; counted as **air‑risk mitigation** in SORA packages.

**Implementation notes:**
- Radio: 868/915 MHz; modest TX power; antenna placement critical for hemispherical view.  
- Data: Proprietary air interface; **open serial ICD** for cockpit/UAV integration; many units also **receive ADS‑B/Mode S**. citeturn1search10

**References:** FLARM overview; PowerFLARM range/tech; manuals. citeturn1search0turn1search1turn1search3

**FAA side‑note:** No FAA mandate; used voluntarily by US glider/GA community; may be added to UAS as a **voluntary DAA aid** in waivers/experiments.

---

#### 5.3 Remote ID (Direct/Broadcast; Network in U‑space)
**Direct/Broadcast RID (EU/CH & US):** Drone **broadcasts** ID + live telemetry (Wi‑Fi/BLE beacons) readable by smartphones/authorities.  
- **EU/CH:** **Mandatory since 2024‑01‑01** for **Specific** and class‑marked **Open** (C1‑C3/C5/C6). Operator **ID must be encoded**. Retrofitting allowed via approved modules. citeturn0search8  
- **US:** Two paths — **Standard RID** (built‑in) or **Broadcast Module**; required since **2024‑03‑16** outside **FRIAs**. citeturn0search4turn0search12

**Network RID (U‑space):** In designated U‑space, the operator streams identity/telemetry to **USSP** for strategic deconfliction and traffic info. This **complements** (not replaces) Direct RID. citeturn0search6

**Implementation notes:**
- **Tx stack:** Periodic BLE/Wi‑Fi NAN frames; ensure **GNSS integrity** & **timestamping**; encode **EU Operator ID** / **FAA reg** per jurisdiction.  
- **Ground app/API:** Make your GCS able to **display nearby RID** and **publish Network RID** to USSP when required.

**References:** EASA Easy Access rules; FAA RID portal. citeturn0search8turn0search4

---

### 6) Pilot Competency (what your ops team needs)
- **EU/CH:** **A1/A3 online course+exam** (Open), **A2** theory exam for close‑to‑people. **Specific:** scenario‑specific training (e.g., STS‑01/02) and any training mandated by your **Operational Authorization**. Mutual recognition EU‑wide. citeturn0search8
- **US:** **Part 107 Remote Pilot Certificate** (knowledge test; recurrent training) for non‑recreational ops. citeturn0search5

---

### 7) SORA — How to write a winning safety case
**Concept of Operations (ConOps):** Exact **what/where/how**: UAV, airspace, altitude, population, comms, automation mode, contingencies.  
**Risk process (v2.5):**  
1) **GRC** (ground risk) from mass/KE + environment → apply **mitigations** (controlled ground area, **parachute**).  
2) **ARC** (air risk) from airspace/traffic → apply **strategic** (airspace/time selection, segregation) and **tactical** mitigations (**DAA**: observers, **ADS‑B/FLARM In**, GBDAA).  
3) Map to **SAIL I–VI**, then satisfy **OSOs** at required robustness (technical, operational, human). citeturn0search7turn0search15

**Engineer’s angle:** SORA drives **design requirements**: redundancy, **termination**, containment, C2 link integrity, logs, health monitoring, and DAA sensors. Build these early to keep SAIL low.

**References:** JARUS **SORA v2.5**; EASA AMC/GM summaries. citeturn0search7turn0search15

---

### 8) Practical Build Guidance (sub‑4 kg BVLOS delivery)
**Avionics/stack checklist**
- **RID:** CE‑compliant Direct RID module/firmware; operator ID provisioning; broadcast self‑tests. citeturn0search8  
- **Geo‑awareness:** Ingest **UAS geo‑zone** data; pre‑arm checks; hard geofence with graceful abort. citeturn0search8  
- **DAA:** **ADS‑B In** (1090) & **FLARM** receiver for cooperative traffic; non‑coop sensing where risk needs it. citeturn2search4turn1search0  
- **Termination/Containment:** Independent **parachute/kill** (C5/C6) with test evidence; C6 **containment** volume in FMS. citeturn0search9  
- **Ops tooling:** SORA artifact generator; flight log integrity; U‑space/USSP API client (when applicable). citeturn0search6

**Program/approval path (EU/CH)**
1) If rural BVLOS fits **STS‑02**, design to **C6** & train STS pilots → **declaration** path.  
2) Otherwise: compile **SORA** (ConOps, GRC/ARC, OSOs), specify mitigations, and apply to **FOCA/NAA**. citeturn0search11

**US comparison:** Part 107 operations baseline; for BVLOS/package delivery, expect **waiver/exemption** and design toward **DAA + containment**; RID mandatory; **no ADS‑B Out**. citeturn0search4turn0search13

---

### 9) Reference Library (authoritative)
- **EASA Easy Access Rules (2019/947 & 2019/945, rev. 2024):** Overview of categories, class standards, pilot competency. citeturn0search8  
- **Reg.(EU) 2019/945:** UAS/class technical requirements (C0–C6). citeturn0search1turn0search9turn0search17  
- **U‑space Reg.(EU) 2021/664 — Easy Access:** Services & obligations in U‑space. citeturn0search6  
- **FOCA (CH) Specific category portal:** Swiss process & maps. citeturn0search11  
- **FAA Remote ID portal:** Compliance paths & modules. citeturn0search4turn0search12  
- **FAA Part 107 (eCFR):** Operating rules, waivers, pilot cert. citeturn0search5  
- **ADS‑B primers (FAA):** Technology, links, services (TIS‑B/FIS‑B). citeturn2search4turn2search1turn2search5  
- **FLARM:** System overview & manuals; technical band info. citeturn1search0turn1search3turn1search10

---

#### Appendix A — Quick glossary
- **Direct/Broadcast RID:** Local Wi‑Fi/BLE beacons with ID/telemetry from UAV.  
- **Network RID:** Internet uplink to UTM/USSP carrying ID/telemetry for deconfliction.  
- **USSP:** U‑space Service Provider (EU).  
- **TIS‑B/FIS‑B:** Ground rebroadcast traffic / weather for ADS‑B In users (US).  
- **OSO/SAIL:** SORA Operational Safety Objective / assurance level I–VI.

---

*© 2025. This learning resource summarizes public regulations — always verify current national notices and airspace data before operations.*