I thought as soon as you turn on the drone motors it breaks the WiFi transmission anyway
Ach have a look at the FAA ( American) videos about this. They seem to live in a utopian world of the future, where it wont be uncommon to see loads of drones in the sky all at once. With people noticing this and instantly checking an app to see why a particular drone is flying. Its a load of boll***s their vision of the future. I do hope the CAA don’t go down this route ![]()
![]()
![]()
My Mini 3 Pro is interesting in that its “RID Sometimes. But not often”.
I’m in an area where its a legal requirement, supported by the firmware and the certificate sent by the authorities has been downloaded to the drone.
So from my end user perspective here, it should “just work” but usually its not.
Stock firmware, with and without FCC mod using a Pixel phone or Samsung tablet with the N1.
In the last month its appeared on exactly 1 flight.
I have no doubt at all the CAA will go down that route.
The consultation results were pre-decided before starting. We know their aim.
For sure. Unfortunately a minority of dickheads that make the news means it’s inevitable.
This is going too far anyone would think we are flying predator drones
So with all the fuss about Remote ID in the US and the mention of it being implemented in the EU, I thought I’d do a search…
It picked up this page.
The big shock was that the initial consultation meeting is going on right this minute… as I post this…

Anyway, it does look like the EU requirements do not cover “privately built” UAVs, but it’s hard to work it out in all the EASA technical waffle.
The CAA page does say:
Don’t think anyone at all believes that last sentence.
This is all about being seen to have a process even if the outcome is pre-determined.
I’ve only just recently been trying or acknowledging as to how this remote id will work if & when it’s implemented,
Or more so since I’ve got a new drone that apparently has remote id within the software,
As per this below was showing remote I’d when running a mod but went when the mod was removed,
So is it now a case for us who’s drones have remote id within the software just now a case of that if & when or if it’s ever implemented, is it then a case the authorities turn on a switch or put a plug in figure of speech, then we are broadcasting for sure, am I right or wrong ? Or would there be another update we would have to do on our drone ? Or an update we could avoid ?
My guessing it’s to late as I’m sure it’s already in the software as shown above it’s capable of broadcasting.
It depends on your drone.
On newer ones, they’re all capable of remote ID but when it becomes mandatory they push a firmware update out that switches it on for that geographical location.
Typically they package these unpopular updates with useful feature improvements in the same release to “encourage” people to update.
Remember regardless of this you’re still transmitting Aeroscope ID and location information anyway.
Firstly thanks for replying to my question & Yes as I understand the drone id but only more so recently,
As said above, never really took any notice of it not because of blatant disregard or ignorance, just never thought it would be a thing tbh, another factor with myself I thought the drone would be just a 5 min wonder, also I probably would have never known any of this or many other things had I had not joined GADC,
Also where this is concerned I’m not the greatest at learning or understanding but I know more than this time last year even if it is only a little, or at least I have a bit of knowledge to take away sometimes, every day is something new ![]()
VLOS will have to go to BVLOS as they are talking load of nonsense about the orientation of your Drone at VLOS and knowing that but quite happy to look at BVLOS for medical deliveries , post , Amazon so the safety in those is same as our stuff , in fact the suggestion from Amazon was that if they had a failure the should destroy it into more parts coming from the sky
Bored now. It is out of our control. It will happen … or not.
![]()
done deal mate ![]()
BVLOS isn’t going to happen on recreational drones for a long time.
Until they have correct detect and avoid it simply isn’t going to happen.
The delivery/medical ones at the moment work by having specific drone corridors to use to minimise conflicts and still have a human in the loop.
The same systems and kit are not in, or even slated to be in, or even standardised off the shelf gear for general public to use.
Until they have fully functional detect and avoid (and self-id which is coming), they’re not safe for BVLOS.
Orientation is essential for safe VLOS as again without knowing that, you cant reliably avoid conflicts by moving in a known direction.
I’d like to see the faces of the CAA people when they get slammed with hundreds of GDPR breaches as under the regs:
Under s170, it is a criminal offence to: Knowingly or recklessly obtain, disclose or procure personal data without the consent of the data controller. Sell that data. Recklessly retain personal data – even if it was obtained lawfully – without the consent of the data controller.
Fines of up to £17.5 million under the UK GDPR,
There’s also a possibility that forcibly disclosing a person’s location using this technology without the users consent could be in contravention to the Computer Miss-use Act of 1990, and to act on that information might contravene the Wireless Telegraphy Act of 2006.
In my previous life, if we wanted to perform any interrogation of a network within the host country we needed a special warrant issued by the Secretary of State.
It’s one thing to scan for a list of SSID’s, we all do this when we want to log into a public network, or private network with the admins permission, but it’s a whole different matter to identify a specific individual, along with their location and other unique information. The last time I checked I couldn’t just call up EE and ask them to give me the location of a specific handset, or ask for historic data to correlate the movement of a handset.
CAA will just write it in to the drone code and make it a condition (that you accept) when flying ![]()
If they do that, how would they react to thousands of “Subject Access Requests” from every body that has to have RID?
They must comply with these requests, unless they are “manifestly unfounded”, or “manifestly excessive”, basically if you’re requesting it to make again from it (eg financial or materially), or if you submit multiple (personal) requests. Each one of the requests must be dealt with so that the reply does not identify any other individual personally, (lots of redacted documents) and must only be your information. If they make a cockup (CAA, surely not) and include any info that’s not yours, they can be fined up to £8.7 million for each breach.
