CARB Fleet Emissions Compliance: DEF Systems, Fault Codes, and Reporting Obligations

A single unresolved DEF system fault on a California-registered Class 8 tractor can trigger a $10,000-per-day civil penalty under CARB enforcement — not per vehicle, per violation. Fleet managers who treat SCR fault codes as routine maintenance tickets instead of compliance events are sitting on exposure they haven't priced into their operating budgets.

California's Advanced Clean Fleets (ACF) regulation and New York's analogous NYSDEC fleet emissions requirements have converged on a shared enforcement philosophy: real-time fault monitoring, mandatory reporting windows, and progressive derate strategies that pull vehicles from service before your dispatcher knows there's a problem. Understanding the exact technical thresholds that trigger each consequence isn't optional anymore.

What CARB Actually Enforces — and Where Fleets Get Caught

CARB's In-Use Compliance Program targets heavy-duty diesel vehicles through two primary pathways: roadside inspection cross-referencing with DOORS (Diesel Off-Road Online Reporting System) for applicable equipment, and fleet-level audits under the Truck and Bus Regulation (CCR Title 13, §2025). The ACF regulation layers on top of this with MY2024+ model year compliance thresholds.

The enforcement trigger most fleets miss isn't the obvious stuff — visible smoke, missing DPF. It's diagnostic trouble code (DTC) accumulation without documented corrective action. CARB inspectors pull J1939 datalink records. They look at SPN 3216 (Aftertreatment 1 SCR Catalyst Outlet NOx) and SPN 3226 (Aftertreatment 1 SCR Conversion Efficiency) alongside the fault history timestamps. If SPN/FMI 3364/31 (Aftertreatment SCR Operator Inducement Active) appears in the ECM history without a corresponding repair order and return-to-spec confirmation, you have a documentation problem even if the fault is currently inactive.

New York takes a slightly different approach under its Clean Trucks and Buses Initiative, administered through NYSDEC's Division of Air Resources. NY-registered fleets operating vehicles over 8,500 lbs GVWR must comply with CARB's own OBD II and HD OBD standards by statutory adoption — meaning California's fault code thresholds and reporting cadence apply directly in New York without modification.

DEF System Requirements: The Engineering Reality Behind the Regulation

Diesel Exhaust Fluid quality and delivery tolerances are where most mechanical failures begin, and where most compliance failures end up.

CARB-compliant SCR systems require DEF concentration between 31.8% and 33.2% urea by weight (ISO 22241 specification). A concentration drift below 30% — common in tanks that get topped with water or contaminated product — drops NOx conversion efficiency below acceptable thresholds and will set SPN 4334 (Aftertreatment 1 Diesel Exhaust Fluid Quality). On Detroit DD15s and Cummins X15s, this fault initiates a 25% torque derate at first detection and a 40% derate within 10 operating hours if uncorrected.

The dosing system pressure spec matters as much as concentration. Bosch DENOXTRONIC 2.2 units (used widely on Freightliner Cascadias) operate at 9.0 bar nominal with an acceptable range of 8.0–10.5 bar. Pressure drop below 7.5 bar throws SPN 3361/FMI 1 (DEF Dosing System Pressure Low). Technicians who replace the DEF pump without pressure-testing the delivery line often see this fault recur within 30,000 miles because the root cause was a partially occluded injector nozzle, not pump failure.

The DEF injector tip carbon threshold is worth committing to memory: 0.8mm orifice diameter at spec. Partial blockage reducing flow by more than 15% will cause SCR outlet NOx to exceed 0.2 g/bhp-hr, which is the compliance boundary under 40 CFR Part 1065 test procedures. You won't see this on a scan tool until the NOx sensor downstream confirms the breach.

Temperature and Freeze Protection Obligations

CARB has specific cold-soak requirements for DEF tank heating systems. The ECM must initiate DEF heating when ambient temperature drops below -11°C (12°F) and must maintain tank temperature above -9°C during operation. Heater circuit faults — typically SPN 3362/FMI 5 (DEF Tank Heater Circuit Open) — are frequently dismissed in warm-weather regions as irrelevant. That's a mistake. CARB inspectors interpret an inactive heater circuit as a system that cannot demonstrate year-round compliance capability, regardless of current ambient conditions.

Fault Code Reporting Obligations: The Timelines That Create Liability

This is the area where the gap between shop practice and regulatory requirement is widest.

Under CARB's Truck and Bus Regulation enforcement guidance (last updated August 2023), fleets are expected to document corrective action for emissions-related OBD faults within 45 days of first occurrence. Emissions-related under CARB's definition includes anything touching the aftertreatment system, EGR circuit, crankcase ventilation, or fuel system. That's a broader net than most maintenance managers apply.

Specific fault codes that trigger mandatory documentation under HD OBD requirements include:

• P2BAD / SPN 3216 — NOx Out of Range High
• P20EE / SPN 3364 — SCR NOx Catalyst Efficiency Below Threshold
• P2002 / SPN 3251 — DPF Differential Pressure Sensor
• P0401 / SPN 412 — EGR Flow Insufficient (the cascade implications of this code are covered in detail in this analysis of EGR valve failure patterns in commercial diesel fleets and the P0401/P0403 cascade effect)
• P11DB / SPN 3363 — DEF Dosing Valve Control

