AB 2043 requires the California Office of Emergency Services (OES) to stand up a Countering Unmanned Aircraft Systems Task Force by January 1, 2027. The task force must craft a statewide strategy to detect, identify, track, and mitigate threats posed by unmanned aircraft systems (UAS), with particular attention to mass gatherings, critical infrastructure, and other soft targets.
The bill sets membership categories spanning state agencies, local public safety, privacy advocates, and private-sector stakeholders (including sports leagues, universities, utilities, and amusement parks). It authorizes a suite of activities—risk assessments, integration of detection systems into existing emergency plans and public‑safety technologies, training, and multi‑jurisdictional exercises—while requiring coordination with federal law.
The act is an urgency measure and takes effect immediately.
At a Glance
What It Does
Requires OES to establish a Countering Unmanned Aircraft Systems Task Force by Jan. 1, 2027 to produce a statewide counter‑UAS strategy and promote operational capacity across jurisdictions. The task force can recommend or develop detection, tracking, identification, and mitigation measures and run exercises and training programs.
Who It Affects
State emergency management and public‑safety agencies, local police, sheriffs, fire departments, tribal governments, and private operators of mass events and critical infrastructure (e.g., sports leagues, utilities, amusement parks, universities). It also includes privacy advocates and the California National Guard in membership.
Why It Matters
This creates a permanent, state‑level coordinating body focused on UAS threats rather than ad hoc responses, pushing integration of UAS detection into incident command, CAD/GIS platforms, and responder training—areas many jurisdictions currently lack standardized guidance on.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
AB 2043 directs the Office of Emergency Services to form a task force charged with closing capability gaps that leave events and infrastructure exposed to malicious or unauthorized drones. The law sets a firm date for establishment, defines the term "unmanned aircraft system" by reference to federal law, and enumerates the kinds of actors—state, local, tribal, private, and civil‑society—that OES should try to include on the task force.
The statute is operational in focus: it asks the task force to produce a statewide strategy and then enables concrete steps to implement that strategy. Those steps include mapping high‑risk locations, updating emergency response plans to incorporate UAS detection, integrating detection feeds into public‑safety tools like GIS and CAD, and developing standard operating procedures for unauthorized UAS incidents.
The bill makes training and multi‑level exercises central to the approach, from tabletop scenarios to full‑scale drills that test multijurisdictional coordination.Crucially, the bill ties state actions to federal law: the task force must coordinate with federal agencies and operate "consistent with applicable laws," which signals awareness of FAA jurisdiction and restrictions around active interdiction methods. The statute does not itself authorize interdiction techniques; instead it focuses on detection, information integration, training, and planning.
The act also takes effect immediately as an urgency statute, which accelerates OES’s timetable for establishing and staffing the task force.
The Five Things You Need to Know
OES must establish the Countering Unmanned Aircraft Systems Task Force by January 1, 2027 and house it within the Office of Emergency Services.
The bill prescribes a wide membership slate—state legal counsel, the State Threat Assessment Center, CHP, CAL FIRE, California National Guard, local police and fire, privacy advocates, Major League Baseball, NFL, UC, CSU, investor‑owned utilities, LA28, FIFA, and amusement park associations.
The task force’s authority centers on planning and capacity building: risk assessments, integrating detection into emergency operation plans and public‑safety tech (GIS/CAD), SOPs for unauthorized UAS, and developing responder training and train‑the‑trainer programs.
The statute explicitly restricts activities to those "consistent with applicable laws" and requires coordination with federal agencies, which preserves FAA primacy over control or interdiction of aircraft.
The bill requires exercises at multiple scales—including tabletop, functional, and full‑scale multijurisdictional drills—and mandates after‑action reviews to capture lessons learned.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Establishment and deadline
This section instructs OES to create the Countering Unmanned Aircraft Systems Task Force and sets the operational deadline (on or before Jan. 1, 2027). Practically, that puts pressure on OES to allocate staff, define governance, and begin outreach to the long list of suggested members within a compressed timeframe.
Definitions
Defines key terms by reference: "Office" (OES), "Task force" (the new body), and "Unmanned aircraft system" (adopts the federal definition in 49 U.S.C. § 44801(12)). Using the federal definition ties the task force’s scope to nationally recognized terminology and helps align state planning with federal regulatory frameworks.
Membership composition
Directs OES to seek a task force membership combining state agencies (legal branch, State Threat Assessment Center, CHP, CAL FIRE, National Guard), local public‑safety and emergency management officials, privacy advocates, and specified private‑sector organizations (sports leagues, universities, utilities, LA28, FIFA, amusement park associations). That list signals priority stakeholders and practical partners for situational awareness, event security, and infrastructure protection.
Purpose and primary objective
Frames the task force’s mission: improve statewide capabilities to detect, identify, track, and monitor UAS threats and support local and tribal governments. The primary objective narrows the mission to ensuring public‑safety entities have resources, training, and operational capacity to deter and counter UAS attacks—emphasizing capacity building over new enforcement powers.
Goals and authorized activities
Lists goals (protect critical infrastructure and mass gatherings, deploy detection systems consistent with law) and a long menu of permitted activities. Those include updating response plans, risk assessments, SOPs, federal coordination, integrating detection into GIS/CAD, responder training and train‑the‑trainer programs, scenario‑based and full‑scale exercises, and after‑action reviews. The granular activity list gives OES a blueprint for measurable deliverables but leaves implementation choices to the task force.
Urgency clause
Declares the bill an urgency statute that takes immediate effect to address evolving UAS threats. Legally, that allows the task force to begin work at once; practically, it shortens the timeline for OES to stand up governance and begin outreach and exercises.
This bill is one of many.
Codify tracks hundreds of bills on Government across all five countries.
Explore Government 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
- Local and tribal public‑safety agencies — Receive standardized plans, training curricula, and integration guidance that reduce their burden when responding to UAS incidents and improve situational awareness during events and at critical sites.
- Operators of mass gatherings (sports leagues, event organizers, amusement parks) — Gain access to coordinated detection strategies, exercises, and recommended SOPs that help them meet security obligations and reduce disruption risk at large events.
- Owners/operators of critical infrastructure (investor‑owned utilities, universities) — Benefit from risk assessments, detection integration guidance, and improved state‑local coordination to protect assets and restore service quickly after incidents.
- First responder training systems and emergency managers — Get train‑the‑trainer programs and scenario exercises that professionalize UAS incident response and create repeatable local capacity.
- State emergency management (OES) and the State Threat Assessment Center — Gain a formal platform to centralize intelligence, harmonize standards, and leverage public‑private partnerships for statewide situational awareness.
Who Bears the Cost
- Office of Emergency Services — Will absorb startup costs: staffing, convening the task force, coordinating exercises, and building integration pilots; the bill contains no dedicated appropriation.
- Local law enforcement and fire agencies — Must commit personnel time to risk assessments, training, and exercises; some may need to invest in compatible technology or staff to integrate detection feeds into CAD/GIS.
- Private partners (sports leagues, utilities, amusement parks, universities) — Face expectations to participate, share operational information, and potentially co‑fund detection or integration efforts for venues they operate.
- Privacy advocates and civil‑liberties groups — May bear monitoring and advocacy costs to review and challenge surveillance use cases and negotiate safeguards around detection technology deployment.
- Taxpayers/public budgets — If the state or localities fund detection systems or exercises, there will be budgetary pressure for procurement, maintenance, and continuous training.
Key Issues
The Core Tension
The bill forces a classic trade‑off: improve protection of public events and infrastructure by accelerating detection, coordination, and training, while avoiding federal preemption, unlawful interdiction methods, and intrusive surveillance—balancing rapid operational readiness against legal limits, privacy protections, and budgetary realities.
The statute is narrow in authority but broad in tasking, and that combination generates a number of implementation questions. First, the bill repeatedly ties actions to "applicable laws" and federal coordination, but it does not clarify which detection or mitigation technologies the state may deploy without violating FAA jurisdiction or federal statutes that restrict radio interference and aircraft control.
Agencies will need legal analysis before pilot programs, and some mitigation options will likely remain off the table for state and local actors.
Second, the bill lists several private‑sector and cultural institutions as members—for example Major League Baseball and investor‑owned utilities—without specifying funding responsibilities or data‑sharing protocols. That raises questions about equity (which venues get prioritized), commercial confidentiality (sensitive security details), and cybersecurity (integrating detection feeds into CAD/GIS or GIS platforms creates new attack surfaces).
The law also contains no appropriation or dedicated funding stream, so scale and sustainability will depend on OES prioritization and partner contributions.
Finally, privacy and civil‑liberties risks are material. Detection technologies can reveal movement and patterns of people and vehicles as well as drone activity; the statute includes privacy advocates on the task force but does not set privacy standards, retention limits, or oversight mechanisms.
The combination of urgency, broad membership, and rapid adoption of new sensors could produce operational momentum before robust legal safeguards are in place.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.