Report 107 · Luxury Home Security
Something keeps circling the property at dusk. You look for a way to make the airspace over your own land off limits, and you find Section 2209, a federal process for restricting drone flights near a site. There is a real rulemaking behind it, published in May 2026. It is not for you, it never was, and in 2024 Congress quietly closed the one door a private estate might have squeezed through.
This is the most common question I get about drones and private property, and it is usually asked in a slightly desperate tone, because by the time somebody asks it they have already called the police and been told there is nothing to be done.
The search that follows lands on Section 2209 of the FAA Extension, Safety and Security Act of 2016. The summaries are encouraging. Congress ordered the FAA to build a petition process so that site owners could ask for drone flights near their property to be restricted. In May 2026 the FAA finally proposed the rule that implements it.
So the process exists. Three things about it decide whether it does you any good, and the coverage I read got at most one of them right.
The proposed rule is Designation—Restrict the Operation of Unmanned Aircraft in Close Proximity to a Fixed Site Facility, published 6 May 2026 at 91 FR 24650, docket FAA-2026-4558, RIN 2120-AL33. It runs 55 pages and proposes a new 14 CFR Part 74. Comments closed 6 July 2026.
The delay is documented in the rule's own footnotes, and it is remarkable. The 2016 statute became law on 7 July 2016 and gave the FAA 180 days to establish the process. The FAA Reauthorization Act of 2018 told the agency to issue a proposed rule by 31 March 2019 and a final rule within 12 months of that. The FAA Reauthorization Act of 2024 told it again: a proposed rule within 90 days of enactment, a final rule within 16 months of the proposal.
The proposal arrived in May 2026. That is roughly seven years past the 2019 deadline and about nine years after the original process was due. Congress has now set the FAA this same homework three times.
I flag the timeline not to score points but because it is load-bearing for your decision. A proposed rule is not a rule. Nothing in Part 74 is available to anyone today, and given the history, "coming soon" is not a safe planning assumption.
Here is the part that decides the question.
Section 2209 never applied to property in general. It applied to specific categories of what the statute calls fixed site facilities. As originally enacted, those were critical infrastructure such as energy production, transmission and distribution facilities and equipment; oil refineries and chemical facilities; amusement parks; and a fourth catch-all category, "other locations that warrant such a restriction." The 2018 reauthorization added railroad facilities. The 2024 reauthorization added State prisons.
A private residence is not on that list. It never has been. The only conceivable route in was the catch-all, and here is what the FAA says happened to it, describing Section 929 of the 2024 Act:
It also removes the "other locations that warrant such a restriction" category from the list of fixed site facilities.
So the list is now closed: critical infrastructure, oil refineries and chemical facilities, amusement parks, railroad facilities, State prisons. The FAA states the consequence plainly, interpreting "fixed site facilities" to mean permanent, non-mobile facilities, and saying that only owners or proprietors of those types of facilities would be eligible to apply.
If you own a home, however large, you are not an eligible applicant. That is the answer, and it is a statutory one, so no amount of engaging with the FAA changes it.
I want to be precise about one thing, because it is where an eager reader will push back. "Critical infrastructure" is defined broadly, by reference to 42 U.S.C. 5195c(e) and the sixteen sectors in Presidential Policy Directive 21 and National Security Memorandum 22, and those sectors include commercial facilities. If your property genuinely contains qualifying critical infrastructure, that is a conversation with an aviation attorney. A large house with a security concern is not that.
Suppose you are a qualifying facility. It is still worth understanding how small the protected volume is, because this surprises people.
Under the proposal, the lateral boundaries of an unmanned aircraft flight restriction must lie entirely within the applicant's property lines, and the altitude ceiling is capped at 400 feet above ground level. There is one exception: if the tallest component of the facility inside those boundaries exceeds 300 feet AGL, the ceiling can rise to that height plus 100 feet, rounded up to the next 50-foot increment. Proposed § 74.60 spells this out, and proposed § 74.50 says the lateral boundary may not exceed the property boundary or overlap a permanent airspace restriction.
Read that again as a security engineer rather than as a lawyer. The restriction is a column of air over your own land, no wider than your deed, no taller than 400 feet in the ordinary case. A drone hovering just outside the property line at 399 feet, with a good sensor, is entirely lawful and entirely outside your restriction. Anyone who has thought about standoff will recognise the problem: the restriction constrains the volume, and the threat picks the volume.
A restriction can be continuous, meaning active year-round, or part-time, up to 290 consecutive days per year.
The rule is unusually candid about its limits, and one sentence in the preamble is the honest summary of this entire report:
While the UAFR serves as a "virtual no trespassing sign," it does not physically prevent unauthorized access.
That is the FAA describing its own product. It is a legal designation. It informs compliant operators of prohibited activity and it lets regulators and law enforcement act against violators. Violating a standard restriction can bring civil enforcement; the more serious "Special" category can carry civil or criminal exposure. What it does not do is stop an aircraft.
This is the distinction I spent a career on, in a different context. A rule constrains the party who is following rules. The operator who is casing your house, or photographing your guests, or simply does not care, is by definition not in that set. A designation raises the consequence if that person is caught and identified. It does nothing to the aircraft in the air tonight.
Enforcement against an unknown drone depends on identifying it, which is what Remote ID is for. I covered that system, and its curious side effects, in the report on security drones and line of sight: a compliant aircraft broadcasts its position and its operator's position once per second. That is a real investigative tool, and it works precisely as well as the other party's compliance allows.
This is the misreading with the worst consequences, so I will quote the rule twice.
On the proposal generally, the FAA writes that the proposed rule and an established restriction "do not provide relief from federal criminal laws to authorize the facility operator or proprietor to use equipment or technology designed to detect, take control of, destroy, or otherwise interfere with an unmanned aircraft." On the restriction specifically: "The UAFR does not authorize the use of detection or mitigation technologies to interfere with unmanned aircraft; such activities remain subject to existing federal laws, including Title 18 and Title 49 U.S.C." And it adds that the restriction "alone does not create a physical or electromagnetic boundary."
Entities with independent statutory authority to run counter-drone systems keep it. The rule neither grants nor expands that authority, and homeowners have never had it.
I have written about how cheap and how effective radio interference against consumer wireless gear is, so let me be blunt about the direction that knowledge should travel. Jamming, spoofing, or shooting at an aircraft are federal crimes, and the fact that the aircraft is over your lawn does not change that. Buying a "drone defeat" device for a private residence is not a grey area you are navigating cleverly. It is the single fastest way to convert a nuisance into your own criminal exposure.
The proposal also creates a Special UAFR for locations with a credible identified threat, with longer five-year designations and stiffer penalties. Under proposed § 74.6 these would be available to federal security agencies, military departments, and designated fixed-site facilities backed by verified security assessments.
Same story, one tier up. Not a category a private owner enters.
Federal law governs the airspace. It does not settle everything that happens in it, and the layer that actually matters for a residence is the one I cannot summarise responsibly here: state statutes on aerial surveillance and voyeurism, state and local privacy law, harassment and stalking law, nuisance and trespass doctrine, and in some states specific drone statutes. Those vary enormously by jurisdiction, several have been litigated, and I did not research fifty states for this report.
What I can say with confidence is where the leverage is. It is in identifying the operator and using ordinary law against a person, rather than in seeking an airspace designation you cannot get or a countermeasure you cannot lawfully use. Document the pattern with times and dates. Report it to local law enforcement and, where there is a safety issue, to the FAA. If the aircraft is Remote ID compliant, its broadcast is a lead.
I help design the AI security systems for a veteran-owned (SDVOSB) luxury home-security company run by fellow veterans; I do not own it and earn nothing from this link. Full policy here. Detection and evidence-gathering are the parts of this problem that technology genuinely helps with, and you should know I have a hand in that work when you read me saying so.
Everything above about the proposal comes from the Federal Register text of the NPRM itself, retrieved through the Federal Register API and read in full. I did not open the docket at regulations.gov, so I have not read the comments filed by the July 2026 deadline, and I do not know what the final rule will look like or when it will appear.
I confirmed there is no final rule by querying the Federal Register for FAA rule-type documents on unmanned aircraft, and by checking the same for the separate Part 108 BVLOS rulemaking. Both remain proposals as of publication. I will note here that at least one industry site is currently publishing an article stating that Part 108 has been finalised. It has not been. The Federal Register record shows the most recent action on that docket is the reopened comment period of 28 January 2026.
I have not examined how many Section 2209 petitions the FAA has received informally over the past decade, nor how the existing FAA Order JO 7400.12 designations were granted before this rulemaking existed.
State and local law governing drones over private property is outside the scope of this report, and it is very likely the part that decides your actual case.
The answer to the question in the title is no, and it is a firmer no than it was three years ago, because in 2024 Congress deleted the discretionary category rather than expanding it. The federal government spent a decade building a process for refineries, railroads, amusement parks and prisons, and your house was never in the frame.
The deeper point is the one the FAA put in its own preamble. What that decade produced is a virtual no trespassing sign. Signs work on people who read signs. If your threat model is a neighbour with a new toy, a sign is genuinely useful. If your threat model is someone deliberately surveilling your property, you are not looking for an airspace designation. You are looking for identification, documentation, and a police report, and none of those require a rule that is still nine years late.
Scope note: this report describes a proposed federal rule as published in the Federal Register. It is not legal advice, not an aviation compliance opinion, and not a security assessment of any property. A proposed rule may be changed or withdrawn, and its status is stated as of the publication date above; any correction will be made in place and dated. Section 2209 eligibility is set by statute, not by the FAA, and the descriptions of proposed Part 74 provisions reflect the proposal rather than any final regulation. State statutes, local ordinances, and property and privacy law governing aerial observation over private residences were outside the scope of this report and are frequently the binding constraint in practice. Nothing here should be read as encouragement to detect, jam, disable, or otherwise interfere with an aircraft; those activities are governed by federal criminal law. Confirm your own situation with a qualified attorney.
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.