BVLOS Drone Inspection in Europe: What Automation Software Can—and Cannot—Do
A dock and autonomous route enable remote operations technically; they do not grant permission. In Europe, BVLOS normally requires a specific-category pathway and risk controls matched to the concept of operations.
Quick answer
Under the EASA framework, an operation outside open-category limits—such as BVLOS—generally falls in the specific category. The operator may use an applicable standard scenario or predefined risk assessment, or seek operational authorization supported by a risk assessment such as SORA. Software can provide planning, status, logs, intervention and evidence, but it does not replace regulatory approval or the operator’s responsibilities.
Why BVLOS usually falls in the specific category
The open category normally requires the remote pilot to keep the aircraft in visual line of sight, subject to its detailed conditions. EASA identifies BVLOS as a typical example of the specific category. Specific-category operations require the applicable declaration or operational authorization unless covered by another valid framework such as suitable LUC privileges.
Requirements depend on the operation, state and current rules. This article is a technical planning overview, not legal advice. Use current EASA and national aviation authority material and involve a qualified aviation professional before committing to a deployment.
- Describe the concept of operations, airspace, ground area and mission frequency.
- Identify hazards and the required containment, communications and contingency controls.
- Select an applicable standard scenario, PDRA or risk-assessment pathway.
- Demonstrate operator competency, procedures, maintenance and system assurance.
- Obtain the required declaration acceptance or authorization before operation.
PDRAs can help frame common inspection operations
EASA publishes predefined risk assessments for selected operation types. PDRA-G03 addresses linear inspections and agricultural work under stated conditions, while other PDRAs cover surveillance and different BVLOS environments. A PDRA is not a blanket permit; the operation must fit its conditions and the operator follows the application pathway.
If the mission does not fit a standard scenario or PDRA, a tailored risk assessment may be necessary. Avoid choosing hardware first and then trying to force the operation into a category. Define the route, area, airspace and response need early.
| Planning layer | Question | Evidence |
|---|---|---|
| Operation | Where, how often and for what inspection purpose? | ConOps and route/site maps |
| Air risk | How are other airspace users detected or separated? | Airspace analysis and mitigations |
| Ground risk | Who or what may be exposed? | Ground-area analysis and containment |
| System | How do command, navigation and recovery behave? | Technical assurance and test records |
| People | Who supervises and intervenes? | Roles, competency and procedures |
What automation software can contribute
Software can standardize route creation, geofences, schedules, readiness checks, live telemetry, video, alerts and mission records. It can make manual intervention available and retain evidence that the approved workflow was followed. Local processing can reduce dependency on a public internet path for selected functions.
SAI-HUB DD supports DJI Dock 2 and Dock 3 mission and virtual-cockpit workflows with on-premises Brain-Box processing. These capabilities may support an operational case, but the competent authority evaluates the complete operation, not the presence of one software feature.
- Implement approved routes and operational boundaries.
- Expose dock, aircraft, weather and connectivity status.
- Provide live information and intervention functions.
- Record mission, media, detection and operator events.
- Support controlled updates and configuration evidence.
What AI detection does not prove
An object-detection model aimed at people, vehicles, smoke or inspection targets is not automatically a detect-and-avoid system for cooperative and non-cooperative air traffic. Airspace risk mitigation has specific performance and assurance requirements. Do not use a payload analytics claim as evidence of collision avoidance unless the system is approved for that function.
Similarly, autonomous mission completion does not remove the remote operator. Define who watches status, who receives alerts, how quickly they can intervene and what occurs after link loss or a failed landing. Human oversight must match the authorization and operations manual.
Build evidence through staged operations
Start with VLOS or otherwise authorized supervised trials at the intended site. Demonstrate route containment, communications, weather limits, local processing, alert workflow and recovery. Exercise failures and document results. Progress toward broader operations only when authorization and evidence allow it.
Treat changes to aircraft, dock, software, route, communications or AI as configuration changes that may affect the safety case. Keep versions, maintenance records and training current. Check EASA and the relevant national authority because requirements and acceptable means evolve.
- Mission success and containment across representative conditions.
- Link performance, latency and loss-of-link behavior.
- Remote-supervisor workload and intervention drills.
- Dock recovery, alternate landing and site access.
- Configuration, update and audit records.
Frequently asked questions
Is BVLOS drone inspection legal in Europe?
Yes, when conducted under the applicable EASA and national framework with the required declaration, authorization or privileges and mitigations. It is not automatically permitted by owning a dock or autonomous software.
Do I need SORA for every BVLOS operation?
Not always. An operation may fit a standard scenario or PDRA, or an operator may have relevant LUC privileges. Otherwise a tailored risk assessment such as SORA may support authorization. Confirm with the competent authority.
Can SAI-HUB DD be used for BVLOS workflows?
It provides remote planning, live situational awareness, records and intervention functions for DJI Dock operations. Legal suitability depends on the complete approved concept of operations and configuration.
Does AI object detection count as detect-and-avoid?
A general inspection detector should not be assumed to meet aviation detect-and-avoid requirements. DAA is a safety function with specific performance, integration and assurance needs.