Prevention FAQ — FMCSR 392.2DL: Fatigue & Illness

Inspectors document observable impairment: drooping eyelids, slurred speech, slow reaction time, difficulty maintaining lane position, or admission of fatigue or illness. Our inspection records show this code is enforced with wide geographic variance. Illinois leads with 129 citations over the last 180 days and a 51.2% out-of-service rate, while North Carolina logged only 14 citations at a 7.1% rate. This signals that Illinois inspectors apply stricter visibility standards and threshold-for-stopping protocols. Focus your training on the early-warning cues inspectors document in violation narratives: complaint-of-fatigue logs, failed coordination tests, or medical event history on file. The code carries a CSA severity weight of 8, so even non-OOS citations accumulate violation points.

Your pre-trip fatigue checklist must prompt drivers to self-assess before engine start. Include: (1) Hours since last 8-hour rest, including breaks under 30 minutes; (2) Quality of previous sleep—nausea, dizziness, or headache; (3) Current medication or over-the-counter drugs affecting alertness; (4) Visible illness signs—fever, coughing, vomiting, or acute injury; (5) Planned trip length vs. remaining hours-of-service; (6) Road/weather hazards that increase fatigue demand. Drivers must sign off daily. Pair this with a gate policy: any driver reporting fatigue or illness is immediately reassigned and sent to rest or care. Our data shows 90 citations in the last 90 days, with a spike in May (78 citations), indicating seasonal demand or lapsed compliance. Quarterly refresh training reinforces the checklist's use.

Drivers must carry: (1) Current medical certification and any DOT medical restrictions; (2) Recent prescription or OTC medication list with dosing; (3) Daily fatigue/wellness pre-trip sign-off sheet; (4) HOS logs (electronic or paper) showing sleep windows and break timing. Carriers must retain: (1) Driver qualification files with medical exam dates and restrictions; (2) 12-month pre-trip checklist archives by driver; (3) Incident reports linking citations to trip logs, weather, and load details; (4) Training attendance and fatigue-awareness test scores. When an inspector cites 392.2DL, obtain the narrative and cross-reference the driver's HOS record and medical file. Document any discrepancies (e.g., HOS shows 4 hours rest but driver reported fatigue). This record protects your DataQs response and identifies systemic gaps.

Across 13 million inspections, 392.2DL most frequently co-occurs with 392.2RG (17 shared inspections in the last 90 days), suggesting drivers are caught in multiple fatigue-linked infractions during the same stop. The second pattern—396.17C (No proof of periodic inspection, 14 co-occurrences)—indicates vehicles with deferred maintenance or inspection gaps correlate with driver fatigue citations, likely because mechanical issues compound driver stress and reduce safe operating margin. Third, 393.9 (Inoperable Required Lamp, 12 co-occurrences) and 395.8A-ELD (Failing to keep records, 7 co-occurrences) suggest systemic compliance gaps: drivers operating unroadworthy or unmonitored equipment are cited more often for fatigue. Root-cause analysis must address: Are vehicles entering service with unresolved defects? Are HOS systems under-monitored? Is driver training on fatigue recognition insufficient?

After a 392.2DL citation or a driver's fatigue report, require: (1) Minimum 10-hour off-duty rest before reassignment, documented in HOS; (2) If illness: a note from a healthcare provider confirming fitness to drive and ruling out contagious disease; (3) If medication: confirmation the drug is DOT-approved and does not impair cognition; (4) Driver self-certification form, signed, confirming full recovery and readiness; (5) A supervised road test (20 miles minimum) with a trainer or safety manager observing reaction time, lane control, and communication clarity. Do not rely on driver assertion alone. Document the checklist completion and sign-off in the driver's file. If the same driver accrues a second fatigue citation within 24 months, escalate to a mandatory fitness-for-duty evaluation by a medical professional. This reduces repeat violations and demonstrates due diligence if a crash occurs.

