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

Inspectors are trained to observe visible signs of impairment before and during a stop — bloodshot or watery eyes, slurred speech, slow or erratic responses to questions, difficulty producing documents, and observable fatigue cues like yawning or head-nodding. Our inspection records show 392.2-SLL ranked #24 of 3,036 FMCSR codes by citation volume, with 53,873 citations in the last 12 months alone, meaning inspectors encounter it regularly and know the indicators well.

Enforcement is geographically concentrated: California led with 3,609 citations in the last 180 days, followed by Kentucky (3,287) and Pennsylvania (2,601). Fleets operating high-frequency lanes through those corridors should treat those states as elevated-scrutiny zones. Inspectors in high-volume states tend to be more attuned to fatigue indicators precisely because they see the pattern repeatedly. Driver demeanor at the window is the primary trigger — build pre-stop composure into driver training.

Build a self-certification step into every pre-trip, separate from the vehicle inspection. The driver should explicitly affirm:

• Sleep: Minimum 7 hours in the last 24 hours; no sleep disorders (apnea, insomnia) currently unmanaged.
• Illness: No fever, vertigo, nausea, or medication side effects that cause drowsiness or impaired judgment.
• Fatigue signals: No microsleep episodes, lane drift, or difficulty maintaining speed on the most recent segment.
• Cumulative hours: Review actual HOS remaining versus planned run length before departure — not just at break points.

The self-certification should be a signed paper or ELD-integrated acknowledgment retained for 30 days at minimum. A dispatcher who receives a pre-trip wellness declaration has documentation that the driver self-reported fit for duty. If a driver declines to certify, the dispatch protocol must have a clear hold-and-replace procedure. Make this non-punitive — drivers who self-report fatigue should not face schedule penalties, or they will stop self-reporting.

Our co-occurrence data shows 396.17C-PI (No proof of periodic inspection) appeared alongside 392.2-SLL in 1,072 shared inspections in the last 90 days, and 395.8A1-HOSP (failure to have a proper record of duty status) appeared in 507 shared inspections. An inspector who finds missing documentation is far more likely to scrutinize driver condition more deeply.

Drivers must carry:

• Current medical examiner's certificate (391.41APC co-occurred in 420 inspections — missing certs compound the stop significantly)
• Accurate, current ELD records or paper RODS going back 7 days
• Proof of periodic inspection (form required on the vehicle)

Carriers must retain:

• Pre-trip wellness self-certifications (30-day minimum, 90-day recommended)
• Dispatch records showing planned vs. actual departure times
• Driver fatigue incident reports and corrective action logs
• Sleep apnea screening and treatment compliance records for flagged drivers

Clean documentation won't prevent a citation, but it narrows inspector discretion and supports a DataQs challenge if the citation is factually unsupported.

The co-occurrence data from the last 90 days reveals three systemic patterns worth building programs around:

1. HOS compliance breakdown (395.8A1-HOSP — 507 shared inspections): Drivers cited for 392.2-SLL frequently also have incomplete or missing duty status records. Root cause: drivers pushing schedules past legal limits without accurate logging, then showing visible fatigue at a stop. Fix: ELD audit cadence, real-time HOS exception alerts to dispatch, and a hard-stop dispatch rule when a driver's 70-hour cycle drops below a defined threshold.

2. Vehicle maintenance neglect (396.17C-PI — 1,072 shared inspections; 393.75A3-TAOL — 444 shared inspections): Fatigue citations co-occur heavily with overdue periodic inspections and tire defects. Root cause: carriers running deferred maintenance schedules correlate with drivers being pushed through without adequate rest. Fix: tie PMI compliance directly to dispatch authorization — no current inspection sticker, no dispatch.

3. Missing medical documentation (391.41APC — 420 shared inspections): Expired or absent medical certificates suggest a broader driver qualification monitoring gap. Root cause: lack of automated cert-expiration tracking. Fix: calendar-based alerts at 90, 60, and 30 days before cert expiration.

Because 392.2-SLL is not OOS-eligible as a standard matter — our data shows only a 0.2% OOS rate across 84,501 all-time citations, compared to the all-FMCSR average of 31.4% — most drivers will not be placed out of service at the roadside. That means the fleet, not the inspector, bears responsibility for confirming fitness before the next dispatch.

Return-to-service protocol after a 392.2-SLL event should include:

• Minimum 10-hour off-duty break documented in ELD before next dispatch, regardless of remaining HOS availability
• Dispatcher phone check-in at dispatch: driver confirms no illness, adequate sleep, no medication affecting alertness
• For repeat events within 90 days: mandatory referral to occupational health or sleep specialist before return
• Signed return-to-duty wellness certification retained in driver qualification file

Do not treat the low OOS rate as a signal that these events are low-risk — the CSA severity weight of 8 means each citation carries significant SMS scoring impact.

Run a structured 5-part review within 72 hours of the citation:

