When DJI announced that the Matrice 4D Series had achieved C6 certification in conjunction with the DJI Dock 3, it was a landmark moment for automated drone operations in Europe. But for pilots and operators who rely on manually pilot operations rather than the docking station, one question lingered: what about standalone operations?
That question now has a definitive answer. The Matrice 4D Series C6 marking now covers the standalone configuration when operated with DJI RC Plus 2 Enterprise, subject to the required firmware and official documentation. The hardware was always there. The C6 label hasn't changed. What has changed is that this compliance now covers both configurations, helping operators prepare for STS-02 workflows.
There is one requirement to keep in mind: your aircraft must be running firmware version 17.1.5 or later. If you haven't updated yet, that's where to start.
Matrice 4TD
C6 is a UAS class marking defined under EU Delegated Regulation 2019/945. It supports certain Specific Category standard scenarios, including STS-02, when the operator also meets the operational requirements under Regulation 2019/947.
To carry the C6 label, a drone must meet a strict set of technical requirements that are built into the aircraft itself:
Maximum Take-Off Mass (MTOM): Less than 25 kg, including all payloads.
Maximum Characteristic Dimension: No greater than 3 meters.
Maximum Horizontal Speed: Not exceeding 50 m/s.
Flight Termination System (FTS): A system independent of the flight controller that activates automatically upon permanent C2 link loss. It is not optional and cannot be switched off.
C2 Link Monitoring: Continuous monitoring with four signal-strength levels displayed to the remote pilot: strong, medium, weak, and loss.
Flight Volume Enforcement: The aircraft must support pre-programmed operational boundaries defined before the mission.
The Matrice 4D Series was engineered to satisfy all of these requirements. Its C6 label reflects hardware compliance. What the standalone firmware update (≥17.1.5) does is extend the verified compliance framework to cover RC controller-based operations in addition to the Dock 3 integration that was previously the only certified configuration.
For operators, this distinction matters. It means you can now operate the M4D within a C6-compliant framework whether you're deploying from a dock for fully automated missions or manually piloting from a ground control station. The same aircraft. The same label. Both configurations now covered under the relevant C6 compliance scope.
To understand why this update is significant, you need to understand what C6 actually unlocks, and that means understanding the difference between STS-01 and STS-02.
STS-01 is designed for operations in controlled urban environments using C5-class drones. It requires VLOS (Visual Line of Sight) at all times, caps horizontal speed at 5 m/s, and constrains the pilot to a defined terrestrial zone with specific safety buffer distances. It is a viable framework for many commercial use cases, but it is fundamentally VLOS-limited.
STS-02 is a different category of operation entirely. It is designed for sparsely populated areas using C6-class drones, and it permits BVLOS (Beyond Visual Line of Sight) flight during the mission, provided the aircraft follows a pre-programmed trajectory.
|
Parameter |
STS-02 Limit |
|
Max Altitude |
120 m AGL (up to +15 m near obstacles >105 m, with authorisation) |
|
Max Distance (no observers) |
1 km from the remote pilot (2 km, with nearest observer stationed ≤1 km from the pilot) |
|
BVLOS |
Permitted mid-flight on pre-programmed trajectory |
|
VLOS Requirement |
Takeoff and landing only |
|
Dangerous Goods |
Not permitted |
|
Aircraft Class |
C6 mandatory |
It is important to highlight that VLOS remains mandatory during takeoff and landing. BVLOS operation during mid-flight is only permitted when the aircraft follows a pre-programmed path. This is exactly the type of operation that the M4D's geocaging and flight volume enforcement systems were designed to support.
C6 compliance in standalone mode opens a meaningful set of professional use cases that were previously either impractical without a docking station or inaccessible under STS-01:
Power lines, pipelines, railways, and road corridors that stretch beyond unaided visual range are classic STS-02 territory. Pre-programme the route, deploy the M4D with its RC controller, and execute a compliant BVLOS inspection without the logistical overhead of a Dock 3 installation.
Matrice 4D Inspecting Powerlines
Search operations on vast areas or in areas where the vegetation limits the possibility of maintaining visual line of sight, become viable within STS-02's BVLOS allowance, removing the need to reposition pilots as the aircraft progresses.
Being clear here matters. The Matrice 4D Series carrying the C6 label, and running firmware ≥17.1.5, satisfies the aircraft-side requirements for STS-02. The operator-side requirements remain your responsibility:
STS-02 Declaration or Operational Authorisation submitted to your national competent authority (NCA)
Theoretical Knowledge Certificate covering standard scenarios (issued by your NCA)
STS-02 Practical Skills Certificate specific to this scenario
Operations Manual aligned with STS-02 requirements
Maintenance Manual and Logbook for the M4D
Emergency Response Plan (ERP)
Observer coordination plan if operating beyond 1 km
None of these are waived by the aircraft's C6 status. The drone being compliant means regulators can verify the hardware meets the standard, it does not substitute for your operational authorisation or pilot certification. If you're already operating under STS-01 and holding your standard scenario competency certificates, the path to STS-02 is adding the STS-02 practical assessment and updating your operations manual accordingly.
The Matrice 4D Series was built for C6 operations all along. What this update confirms is that all of that capability is now fully accessible in both Dock and Standalone deployment scenarios, giving operators the flexibility to choose the right configuration for the mission without sacrificing regulatory standing.
Footnote: All regulatory information in this article is referenced against EASA Delegated Regulation (EU) 2019/945 and the EASA Standard Scenarios framework. Operators should verify current requirements with their national competent authority before conducting STS-02 operations.