AB 272 directs the California Air Resources Board (state board) to adopt and implement a Heavy‑Duty Vehicle Inspection and Maintenance (I/M) Program for nongasoline on‑road vehicles with a gross vehicle weight rating over 14,000 pounds, no later than two years after the completion of the pilot required by Section 44156 and to the extent allowed by federal law. The bill requires the state board to set test procedures (including use of onboard diagnostics and optional greenhouse gas measures), create a Heavy‑Duty Vehicle Inspection and Maintenance Compliance Certificate, build an IT database to track results and feed DMV registration, and develop enforcement, licensing, and outreach mechanisms.
It also lists explicit exemptions (zero‑emission vehicles, emergency and tactical vehicles in limited circumstances, and newly certified low‑NOx vehicles for four years), and phases out the existing Periodic Smoke Inspection Program once fully implemented.
The program matters because it creates a single statewide compliance structure for heavy‑duty non‑gasoline fleets — including out‑of‑state vehicles that operate in California — and couples testing with registration. That linkage raises compliance, administrative, and commercial implications for fleets, inspection businesses, and state agencies: new testing standards, a mandated database feeding DMV, citation and administrative enforcement procedures, and explicit cost‑containment language that requires at least one affordable testing option for owners.
At a Glance
What It Does
The bill requires CARB to adopt a heavy‑duty I/M regulation covering nongasoline on‑road vehicles >14,000 lbs, define test procedures by model year and emissions technology (including OBD and possible GHG measures), establish enforcement and licensing standards, and create a compliance certificate tied to DMV registration.
Who It Affects
Commercial truck and fleet operators (including single‑vehicle fleets), out‑of‑state carriers that enter California, inspection and repair businesses, CARB/DMV/CHP operations, and communities downwind of major freight corridors and ports.
Why It Matters
AB 272 centralizes heavy‑duty emissions compliance and links it to registration, potentially accelerating NOx and PM reductions while imposing new operational and IT obligations on registrants and state agencies. The law also creates specific correction timelines, citation procedures, and an explicit requirement that at least one testing path remain financially accessible.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
AB 272 tasks the state board with implementing a comprehensive inspection and maintenance program for non‑gasoline heavy‑duty on‑road vehicles over 14,000 pounds. The board must tailor test procedures to different model years and technologies — for example, using onboard diagnostics (OBD) data where available and crafting physical or functional tests for older or different systems — and may include methods that measure greenhouse gas control effectiveness.
Critically, the bill requires the board to ensure at least one testing procedure does not impose aggregate charges on owners that exceed the maximum allowable compliance fee (aside from necessary repair costs) and that this option be reasonably accessible.
The program links emissions compliance to vehicle registration: vehicles must pass the required tests to be registered or operated in California, and the state board must create and issue a Heavy‑Duty Vehicle Inspection and Maintenance Compliance Certificate containing standard owner and vehicle information. To operationalize this, the bill requires development of an IT database that collects and evaluates test data, produces lists of compliant VINs, and transmits them to DMV for registration notices.
The state board may also license inspectors and set standards for testing equipment, including protocols and software used to submit data.Enforcement is administrative and operational. The state board may conduct visual and functional inspections, require emissions testing, issue citations, and set correction timetables (not less than 45 days generally, 75 for vehicles used exclusively in agricultural operations).
Refusal to submit to a required test may be treated as an admission. For willful tampering of emissions controls, the bill bars operation of the vehicle.
The bill also preserves streamlined paths for fleets with good compliance histories, including electronic transmission of emissions data in lieu of annual physical testing, though such streamlining does not create an exemption from the testing requirement itself.Implementation requires coordination with multiple agencies: the Department of Transportation for permits to deploy equipment on state highways, CHP for safety and weight enforcement cooperation, the Department of Food and Agriculture and Caltrans for data and site facilitation, and DMV for registration integration. The state board must also develop validation methods to assess program effectiveness, investigate fraud, and conduct research.
Finally, once the program is fully implemented, AB 272 sunsets the existing Periodic Smoke Inspection Program and requires biennial reporting on enforcement, downtime, emissions reduced, and cost‑effectiveness.
The Five Things You Need to Know
AB 272 applies to nongasoline on‑road heavy‑duty vehicles with a gross vehicle weight rating greater than 14,000 pounds, including vehicles registered out‑of‑state that operate in California.
The state board must ensure at least one test procedure, when combined with the compliance fee, does not impose aggregate charges on owners that exceed the statutory maximum compliance fee — except for necessary repair costs — and must make that low‑cost option reasonably accessible.
The state board can issue citations for violations, require tests (with refusal to test treated as admission), and impose correction windows of at least 45 days for general vehicles and at least 75 days for vehicles used exclusively in agricultural operations.
CARB must build an information technology database to collect vehicle test data, determine compliance, and transmit lists of compliant VINs to DMV so that registration notices reflect program status.
Zero‑emission vehicles are exempt, and new vehicles certified to meet the most stringent optional reduced NOx standard are exempt for four years after inspections under the program begin.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Test procedures, cost‑containment, and applicability
This provision requires the state board to develop test procedures differentiated by model year and emissions technology, explicitly allowing OBD‑based protocols and tests for GHGs. It also contains a cost‑containment mandate: at least one testing path must not lead to charges in excess of the statutory maximum compliance fee (excluding repair costs), and must be reasonably accessible. Practically, that forces the board to pick or design a low‑cost testing option (for example, a remote OBD check or simplified functional test) and to justify other testing costs relative to the compliance fee cap.
Streamlined compliance, validation, and enforcement toolkit
The bill authorizes a streamlined path for fleets with good compliance histories — notably electronic transmission of emissions data instead of annual physical inspections — but does not exempt them from program requirements. It also directs the board to develop program validation methods (for effectiveness and fraud detection) and to craft enforcement tools that include visual and functional inspections and additional emissions testing. Those requirements create both flexibility for efficient fleet operators and explicit mechanisms to audit and enforce compliance.
IT database and compliance certificate tied to DMV
CARB must design an IT system to ingest and assess test data, generate lists of compliant VINs, and transmit those lists to DMV for registration processing. The creation of a Heavy‑Duty Vehicle Inspection and Maintenance Compliance Certificate formalizes proof of compliance and standardizes the data fields (issue/expiration dates, owner address, VIN, year/make/model), which will be used operationally by DMV and by vehicle owners to demonstrate compliance during stops or audits.
Licensing, interagency coordination, permits, and inspection locations
The state board may set licensure or qualification standards for inspectors and approve testing equipment (protocols, hardware, software). It also can request permits to deploy equipment on the state highway system, and must work with Caltrans and CHP when selecting inspection sites — including private in‑state fleet facilities. These cross‑agency provisions make implementation an engineering and logistics exercise as much as a regulatory one: deployment will require site agreements, permission processes, and equipment standards that affect inspection businesses and state operations.
Citation, correction windows, hearings, and judicial enforcement
CARB can issue citations, require tests, and treat refusals to test as admissions. The board sets correction periods (minimums: 45 days general, 75 for agricultural vehicles) and may consider temporary DMV permits when deciding citations. Vehicle owners are entitled to administrative hearings under the referenced California Code of Regulations procedures; final administrative orders can be converted into judgments in Sacramento Superior Court if not challenged. The mechanism gives CARB administrative bite while preserving procedural hearing rights and a path to court enforcement of penalties.
Out‑of‑state compliance, program sunset, and reporting
The board must provide mechanisms for out‑of‑state owners to establish compliance before entering California, reducing surprises at the border. Upon full implementation, the bill sunsets the Periodic Smoke Inspection Program. It also requires two biennial reports beginning within four years after full implementation (the first report is to appear on the board’s website and cover enforcement, downtime, emissions reductions, and cost‑effectiveness), a provision that will shape how the board measures program performance and public accountability.
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
- Communities near freight corridors and ports — will likely see faster, more consistent reductions in NOx and particulate emissions because the program targets heavy‑duty, non‑gasoline sources that are significant local emitters.
- Large and compliant fleet operators — gain a predictable regulatory pathway, including the option for streamlined electronic compliance that can lower inspection downtime and administrative friction.
- Manufacturers of zero‑emission and certified low‑NOx vehicles — receive an implicit market advantage through explicit exemptions that reduce near‑term compliance costs for their customers.
- State agencies and planners — obtain standardized, VIN‑linked emissions data that can improve air quality modeling, enforcement targeting, and policy evaluation.
Who Bears the Cost
- Commercial truck and fleet owners (especially small and single‑vehicle operators) — face testing fees, potential repair bills, and administrative steps to obtain compliance certificates; the bill limits aggregate testing charges but not repair costs.
- Inspection businesses and equipment vendors — must invest to meet new licensure and equipment approval standards and to integrate with the state IT system, creating upfront compliance costs even as they gain business opportunities.
- CARB, DMV, CHP, and Caltrans — bear implementation burdens: building and securing the IT database, coordinating permits and inspection sites, and managing outreach and enforcement, which may require additional staffing and funding.
- Out‑of‑state carriers and interstate shippers — must establish pre‑entry compliance or obtain certificates, adding logistics and administrative steps to interstate operations.
Key Issues
The Core Tension
The bill balances two legitimate aims — achieving measurable emissions reductions from heavy‑duty fleets and avoiding excessive compliance burdens — but those goals pull in opposite directions: stricter, technologically specific testing yields better air quality data and faster emissions cuts, while broader exemptions, lengthy correction windows, or low‑cost testing floors protect small operators and interstate commerce; CARB will face tradeoffs between regulatory stringency and economic and constitutional constraints when it designs the program.
AB 272 packs significant operational detail into broad delegations to the state board, which creates a number of implementation challenges. First, the statute’s mandate that at least one testing procedure not result in aggregate charges above the maximum compliance fee begs practical questions about who pays for repairs and how the board will design truly accessible low‑cost options across urban and rural contexts.
Second, the bill conditions implementation “to the extent authorized by federal law,” which raises preemption and interstate commerce questions for out‑of‑state registration and enforcement practices; the board will need to align any testing, detention, or pre‑entry certificate processes with federal constraints and interstate trucking operations.
Data management and privacy are another open issue. The IT database will collect VIN‑linked emissions and owner data and push compliance lists to DMV — a useful enforcement tool but also a cybersecurity and privacy responsibility that requires funding, access rules, and retention policies.
Enforcement provisions that treat refusal to test as an admission and allow rapid administrative citations create procedural risks: owners may challenge the scientific validity of tests, the fairness of correction windows, or the scope of temporary permits, producing litigation over due process and evidentiary standards. Finally, the bill contains an apparent internal inconsistency in the reporting timing language (naming multiple dates and a four‑year window), which the board will need to resolve before producing the required biennial reports.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.