1. ELD pull: Review the full 8-day HOS record. Identify any false restarts, split-sleeper abuse, or logged driving time inconsistent with the cited location.
2. Dispatch timeline audit: Compare scheduled vs. actual departure, loading delays, and any dispatch-initiated early departures that compressed rest time.
3. Driver interview: Non-punitive conversation focused on what conditions contributed — home sleep quality, dispatch pressure, illness onset.
4. Co-violation review: Check the full inspection report for companion violations. Given that 396.17C-PI appeared with this code in 1,072 inspections in 90 days, a missing periodic inspection on the same report signals a maintenance workflow failure, not just a driver issue.
5. Pattern check: Query your internal records for other drivers on the same lane or operating terminal who have received this code in the last 6 months. A cluster at a specific terminal suggests a scheduling or dispatch culture problem, not individual driver behavior.

Document findings and corrective actions in a safety management system with a 30-day follow-up trigger.

392.2-SLL carries a CSA severity weight of 8, placing it in the upper tier of the scoring scale. It falls within the Unsafe Driving BASIC, which is one of the most scrutinized categories during carrier safety reviews and new entrant evaluations.

The national ranking context matters: at #24 of 3,036 FMCSR codes by citation volume — with 84,501 all-time citations — this code is well-known to FMCSA data analysts. High citation frequency combined with a severity weight of 8 means even a moderate number of events at a mid-size carrier can generate an elevated Unsafe Driving BASIC percentile.

Unlike equipment codes that can be corrected through repair documentation, fatigue and illness citations don't have a mechanical fix to document. The only BASIC score mitigation over time is citation-free inspections, which reduce the time-weighted score as events age out. That means prevention volume matters more than post-event remediation for this code specifically. Increasing the number of clean inspection passes through targeted pre-trip compliance is the primary lever available to safety managers.

The top cited vehicle makes in our database — FRHT (10,411 citations), FREIGHTLIN (9,369), FORD (6,773), KENWORTH (4,423), and PETERBILT (4,245) — span both heavy Class 8 and lighter commercial configurations. The Ford concentration in particular suggests exposure among drivers operating lighter CMVs, who may not have received the same fatigue management training as OTR Class 8 drivers.

Priority training topics:

• Fatigue science basics: Sleep debt, circadian rhythm disruption, and why 6 hours of broken sleep does not equal 6 hours of rest — without drowsiness-shaming
• Self-assessment tools: How to recognize microsleep precursors, and when to pull over versus push through
• Medication awareness: OTC antihistamines, cold medications, and muscle relaxants that impair alertness and their interaction with hours-of-service status
• Inspector interaction: What an inspector observes and how composure, clear speech, and organized documents reduce scrutiny
• Non-punitive reporting: How to declare fatigue to dispatch without fear of route reassignment penalties

For fleets with Ford-heavy vocational or last-mile operations, fatigue training is often absent from onboarding. Close that gap explicitly.

A DataQs challenge is worth pursuing when the inspection record contains a factual error that can be demonstrated with documentary evidence. For 392.2-SLL specifically, viable grounds include:

• ELD contradiction: The driver's electronic log shows a compliant rest period (10+ hours off-duty) immediately preceding the citation, and the inspector's basis for the citation was only subjective (appearance) with no supporting documentation of erratic driving, accident, or admission
• Medical documentation error: The inspection report cites a missing or expired medical certificate, but the carrier has a valid, unexpired certificate on file with the correct issue and expiration dates
• Companion code error: A co-occurring violation (such as 396.17C-PI) that formed part of the inspection context was itself factually incorrect, and correcting it removes the evidentiary basis for the fatigue determination
• Identification error: Wrong USDOT number, vehicle unit, or driver recorded on the inspection report

Do not challenge based solely on disagreement with the inspector's subjective judgment — those challenges have low success rates and consume safety staff time. Build the file before filing: ELD export, driver logs, dispatch records, and medical certificate copies all in one submission package.

Our inspection records show a clear monthly volume pattern worth building an audit calendar around. Citations in the last 12 months ranged from a low of 1,617 in April 2025 (partial month) to a high of 5,264 in September 2025, with consistently elevated counts from July through March — the 5,163 citations in July 2025, 5,136 in October, and 5,073 in March 2026 indicate sustained enforcement pressure across multiple seasons, not a single enforcement surge.

December 2025 stands out: 4,653 citations with 30 OOS placements, the highest OOS count in the 12-month window. That spike coincides with winter weather, holiday scheduling pressure, and driver fatigue from compressed delivery windows — a direct signal to run a focused fatigue audit in late November before the December surge hits.

Recommended cadence:

• Monthly: ELD exception reports reviewed for HOS boundary violations correlated with driver fatigue risk
• Quarterly: Full pre-trip wellness certification compliance audit across the fleet
• Semi-annually: Dispatch scheduling review to identify lanes where run times consistently leave less than a 10-hour buffer before next dispatch
• Pre-December: Mandatory refresher training and wellness check-in for all active drivers by November 30