SB 260 makes it an infraction to operate a drone, unmanned aerial vehicle, or remotely piloted aircraft too close to specified “critical infrastructure facilities,” subject to a $1,000 fine. The bill defines which sites qualify as critical infrastructure and ties protection to either physical barriers or plainly visible signage; it also expands the list during a declared statewide emergency.
The measure creates a bright-line 400-foot proximity rule and a separate, subjective prohibition against flying close enough to interfere with facility operations, then lists several exemptions (federal, state, FAA‑authorized commercial operations, contractors, and anyone with prior written consent). For operators and infrastructure owners, the text raises immediate questions about altitude measurement, enforcement evidence, and the interaction with federal aviation authority over airspace and commercial authorizations.
At a Glance
What It Does
The bill makes it an infraction to operate a drone within 400 feet of— or below 400 feet above—designated critical infrastructure facilities, or at any distance that interferes with facility operations, punishable by a $1,000 fine. It spells out which locations qualify as critical infrastructure and when additional sites become covered during a statewide emergency.
Who It Affects
Recreational and non‑FAA‑authorized commercial drone pilots, operators working near refineries, power plants, water and wastewater facilities, ports, certain bridges and dams, and public safety and infrastructure owners who may need to post signage or fencing to trigger protection. Law enforcement and local regulators will carry enforcement responsibility.
Why It Matters
The bill attempts to give infrastructure owners clearer legal cover against intrusive drone operations and to create a simple proximity standard, but it also creates potential conflicts with federal aviation regulation, ambiguous operational standards for enforcement, and new compliance burdens for drone operators and infrastructure owners.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
SB 260 sets two related limits on operating unmanned aircraft around sensitive sites. First, it creates a proximity limit tied to the number 400: operators may not allow their drone to come within 400 feet of designated critical infrastructure facilities, and the text also bars operating at altitudes described as “below 400 feet above” those locations.
Second, the bill adopts a back‑stop rule that prohibits operations at any distance that are “close enough to interfere” with the facility’s operations. The draft treats those as infractions punishable by a $1,000 fine.
The bill’s definition of “critical infrastructure facility” is list‑based but conditional. A set of industrial and utility sites—refineries, pipelines, power plants and substations, water and wastewater facilities, compressor stations, LNG terminals, ports, and FAA‑designated national security‑sensitive facilities—qualify only when the location is completely enclosed by a physical barrier meant to exclude intruders or when the property is clearly posted with a sign forbidding entry.
Separately, during a declared statewide emergency the bill adds alternate government facilities, State Operations Centers, and hospitals treating a majority of victims of the emergency. It also explicitly covers city halls, certain bridges on state or federal highways, and DWR‑classified high or extremely high hazard dams.SB 260 builds a relatively long exemption list.
The prohibition does not apply to federal or state entities acting in regulatory or public‑safety roles, to contractors acting on their behalf, or to commercial operators who hold the required FAA authorizations and who comply with FAA rules and exemptions. It further exempts persons under contract with a facility owner or acting with the owner’s prior written consent, and the owner or occupant themselves.
Practically, that means an FAA‑authorized delivery service could operate near a listed facility if it holds the appropriate federal approvals, while an unpermitted recreational pilot could be cited even if they claim they were passing through the airspace.Operationally, the bill shifts several burdens. For private infrastructure owners, the requirement that protection attaches only to fenced or clearly signed sites creates an incentive to post signs or install barriers; absent those measures, the location may not qualify for the statute’s bright‑line buffer.
For operators, the law creates a new compliance question about how to measure the 400‑foot limit in mixed urban terrain and how to document written consent. For regulators and courts, the “close enough to interfere” standard and the odd phrasing around altitude create enforcement discretion and potential litigation over statutory meaning and evidence needed for a citation.
The Five Things You Need to Know
SB 260 makes violating the proximity rules an infraction punishable by a $1,000 fine.
The bill prohibits allowing an unmanned aircraft to come within 400 feet of, or to operate at an altitude described as “below 400 feet above,” a qualifying critical infrastructure facility.
A location only counts as a protected critical infrastructure facility under many clauses if it is fully enclosed by a fence or similar barrier intended to exclude intruders, or if it is clearly posted with a sign forbidding entry.
During a declared statewide emergency the statute temporarily expands covered sites to include alternate emergency response facilities, State Operations Centers, and health care facilities treating a majority of emergency victims.
Exemptions include the federal or state government and their contractors, FAA‑authorized commercial operations that comply with FAA rules and authorizations, persons with prior written consent from the facility owner, and the facility owner or occupant.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
List of industrial and utility sites and the fencing/signage trigger
This subsection names the core categories that the bill treats as critical infrastructure—refineries, pipelines and drilling sites, power generating facilities and substations, water and wastewater facilities, natural gas compressor stations, LNG terminals, ports, gas processing plants, and FAA‑designated national security‑sensitive facilities. Critically, many of these entries only qualify when the property is either completely enclosed by a fence or other physical barrier designed to exclude intruders, or when the property is clearly posted with a sign forbidding entry. That conditional approach creates a practical compliance lever: posting signage or erecting barriers activates statutory protection.
Expanded coverage during declared statewide emergencies
When a statewide emergency is declared, the bill temporarily adds certain government and health care facilities to the protected list: alternate government facilities used in emergency response, State Operations Centers, and critical access hospitals or other health care facilities where most admitted patients are victims of the declared emergency. This clause is event‑driven and narrows protection to facilities directly implicated in the declared crisis rather than creating a permanent expansion.
Other civic infrastructure and dam definition reference
The statute also covers city halls or county administrative buildings where boards of supervisors meet, bridges on the state/federal highway system, and dams classified by the Department of Water Resources as high or extremely high hazard. The bill references the Water Code definition of “dam,” tying the term to existing state hydrology classifications rather than creating a new statutory definition.
Prohibition, dual standards, and penalty
Subdivision (b) creates two distinct operative prohibitions: a numeric proximity rule (the 400‑foot threshold) and a performance standard forbidding flight conducted at any distance sufficient to interfere with facility operations. Violation is an infraction with a $1,000 fine. The coexistence of a bright‑line distance and an ambiguous interference standard means enforcement can proceed either on the clear metric or on the more subjective operational impact.
Exemptions and their limits
Subdivision (c) lists multiple exemptions: federal, state, and governmental entities acting in regulatory or public‑safety roles; contractors acting for those entities; commercial operators who hold and comply with FAA rules and authorizations; personnel acting under contract with or on behalf of the vital facility owner/operator; anyone with prior written consent from the owner/operator; and the owner or occupant themselves. The commercial‑operator carve‑out explicitly ties compliance to FAA authorizations, undercutting state reach where federal approvals exist, while leaving ambiguity for operations that claim FAA compliance but lack documentation at the point of enforcement.
This bill is one of many.
Codify tracks hundreds of bills on Transportation across all five countries.
Explore Transportation in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Owners and operators of designated critical infrastructure facilities — the fencing/signage trigger and proximity rule give them a statutory basis to restrict drone operations near their property and to seek enforcement against intrusive flights.
- Emergency response coordinators and State Operations Centers — temporary expansion of covered sites during declared statewide emergencies reduces drone interference risk at surge facilities and hospitals treating emergency victims.
- Local law enforcement and security teams at protected sites — the statute establishes a legal tool (an infraction) they can use to cite operators detected inside the buffer or otherwise interfering with operations.
Who Bears the Cost
- Recreational drone pilots and hobbyists — they face a new liability exposure and a $1,000 fine risk if they enter marked or fenced areas or inadvertently fly within the 400‑foot threshold.
- Small and emerging commercial drone operators without full FAA waivers or documented authorizations — they may be excluded from operations near many infrastructure sites unless they secure both federal approvals and written consent, increasing transactional friction.
- Infrastructure owners who want protection but lack barriers or signage — to gain statutory cover they will likely need to invest in posting signs or installing fencing, creating costs and operational choices (e.g., posting vs. relying on enforcement).
- Local agencies and courts — they may see a rise in enforcement actions and will need protocols to measure distances, verify consents and FAA authorizations, and adjudicate subjective “interference” claims.
Key Issues
The Core Tension
The bill balances two legitimate goals—protecting infrastructure and preserving safe, authorized use of airspace—but the tools it uses create a trade‑off: a bright‑line buffer and owner‑triggered protection give operators of critical sites clear recourse, yet the statute’s ambiguous phrasing, subjective interference standard, and overlap with federally regulated airspace risk inconsistent enforcement, litigation, and unintended constraints on lawful drone activity.
The bill rests on two provisions that create real implementation and legal friction. First, the 400‑foot metric is simple in theory but awkward in practice: the statute’s wording referencing both “within 400 feet of” and “below 400 feet above” the facility is unusually drafted and invites disputes over horizontal versus vertical measurement, datum for altitude, and how to treat multi‑level infrastructure.
Second, the interference standard—prohibiting flight at any distance “close enough to interfere with the operations of the property”—is intentionally flexible but will shift enforcement into fact‑specific inquiries about whether a drone actually disrupted operations, creating a heavy evidentiary burden for prosecutors and uncertainty for pilots.
The interplay with federal aviation law is another major loose end. The bill exempts FAA‑authorized commercial operations, but it does not resolve cases where federal authorization exists for an operation that state actors believe threatens infrastructure.
Federal preemption of navigable airspace remains a contested legal area; courts have sometimes limited state power to regulate aircraft operations. Finally, the statute’s reliance on fencing or “clearly posted” signage to trigger protection places costs and strategic choices on facility owners and may produce uneven coverage across sites—some critical facilities will be protected by statute only if they take affirmative physical or posting steps.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.