Prevention FAQ — FMCSR 392.2-SLLOWZ: Fatigue & Illness Citations

Across our inspection records, 63 citations for this code in Missouri alone over the last 180 days indicate inspectors are looking for observable signs of impairment: drowsy driving (weaving, erratic lane control), slow or delayed reactions at checkpoints, slurred speech, or driver admission of illness or fatigue. The 0.0% out-of-service rate across all 474 all-time citations suggests officers are documenting the behavior but not removing the driver immediately—meaning the violation is typically recorded during the interaction itself. Inspectors in high-citation states like MO, AZ (31 citations), and PA (28 citations) are particularly trained to spot these markers during routine stops. Train dispatch and safety teams to understand this is primarily a behavioral observation code, not a mechanical defect.

Add a driver attestation section covering: (1) hours slept in the past 24 hours, (2) any illness symptoms (fever, medication effects, congestion), (3) medication use that may impair alertness, and (4) confirmation that the driver feels fit to operate. This is not a mechanical checklist—it's a health/readiness gate. Have drivers initial and time-stamp this section. Given that 77 citations occurred in the last 90 days alone, and the violation is non-mechanical, the preventive control is dispatch authorization. Pair this with a policy that grants drivers explicit permission to delay departure or hand off a load if they report fatigue or illness before getting behind the wheel. Document all such decisions. This shifts accountability from the driver (who faces a citation) to the carrier (who can demonstrate duty of care).

Drivers should carry a dated fitness-to-operate log signed at each pre-trip. Carriers must retain: (1) the signed pre-trip attestation, (2) dispatcher notes on any fatigue or illness reports and how they were handled, (3) driver training records showing education on fatigue risk, and (4) any medical clearances if a driver returns after illness. The 8 co-occurring citations for HOS/ELD violations (code 395.24) in the last 90 days show a pattern: fatigue is often discovered during hours-of-service audits. Ensure your ELD records align with driver attestations—discrepancies flag systemic fatigue issues. Keep all documentation for at least 3 years. This creates a defensible record if a citation is contested via DataQs.

Our inspection records show three dominant patterns: HOS/ELD violations (8 shared inspections in 90 days) indicate drivers are operating after exceeding legal hours without proper rest—fatigue is the symptom of broken scheduling. Periodic inspection failures (4 shared inspections) suggest vehicles with deferred maintenance are being pushed by fatigued drivers in poor mechanical condition. False duty-status records (3 shared inspections) show drivers misreporting hours to mask schedule pressure. The root cause is rarely a one-time personal illness; it's a system failure—unrealistic dispatch schedules, inadequate home time, and pressure to meet delivery windows that force drivers onto the road tired. Audit your load planning and delivery windows. If drivers are regularly hitting 70-hour limits, your scheduling is broken, not your drivers.

After a fatigue-related citation, the driver must provide: (1) a statement of the circumstances (when they last slept, what triggered the citation), (2) confirmation they have rested (8+ hours sleep, or medical clearance if illness), and (3) signed acknowledgment of company fatigue policy. Do not return the driver to active status based on self-report alone. If the citation was illness-related, require a fit-for-duty certification from a healthcare provider or your occupational health service. For fatigue, require the driver to sit out the remainder of their 34-hour restart or equivalent rest period—do not resume duty mid-cycle. Document all steps. This is not punitive; it's verification. Given the 283 citations in the last 12 months across the industry, establishing a clear return-to-duty protocol protects your carrier from repeat offenders.

Conduct a post-citation review within 48 hours: (1) Pull the driver's HOS/ELD records for the 14 days prior to the citation—look for consecutive long days or nights with minimal breaks. (2) Review dispatch notes and load assignments for that period to identify scheduling pressure. (3) Check the driver's medical history with your occupational health provider (if enrolled) for any unreported illness. (4) Interview the driver about sleep quality, nutrition, and any personal stressors. (5) Analyze the specific location and time of the citation—if it's at a known enforcement corridor at 2 AM, was your dispatch routing drivers through that zone during high-fatigue hours? The 34 citations in May 2025 and 37 in February 2026 (both peaks in the last 12 months) suggest seasonal or planning patterns. Document findings in the driver's safety file and create a corrective action plan.

This code has a CSA severity weight of 8—moderate—but ranks #941 of 3,036 FMCSR codes by citation volume, meaning it is relatively uncommon. However, it does NOT increase the Vehicle Maintenance BASIC; it feeds into the Unsafe Driving BASIC. That said, the frequency matters: 474 all-time citations and 283 in the last 12 months shows this is being cited at a steady rate. Accumulation of citations—even non-mechanical ones—can increase your Unsafe Driving BASIC percentile. Conversely, our data shows 0% of all citations resulted in out-of-service orders, compared to the 31.4% all-FMCSR average. This suggests the violation is treated as a behavioral coaching opportunity, not a safety-critical defect. Use this to your advantage: invest in fatigue management training and driver wellness to prevent citations before they accumulate.

Mandatory training should cover: (1) Circadian Rhythm & Sleep Science: How fatigue builds, why consecutive nights worsen it, and what 6 hours of sleep means for reaction time. (2) Medication & Illness Self-Assessment: Common OTC and prescription drugs that impair alertness, when to self-report, and when illness disqualifies a driver. (3) Fatigue Recognition in Others: Teach drivers to spot impairment in their co-driver or passengers—peer accountability matters. (4) Dispatch Communication: How and when to report fatigue to dispatch without fear of reprisal; make it part of safety culture, not a career risk. (5) Load Planning Context: Help drivers understand why certain routes have tight windows and what flexibility exists. Train monthly, not annually. Pair training with policy: drivers who report fatigue are protected from discipline. This flips the incentive from hiding fatigue to disclosing it early.

File a DataQs challenge if: (1) the driver has contemporaneous documentation (signed fitness-to-operate form, driver statement, witness, or dash-cam) proving they were alert and capable at the time of inspection. (2) The inspector's notes are vague (e.g., "driver appeared tired" without behavioral detail). (3) Medical records show the driver had a cleared, minor condition (e.g., mild cold) with no functional impairment. (4) There's a timing/HOS discrepancy: if the driver's ELD shows they had adequate rest before the citation, and the inspector documented no observable behavior, challenge it. However, do not challenge if the driver self-admits to fatigue or if the citation is paired with HOS violations—the co-occurrence pattern (8 HOS violations paired with this code in 90 days) makes those challenges weak. Focus challenges on documentation gaps, not driver credibility disputes.

Conduct a formal fatigue audit quarterly (every 90 days) and a rapid 48-hour pulse audit whenever any fatigue or illness citation occurs. Justification: your inspection data shows 77 citations in the last 90 days, and monthly peaks (34 in May 2025, 37 in February 2026, 32 in March 2026) indicate seasonal or operational clustering. If you have 100+ active drivers, expect 1–2 citations per quarter. Quarterly audits let you identify systemic patterns—route design, seasonal dispatch load, driver population turnover—before they accumulate into Unsafe Driving BASIC issues. The 90-day cadence aligns with CSA Behavioral Analysis Snapshots and gives you a 30-day buffer to implement corrective action before your next snapshot. For fleets under 50 drivers or with zero citations in the last 12 months, semi-annual audits are sufficient; escalate to quarterly if you record any citation.