The CSA Vehicle Maintenance BASIC: How Repairs Become a Score
Roadside maintenance violations feed a score that affects who will insure you, who will load you, and how often you get inspected. Here is how the weighting works and which repair decisions actually move it.
Updated
Defines the safety fitness and rating framework within which FMCSA's compliance and enforcement programme operates.
Quoted from the eCFR. Regulations change; check the linked text for the current version.
Why a maintenance page talks about scores
For most small carriers the largest cost of a deferred repair is not the repair. It is the insurance premium, the lost shipper qualification, and the increased inspection frequency that follow the violation into the Safety Measurement System and stay there for two years.
What the system actually measures
FMCSA's Safety Measurement System sorts roadside inspection and crash data into behaviour categories called BASICs. Vehicle Maintenance is one of them, and it collects every equipment-related violation written at roadside. The score is not a simple violation count. Each violation carries a severity weight, that weight is multiplied by a time factor that decays as the violation ages, and the total is normalised against the carrier's exposure — roughly, how many inspections it has had — and then expressed as a percentile against peer carriers with similar exposure.
- Severity weight — set per violation code, higher for conditions more strongly associated with crash risk
- Out-of-service uplift — an additional weight applied when the violation resulted in an out-of-service order
- Time weight — recent violations count for more; the weight steps down as the violation ages and drops out entirely after twenty-four months
- Exposure normalisation — a carrier with more inspections is compared on a rate basis rather than a raw total
- Peer group percentile — the published number is a rank against similar carriers, not an absolute measure
TODO(verify)
Current severity weight values by violation group, current time-weight step values, and the current intervention threshold percentile for the Vehicle Maintenance BASIC, taken from the published SMS Methodology document for the current version. The methodology has been revised repeatedly and we will not publish figures from an outdated edition.
The percentile is the part that misleads people
Because the score is a percentile within a peer group, a carrier can improve in absolute terms and see its number get worse, or clean up nothing and see it improve, purely because the peer group moved. Two consequences follow. First, a single bad inspection hurts a small carrier with few inspections far more than it hurts a large one, because the exposure denominator is small. Second, chasing the number month to month is not useful; the thing to manage is the violation rate per inspection over time.
Which repair decisions actually matter
The violations that carry the most weight are also, unhelpfully, the cheapest to prevent. Brake adjustment, tire tread depth, lamp function, and air system integrity account for a large share of vehicle maintenance violations, and every one of them is findable in a proper walkaround.
| Deferred item | Repair cost if done in a shop | What it can cost at roadside |
|---|---|---|
| Brake adjustment | Low — often part of routine service | OOS order, tow or mobile call-out, violation with OOS uplift for 24 months |
| Steer tire near minimum tread | One tire | OOS order, roadside tire service at premium rates, weighted violation |
| Inoperative marker lamp | Minimal | Citation and a violation on the record; multiple lamps can escalate |
| Air leak within tolerance today | Fitting or hose | Air loss rate measured over the limit, OOS, and a stranded truck |
| Low air warning device not working | Switch or wiring | OOS regardless of how well the rest of the system performs |
Documentation is a control, not paperwork
The DVIR trail under 49 CFR 396.11 and the maintenance records under 396.3 are what an investigator reads first. A carrier with a violation and a clean record showing the defect was found and repaired promptly is in a materially different position from one whose records show the defect was reported three times and nothing happened. Keeping the receipts is not administrative overhead; it is the evidence that the system was working.
DataQs exists and is underused
If a violation is factually wrong — wrong vehicle, wrong code, a condition that did not exist — the DataQs system is the mechanism for challenging it, and challenges supported by dated repair documentation succeed at a meaningfully higher rate than challenges that are just disagreement. This is another reason to keep every invoice.
Fault codes this covers
What the work costs
Shops that handle this work
We call every shop before it appears here, and publish the date.
Sample records only — seeded to demonstrate the directory. None of these numbers has been called.
Memphis, TN · 24/7 · mobile service
Indianapolis, IN · Mon-Fri 6am-6pm · mobile service
Laredo, TX · Mon-Sat 6am-9pm · mobile service
Phoenix, AZ · 24/7 · mobile service