Prevention FAQ — FMCSR 393.205B: Elongated Stud/Bolt Holes

Actionable guidance for fleet safety managers on preventing elongated wheel studs/bolts. Covers inspection protocols, pre-trip checklists, root-cause patterns, and audit cadence based on 13M+ inspection records.

Severity Weight
2
OOS Eligible
No
BASIC Category
Vehicle Maintenance
Code System
FMCSR
Code:
393.205B
Code System:
FMCSR
BASIC Category:
Vehicle Maintenance
OOS Eligible:
No
Severity Weight:
2
Violation Group:
Wheels Studs Clamps Etc.

Ranks #1,566 of 3,146 FMCSR codes by citation frequency • OOS rate of 65.2% is above the FMCSR-wide average of 33.3%.

Violation Description

Stud/bolt holes elongated on wheels

Prevention FAQ for Fleet Managers

Pre-trip discipline, inspector focus, and root-cause fixes

What exactly are inspectors looking for when they cite 393.205B?

Inspectors are checking for visible stretching or widening of the holes in wheel rims where studs or bolts pass through. This damage typically appears as oval or enlarged holes instead of round ones, and is often visible without disassembly. Our inspection records show this violation is cited at notably high enforcement intensity in Texas (9 citations in the last 180 days) and Iowa (2 citations with a 100% out-of-service rate), suggesting roadside inspectors in these states prioritize wheel integrity checks. The damage usually results from loose fasteners vibrating under load, so inspectors are looking for evidence that studs or bolts weren't properly torqued or maintained. Even minor enlargement counts—the standard requires holes to remain true and undeformed.

What should our drivers check on the pre-trip inspection for wheel stud/bolt integrity?

Add these three checks to your pre-trip walk-around: (1) Visual inspection of all wheels: walk around each wheel and visually confirm stud holes are circular and not elongated or cracked. Use a marker to mark the stud positions if needed for consistency. (2) Manual torque check: use a torque wrench to verify each stud/bolt is tight to the vehicle manufacturer's specification (typically 400–600 ft-lbs for Class 8 trucks, but check your specific make). Loose fasteners are the root cause. (3) Photo documentation: have drivers photograph any wheel that shows signs of stress, enlarged holes, or corrosion around fasteners. This creates a baseline for trend analysis. Elongated holes cannot be field-repaired—wheels must be replaced—so early detection prevents roadside out-of-service citations.

What documentation should drivers carry and fleets retain?

Drivers should carry: (1) a wheel torque specification sheet (laminated card) for each vehicle type in your fleet, (2) pre-trip inspection reports signed and dated weekly. Fleets should retain: (1) maintenance records showing stud/bolt torque checks and dates, (2) photos of wheels from each pre-trip inspection (searchable by date and vehicle ID), (3) repair invoices for any wheel replacement or fastener service, with before/after photos, (4) driver training logs confirming each driver completed wheel integrity training. When a citation is issued, document the inspector's findings (copy of citation), the vehicle's maintenance history 90 days prior, and any corrective actions taken. This trail protects you in CSA disputes and helps identify whether the issue was a one-off or a systemic torque/inspection failure.

What root causes does the co-occurrence data reveal?

Across our 13 million inspection records, elongated wheel studs frequently co-occur with three patterns: (1) Turn signal and lamp defects (393.9TS, 393.9, and 393.11 appear in 3 inspections each in the last 90 days)—these suggest rushed or deferred maintenance cycles where wheels weren't checked as part of routine servicing. (2) Missing emergency equipment (393.95A, fire extinguisher, in 3 co-occurrences)—indicates a lack of systematic pre-trip discipline across the entire vehicle. (3) Medical certificate and CDL violations (391.41APC and 383.23A2, 2 co-occurrences each)—suggest driver or carrier-level oversight failures that cascade to neglected mechanical checks. The pattern indicates this code is rarely an isolated fastener problem; it reflects a broader maintenance culture issue. Fleets with this citation should audit their entire pre-trip and PM checklist compliance, not just wheel torque.

How should we verify wheel repairs before a vehicle returns to service?

After any wheel replacement or stud/bolt service, follow this verification protocol: (1) Torque verification at the shop: require the repair facility to document final torque on each fastener with a calibrated wrench and sign-off form. (2) Re-torque at carrier facility 50 miles later: wheels often settle after initial torque; retorque all fasteners 50 miles after the vehicle leaves the shop. Document this with date, mileage, technician name, and torque values. (3) Visual inspection of hole geometry: photograph each wheel to confirm holes are round and true, with no signs of cracking or stress around fastener perimeters. (4) Driver sign-off: have the assigned driver perform a final visual check and sign a form confirming wheel condition before taking the vehicle on a revenue run. This multi-step approach prevents the vehicle from returning to service with marginal repairs and catches installation errors the shop may have missed.

What should our fleet review after receiving a 393.205B citation?

