Codify — Article

California exempts emergency telecom bucket trucks and COWs from Advanced Clean Fleets rules

AB 911 carves an explicit exemption for certain medium- and heavy‑duty emergency telecommunications vehicles to ensure restoration of 911, EAS, and wireless service during outages.

The Brief

AB 911 adds Section 43109 to the Health and Safety Code to exclude specified emergency telecommunications vehicles from Article 3.4 of Title 13 (the Advanced Clean Fleets Regulations). The exemption covers bucket trucks and cell-on-wheels units owned or purchased by emergency telecommunications service providers when those vehicles are used to participate in the federal Emergency Alert System, provide access to 911, or restore wireless connectivity during service outages.

The bill matters because it creates a narrow carve‑out from California’s medium‑ and heavy‑duty zero‑emission vehicle transition for assets that states and private carriers rely on for emergency communications. That relieves certain operational constraints tied to current ZEV timelines, but it also raises practical questions about enforcement, leasing, and whether the exemption will slow adoption of cleaner technologies in a defined but critical subset of fleets.

At a Glance

What It Does

AB 911 creates a statutory exemption from Article 3.4 of Title 13 (Advanced Clean Fleets) for emergency telecommunications vehicles used for the Emergency Alert System, 911 access, or to provide wireless connectivity during outages. It specifies vehicle types (bucket trucks and cell on wheels units) and defines eligible providers.

Who It Affects

The exemption applies to public and private entities that must participate in the federal Emergency Alert System, provide 911 access, or offer emergency wireless connectivity (including support to FirstNet/Nationwide Public Safety Broadband Network). It affects fleet managers, utilities, wireless carriers, and vendors supplying bucket trucks and COW units.

Why It Matters

The bill prioritizes operational reliability over immediate ZEV conversion for a narrow class of vehicles that restore communications during disasters. Compliance officers, procurement teams, and environmental program managers should reassess fleet transition plans, procurement specifications, and the interplay between emergency preparedness and state emissions targets.

More articles like this one.

A weekly email with all the latest developments on this topic.

Unsubscribe anytime.

What This Bill Actually Does

AB 911 places a targeted exemption into California’s Health and Safety Code by adding Section 43109. The text says that Article 3.4 of Title 13 — the regulatory framework that drives medium‑ and heavy‑duty fleets toward zero‑emission vehicles — does not apply to certain emergency telecommunications vehicles.

The exemption is written broadly enough to preempt other laws that would otherwise impose the Article 3.4 requirements, using the standard "notwithstanding any other law" phrasing.

The bill restricts the exemption to vehicles owned or purchased by entities the statute defines as emergency telecommunications service providers and limits the allowed operational uses to participation in the federal Emergency Alert System, provision of 911 access, or restoring wireless connectivity during outages. That creates a two‑part gate: an entity must fall within the provider definition and the vehicle must be used for the enumerated emergency functions to qualify for the carve‑out.

The provider definition covers both public and private actors who are required to participate in EAS or to provide 911 access, and it explicitly includes entities that support FirstNet or the Nationwide Public Safety Broadband Network.AB 911 also defines the vehicle types to which the exemption applies. "Emergency telecommunications vehicle" is limited to bucket trucks (vehicles with an affixed aerial lift and operator platform) and cell‑on‑wheels units (mobile platforms equipped with antennas or network equipment for rapid deployment). The bill does not create certification, reporting, or inspection requirements tied to the exemption, nor does it prescribe alternative emissions controls or timelines for replacing exempted units.Taken together, the law preserves the ability of telecom operators and first‑responder support vendors to use conventional internal combustion equipment for certain emergency roles without triggering the Advanced Clean Fleets mandates.

At the same time, by using ownership/purchase and operational‑use gates rather than a technology or performance standard, the bill leaves implementation details — oversight of operational use, leased equipment, and potential second‑order effects on fleet transition plans — to regulators and procurement officers to resolve.

The Five Things You Need to Know

1

AB 911 adds Section 43109 to the Health and Safety Code and uses a "notwithstanding any other law" clause to make the exemption override Article 3.4 of Title 13 for covered vehicles.

2

The exemption applies only to vehicles that are owned or purchased by an eligible emergency telecommunications service provider — it does not explicitly cover leased, rental, or contractor‑operated units.

3

Covered operational uses are limited to participating in the federal Emergency Alert System, providing access to 911 emergency services, or restoring wireless connectivity during outages (including support to FirstNet/NPSBN).

4

The bill narrows the exempted equipment to two defined vehicle types: 'bucket truck' (an affixed aerial lift with an operator platform) and 'cell on wheels unit' (a mobile unit with mounted telecommunications infrastructure).

5

AB 911 does not establish alternative emission standards, reporting obligations, certifying authorities, or sunset dates for the exemption — it simply removes specific vehicles from Article 3.4 coverage.

Section-by-Section Breakdown

Every bill we cover gets an analysis of its key sections. Expand all ↓

Section 1

Findings and purpose

