Understanding UAS Operator and Aviation Authority Challenges with the SORA Process for UAS Operational Approval in DACH Nations
Bibliographic record
Abstract
The new SORA process for authorization of unmanned flight operations has quickly become an important method and major challenge for UAS operations in and around Europe, particularly in the German-speaking DACH nations. Under the SORA process, UAS operators often experience significantly higher application workloads, costs, and time until authorization. Through a targeted set of industry outreach and data gathering initiatives, the UAV DACH SORA Focus Group sought to understand the challenges faced on all sides of the SORA process. Findings show that SORA applicants are typically very small groups with diverse experience levels, missions, and aircraft - often not from aircraft safety/certification backgrounds. On average, DACH applicants needed nearly six months for full UAS operational approval, and this long time was rated as the most painful element in the SORA process. UAS operators overall support the methodology and vision of the SORA process. With increased clarity in rules and expectations, standardization across regions, availability of aids and training materials, and additional PDRAs and STSs, the SORA process could run much more efficiently and better support the growing complexity of DACH-region UAS operations.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.036 | 0.044 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.013 | 0.004 |
| Scholarly communication | 0.009 | 0.006 |
| Open science | 0.001 | 0.004 |
| Research integrity | 0.002 | 0.004 |
| Insufficient payload (model declined to judge) | 0.007 | 0.001 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".