AB 525 amends Vehicle Code section 34501.12 to exclude agricultural vehicles as defined in section 34500.6 from the Basic Inspection of Terminals (BIT) program. The statutory text otherwise keeps the BIT framework intact: terminal identification and records obligations, sample‑based vehicle inspections, a performance‑based selection system, reinspection timelines, certification requirements for contracted carriers, public reporting, and a sunset date.
For farm operators and businesses that move implements of husbandry or other statutorily defined agricultural vehicles, the change removes BIT inspection exposure. For regulators and carriers with mixed fleets, it narrows the universe of inspectable vehicles and raises practical questions about classification, recordkeeping, and how the department reallocates inspection resources during the program’s remaining statutory term.
At a Glance
What It Does
The bill removes agricultural vehicles (per Vehicle Code §34500.6) from the BIT program’s inspection scope while leaving the program’s operational rules — terminal identification, sampling, selection priorities, and reporting — untouched.
Who It Affects
Primary audiences are farm vehicle owners and operators, motor carriers that mix agricultural and non‑agricultural equipment, terminal operators, and the department responsible for BIT inspections and data systems.
Why It Matters
The change reduces regulatory friction for the agricultural sector but concentrates BIT enforcement on non‑agricultural carriers and terminals, creating compliance, classification, and enforcement trade‑offs for regulators and carriers operating mixed fleets.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill narrows who the department may inspect under the BIT program by removing from scope vehicles that meet the statutory definition of an agricultural vehicle. That narrowing does not repeal the broader inspection architecture: motor carriers must still identify terminals where inspectable vehicles and records are kept, and the department retains authority to select terminals for inspection using the program’s performance‑based rules.
Inspections continue to operate on a sampling model tied to fleet size, and lessors remain obligated to make vehicles available when the department inspects a lessee’s terminal. The department’s selection machinery — which is to incorporate FMCSA‑style quantitative methods and other safety data — remains central: the agency must build a database that provides near real‑time performance information and prioritize never‑inspected terminals, those identified by the selection algorithm, and terminals handling certain hazardous materials.Procedural features survive the amendment: an unsatisfactory terminal rating triggers a reinspection within 120 days and can suspend a carrier’s permits or authority pending administrative processes; carriers that use subcontractors must obtain a written certification of the subcontractor’s compliance and retain it for the contract period plus two years; and the department must publish inspection completion data for public review.
Finally, the entire section remains subject to an existing sunset on January 1, 2031, meaning the program as amended is temporary unless the Legislature acts to extend it.
The Five Things You Need to Know
The department’s terminal inspection sample is explicit and size‑based: terminals with 1–2 units have all vehicles inspected; 3–8 units → 3 inspected; 9–15 → 4; 16–25 → 6; 26–50 → 9; 51–90 → 14; 91+ → 20.
The department must build and maintain a performance database that feeds a selection priority system using methodologies consistent with the FMCSA and including citations, accidents, and inspection data to produce near real‑time selection triggers.
An inspected terminal receiving an unsatisfactory rating must get a department reinspection within 120 days; suspensions of Motor Carrier of Property permits or PUC authority pause reinspections until the relevant licensing agency requests reinstatement inspection.
Motor carriers must obtain a written compliance certification from any contracted motor carrier before engaging services, keep that certification for the life of the contract plus two years, and present it immediately upon department request.
Certain categories were already carved out of BIT: historical vehicles, vehicles with special identification plates, implements of husbandry and farm vehicles, and federal government‑owned or -operated vehicles are not subject to the section’s inspection rules.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Scope of BIT and the agricultural exclusion
This subdivision defines which classes of vehicles the department may inspect under BIT. The amendment explicitly removes vehicles that meet the statutory definition of an agricultural vehicle. Practically, that narrows the pool of power units and trailers the department treats as subject to terminal inspection; for carriers, the change shifts which pieces of equipment they must identify and make available when the department asks for terminal access.
Terminal identification and inspection sample framework
Motor carriers must still identify every in‑state terminal where inspectable vehicles may be examined and where records are kept. The subdivision codifies the representative sample the department will pull at each terminal, with separate counts for power units and trailers tied to fleet size; carriers should expect the department to apply that sampling table to each terminal fleet independently, not to a company’s statewide total.
Selection priority, data, and inspection sequencing
This subsection instructs the department to adopt a performance‑based selection system that mirrors FMCSA quantitative techniques and to compile a real‑time database of inspection and safety performance data. It also establishes the department’s prioritization order — uninspected terminals first, algorithm‑flagged terminals next, and terminals with specific hazardous material operations — and clarifies when the department may refrain from reinspecting terminals that already earned a satisfactory rating.
Contractor certification and record retention
When a motor carrier hires another carrier, the hiring carrier must obtain a written certification (in the department’s form) that the contracted carrier is compliant with the applicable title and regulations. That certification must be kept for the duration of the contract plus two years and produced on demand; combining this certification with other statutorily required documents is permitted, but the duty to collect, store, and produce these records creates an audit trail requirement for contracting carriers.
Unfavorable ratings, reinspections, review windows
An unsatisfactory terminal rating triggers a department reinspection within a 120‑day window and creates a narrow five‑business‑day window for the carrier to request administrative review, with the department to complete that review within ten business days. If a carrier’s permits or operating authority are suspended as a result of the rating, reinstatement reinspections are deferred until the licensing agency asks the department to act, creating a procedural coordination point between enforcement and licensing agencies.
Transparency, program name, and sunset
The statute requires public disclosure of inspection completion data and retains the BIT program name. Importantly, the section keeps the existing sunset date of January 1, 2031, meaning the program’s amended scope is time‑limited unless the Legislature repeals or extends that sunset before it occurs.
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
- Small and family‑owned farms that operate implements of husbandry or other vehicles meeting the agricultural definition — they reduce exposure to terminal inspections, potential downtime, and the administrative burden of producing records tied to BIT contacts.
- Carriers strictly operating agricultural vehicles — these operators avoid the sampling, reinspection cycle, and rating process under BIT so long as their fleet fits the statutory agricultural definition.
- Equipment owners who lease agricultural machinery to farmers — fewer involuntary inspections when lessees operate in agricultural categories can cut interruption risk and reduce coordination costs around terminal access.
Who Bears the Cost
- Non‑agricultural motor carriers and terminals — by narrowing the inspectable universe, the department may concentrate inspections on remaining carriers, increasing scrutiny and the likelihood of being selected by the performance algorithm.
- The department (and its inspectors) — implementing the amendment requires updating the BIT selection database, training staff to screen for agricultural classification, and reallocating inspection schedules, all without additional appropriation in the text.
- Mixed‑fleet carriers — companies operating both agricultural and non‑agricultural equipment face added compliance complexity: they must distinguish eligible vehicles, maintain segregated records, and justify classification decisions under department review.
Key Issues
The Core Tension
The bill pits reducing regulatory burden for agricultural operators and preserving farm‑sector flexibility against the public‑safety regulator’s need for comprehensive, data‑driven oversight: exclude too much and you blind enforcement to on‑road risks; exclude too little and you keep imposing inspection costs that the agricultural sector seeks to avoid.
The amendment’s practical effects hinge on how the department interprets "agricultural vehicle" under §34500.6 and how it applies that definition at terminals where mixed uses occur. If the definition is narrow, many vehicles commonly used on farms could still fall inside BIT; if broad, carriers may reclassify equipment or alter operations to avoid inspection.
Implementation requires operational rules the statute doesn’t supply — inspection checklists, evidence thresholds for classification, and guidance for handling dual‑use vehicles.
Removing inspection coverage creates a data gap: BIT’s database and public reporting will no longer capture safety performance for excluded agricultural vehicles, complicating risk‑based selection models and public oversight. The sunset date adds another layer of uncertainty: agencies must decide how much to invest in system changes for a program that may lapse in 2031 unless the Legislature extends it.
Finally, the law leaves open the potential for strategic behavior — misclassification, contracting structures, or lease arrangements— that could reduce BIT’s reach without changing safety outcomes, forcing the department to rely on audits and enforcement discretion to preserve program integrity.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.