Prevention FAQ — FMCSR 393.91

Inspectors conducting Level I–III roadside inspections examine the specific vehicle system or component this code addresses. Our inspection records show 128 citations all-time for this code, with 68 resulting in out-of-service placement—a 53.1% OOS rate, significantly higher than the all-FMCSR average of 31.4%. This elevated OOS rate indicates inspectors are flagging serious defects. During pre-trip and roadside checks, officers look for the presence, condition, and proper function of the component in question. Pay particular attention during visual walk-arounds: inspectors often cite this violation when they observe damage, deterioration, or missing parts. Document the exact condition noted on the citation so your maintenance team can address root cause, not just surface symptoms.

Build your pre-trip checklist to include a dedicated section for the system or component covered by 393.91. Have drivers perform a tactile inspection—not just a visual scan—checking for secure fastening, cracks, corrosion, or wear. Document the result in writing before the vehicle leaves the yard, even if the item passes. This creates a timestamped record that protects your carrier if a citation is later challenged. Require drivers to photograph the component if damage is suspected and report it immediately to dispatch. Include specific pass/fail criteria in the checklist so drivers understand the standard. Train drivers that a pre-trip catch prevents a roadside citation and keeps the vehicle in revenue service. Rotate checklist custodians weekly so no single driver becomes complacent about the inspection routine.

Drivers must carry proof of the last maintenance or inspection relevant to this component. Your fleet should retain: dated work orders describing the repair or inspection performed, technician name and signature, parts replaced (with part numbers), and the mileage at service. For pre-trips, keep a log or digital record of driver certifications for every vehicle departure. If a citation is issued, the work order dated before the violation helps establish that you maintained the vehicle to standard. FMCSR 396.11 and 396.13 require records be kept for one year; treat pre-trip logs the same way. In your maintenance management system, flag this component for monthly review so you catch deterioration before it leads to a roadside stop. Digital records (photos, scanned work orders, time-stamped pre-trip forms) are admissible in DataQs challenges and CSA audits.

Our inspection records show 393.91 often appears alongside other Vehicle Maintenance code violations, though we have limited historical co-occurrence data for this low-volume code (0 citations in the last 90 days). However, the pattern across similar codes—such as 396.3(a)(1) at 45.3% OOS rate and 393.47E at 0.0%—suggests that citations cluster when fleets lack systematic inspection or have gaps in technician training. Root causes typically include: (1) deferred maintenance on older equipment (note that THMS, BLUB, and FORD vehicles dominate our citation list for this code), (2) incomplete repair verification after work orders are filed, and (3) missing or unclear maintenance schedules. Conduct a vendor audit: verify your repair shops document work with photos and mileage. For each citation your fleet receives, ask: Was this component on the last PM schedule? Was the repair verified by a second technician? These questions expose systemic gaps.

Require a two-step verification process: (1) the technician who performed the repair completes a detailed work order with photos before and after, and (2) a second licensed technician or safety manager independently inspects the component and signs off before the vehicle is released to a driver. This peer-review step catches incomplete repairs and reinforces quality standards. For components covered by 393.91, document the exact measurement, torque specification, or functional test applied (e.g., 'fastener torqued to X ft-lbs' or 'component tested under load for Y minutes'). Create a verification checklist specific to this code so nothing is overlooked. After repair, schedule a test drive or controlled-environment operation to confirm the fix works under real conditions. If the same component is cited again within 12 months, escalate to your maintenance director: it signals either poor repair quality or inadequate root-cause analysis. Track repair-to-citation intervals in a spreadsheet so you spot repeat failures early.

Within 48 hours of a citation, convene a brief root-cause meeting with the driver, your maintenance manager, and safety director. Review the citation document: exactly what condition was noted? At what mileage? Compare it to your last pre-trip log and maintenance record. Ask: (1) Was this component on the last PM? (2) Did the driver report any symptoms before the stop? (3) How long had the vehicle been in service since the last inspection? Use your answers to update the PM interval if needed. Photograph the cited component in its current state and retain that photo in your inspection file. If the violation is valid, do not challenge it; instead, use it as a training moment. Schedule a 15-minute toolbox talk for all drivers reviewing the specific defect and how the preventive check would have caught it. Enter the citation into your maintenance tracking system so future work orders for this vehicle flag the history. Document the entire review process: it demonstrates due diligence if FMCSA ever audits your safety program.

FMCSR 393.91 is classified under the Vehicle Maintenance BASIC, which directly influences your carrier's CSA score and safety rating. Our data shows this code ranks #1356 of 3,036 FMCSR codes by citation volume, but the 53.1% out-of-service rate—69 percentage points above the all-FMCSR average of 31.4%—signals that when this violation occurs, it is severe enough to sideline the vehicle. Each out-of-service citation contributes to the Vehicle Maintenance BASIC percentile and to your Acute Violation count. A single OOS citation here may trigger a safety audit or increased scrutiny from FMCSA. While this code itself is not high-volume, the high OOS rate means each citation carries more weight in regulatory evaluation. Prioritize prevention through regular PM audits and driver training. Monitor your CSA BASIC scores monthly: if Vehicle Maintenance is trending upward, this code may be part of the problem, even if total citation count is low.

Develop a focused training module on pre-trip inspection that covers the specific system or component in 393.91. Include: (1) a visual guide showing what a defective component looks like versus a compliant one, (2) hands-on practice so drivers can feel for looseness, cracks, or corrosion, and (3) the exact reporting procedure if a problem is found (e.g., 'call dispatch immediately; do not attempt to repair'). Our data shows THMS, BLUB, and FORD vehicles were cited most often; tailor training examples using your fleet's dominant makes so drivers recognize the risks in their assigned equipment. Require annual recertification and include a written test so you document driver competency. Pair training with incentives: drivers who complete zero PM-related citations in a quarter earn a small safety bonus. This reinforces the connection between pre-trip diligence and paycheck. For new hires, embed this training in onboarding before they operate a vehicle.

Consider a DataQs challenge if: (1) your maintenance records clearly show the component was inspected and compliant on the day before the citation, (2) the inspector's notes lack specific detail (e.g., 'defective' with no measurement or functional test described), or (3) you have photographic evidence contradicting the citation. File within 90 days of the violation. Gather your work order, dated pre-trip form, photos, and technician statement, and submit via the DataQs portal with a clear narrative explaining why the citation is inaccurate. DataQs success rates are higher when your documentation is digital and timestamped. Do not challenge frivolous violations; instead, use them as training. However, if the same component is cited by different inspectors within months—and your maintenance records show it was properly repaired and monitored—a second citation may warrant challenge. Consult your safety manager and compliance software before filing; a strong DataQs package takes time to assemble correctly.

Establish a monthly self-audit cycle for this code. Our inspection records show zero citations in the last 90 days and zero in the last 12 months, suggesting the violation is rare or your fleet is performing well. However, the rarity does not justify complacency: the 53.1% out-of-service rate means when it does occur, it is severe. Conduct audits by pulling 5–10% of your fleet at random each month, performing a Level I inspection checklist that includes the 393.91 component, and documenting results. If you identify defects during self-audit, correct them before a roadside inspector finds them. Also, audit your maintenance records quarterly to verify that PM schedules include this component and that work orders document completion. If your fleet exceeds 500 vehicles, assign a dedicated compliance officer to track this code and alert management if any defects emerge. The low recent citation volume suggests prevention is working; maintain this standard by staying vigilant even when citation counts are low.