Report 061 · Defense Tech
There is a drone hovering over your property. You own a rifle, and you could buy a jammer online this afternoon. The engineering question, how do I bring that thing down, has four good answers. Each one of them is a separate federal crime, under a separate statute, and only four departments of the federal government are exempt from any of them. The detection half surprises people most.
I spent my Army career on the counter side of remote-controlled threats. Counter-IED and electronic warfare, which is mostly the discipline of thinking very carefully about somebody else's radio link. So when people ask me what to do about a drone over their house, my instinct is to answer the engineering question, and the engineering question is not hard. There are four families of counter-drone technique and I can describe all of them.
The problem is that the engineering answer and the legal answer have almost nothing to do with each other, and the gap between them is not a technicality. It is the entire subject. Nearly every consumer-facing article on this gets it half right: it tells you not to shoot, and then stops, as if shooting were the only prohibited option and everything quieter were a workaround. It isn't. The quiet options are prohibited too, by different laws, for different reasons, and one of them applies before you have done anything to the drone at all.
So here is the map, statute by statute, with what each countermeasure physically does and which law it runs into. Everything below is quoted from the U.S. Code or from the Congressional Research Service.
This is the load-bearing fact, and it is much broader than most people expect. Federal law defines an aircraft, at 49 U.S.C. § 40102(a), as "any contrivance invented, used, or designed to navigate, or fly in, the air."
Read that again. There is no weight floor, no altitude qualifier, no carve-out for hobby equipment, no requirement that anyone be aboard. A contrivance designed to fly in the air. A $200 quadcopter satisfies that definition as completely as a 737 does.
That matters because of what attaches to the word. Under 18 U.S.C. § 32(a)(1), it is a federal felony to "set fire to, damage, destroy, disable, or wreck any aircraft in the special aircraft jurisdiction of the United States or any civil aircraft used, operated, or employed in interstate, overseas, or foreign air commerce." The penalty in the same subsection: a violator "shall be fined under this title or imprisoned not more than twenty years or both."
Twenty years. That statute was not written with quadcopters in mind, and the jurisdictional language does real work that a short article should not pretend to resolve. But the definition of aircraft is the definition of aircraft, and it is the reason every serious source tells you the same thing about the shotgun. It is not a property-rights question, and the drone being over your yard is not the relevant fact.
Now the part that is usually missing. "Don't shoot it down" is one line of a four-line answer, because there are four physically distinct ways to interfere with a drone and they are governed by four different bodies of law.
Kinetic. Shoot it, net it, ram it, hit it with anything. You are damaging or wrecking an aircraft. This is the 18 U.S.C. § 32 branch described above, and it is the one everybody already knows about.
Radio-frequency jamming. Radiate energy on the control and video bands until the link stops resolving. This is the technique I used to work with professionally, and it does not touch § 32 at all, because you have not laid a finger on the airframe. It runs into the Communications Act instead. 47 U.S.C. § 333 is one sentence long: "No person shall willfully or maliciously interfere with or cause interference to any radio communications of any station licensed or authorized by or under this chapter or operated by the United States Government."
Protocol takeover, sometimes called spoofing or hijacking. Instead of drowning the link, you speak on it. You send commands the aircraft accepts as legitimate and fly it away, or you feed its navigation receiver a counterfeit position and let it correct itself into the ground. Physically this is elegant, and it is the technique vendors like best because it ends with an intact drone on the ground instead of debris. Legally it is not a spectrum problem, it is a computer problem: you are issuing instructions to somebody else's computer without authorization.
Detection. Not attacking the drone. Listening to it. And this is where the article you read last week probably stopped short.
Passive RF detection is the most reasonable-sounding counter-drone measure there is. You radiate nothing, you touch nothing, you break nothing. You put up a receiver and it tells you a drone is present. What could possibly be wrong with listening?
It depends entirely on how deep you listen. There is a real difference between detecting that energy exists on a band and decoding what that energy says. Most commercial drone-detection systems do the second thing, because the second thing is what makes them useful. They demodulate the control and telemetry link to tell you the make and model, the drone's position, and often the operator's position. That last feature is the one people buy the system for.
But a control link is a communication between two parties, and reading it is interception. The Congressional Research Service names this directly. In its March 2025 report on Department of Defense counter-UAS efforts, CRS writes that "there are a number of applicable federal laws that might prohibit DOD from operating certain equipment for detecting and mitigating UAS within the United States, including statutes prohibiting interference with the signal spectrum, computer hacking, wiretap, and tampering with or damaging an aircraft."
Note what that sentence is about. It is not about private citizens. It is about the Department of Defense, on the question of whether it may operate detection equipment inside the United States. And note the verb pairing: detecting and mitigating. The prohibitions in play do not begin at the moment you attack the drone. Some of them begin at the moment you decode it.
If the constraint is tight enough that DOD's own general counsel has to work around it, the answer for a homeowner with a $3,000 detection box is not going to be more permissive.
So who is allowed to do any of this? CRS is precise: "DOD is one of four federal agencies — the others are the Department of Energy (DOE), Department of Homeland Security (DHS), and Department of Justice (DOJ) — granted limited authority by Congress to take actions against drones."
Four departments. Not four thousand police forces, not private security firms, not stadium operators, not you.
And the way Congress wrote those authorities tells you more about the underlying law than any summary could. Look at how 10 U.S.C. § 130i, the Defense Department's authority, opens. Before it grants the Secretary of Defense anything, it has to clear a path:
"Notwithstanding section 46502 of title 49, or section 32, 1030, or 1367 or chapter 119 or 206 of title 18"
The Homeland Security and Justice authority at 6 U.S.C. § 124n opens with essentially the same list. Now decode it, which CRS effectively does in the sentence quoted above. Section 46502 of title 49 is aircraft piracy. Section 32 of title 18 is destruction of aircraft. Section 1030 is computer fraud, the statute behind the takeover case. Section 1367 is interference with a satellite. Chapter 119 is the wiretap chapter. Chapter 206 is pen registers and trap-and-trace devices, the law about capturing the addressing information of a communication rather than its contents.
That "notwithstanding" list is a confession. Congress had to name six separate criminal provisions to get out from under them, which means those six provisions are exactly what ordinary counter-drone activity collides with. The last two are the tell. Chapters 119 and 206 are not there because DOD might shoot a drone. They are there because DOD might listen to one.
What each authority then permits is a graduated ladder. Under 6 U.S.C. § 124n(b)(1) the authorized actions run from "detect, identify, monitor, and track the unmanned aircraft system or unmanned aircraft, without prior consent," through warning the operator, to "disrupt control of the unmanned aircraft system or unmanned aircraft, without prior consent," then seizing or exercising control of it, then confiscating it, and finally to "use reasonable force, if necessary, to disable, damage, or destroy the unmanned aircraft system." Section 130i grants DOD a parallel set.
Notice that even for the agencies that hold the authority, it is not general. Section 124n ties it to a "covered facility or asset," which the statute's definitions require to be identified as high-risk and a potential target for unlawful unmanned aircraft activity, located in the United States, and directly related to specified federal missions. The authority is attached to places, not granted at large. There is a route for state, local, tribal and territorial law enforcement to act under § 124n, but it runs through that federal framework and required training, not around it.
Of the four techniques, jamming is the one people are most convinced should be allowed, because it feels proportionate. You are not destroying anything. You are just making the drone go away.
I want to explain why that intuition fails, from the operator's side rather than the lawyer's, because this is the part I actually know.
A jammer is not a shield and it is not aimed in any meaningful sense. It is a transmitter. It radiates power across a band, and a band is shared. The consumer drone bands are 2.4 and 5.8 GHz, which is to say Wi-Fi. The navigation band is GPS, which is to say the timing reference underneath cell networks, aviation, and a great deal of infrastructure that has no idea you have a drone problem. When I have written before about electronic fratricide, this is the mechanism: the counter-IED jammers that protected convoys in Iraq also took down the radios of the units they were protecting, because a transmitter has no way of knowing whose receiver it is reaching.
Now put that device in a residential neighborhood. Your neighbor's Wi-Fi, the medical alert pendant three houses down, the aircraft on approach overhead. The reason § 333 has no residential exception is not that Congress failed to consider homeowners. It is that a jammer with a residential exception is not a different device. There is no version of it that stops at your property line, because radio does not know where your property line is.
The same physics is why the FCC treats jamming equipment as unlawful to market and sell, not merely to use. You cannot regulate the intent of a transmitter. You can only regulate the transmitter.
Having taken away all four techniques, I should say what remains, because "nothing" is not the honest answer.
What remains is everything that does not touch the aircraft or its link. Document it: time, date, direction, duration, photographs. Drones above a certain weight are required to broadcast Remote ID, which a phone app can receive as a broadcast without decoding a private link, and which is designed to be read. Report it to local law enforcement and to the FAA, which is the agency with actual jurisdiction over the airspace. If the drone is being used to look into your home, the conduct is likely reachable under state privacy, harassment, stalking or voyeurism law, which is where these cases mostly get resolved in practice, and which does not require you to touch the drone at all.
That is unsatisfying. It is unsatisfying in the same way that "call the police" is unsatisfying when someone is in your driveway right now. But the alternative on offer is a felony with a twenty-year ceiling, and the person most likely to be identified afterward is the one who fired from a known address at a known time.
A few things I am not claiming. I am not a lawyer and this is not legal advice. Whether § 32 reaches a particular small drone in a particular flight involves jurisdictional elements I have quoted but not analyzed, and that is a question for counsel and for courts, not for me. State law varies enormously and I have not surveyed it. The counter-UAS authorities have been amended repeatedly and the state and local provisions in § 124n are recent enough that the practical rules are still settling. I have quoted the statutory text as it currently reads and the CRS report as of March 31, 2025.
I have also deliberately not cited the FAA and DOJ interagency legal advisory on this subject, which is the best single document on it, because the copies I could reach today would not open. It exists, it is authoritative, and it is worth finding.
The thing to carry out of this is not the list of statutes. It is the structure underneath them.
Counter-drone is not one capability with one rule. It is four different physical interventions, and the law tracks the physics almost exactly: damage the airframe and you are in aviation law, radiate at the link and you are in communications law, speak on the link and you are in computer-crime law, decode the link and you are in surveillance law. That is why there is no single "can I stop a drone" answer, and why an article that only warns you about the shotgun has told you a quarter of it.
And it is why the exemption Congress wrote is shaped the way it is. When the government wanted to defend its own installations, it did not pass a counter-drone law. It passed a list of six criminal statutes it needed to be excused from. If you want to know what the real constraints on a technology are, that list is usually a better guide than the marketing copy of anyone selling you a box.
U.S. Army combat veteran (Counter-IED / Electronic Warfare), peer-reviewed researcher in microwave spectroscopy, and founder & CEO of Shroombiosis. Consults on laboratory operations, AI, and supplement formulation.