This opening section explains why the Legislature views uninterrupted telecommunications as critical to emergency response and recovery, and it frames the exemption as necessary to avoid hindering restoration of communications during severe disruptions. Practically, these findings provide legislative intent that can guide later interpretation — for example, courts or regulators will reference the emergency‑response rationale when resolving disputes about whether a use qualifies as an "emergency" under the statute.

Section 43109(a)

Express exemption from Article 3.4

Subsection (a) is the operative carve‑out: it says Article 3.4 (the Advanced Clean Fleets Regulation) "does not apply" to eligible emergency telecommunications vehicles. The phrasing is broad — it preempts other laws to the extent they would impose Article 3.4 requirements on these vehicles — which simplifies the legal effect but also removes that fleet subset from a primary state mechanism that drives medium‑ and heavy‑duty ZEV uptake.

Section 43109(b)(1)

Who counts as an emergency telecommunications service provider

Subsection (b)(1) defines eligible providers to include public or private entities mandated to participate in the federal Emergency Alert System or to provide 911 access, and entities that provide emergency wireless connectivity services (explicitly mentioning support for FirstNet and the Nationwide Public Safety Broadband Network). This definition pulls in a range of actors — municipal 911 centers, incumbent carriers, utilities with EAS obligations, and private contractors — and is consequential for procurement and fleet classification decisions.

1 more section
Section 43109(b)(2)

What vehicles are exempt: bucket trucks and cell‑on‑wheels units

Subsection (b)(2) gives specific vehicle definitions: a bucket truck is a vehicle configured with an affixed aerial lift and operator platform; a cell‑on‑wheels unit is a mobile unit equipped with telecommunications infrastructure for rapid deployment. Limiting the exemption to these configurations narrows the carve‑out to vehicles that perform hands‑on repair or temporary network deployment, rather than all medium‑ or heavy‑duty fleet vehicles owned by a provider.

At scale

This bill is one of many.

Codify tracks hundreds of bills on Environment across all five countries.

Explore Environment 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 state 911 centers and public safety communications units — they retain access to proven equipment that crews rely on for rapid restoration of emergency voice and data links without being constrained by current ZEV procurement rules.
  • Utilities and incumbent telecom carriers that operate bucket trucks for pole work and contingency restorations — the exemption reduces immediate procurement complexity and avoids potential operational limitations tied to emergent ZEV lift technologies.
  • Private contractors who supply and deploy cell‑on‑wheels units (COWs) — they avoid near‑term retrofit or replacement costs for units used in emergency deployments.
  • Rural and hard‑to‑serve communities — by preserving conventional fleet options, the bill aims to sustain timely restoration of connectivity where ZEV infrastructure or range might otherwise limit response speed.

Who Bears the Cost

  • California Air Resources Board (CARB) — the exemption narrows the population of vehicles subject to Article 3.4, complicating CARB’s emissions reduction accounting and potentially requiring adjustments to fleet‑level targets or enforcement priorities.
  • State and local environmental program managers — they may face higher administrative burdens to reconcile the exemption with broader ZEV rollout plans and to track exempted vehicles across jurisdictions and procurement agencies.
  • Manufacturers and suppliers of zero‑emission medium‑ and heavy‑duty aerial lift equipment — demand for ZEV versions of bucket trucks and COWs could slow, delaying scale economies and product development incentives.
  • Taxpayers and ratepayers if agencies or utilities need to maintain parallel fleets or pay premiums for rapid‑response non‑ZEV equipment, shifting costs from capital investments in ZEVs to operational resilience expenditures.

Key Issues

The Core Tension

The bill forces a choice between immediate operational resilience for emergency telecommunications (which favors keeping proven combustion‑engine bucket trucks and COWs available) and California’s longer‑term decarbonization goals for medium‑ and heavy‑duty vehicles (which favor broad, technology‑agnostic ZEV mandates); reconciling those priorities requires careful implementation design to avoid creating a permanent loophole.

AB 911 resolves one practical tension — ensuring emergency telecommunications are not constrained by ZEV mandates — but it leaves several implementation questions unaddressed. The statute ties the exemption to ownership/purchase status, creating ambiguity around leased units, short‑term rentals, and contractor‑operated equipment that many jurisdictions rely on for surge capacity.

Because the bill does not require reporting, certification, or an approval process to demonstrate an eligible vehicle’s use for EAS/911/connectivity restoration, regulators will face enforcement and audit challenges: how to verify that an exempted vehicle is genuinely used in qualifying emergency roles and not reassigned to routine service.

The bill also creates a potential strategic trade‑off: by protecting a narrow class of vehicles from Article 3.4, California may slow ZEV adoption in specialized equipment where technical constraints already make ZEV solutions more costly or less mature. That raises secondary questions about procurement incentives, whether grants or exemptions should be paired with targeted R&D funding for ZEV bucket lifts and COW power systems, and how to measure the exemption’s emissions impact over time.

Finally, the lack of a sunset date or periodic review means the exemption could persist even as ZEV technology for these vehicle types matures, unless regulators or future legislation revisit the policy.

Try it yourself.

Ask a question in plain English, or pick a topic below. Results in seconds.