The 45-day window is measured from ECM timestamp, not from when the code was discovered during a scheduled PM. This distinction is critical. If a fault first set six weeks before a vehicle's next oil service interval, the clock has already been running.

New York's enforcement arm uses CARB's HD OBD II standards directly, but adds a layer through its Enhanced Inspection and Maintenance (E/I-M) program for vehicles over 8,500 lbs. Vehicles failing emissions testing generate a Form MV-619 which must be addressed within 30 days or the registration renewal is blocked. For fleet managers running vehicles in both states, the NY 30-day window is the controlling constraint.

A Real Fault Pattern: 2019 Peterbilt 579, 487,000 Miles

This scenario came from a 47-truck refrigerated carrier fleet out of the Inland Empire. The vehicle was a 2019 Peterbilt 579 with a PACCAR MX-13 engine, 487,000 miles, Bendix aftertreatment system.

At 481,000 miles, the ECM logged SPN 3216/FMI 16 (NOx Sensor Rationality High) as a pending code — not active, not illuminating the MIL. The fleet's telematics platform didn't surface it because the fault wasn't active. At 484,500 miles, SPN 3364/FMI 31 (SCR Inducement Active) set as active, triggering the first derate. The driver reported reduced power to dispatch, who logged it as a service request for the next scheduled stop, six days out.

When the truck arrived at the shop, the technician cleared the fault and performed a DEF quality check — concentration read 32.1%, within spec. Fault returned within 200 miles. Second shop visit: SCR inlet NOx sensor (Cummins PN 4326866) was replaced at $380 parts/$220 labor. Fault returned at 486,100 miles.

The actual root cause was a cracked DEF injector return line — a $28 part — causing intermittent air ingestion into the dosing circuit. The system had been masking the real fault with sensor replacements for 5,200 miles. Total unnecessary parts cost: $1,840. CARB audit compliance gap: the initial SPN 3364 was now 38 days old without a confirmed root-cause repair order, sitting inside the 45-day window but with documentation showing only parts swaps and no root-cause confirmation. Fifteen more days of this and the fleet would have had an enforcement exposure.

This is precisely the failure pattern that statistical fault recurrence analysis is designed to catch. Understanding fault code recurrence intervals through a statistical framework tells you whether a cleared code is truly resolved or cycling toward a more severe event.

ACF Regulation Transition Planning: Model Year and Mileage Thresholds

The Advanced Clean Fleets regulation phases in stringency by fleet type and vehicle use case. The thresholds fleet managers need to track:

| Fleet Category | Zero-Emission Requirement Trigger | Affected MY Range | |---|---|---| | High-priority fleets (100+ vehicles or >$50M revenue) | 50% ZEV purchase requirement by 2030 | MY2024+ acquisitions | | State and local government fleets | 100% ZEV by 2027 | All MYs | | Drayage fleets (CARB registered) | No new diesel additions after 2024 | MY2025+ | | General private/for-hire | Mileage-based phase-out, MY2010 and older first | Pre-2010 MYs |

The drayage provision deserves specific attention. Any truck operating within a California port or intermodal rail yard must be CARB-registered under the Drayage Truck Registry (DTR). Trucks with engine model years 2010–2023 must meet 0.01 g/bhp-hr PM and 0.2 g/bhp-hr NOx to remain DTR-eligible. A single failed regen cycle that causes DPF loading beyond 80% calculated soot mass — surfaced as SPN 3251/FMI 15 — can pull a truck from DTR eligibility until a verifiable regen and DPF inspection is documented.

What Your Telematics Stack Needs to Report

Most fleet telematics platforms report active fault codes. CARB compliance requires more than that. You need:

Pending code history with ECM timestamps. A fault that sets as pending and clears before the next active threshold has still been logged to the ECM. CARB inspectors pull J1939 extended fault records, not just the active code stack.

Freeze frame data for emissions-relevant SPNs. At minimum: engine load at fault onset, coolant temp, vehicle speed, DEF tank level percentage, aftertreatment system temperature (SCR bed temp typically referenced via SPN 3246), and cumulative idle hours.

Fault duration tracking. The 45-day corrective action window requires knowing when a fault first appeared, not just that it appeared. Duration metrics also feed directly into the kind of fleet risk scoring frameworks that support both DOT audit preparation and insurance risk conversations.

Platforms that only surface active faults during a trip are a liability in CARB-regulated fleets. The ECM data is there. The question is whether your telematics architecture is accessing it.

The Bottom Line

CARB and New York emissions compliance is not a PM checklist item — it's a real-time data management problem. The fault codes that create enforcement exposure are often pending, intermittent, or recurring at below-active thresholds, and the 45-day documentation window starts from ECM timestamp regardless of when your shop sees the vehicle. DEF system integrity requires pressure testing to spec (8.0–10.5 bar on DENOXTRONIC systems), concentration verification at every service interval, and heater circuit confirmation even in warm climates. A single misdiagnosed SCR fault can run up $1,800 in wrong-parts costs while the compliance clock expires underneath you.

Routiq gives fleet managers continuous access to pending fault histories, ECM freeze frame data, and recurrence pattern analysis across the full J1939 SPN stack — exactly the visibility layer that separates a documented compliance posture from an enforcement exposure. Start a free trial at Rooutiq and see what your ECMs have been logging that your current platform isn't surfacing.