The reality of Direct Remote ID

What is Direct Remote ID

EASA Direct Remote ID

Direct Remote ID, or DRI as we will refer to it from here on, is a Digital Signature emitted from the drone, which is meant to allow the public and authorities to identify the drone and the operator, including their location, much in the way that a license plate identifies a vehicle.

How does DRI work?

The drone operator inputs their unique Operator Registration number, obtained at registration with their National Aviation Authority, into the drone’s controller. From this point, as soon as the motors start to spin, the drone emits the Operator Registration number in the form of a Bluetooth and Wifi signal.

Does Direct Remote ID work?

The simple answer is that it does not work as intended, and there are numerous reasons for this.

Direct Remote ID vs Network Remote ID

The fundamental difference between Direct Remote ID and Network Remote ID is the broadcast method. DRI uses Bluetooth and Wi-Fi, which have very limited range and compatibility issues. Network Remote ID uses a GSM/LTE network to pinpoint the drone’s location, assuming it has signal coverage; range is only limited by network coverage. Network Remote ID is provided as a module attached to the drone, such as the Dronetag Mini connected to the Mavic 3 below.

As you can see, we have a network remote ID module that we have tested with various apps; it is a far more robust solution to the problem of security and privacy concerns.

DJI Mavic 3 with Dronetag

The concept of DRI

While the concept of direct remote ID is good, the implementation is far from acceptable. The social acceptance of the public being able to identify a drone over or near their property is fair. Still, there are risks for operators, and it leaves the public with a false sense of security. Being told by regulators of the virtues of DRI, yet not informed of the limitations

Why is Direct Remote ID so Ineffective?

These are some of the reasons why DRI has failed and will continue to fail until updated regulation is implemented. 

  • iPhones cannot detect DRI due to the software’s closed nature, meaning about 50% of the public will never be able to detect the drone over their house, as intended.
  • Many Android platforms fail to detect DRI signals. In a recent audit by an NAA, which had six devices with them, the DRI was detected on one device briefly before it disappeared and was not detected again. The drone was within feet of the android device.
  • The range of Wifi and Bluetooth signals is minimal. Regulators expect everyone to fly within the regulations, but this is not always the case.
  • If the person does not have their operator ID input, the drone’s serial number is broadcast. An excellent backup until you realise the NAA does not have a list of serial numbers, as they are no longer required under EASA regulations. 
  • Direct Remote ID cannot be used to deconflict UAS traffic.

Share this post with your friends