Conduct a structured post-citation review within 48 hours: (1) Pull the vehicle's maintenance history for the 90 days prior to the citation. Check all torque records, PM logs, and pre-trip reports. (2) Compare against driver logs: did the assigned driver note any looseness, vibration, or wheel damage in pre-trip reports before the citation? If yes, why wasn't it escalated? If no, retraining is needed. (3) Audit the repair shop's work: if this vehicle had recent wheel service, contact the shop and obtain their torque documentation. (4) Review fleet-wide wheel torque data: pull torque records for all vehicles of the same make/model—if you see a pattern of low torque values across multiple units, this points to a shop or training issue affecting the whole fleet. (5) Retrain the driver and dispatcher on escalation procedures for safety-critical items. Document the entire review and file it alongside the citation for CSA tracking.

How does this citation impact our CSA Vehicle Maintenance BASIC?

Our inspection records show 393.205B is cited 65 times all-time and ranks #1548 of 3,036 FMCSR codes by volume, making it a relatively low-frequency violation. However, the out-of-service rate is 64.6%—nearly double the all-FMCSR average of 31.4%—which means when inspectors find elongated studs, they routinely ground the vehicle. This high OOS rate signals to CSA algorithms that the violation, though rare, is serious. A single 393.205B citation carries relatively modest CSA weight compared to high-volume codes like inoperable lamps (393.9, 660,737 citations), but the 64.6% OOS rate flags your vehicle maintenance culture. Multiple citations within a rolling year will trigger CSA safety alerts. The best defense is prevention: a documented torque program with monthly spot-checks across your fleet will keep this code off your record entirely.

What training should we provide to drivers on wheel integrity?

Design a 30-minute annual training module covering: (1) Why stud elongation matters: explain that loose wheel studs can cause uneven tire wear, vibration that damages suspension, and in extreme cases, wheel separation. Make it concrete—show a photo of an elongated hole vs. a healthy one. (2) Pre-trip walk-around protocol: walk drivers through the exact steps: visual scan of all wheels, listening for rattles, and knowing when to escalate. (3) What to report: teach drivers the language—"bolt hole appears enlarged", "stud is loose", "visible cracking around fasteners"—so they communicate clearly with maintenance. (4) Who to notify: clarify the escalation path (dispatcher, maintenance manager, phone number) and emphasize that safety concerns stop the vehicle—they don't proceed. (5) Fleet-specific data: share that our inspection records show Freightliner trucks (22 citations all-time) and Kenworth trucks (7 citations) dominate this violation, so if your fleet runs these makes, emphasize they require extra vigilance. Use your post-citation review findings (if applicable) as a teaching case.

When should we consider filing a DataQs challenge on a 393.205B citation?

File a DataQs challenge if: (1) The inspection report does not describe the specific hole(s) affected or provides no measurement/photo evidence. Vague citations ("wheels defective") without identification of which studs were enlarged are challengeable. (2) Your maintenance records show documented torque checks within 72 hours prior to the inspection that confirm fasteners were tight and holes were sound. This creates a timeline conflict. (3) The vehicle received a wheel replacement or stud service fewer than 100 miles before the citation, and the repair shop's documentation shows proper torque. This suggests inspector error in the post-repair assessment. (4) Multiple independent inspections (pre-trip, PM, prior roadside check) show no elongation, but the cited inspection claims to find it. This raises credibility questions. Do not challenge a citation simply because you disagree with the outcome—file only when the inspection narrative lacks specificity or contradicts documented evidence. Our 13 million records show 64.6% of these citations result in OOS placement, so challenges are uncommon but valid when evidence is clear.

How often should we audit our fleet for elongated wheel studs?

Our inspection records show 6 citations in the last 90 days and 31 in the last 12 months—a pattern of sporadic but steady enforcement. Establish this audit cadence: (1) Monthly spot-check: randomly select 10% of your fleet and torque-check all wheels. Document results. (2) Quarterly deep audit: pull maintenance records for all vehicles and compare torque logs against your standard. Flag any vehicle with torque readings below spec or missing data. (3) Post-maintenance verification: within 50 miles of any wheel service, retorque and document. (4) Annual training refresh: review your fleet's 393.205B citation history (if any) and reinforce driver pre-trip discipline. If your fleet has never been cited for this code, monthly spot-checks are sufficient. If you've had even one citation, increase frequency to biweekly torque audits until you've achieved six consecutive months of perfect compliance. The monthly trend in our data shows May 2025 had the highest volume (4 citations); if your fleet runs similar vehicle makes (Freightliner, Kenworth), increase vigilance in spring months when heavier loads and longer seasons stress wheel fasteners.

Last updated: 2026-04-20T15:42:31.922Z Guidance derived from TruckCodex inspection data Read the full article → Quick Q&A →

Top Enforcing States

Where 393.205B is most commonly cited (last 180 days)

1. Texas
6
OOS 83.3%
2. Iowa
1
OOS 100.0%

Often Cited Together

Other violations commonly found on the same inspection (last 90 days)

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.