Within 48 hours of a 392.2DL citation, convene safety and operations: (1) Obtain the inspector's violation narrative and any video; (2) Pull the driver's HOS logs, trip sheet, and medical file for that date; (3) Check vehicle maintenance records—was any repair incomplete or deferrable? (4) Interview the driver: What was the fatigue/illness trigger? Sleep quality issues? Medication? Undiagnosed sleep apnea? (5) Review the load and route assigned—was it realistic for the available hours? (6) Assess prior training: When was fatigue awareness training last delivered? Did the driver miss a session? (7) Determine the citation's impact on CSA safety scores and your organization's Vehicle Maintenance or Unsafe Driving BASIC. Document findings and assign corrective action: retraining, medical evaluation, route reassignment, or equipment repair. Share anonymized findings with your driver population to signal zero tolerance.

FMCSR 392.2DL carries a CSA severity weight of 8 and ranks 692 out of 3,036 FMCSR codes by citation volume. While the all-time volume is 1,100 citations across your 13M-record database—lower than high-frequency codes like 392.2 itself (1.2M citations)—the severity weight of 8 places it in the upper-middle tier for enforcement attention. Each citation contributes directly to your Unsafe Driving BASIC, which directly affects insurance premiums, CSA audit priority, and shipper confidence. Non-OOS citations still count; our records show a 25.6% all-time out-of-service rate for 392.2DL, lower than the all-FMCSR average of 31.4%, meaning most inspectors issue a warning or citation without roadside removal. However, repeated citations or patterns flagged by FMCSA can trigger a focused investigation. Monitor your fleet's Unsafe Driving BASIC percentile quarterly and cross-reference 392.2DL trends.

Mandatory annual training must cover: (1) Sleep physiology—circadian rhythm, sleep debt, and how long it takes to fully recover; (2) Early warning signs: microsleep, lane drift, difficulty focusing, reaction-time lag; (3) Fatigue vs. illness triage: when to pull over, when to call dispatch, when to seek medical care; (4) Medication awareness: OTC cold/allergy drugs, prescription opioids, and stimulants that mask fatigue without improving safety; (5) HOS strategy: how to plan rest stops, use sleeper berths, and communicate delay risks to dispatch; (6) Pre-trip self-assessment role-play using your checklist. Include case studies from your own citations—anonymized—so drivers see local enforcement patterns. Our vehicle-make data shows FRHT (240 citations), INTL (95), and KW (88) are most frequently cited for 392.2DL; if your fleet operates these models, emphasize their longer wheelbase and weight characteristics, which demand sharper alertness. Require annual re-certification with a written test.

File a DataQs challenge if: (1) The citation narrative lacks specific, observable impairment cues (e.g., 'driver looked tired' without noting drooping eyelids, slurred speech, or failed coordination); (2) Your HOS logs directly contradict the inspector's fatigue finding—for example, logs show 10 hours rest and the citation asserts fatigue from insufficient sleep; (3) Medical records show the driver was cleared by a healthcare provider for duty that day, and the citation disregards that documentation; (4) The citation was issued alongside vehicle defects (e.g., 393.9 Inoperable Lamp) that may have triggered an improper stop; (5) The same inspector has issued multiple 392.2DL citations at the same location with generic narratives, suggesting non-objective enforcement. Document all supporting evidence—medical clearance, HOS printouts, vehicle maintenance records, driver training records—before filing. A successful challenge removes the citation from your CSA record.

Audit monthly based on our trend data. The last 90 days logged 90 citations (an average of 30 per month), but monthly volatility is significant: May peaked at 78, while April saw only 22 and November just 26. This variance reflects seasonal demand, weather, and operational intensity. A monthly audit cadence lets you catch emerging patterns—repeated citations from one driver, a spike in a specific route, or a lapse in pre-trip compliance—before they compound into a CSA BASIC violation. Your audit should: (1) Pull all HOS exceptions and fatigue-related dispatch delays; (2) Review any driver complaints of fatigue or illness; (3) Cross-check against medical certification renewal dates; (4) Verify pre-trip checklist sign-offs and completion rates; (5) Audit training attendance and test scores. Quarterly, escalate findings to operations and safety leadership. Annual comprehensive review should include benchmarking your fleet's citation rate against peers and identifying systemic root causes (e.g., route design, equipment reliability, staffing levels).