Prevention FAQ — FMCSR 393.75(b): Steer Tire Tread Depth
Fleet safety FAQ for FMCSR 393.75(b) steer tire tread violations: inspector focus areas, pre-trip checklists, CSA impact, and root-cause guidance.
- Code:
- 393.75(b)
- Code System:
- FMCSR
- BASIC Category:
- Vehicle Maintenance
- OOS Eligible:
- No
- Severity Weight:
- 8
- Violation Group:
- Tires
Ranks #223 of 3,146 FMCSR codes by citation frequency • OOS rate of 21.0% is below the FMCSR-wide average of 33.3%.
Violation Description
Tire-front tread depth less than 4/32 of inch on a major tread groove
Prevention FAQ for Fleet Managers
Pre-trip discipline, inspector focus, and root-cause fixes
› What exactly do inspectors measure and observe when citing 393.75(b)?
Inspectors focus on the steer axle tires specifically — the legal threshold is less than 4/32-inch tread depth anywhere in the major tread grooves. They use a calibrated tread depth gauge, not a visual estimate, and will check both steer tires. The 4/32-inch standard for steers is stricter than the 2/32-inch threshold applied to other axle positions, so inspectors often target steers first as the highest-stakes position.
Our inspection records show 10,962 all-time citations for this code, placing it at #218 of 3,036 FMCSR codes by citation volume — meaning inspectors encounter it regularly enough to have a practiced eye. FREIGHTLINER-family trucks (FRHT: 876 citations, FREIGHTLIN: 495 citations) and FORD vehicles (688 citations) account for the highest citation counts by make in our database, so inspectors working high-volume freight corridors have seen this violation most often on those platforms.
› What specific items belong on a driver's pre-trip checklist to catch low steer tread before a roadside inspection does?
Add these mandatory line items to your pre-trip form for the steer axle:
- Visual tread groove check — look for tread wear indicators (TWI bars) flush with the tread surface; if visible, the tire is at or below 2/32-inch and already dangerously past the 4/32-inch steer threshold.
- Gauge measurement — require drivers to carry and use a tread depth gauge on both steer tires at every pre-trip. Record the measured depth (e.g., "LF steer: 5/32, RF steer: 5/32").
- Irregular wear notation — cupping, feathering, or one-sided wear can mask remaining depth; require drivers to flag any uneven wear pattern for shop review.
- Sidewall and bead condition — low tread often co-occurs with other tire deterioration that triggers additional violations.
Set a pull-for-service threshold at 5/32-inch on steer tires so vehicles are rotated or replaced before reaching the 4/32-inch enforcement line. This single intervention directly targets the most common failure point.
› What documentation must drivers carry and what records must the carrier retain for steer tire compliance?
Drivers do not carry tire measurement logs in the cab, but carriers must retain records that demonstrate proactive compliance:
- Pre-trip inspection reports that include recorded tread depth readings, per 396.11. Retain these for at least 3 months.
- Periodic inspection records (per 396.17) showing tread depth at time of inspection. Our database shows 396.17(c) — no proof of periodic inspection — has 198,331 citations in our records, confirming that inspectors actively request these documents at the roadside.
- Tire replacement/rotation work orders with date, mileage, tire position, and measured depth at time of swap. This creates a traceable service history.
- Driver vehicle inspection reports (DVIRs) noting any tread defects flagged between formal inspections.
For fleet managers: store records in a maintenance management system that timestamps entries and links work orders to vehicle IDs. If a DataQs challenge becomes necessary, a timestamped work order showing tread depth above 4/32 on the inspection date is your primary evidence.
› What are the root causes behind steer tread violations, based on what other violations appear alongside this code?
Our co-occurrence data points to three systemic patterns fleet managers should address:
1. General maintenance program breakdown — 396.3(a)(1) (inspection/repair/maintenance — general) carries a 45.3% OOS rate in our database and is a frequent companion code. When steer tread is low, it suggests the broader maintenance cycle — interval scheduling, shop throughput, and driver defect reporting — has broken down, not just tire management.
2. Periodic inspection gaps — 396.17(c) (no proof of periodic inspection) shows 198,331 citations in our records with a 0.0% OOS rate, meaning inspectors write it as a paperwork violation constantly. Pairing with tread citations suggests vehicles are operating beyond inspection intervals, allowing tread wear to accumulate undetected between formal shop reviews.
3. Lamp and visual inspection failures — 393.9(a) (inoperable required lamps, 660,737 citations) appearing alongside tread violations signals that drivers are not completing thorough pre-trips. A driver who misses an inoperable lamp is equally likely to skip a tread gauge measurement.
Address all three root causes — not just tire replacement — to prevent recurrence.
› How should the shop verify a steer tire repair or replacement before the vehicle returns to service?
After replacing or rotating steer tires, the shop must complete a documented return-to-service checklist:
- Measure and record tread depth on both steer positions using a calibrated gauge. Log the actual number (e.g., "14/32") on the work order — not just "new tire installed."
- Verify correct tire specification — load range, speed rating, and size must match the vehicle's tire placard. An undersized or incorrect-spec tire may be legally compliant on tread but mechanically non-compliant.
- Inspect for alignment indicators — if a steer tire wore below 4/32 before its expected service life, pull an alignment check. Premature wear on one shoulder is a red flag; correcting alignment prevents the next replacement from wearing down prematurely as well.
- Clear the DVIR defect entry — the driver who flagged the defect must receive a signed-off copy showing the defect was repaired, per 396.11(c).
- Update the maintenance management system with mileage, measured depth, and technician ID so the next service interval resets from this baseline.
› What post-citation review process should the fleet run after a driver receives a 393.75(b) citation?
Run a structured post-event review within 72 hours:
Step 1 — Pull the inspection report. Obtain the DataQs record or FMCSA SAFER entry. Confirm the cited vehicle, axle position, and measured depth recorded by the inspector.
Step 2 — Audit maintenance records. Pull the last three pre-trip DVIRs, the most recent periodic inspection, and all tire work orders for that vehicle. Identify the last recorded tread depth measurement and calculate whether wear rate was normal or accelerated.
Step 3 — Interview the driver. Determine whether the gauge measurement step was performed at pre-trip or skipped. If skipped, document it as a training and accountability gap.
Step 4 — Fleet-wide spot check. When one vehicle fails steer tread, audit the steer tires on at least the 10 vehicles with the highest mileage since last tire service. Our database shows 10,962 total citations for this code — fleets that catch one citation often have a systemic issue, not an isolated incident.
Step 5 — Root cause log. Document findings in a corrective action report tied to the vehicle ID and driver file.
› How does a 393.75(b) citation hit the carrier's CSA Vehicle Maintenance BASIC score?
This code carries a CSA severity weight of 7 — on a scale where most Vehicle Maintenance violations range from 1 to 10, a 7 is a meaningful hit. Every citation is eligible for time-weighting: violations in the most recent 6 months carry the highest weight, then decay over 24 months.
With an all-time OOS rate of 21.0% for this code, roughly 1 in 5 citations results in an out-of-service order. Our all-FMCSR average OOS rate is 31.4%, so this code's 21.0% rate is below average — but an OOS event on the steer axle is operationally severe: the vehicle cannot move until the tire is replaced.
For context, this code is ranked #218 of 3,036 FMCSR codes by citation volume, meaning it is a well-known violation that FMCSA's SMS algorithm has ample data on. Fleets with multiple citations in a 24-month window will see Vehicle Maintenance BASIC percentile scores rise, potentially triggering intervention. The severity weight of 7 means even a single citation has more impact than lower-weight codes.
› What driver training topics specifically address the knowledge gaps that lead to steer tread violations?
Our vehicle make data shows FREIGHTLINER-family units (FRHT: 876 citations, FREIGHTLIN: 495 citations) and FORD vehicles (688 citations) dominate the citation list. If your fleet runs either platform heavily, prioritize training for those driver populations first.
Core training modules to build or update:
- The 4/32-inch rule for steers — many drivers know the 2/32-inch rule for drive and trailer tires but are unaware the steer threshold is double that. Make the distinction explicit.
- How to use a tread depth gauge — hands-on, not slide-deck. Require each driver to demonstrate correct gauge placement at multiple groove positions.
- Identifying abnormal wear patterns — cupping, center wear, and one-sided shoulder wear as early indicators requiring shop escalation, not just a note on the DVIR.
- Consequences of a steer OOS event — 21.0% of 393.75(b) citations result in an out-of-service order. Drivers should understand that a missed pre-trip check can ground the truck on the side of the road, not just generate a citation.
- Pull-for-service protocol — what to do, who to call, and that the decision to pull a tire is non-negotiable regardless of schedule pressure.
› Under what circumstances should the fleet file a DataQs challenge after a 393.75(b) citation?
Challenge the citation if you can establish at least one of the following with documentation:
1. Measurement error. If your work orders show a tread depth reading above 4/32-inch within a short window before the inspection — and the vehicle's mileage since that reading is inconsistent with wearing below threshold — the inspector's measurement may be challengeable. Tread depth gauges can malfunction or be misapplied.
2. Wrong axle cited. Inspectors occasionally cite the steer axle when the low-tread tire was actually on a drive position, which carries a different standard. Confirm the inspection report specifies the steer axle.
3. Clerical or vehicle identification errors. If the cited USDOT number, vehicle VIN, or date of inspection does not match your records, file immediately — these errors can attach violations to the wrong carrier's CSA record.
Do not challenge a citation simply to remove a legitimate violation. The CSA severity weight of 7 makes the score impact real, but a weak challenge wastes resources and is unlikely to succeed without documentary evidence. Reserve DataQs for cases where you have timestamped, third-party documentation contradicting the inspector's finding.
› How frequently should the fleet self-audit steer tires, and what does the enforcement trend data suggest about timing?
Our database shows 0 citations in the last 90 days and 0 citations in the last 12 months for this code. That does not mean steer tire enforcement has stopped — it reflects the inspection sample flowing into our database during that window. With 10,962 all-time citations logged, this is an established enforcement target that recurs across inspection cycles.
Recommended self-audit cadence:
- Every pre-trip (daily): driver-level tread gauge measurement recorded on the DVIR — this is the first line of defense.
- Every 30 days: shop-level measurement of all steer tires on active units, logged in the maintenance management system with gauge readings.
- At every periodic inspection: formal tread depth documentation as a required line item, not optional.
- After any tire rotation or replacement: immediate post-service measurement before return to service.
Set your internal pull-for-service trigger at 5/32-inch on steers to maintain a buffer above the 4/32-inch enforcement line. For fleets operating FREIGHTLINER or FORD units — the two most-cited makes in our database — apply the 30-day shop audit as a non-negotiable standard given their citation history.
Related Records
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.
Vehicle recall campaigns, defect investigations, and consumer safety complaints (SCRS).
Cross-border carrier registry and Canadian recall campaigns where applicable.
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.