What is 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, No, it does not work as it was intended to, and there is a long list of reasons why.
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 comes in the form of a module attached to the drone, like the Dronetag Mini attached to the Mavic 3 below.
As you can see, we have a network remote ID module and have tested it with various apps; it is a far more robust solution to the problem of security and privacy concerns.
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, but there are risks for operators and a leave the public with false sense of security. Being told by regulators of the virtues of DRI, yet not informed of the limitations
Why is DRI 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 closed nature of the software, which means about 50% of the public will never be able to detect the drone over their house, as was intended.
- Many Android platforms fail to detect DRI signals. In a recent audit by an NAA, who has 6 devices with them, they detected the DRI on one device briefly, before it disappeared and didn’t detect it again. The drone was within feet of the android device.
- The range of Wifi and Bluetooth signals are very limited. The expectation by the regulators is that everyone is flying within the regulations, which is not always the case.
- If the person does not have their operator ID input, the drone’s serial number is broadcast. A great 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.