Prevention FAQ — FMCSR 392.2-SLLIT: Operating While Ill or Fatigued

Our inspection records show 1,306 citations for this code in the last 12 months across the U.S., with Georgia leading at 125 citations in the past 180 days. Inspectors are trained to observe behavioral and physical indicators: drooping eyelids, slow responses, erratic lane control, delayed reaction to traffic, slurred speech, or driver admission of illness or fatigue. The citation is issued at the point of inspection, not retroactively, so the inspector documents observable impairment in real time. In high-enforcement states like Georgia, Pennsylvania (89 citations), and California (59 citations), troopers are particularly alert during routine traffic stops and weigh station inspections. There is no out-of-service requirement—all 2,040 all-time citations resulted in the driver continuing to operate—but the CSA severity weight of 8 makes this a compliance priority.

Require drivers to document on their Daily Vehicle Inspection Report (DVIR) two baseline items: (1) a yes/no self-assessment of adequate sleep and alertness before departure, and (2) observable vehicle conditions that might trigger fatigue (e.g., climate control function, seat comfort, lighting adequacy). The checklist should also prompt the driver to report any medication side effects or illness symptoms at the start of shift. Pair this with a carrier policy that explicitly permits drivers to defer a trip if they cannot truthfully confirm alertness. Across our data, 294 citations occurred in the last 90 days; the monthly trend shows peaks in December (137 citations) and March (135 citations), suggesting seasonal fatigue patterns. Winter driving and end-of-quarter pressure may compound alertness risk—your checklist should intensify during these periods.

Drivers must carry proof of a valid medical certificate (DOT card) at all times; the data shows 391.41APC (missing medical certificate) co-occurred with 392.2-SLLIT in 13 shared inspections over 90 days, indicating inspectors view fatigue and medical fitness together. The carrier must retain: (1) the driver's valid medical certification; (2) any fitness-for-duty reports or medical clearances if the driver has disclosed a condition; (3) DVIRs that document the driver's self-assessment before each trip; and (4) HOS records (electronic or paper) to prove compliance with 49 CFR 395 rest requirements. The co-occurrence of 395.24 (HOS ELD violations) in 8 shared inspections suggests that fatigue citations often arise during inspections of drivers with questionable rest records. Retain all documentation for at least 3 years to support a DataQs challenge if needed.

Our data reveals three systemic patterns. First, 28 co-occurrences with 396.17C-PI (no proof of periodic inspection) suggest drivers operating under deferred maintenance schedules—a fatigued driver in a poorly maintained truck is a compounding risk. Second, 13 co-occurrences with 391.41APC (missing/invalid medical certificate) indicate some drivers lack medical oversight; they may not have disclosed sleep apnea, hypertension, or other conditions that impair alertness. Third, 20 co-occurrences with 392.2-SLLSR (another fatigue variant) show fatigue violations cluster—one citation often precedes another in the same driver's record, suggesting repeat offenders or systemic scheduling pressure. Root-cause questions: Are dispatch schedules achievable without mandatory overtime? Do drivers feel safe reporting fatigue? Is your medical certification renewal process robust? Interview any driver with a 392.2-SLLIT citation and map the hour before the citation to HOS and load data.

Do not focus solely on vehicle mechanics—this is a driver condition violation. Instead, require: (1) a fitness-for-duty evaluation if the driver was ill (obtain medical clearance before return); (2) a conversation with dispatch to confirm no unrealistic scheduling contributed to fatigue; (3) a review of the driver's HOS records for the 72 hours prior to the citation to identify rest shortfalls; and (4) mandatory rest (minimum 34 consecutive hours off-duty) before the next dispatch, regardless of the driver's stated readiness. The vehicle itself should pass a standard pre-trip (air brakes, lights, steering, tires, coupling devices) to ensure no mechanical issues compound fatigue risk. Given that Freightliner units lead with 371 all-time citations for this code, ensure older or high-mileage Freightliners receive extra attention to climate control, suspension, and seat condition—physical discomfort accelerates fatigue.

