Prevention FAQ — FMCSR 392.2-SLML: Fatigue & Illness

Our inspection records show 1,559 all-time citations for 392.2-SLML across 13 million inspections. Inspectors focus on observable driver impairment: slurred speech, inability to maintain alertness during the inspection, bloodshot or glazed eyes, poor coordination, and delayed responses to questions. They also note environmental clues—driver asleep in cab, evidence of medication bottles in the cab, or statements by the driver acknowledging sickness or exhaustion. The violation is ranked #589 nationally by citation volume, making it a secondary enforcement issue rather than a priority stop. However, when officers do cite it, they're responding to clear, visible signs of impairment that create immediate safety risk. Document any pre-trip observations of driver condition and remedial actions taken.

Build a driver self-assessment component into your pre-trip that covers: (1) hours of sleep in the last 24 hours (target minimum 6); (2) any medication taken and whether it causes drowsiness; (3) current symptoms (fever, cough, dizziness, nausea); (4) use of any over-the-counter cold/allergy medication; (5) recent illness or injury affecting alertness. Drivers must sign off that they are fit to operate. This creates both a safety gate and a liability shield. Because 0 out of 1,559 citations resulted in out-of-service orders—despite the violation's CSA severity weight of 8—prevention at the driver-decision level is your only control. Make the checklist digital if possible; timestamp and geotag it. When a driver marks "no" on any fitness question, require manager approval before dispatch.

Drivers must carry any prescription medications in original labeled bottles, showing the driver's name, medication name, dosage, and any warnings about drowsiness or impairment. Over-the-counter medications should be documented in the logbook or on a medication disclosure form (dated and signed by driver). Fleets should retain: (1) signed driver fitness declarations for each shift; (2) any medical restrictions or limitations issued by the driver's physician; (3) records of any fatigue-related incident discussions; (4) driver training completion records on fatigue recognition. Because this code is never placed out of service (0% OOS rate vs. 31.4% FMCSR average), the citation itself is the enforcement outcome—documentation prevents the citation by establishing a culture of fitness verification and creating evidence of due diligence if a crash occurs.

Across our 13 million inspection records, 392.2-SLML citations cluster with violations indicating inadequate driver management: long runs without mandatory rest breaks, failure to enforce hours-of-service compliance, and insufficient trip planning. The violation's peer codes show 392.2 (the parent code) has 1,208,164 citations with a 0.8% OOS rate, suggesting that fatigue citations are widespread but rarely severe enough to ground vehicles. This indicates a culture issue—drivers are dispatched fatigued because scheduling and load planning don't enforce real rest windows. Audit your dispatch system: Are drivers given 10-hour breaks between shifts? Are loads scheduled with buffer time, or are drivers racing the clock? Are drivers sleeping in hot cabs without facilities? These systemic failures create fatigue. Implement mandatory rest protocols, geofence dispatch rules to prevent back-to-back runs, and provide access to rest facilities or motel costs.

If a driver is pulled off duty for illness or extreme fatigue, require a fitness-to-duty assessment before re-dispatch. For minor illness (cold, mild flu), the driver must be symptom-free for 24 hours and sign a re-entry fitness form. For medication changes or ongoing illness, require a note from a healthcare provider stating the driver is safe to operate and any medication will not impair alertness. Document the date, time, and assessor. Verify logbook compliance for the 24 hours before re-entry—ensure the driver actually took adequate rest, not just logged it. Because 0 out of 1,559 citations placed drivers out of service, your fleet liability is high if a fatigued driver causes a crash. Treat fitness-to-duty as seriously as a DOT medical certificate renewal.

Immediately after a citation, conduct a four-step review: (1) Pull the driver's logbook, dispatch notes, and pre-citation fitness forms. Did the pre-trip assessment miss warning signs? (2) Interview the driver and inspector (if possible through FMCSA records) about specific symptoms observed. (3) Audit the trip that led to the citation: Was the driver's route and schedule realistic? Were load assignments excessive? (4) Check the driver's prior 30 days of logs for patterns—insufficient rest, back-to-back runs, or medication changes. Document findings and corrective action (retraining, schedule adjustment, medical referral). Because our records show 0 citations placed out of service despite a CSA weight of 8, the citation alone is your enforcement tool. Use it to identify whether this was an individual driver slip or a systematic scheduling failure affecting multiple drivers.

No. This code (392.2-SLML) is an unsafe-driving violation, not a vehicle-maintenance issue. However, it carries a CSA severity weight of 8, making it a significant contributor to your Unsafe Driving BASIC. Our inspection records show 1,559 all-time citations for this code ranked #589 nationally—a moderate enforcement priority. Citations do not generate out-of-service orders (0% OOS rate), so they don't trigger immediate compliance reviews. However, repeated citations will degrade your Unsafe Driving BASIC percentile and trigger carrier safety audits. If you receive multiple 392.2-SLML citations in a 24-month window, FMCSA may investigate your scheduling practices, fatigue management, and medical screening. Prevent the pattern, not just individual citations.

Mandate annual training covering: (1) recognizing early signs of fatigue (microsleeps, lane drift, difficulty focusing); (2) sleep physiology—why 6–8 hours matters more than log compliance; (3) medication effects—which common OTC drugs impair alertness and for how long; (4) caffeine and stimulant risks (brief wakefulness followed by crash); (5) illness protocols—when to call dispatch and what constitutes "unsafe to operate"; (6) circadian rhythm and shift scheduling—why mid-afternoon and 2–4 a.m. are highest-risk windows. Use real-world scenarios from your fleet. Our inspection data shows 1,559 citations over the entire enforcement history, suggesting this violation is often a one-time individual lapse rather than systemic. Emphasize driver empowerment: drivers have the legal right and responsibility to refuse dispatch if unfit, and the fleet will support that decision.

Challenge if: (1) the citation was issued without clear observational evidence (e.g., inspector noted "appeared drowsy" but no specific behavioral description); (2) the driver has contemporaneous evidence of fitness—signed pre-trip forms, logbook showing adequate rest, or medical clearance; (3) the driver was stopped for a different reason and fatigue was alleged post-hoc without direct observation; (4) the inspector's written report contradicts the violation narrative. Because this violation relies entirely on subjective observation rather than objective equipment failure, documentation of driver fitness at the time of stop is your strongest defense. Gather the driver's logbook for 72 hours prior, pre-trip fitness declaration, and any dash-cam footage. Challenge promptly (within 30 days) if evidence supports it. However, if the driver's log shows insufficient rest or the driver admits to fatigue, don't challenge—use it as a coaching event and system fix.

Our inspection records show 0 citations for 392.2-SLML in the last 12 months and 0 in the last 90 days, despite 1,559 all-time citations. This suggests enforcement is sporadic and reactive to visible incidents, not proactive sweeps. Conduct quarterly self-audits: (1) pull a random sample of 50 logbooks and verify adequate rest windows (10-hour minimums between shifts); (2) audit dispatch schedules for the same 50 drivers to identify back-to-back runs or unrealistic deadlines; (3) review driver fitness forms from the last 90 days—are drivers consistently checking "fit" or are some flagging warnings? (4) survey drivers anonymously about whether they feel pressured to drive fatigued. Because the code carries a CSA weight of 8 and sits at #589 nationally, it's not your top risk. But a cluster of citations would signal scheduling or culture problems. Annual deeper audit (full sample, all drivers) is sufficient for most fleets; escalate to quarterly if you have any recent citations.