“Can I legally detect drones flying over my property?” We get this question weekly, and the short answer in the US, UK and EU is: receiving is fine, jamming is a crime, and the data you log has its own rules. This article maps the lines — it is not legal advice, and the regulations deserve a lawyer’s read before you act on them.
Receiving is (mostly) legal
Passive detection — listening to what a drone broadcasts or transmits — is generally lawful. Remote ID broadcasts are, by design, public signals: regulators built the system precisely so that third parties could receive them. A RID receiver or an RF sensor that only listens stays on the right side of interception law in the jurisdictions we advise on. Lawfulness still depends on the country, what the equipment captures, where it is deployed and who operates it — verify local rules before any fixed installation. Radar is different in kind: transmitting energy into the airspace can trigger aviation and planning rules that a receiver never touches, which is one more reason it sits outside our advisory scope.
Jamming is a crime — full stop
Everything that transmits to stop a drone — jammers, spoofers, force-landing devices — is illegal to operate for almost everyone in the US, UK and EU. In the United States the FCC treats jamming as a violation of the Communications Act with substantial penalties; in the UK the Wireless Telegraphy Act does the same work. Only a handful of government agencies hold exemptions. Buyers frequently ask us “and then it lands it, right?” — and the answer is that the kit which does that is not something a private site can legally switch on. (Sources: FCC jammer enforcement guidance; Ofcom/WTA framework.)
The data you log is the quiet trap
A detection log is not anonymous. A Remote ID record ties a serial number to a position and a timestamp; correlated over time, it traces an individual pilot’s home and habits. Under GDPR in the EU, and under comparable privacy expectations elsewhere, that makes detection logs personal data — with retention limits, access control and a lawful basis attached. We say this as advisers, not lawyers: the detection project that forgets data protection usually discovers it in the worst possible meeting. Our own handling is published on the privacy page.
How we evaluated the rules
Method: this summary rests on the published positions of the FCC, Ofcom and EU data-protection guidance, checked September 2026, plus the Regulatory texts themselves (14 CFR Part 89 for the US, the UK CAA framework for Britain). We are technologists, not a law firm — where your deployment touches aviation authority permissions, security-of-persons exemptions or employment law, get professional advice.
| Action | US | UK / EU |
|---|---|---|
| Receiving broadcasts (RID/RF listening) | Generally lawful | Generally lawful |
| Jamming / spoofing / force-landing | Illegal (FCC) | Illegal (Ofcom / WTA) |
| Logging detection data | Fine; mind data care | Personal data under GDPR |
| Sharing logs publicly | Careful | Lawful basis required |
Where to go next: the survey checklist includes the data-handling check most deployments skip, and the free screening is the place to surface compliance questions before they become procurement questions.
Sources: FCC jammer guidance; Ofcom / Wireless Telegraphy Act framework; 14 CFR Part 89; GDPR guidance. Not legal advice.