Remote ID - The Good, the Bad and the Ugly - Everything you need to know

[PingSpike]

CAP3105, published today, contains significant information relating to Remote ID.

We propose to:

• Implement Direct Remote ID product and operational requirements from 1st January
2026. These requirements will come into force for UK1, UK2, UK3, UK5 and UK6 UAS, unless exempted under a Specific Category Operational Authorisation (OA).

• Amend the regulation to extend the implementation of Direct Remote ID product and operational requirements from 1st January 2028. The further requirements will come into force for:

• UK0 UAS weighing 100g or more with a camera;
• Model Aircraft (e.g. UK4 UAS) unless exempted;
• Privately built UAS weighing 100g or more with a camera;
• Legacy UAS (i.e. those not within the scope of UK class marking) weighing 100g or more with a camera.

And:

Continue to work with government, industry and operators to progress towards geo-fencing and a full Hybrid Remote ID solution (i.e. Network and Direct Remote ID) over a longer time period.

This will support the enforcement of UAS regulations, deter unlawful operations, and will have a low impact to lawful UAS operators. This phased approach provides the time needed to implement geo-fencing and Hybrid Remote ID effectively.

And:

Remote ID is the ability of a UAS to communicate identification and location information during flight. Remote ID will make it possible to differentiate between legitimate UAS operators and those misusing UAS, enabling more effective enforcement and deterrence. The consultation set out the CAA, Home Office, the DfT and police’s views of why Remote ID will be important in mitigating security risks from UAS.

The consultation proposed Hybrid Remote ID as the favoured technical approach to implementing Remote ID – i.e. Network Remote ID as the default approach, with Direct Remote ID providing a back-up in areas of poor connectivity, technically enforced on the device.

Respondents were largely unsupportive of the proposed technical approach to implementing Remote ID, with 85.9% disagreeing.

Yup, 86% DISAGREE.

Never mind that number though, CAA & Cohorts will continue regardless

---

See section 5 of the CAP3105 document for more RID details.