Obsidian-MBPM4
dc4a97832d
Affected files: .obsidian/workspace.json 2 Personal/Lists/Business Ideas.md Temporary/Drone Regulations Requirements.md
52 lines
2.4 KiB
Markdown
52 lines
2.4 KiB
Markdown
---
|
|
title: Drone Regulations Requirements
|
|
created_date: 2025-09-11
|
|
updated_date: 2025-09-11
|
|
aliases:
|
|
tags:
|
|
---
|
|
# Drone Regulations Requirements
|
|
|
|
## Regulatory Landscape
|
|
- SORA
|
|
- Categories: Open, Specific and Certified
|
|
- Remote ID
|
|
- ADS-B In / Out
|
|
- EASA Design Standards: Class C6 vs C1-C3
|
|
- airspaces: controlled, vs uncontrolled, U-Space (unmanned traffic managment framework)
|
|
- U-Space service providers (USSP): --> remote ID, flight planning and authorization, tracking and traffic information
|
|
- Pilot Certification (Proof of Competency: Open Category A1/A3, additional exam for A2 - Specific category (BVLOS) --> theory exam and practical skill test - Light UAS Operator Certicifcate (LUC) which allows to self-authorize operations)
|
|
|
|
|
|
## Requirements
|
|
### Remote ID
|
|
Applicable in CH, EU
|
|
- integrated or retrofit --> upload into the RID system
|
|
|
|
### ADS-B In / Out
|
|
ADS-B Out is not mandated
|
|
Electronic Conspicuity and U-space network identification are favored.
|
|
|
|
ADS-B In is optional but highly encouraged
|
|
|
|
### BVLOS
|
|
For BVLOS flights an operational risk assessment is required (SORA). If the SORA meets a published STandard Scenario (STS) a simplified declaration can be used instead of a full authorization
|
|
- STS-01 - VLOS over controlled ground area
|
|
- STS-02 - BVLOS with observers over a sparsely populated controlled area. Requires a class C6 label. Ops must occur in controlled ground area with an airspace observer scanning for aircraft. Limited to sparsely populated areas
|
|
If all conditions are met an operator can file STS-01/02 declaration, meaning no case-by-case study is needed
|
|
|
|
For urban deliveries a case by case study is needed, since the condition of sparsely populated fails.
|
|
|
|
The operator prepares a **Concept of Operations and risk assessment (ConOps)** document, which implements mitigations (fail-safes, parachute, ...). Based on the ConOps FOCA gives an authorization with conditions.
|
|
|
|
### Geo-awareness & Airspace integration
|
|
Drones in Switzerland and EU must respect *UAS Geographical Zones* (e.g. restricted airspace, no-fly zones).
|
|
- limited to 120 m above ground level (AGL) in uncontrolled airspace
|
|
- geofenced no-fly areas
|
|
|
|
#### U-Space
|
|
- manned aircraft must be electronically conspicuous (ADS-B out) so that drone operators can detect and avoid them
|
|
|
|
### Operations Registration
|
|
- In CH we need to obtain a unique UAS Operator Number to label the drone.
|
|
- Remote pilots must be certified (proof of c) |