Within 24 hours of a 392.2-SLLIT citation, conduct a three-part review: (1) Driver interview: Ask when the driver last slept, what symptoms were present, whether they reported fatigue to dispatch, and whether they felt pressured to continue. Document verbatim. (2) Operational audit: Pull HOS records, dispatch notes, and load details for the trip. Check whether the driver was within legal limits and whether scheduling was realistic. (3) Peer comparison: Cross-reference the driver's safety record against your fleet average and against industry patterns. Western Express Inc., J B Hunt Transport Services, and Federal Express each show 12–14 all-time citations—if your carrier is smaller and your ratio is higher, fatigue may signal dispatch or culture issues. File the post-review summary in the driver's personnel file and share findings with dispatch and safety leadership. Use this data to inform your next safety meeting.

Although 392.2-SLLIT is categorized as Unsafe Driving, not Vehicle Maintenance, it still carries a CSA severity weight of 8, which is substantial. The FMCSR category average out-of-service rate is 31.4%, but 392.2-SLLIT has a 0.0% rate—inspectors are citing and releasing, not impounding. This means each citation counts against your CSA safety metrics but does not trigger an immediate vehicle removal. Over time, accumulation matters: a carrier with multiple fatigue citations may face elevated audit frequency and heightened scrutiny during roadside inspections. The pattern also suggests that if a fatigue citation co-occurs with vehicle maintenance codes (e.g., 396.17C-PI in 28 shared inspections), the combined impact on your audit risk increases. Monitor your fatigue citation trend monthly; if you see a spike (our data shows variation from 39 citations in April 2025 to 137 in December 2025), implement corrective action immediately to avoid compounding CSA penalties.

Design training around three core topics: (1) Sleep hygiene and circadian rhythm management—fatigue is not just about hours asleep but sleep quality; teach drivers about caffeine timing, light exposure, and avoiding medication side effects. (2) Self-recognition of impairment—drivers must learn to identify their own early warning signs (heavy eyelids, mind drift, lane drift) and take action (pull over, call dispatch, request a break). (3) Communication with dispatch—create a culture where reporting fatigue is safe and rewarded, not punished. Include case studies from your own citations; if Western Express Inc. (14 all-time citations) or J B Hunt Transport Services (12 citations) operate in your market, review their public safety records and highlight what you're doing differently. Annual refresher training is minimum; consider quarterly fatigue awareness topics during safety huddles, especially before winter (peak citation months).

Challenge only if there is clear factual error—e.g., the citation was issued to the wrong driver, the date is incorrect, or the inspector's notes contradict observable facts. Fatigue is subjective; challenging the officer's judgment of impairment is rarely successful unless you have contemporaneous video, medical evidence (e.g., driver was not ill; doctor cleared them), or a documented prior dispute with that officer's citation practices. Retain all DVIRs, HOS records, dispatch notes, and the driver's contemporaneous statement. If the driver claims they were alert and the officer's notes lack specific behavioral observations (e.g., 'swerved lane', 'slow to respond'), you have grounds to file a DataQs request. Most importantly, do not delay filing—FMCSA DataQs windows are time-limited. A successful challenge removes the citation from your CSA record; given the 0.0% out-of-service rate and frequent co-occurrences with other violations, challenging even one citation can lower your audit exposure.

Audit monthly using your last 30 days of DVIR, HOS, and dispatch data. Our inspection records show 294 citations in the last 90 days, averaging approximately 98 per month; monthly audits let you spot clusters. However, deepen your audit cadence in high-risk windows: the data shows peaks in December (137 citations), March (135 citations), and June (126 citations). These months warrant weekly spot-checks of DVIRs and HOS records for fatigue flags (e.g., drivers logging short breaks, high mileage consecutive days, late-night dispatch). Annually, conduct a full-fleet fatigue risk assessment: interview dispatch, review your violation trend against the national rank (392.2-SLLIT ranks #531 of 3,036 codes), and benchmark your citation rate per 1,000 roadside inspections against peers. If your rate exceeds your peer group, implement a targeted scheduling or culture intervention. The 12-month trend shows consistent enforcement (1,306 citations), so fatigue is a permanent audit risk—plan accordingly.