396.11(c) DVIR Defect Citation: What It Means & How to Fight Back

You were cited for failing to repair defects noted on your vehicle inspection report before dispatch. Here's what happens next and how to prevent it.

Severity Weight
5
OOS Eligible
No
BASIC Category
Vehicle Maintenance
Code System
FMCSR
Code:
396.11(c)
Code System:
FMCSR
BASIC Category:
Vehicle Maintenance
OOS Eligible:
No
Severity Weight:
5
Violation Group:
BASIC 5

Ranks #3,037 of 3,146 FMCSR codes by citation frequency.

Violation Description

Motor carrier failing to repair defects listed by driver on DVIR before dispatching vehicle.

In-Depth Explainer

Grounded in TruckCodex roadside-inspection data

What 396.11(c) means in plain language

When you complete your Daily Vehicle Inspection Report (DVIR), you're documenting the condition of your truck before you hit the road. If you note a defect—anything from a cracked mirror to worn brakes—your motor carrier has an obligation: they must repair that defect before they dispatch the vehicle again.

A 396.11(c) citation means a inspector found evidence that your carrier sent a truck out with a known defect still unrepaired. This could happen in a few scenarios: you reported something on yesterday's DVIR, it didn't get fixed overnight, and you were assigned the same truck the next morning. Or the defect was noted and the vehicle was sent out anyway without the repair being completed. Either way, the regulation requires motor carriers to address documented defects before the vehicle returns to service.

This is fundamentally about accountability in the maintenance chain. You do your job reporting what you see. The carrier's job is to fix it. When that handoff breaks down, an inspector catching it can issue this citation.

What our enforcement data actually shows

This code is extraordinarily rare in roadside enforcement. Across our database of 13 million+ real inspection records, we have recorded zero citations for 396.11(c) in the last 12 months, zero in the last 90 days, and zero all-time. No vehicles have been placed out-of-service under this code.

The rarity of this citation suggests one of two things: either motor carriers are nearly universally repairing documented defects before dispatch, or inspectors rarely have the inspection records available at roadside to verify whether a defect was actually repaired. Most likely, it's a combination. Inspectors typically don't have access to the previous day's DVIR when they stop a truck, so the violation is hard to prove in the field. Your carrier's maintenance logs and dispatch records would need to be subpoenaed or reviewed during a safety audit for this code to surface.

Who gets cited most

With zero citations on record, there is no geographic or carrier concentration to report. This code does not appear in the enforcement patterns across our roadside inspection data.

How severe is this compared to similar codes

Vehicle maintenance violations are common. In the same broad category, 396.3(a)(1)—general inspection, repair, and maintenance defects—shows 236,919 citations with a 45.3% out-of-service rate. Brake-related issues like 393.47E (slack adjuster defective) logged 180,363 citations with a 0.0% out-of-service rate. Lamp violations such as 393.9(a) (inoperable required lamps) generated 660,737 citations, the highest among peer codes, with a 15.4% out-of-service rate.

By comparison, 396.11(c) is essentially non-existent in enforcement. This doesn't mean the requirement is unimportant—it means the violation is either not being caught at roadside or is being resolved through other channels (like carrier audits or follow-up compliance reviews).

How to avoid it

Your defense against this citation starts before you even turn the key.

  • Document every defect you find, no matter how minor. Use your DVIR system (electronic or paper) to record exact descriptions: "brake pedal spongy," "right mirror glass cracked," "interior dome light inoperative." Vague notes like "something feels off" give your carrier no actionable repair target and create ambiguity if an inspector later questions whether it was actually repaired.

  • Never accept a truck with an open defect from the previous shift. If your pre-trip inspection confirms a defect that you know was reported on yesterday's DVIR, refuse the dispatch and notify your safety or maintenance department in writing (email, text, or your carrier's app). This creates a documented trail that you did your part and puts the onus on the carrier to either repair it or officially clear it.

  • Cross-check the maintenance log at pickup. Some carriers maintain a whiteboard or log at the dispatch area noting which vehicles are down for repair. Before accepting a unit, verify that any defect you or the previous driver reported has been marked "repaired" or "inspected—no defect found." If it's unmarked or you see "pending," don't take the truck.

  • Request proof of repair before dispatch. If your carrier uses a maintenance management system (Samsara, Verizon Connect, Zonar, etc.), ask to see the work order or repair ticket showing the defect was addressed. This is your protection and the carrier's documentation.

  • Report the pattern if it persists. If you repeatedly see the same vehicle or defect type being dispatched unrepaired, escalate to your fleet safety manager or compliance officer. A pattern can trigger a focused audit, which is far better than waiting for a roadside citation.

The practical reality is that inspectors rarely cite 396.11(c) at the roadside because they lack the historical DVIR records to prove the violation. Your real risk is during a carrier compliance audit, where FMCSA can pull your DVIR logs and maintenance records and spot the gaps. That's when this code becomes actionable—and it signals deeper systemic problems in how your carrier manages defect repairs. By being meticulous with your own DVIR documentation and refusing to drive unsafe equipment, you protect yourself and help your carrier stay compliant.

Last updated: 2026-04-20T18:48:24.927Z Based on TruckCodex inspection data See 396.11(c) Q&A → Fleet FAQ →

Data sources & freshness

TruckCodex aggregates official public-sector datasets. See the Source registry for dataset-level coverage and the Freshness log for last-import timestamps.

Census, SAFER, SMS, Licensing & Insurance (L&I), roadside inspections, crashes, and authority history.

Refreshed daily.

Vehicle recall campaigns, defect investigations, and consumer safety complaints (SCRS).

Refreshed daily.
EIA

Retail diesel and gasoline price history and state fuel-tax tables.

Refreshed weekly.

Cross-border carrier registry and Canadian recall campaigns where applicable.

Refreshed weekly.

TruckCodex is an independent aggregator; it is not affiliated with FMCSA, NHTSA, EIA, or Transport Canada. Always verify compliance-critical information directly with the originating agency.