Step 1 β Detailed Operational Information (DOI)
// SORA 2.5 STEP #1 Β· FORMERLY "ConOps" Β· BASED ON ANNEX A TEMPLATE
In SORA 2.5, the concept of ConOps has been replaced by Detailed Operational Information (DOI).
DOI is the structured information baseline that underpins all subsequent risk assessment steps (Annex A, ED Decision 2025/018/R).
Fill in the essential information below. Expand Full ConOps if you wish to add a complete operational description.
β‘ QUICK LOAD β MISSION FILES
Upload ArduPilot mission files to automatically populate waypoints, calculate flight time and energy.
Formats: QGC WPL 110 (.waypoints) Β· QGC Plan (.plan) Β· Litchi CSV
βΈ A1 β IDENTIFICATION
Coordinated Universal Time (UTC / Zulu)
Auto-calculated from waypoints and cruise speed
βΈ A2 β UAS CHARACTERISTICS (SORA 2.5 QUANTITATIVE GRC)
SORA 2.5 replaces MTOM-based GRC with characteristic dimension (m) and max speed (m/s) as primary parameters (Annex F, Table 2).
Largest dimension (diagonal for multirotor)
Default 10 m/s. Used to calculate flight time from waypoints.
Hover/dwell time per waypoint (hover, photo etc). Default 0 s.
βΈ A2b β ENERGY CALCULATION & BATTERY BUDGET
Energy consumption per flight phase as % of total battery per minute.
Values are pre-filled from the UAS database when you select a model above β adjust to match your actual experience.
Fixed overhead before take-off
High power β vertical ascent phase
Horizontal cruise phase
Lower power β descent phase
Recommended β₯20% (RTL margin)
βΈ A3 β OPERATION CATEGORY & FLIGHT REGIME
βΈ A4 β OPERATIONS VOLUME & LOCATION
Ground risk buffer (SORA 2.5 Β§2.2.4)
Adjacent area (SORA 2.5 Β§2.2.5) β used in containment step 8
Adjacent airspace (SORA 2.5 Β§2.2.6)
βΈ A5 β FULL ConOps / DOI (OPTIONAL)
Detailed operational description per SORA 2.5 Annex A. Complete the sections relevant to your operation.
All information here is included in the final briefing document.
Step 2 β Volume Planner
// FLIGHT GEOGRAPHY Β· CONTINGENCY VOLUME Β· GROUND RISK BUFFER (DIPUL METHOD)
Configure your operational volumes based on kinematic parameters. The map uses your waypoints from Step 1.
The calculated buffers will automatically carry over to the Containment and Risk Assessment steps.
Typical: 3.0s
Typical: 1.0s
MAP & SAFETY BUFFERS
VOLUME RADII
β Flight Geography: 0 m
β Contingency Vol: 0 m
β Ground Risk Buffer: 0 m
TOTAL RADIUS: 0 m
Steps 2β7 β iGRC Β· GRC Β· ARC Β· SAIL
// SORA 2.5 QUANTITATIVE RISK ASSESSMENT Β· JARUS JAR-doc-25 TABLE 2
βΈ STEP 2 β INTRINSIC GROUND RISK CLASS (iGRC)
SORA 2.5 determines iGRC from characteristic dimension (m) and max speed (m/s) + population density.
Dimensions fetched automatically from DOI step. iGRC scales 1β10; values >7 are outside SORA scope (certification category).
βΈ STEP 3 β GROUND RISK MITIGATIONS (FINAL GRC) β ANNEX B
SORA 2.5 categorises mitigations as M1A (sheltering), M1B (operational restrictions), M1C (ground monitoring) and M2 (technical energy reduction on impact).
βΈ STEP 4 β INITIAL AIR RISK CLASS (ARC) β DECISION TREE
Initial ARC is determined from the Airspace Encounter Class (AEC) decision tree
[SORA v2.5 Main Body, Figure 6 and Annex C, Table C.1]. Answer each question in order.
βΈ STEP 5 β STRATEGIC MITIGATION (RESIDUAL ARC)
The operator may demonstrate that the local manned traffic density in the operational
volume is lower than the generalised AEC rating, reducing the ARC.
[SORA v2.5 Annex C, Table C.2] | Note: AEC 10, 11 and 12 are not in Table C.2.
βΈ STEP 6 β TACTICAL MITIGATION PERFORMANCE REQUIREMENT (TMPR)
TMPR is determined automatically from the residual ARC.
VLOS/EVLOS operations are exempt from TMPR β see-and-avoid is an acceptable
tactical mitigation for all ARC levels. [SORA v2.5, Section 4.6.4]
// LIVE SORA 2.5 ASSESSMENT
β
iGRC
β
FINAL GRC
β
RESIDUAL ARC
β
Step 8 β Containment
// NEW DEDICATED STEP IN SORA 2.5 Β· ANNEX E Β§E.4
Containment ensures that the Target Level of Safety is achieved in the adjacent area.
In SORA 2.5, containment is a dedicated step (#8) before OSO. Three robustness levels: Low / Medium / High.
Requirements depend on UA size, SAIL, population density in adjacent area, and presence of crowds within 1 km.
βΈ ADJACENT AREA
βΈ CONTAINMENT MEASURES
// CONTAINMENT ASSESSMENT
Select containment parameters above for assessment.
Step 9 β OSO (17 Operational Safety Objectives)
// SORA 2.5 ANNEX E Β· OSO #01β09, #13, #16β20, #23β24 Β· CLICK TO TICK OFF
SORA 2.5 has 17 OSOs with specific numbering: #01β#09, #13, #16β#20, #23β#24.
Note: OSO #10 (from 2.0) has been merged into OSO #05 in version 2.5. Numbers #10β#12, #14β#15, #21β#22 do not exist in SORA 2.5.
Robustness level (Low/Medium/High) is based on your SAIL. Click to mark as fulfilled.
OVERALL PROGRESS
0 / 17 confirmed
βΈ TECHNICAL ROBUSTNESS (OSO #01β#09)
βΈ OPERATOR & PERSONNEL (OSO #13, #16β#17)
βΈ HUMAN & AUTOMATION (OSO #18β#20)
βΈ ENVIRONMENT & EXTERNAL FACTORS (OSO #23β#24)
Weather & Airspace Requirements
// MANUAL INPUT Β· DIRECT LINKS TO SMHI & YR.NO Β· LIVE ASSESSMENT
βΈ OPEN WEATHER SERVICE IN NEW TAB β ENTER VALUES BELOW
Enter coordinates in the DOI step β the links below open the correct forecast page automatically.
Assessment updates in real time as you enter values in the fields.
βΈ CURRENT WEATHER CONDITIONS
WIND SPEED
Max recommended: 8 m/s (15.5 kt)
WIND DIRECTION
0β360Β°
VISIBILITY
VLOS minimum: 800m
CLOUD COVER
0β8 oktas
TEMPERATURE
Check UAS operating temperature range
RELATIVE HUMIDITY
High humidity β icing risk
PRECIPITATION
>0.5 mm/h = avoid
AIR PRESSURE
Reference: 1013 hPa
| Time | Temp (Β°C) | Wind (m/s) | Gust (m/s) | Prec (mm) | Cloud (%) | Visi (m) |
|---|---|---|---|---|---|---|
| Click fetch to load hourly data... | ||||||
βΈ AIRSPACE MAP
In-app maps use ESRI WorldTopo as base layer. With an OpenAIP API key (free account at openaip.net) a complete airspace overlay is added to all maps β CTR, TMA, restrictions, UAS zones etc.
Without a key, no airspace data is shown on the map (use the external links below).
The key is saved in the browser localStorage and loaded automatically on next start.
Register free at openaip.net β My Account β API Keys
βΈ METAR Β· TAF (CHECKWX) & MANUAL NOTAM
Fetches METAR and TAF within a 50 km radius via CheckWX.
NOTAMs cannot be fetched automatically (since we do not use US sources and no free European APIs exist). Use the links below for LFV ARO or Eurocontrol EAD and paste manually.
βΈ RADIO FREQUENCIES & CONTACTS (<50KM)
Click Refresh or load coordinates to calculate nearby airport frequencies.
βΈ AIRSPACE AUTHORISATIONS
βΈ LOCAL RESTRICTIONS
Emergency & Contingency Plan
// EMERGENCY & CONTINGENCY PROCEDURES
βΈ EMERGENCY PROCEDURES
βΈ CONTINGENCIES β OPERATION ABORT
βΈ RESCUE & REPORTING
Threats and Error Management (TEM)
// IDENTIFICATION AND MITIGATION OF THREATS & ERRORS
Threats are events or hazards that occur outside the influence and control of the flight crew or operational personnel. An error is an action or inaction by an operational person that leads to deviations from organizational or personal intentions and expectations.
βΈ THREATS
βΈ ERRORS
Charts & Annexes
// UPLOAD FLIGHT CHARTS, MAPS OR PERMITS (PDF OR IMAGES)
Upload PDF files or Images (PNG/JPG) of your flight charts, U-space approvals or operational area maps.
These will be automatically appended to the final Briefing document.
Operations Briefing
// GENERATED DOCUMENT β READY TO PRINT OR SAVE
OPERATIONS BRIEF β GENERATED
Operational Flight Plan
// UAS OFP Β· BASED ON ADS/LUND UNIVERSITY OFP TEMPLATE REV 03
Generate briefing first, then click OFP FLIGHT PLAN in the nav bar.
Settings
// API KEYS Β· PREFERENCES Β· APPLICATION SETTINGS
API keys are stored locally in your browser's localStorage and are never sent to any server other than the respective API provider.
They persist between sessions automatically.
βΈ OPENAIP β AIRSPACE DATA
Enables airspace overlay on all in-app maps (CTR, TMA, restrictions, UAS zones). Register free at openaip.net β My Account β API Keys.
βΈ CHECKWX β METAR / TAF WEATHER
Used to fetch METAR and TAF reports within 50 km of your operation area. Register free at api.checkwx.com.
βΈ APPLICATION PREFERENCES
0
βΈ DATA MANAGEMENT
Clearing API keys removes them from localStorage. Mission data is only cleared when you start a new plan.
βΈ ABOUT MISSIONDESK
APPLICATION MissionDesk β EASA SORA UAS Operations Briefing System
REGULATION EASA SORA v2.5 Β· EU 2019/947 Β· EU 2019/945 Β· ED Decision 2025/018/R
FRAMEWORK Tauri v1.6.3 Β· Vite Β· Vanilla JS ES Modules
DATA SOURCES CheckWX (METAR/TAF) Β· OpenAIP (Airspace) Β· SMHI (Observations)