Prevention FAQ — FMCSR 392.2RG: Driver Fatigue & Illness

Inspectors cite 392.2RG when observable signs suggest a driver's ability to safely operate is compromised by fatigue, illness, or a similar cause — not merely self-reported tiredness. Our inspection records show Texas alone generated 21,497 citations in the last 180 days, meaning Texas inspectors are actively screening for this at scale. Watch for these common triggers:

• Red eyes, slurred speech, or slow reaction during the inspection interaction
• Hours-of-service logs that reveal minimal off-duty time before the current duty period
• Admission during questioning that the driver feels unwell or hasn't slept adequately
• Erratic driving behavior observed by the inspector prior to the stop (weaving, inappropriate speed)
• Medication packaging visible in the cab that could cause drowsiness

Illinois stands out with a 1.9% out-of-service rate on this code versus the 0.1% national average for 392.2RG, suggesting Illinois inspectors apply a higher evidentiary bar before writing the citation but are more willing to place drivers OOS when they do. Train drivers to know that the inspection conversation itself is evidence.

The pre-trip check for this code is about the driver's condition, not the vehicle's. Build a two-minute structured driver self-assessment into your dispatch release process:

1. Sleep confirmation: Driver affirms at least 8 consecutive off-duty hours in the prior 10 hours. Dispatcher verifies against the ELD.
2. Illness screening: Driver confirms no fever, active infection, severe congestion, or vomiting in the prior 24 hours.
3. Medication review: Driver discloses any new prescription or OTC medication taken within 12 hours; dispatcher cross-references your approved medication list.
4. Fatigue self-rating: Use a simple 1–5 fatigue scale (e.g., Karolinska Sleepiness Scale). Any driver rating themselves 4 or 5 does not roll.
5. Dispatcher sign-off: The dispatcher logs the confirmation with a timestamp in your TMS or a paper release form before the driver departs.

This process creates a contemporaneous record showing the carrier exercised duty of care — critical if a citation is later challenged via DataQs.

392.2RG is not OOS-eligible in most cases — our database shows a 0.1% OOS rate across 96,652 all-time citations — but the citation still scores an 8 on CSA severity weight, making documentation your primary defense tool.

Drivers should carry:

• Current ELD printout or log showing compliant off-duty hours
• Any medical waiver or exemption documentation
• Dispatcher release confirmation (printed or accessible on a fleet app)

Carriers must retain:

• Driver qualification files, including the most recent medical examiner's certificate
• Dispatch release logs with timestamps for the cited trip
• ELD data for the 8 days preceding the citation
• Any fatigue-screening records from the day of dispatch

Retain all of these for a minimum of 12 months, longer if a DataQs challenge or litigation is anticipated. Gaps in any of these records make it materially harder to contest the citation at the SMS level.

Across our inspection records, three co-occurring codes dominate the last 90 days and point to specific systemic failures:

393.9 — Inoperable Required Lamp (3,034 shared inspections): When a fatigued-driver citation pairs this frequently with burned-out lights, it signals vehicles are leaving terminals without adequate pre-trip inspections. Drivers too tired to do a proper pre-trip are also too tired to drive.

396.17C — No Proof of Periodic Inspection (2,730 shared inspections): This pairing suggests a carrier-level maintenance culture problem. Fleets that let PMI documentation lapse are likely also lax on driver wellness standards.

393.78 — Defective Windshield Condition (1,663 shared inspections): A cracked or obstructed windshield rarely appears overnight. Its pairing with 392.2RG suggests drivers are operating vehicles they know are defective — a behavior pattern consistent with pressure to roll despite unsafe conditions, which is also the same pressure that produces fatigued driving.

The actionable takeaway: 392.2RG is rarely an isolated driver behavior issue. It frequently accompanies deferred maintenance and skipped inspections, which are carrier-level failures.

Because 392.2RG addresses driver condition rather than a repairable vehicle defect, 'return to service' means clearing the driver, not closing a repair order.

Immediate steps:

1. Pull the driver's ELD data and confirm they obtain a full compliant rest period before any next dispatch.
2. If illness was cited or suspected, require a signed physician clearance — or at minimum a 48-hour symptom-free hold — before the driver re-dispatches.
3. If medication was a contributing factor, route the driver through your medical review officer or a DOT-qualified medical examiner for a fitness determination.

Documentation before re-dispatch:

• Log the rest period achieved post-citation with ELD timestamps
• Have the driver complete a return-to-duty fatigue self-assessment (same checklist as pre-trip)
• Safety manager countersigns the return-to-service record

Do not rely solely on the driver's self-report. Pair it with ELD data. Keep the return-to-service record in the driver's file alongside the citation documentation.

Run a structured post-event review within 48 hours of the citation, while details are fresh. Cover these five areas:

1. Timeline reconstruction: Pull ELD data for the 72 hours preceding the citation. Map on-duty, driving, and off-duty periods. Identify where the fatigue likely originated.
2. Dispatch pressure audit: Review the load assignment and communication logs. Was the driver dispatched on a tight turnaround? Did they request more rest and get overridden?
3. Co-occurring violation debrief: Cross-reference the inspection report for additional violations. Our data shows 393.9, 396.17C, and 393.78 are the top companions — if any appear, expand the review to the pre-trip process and maintenance records.
4. Driver interview: Conducted without punitive framing. The goal is to surface systemic barriers (dispatch pressure, home terminal culture, sleep disorder) not to assign blame.
5. Corrective action log: Document what process change, training assignment, or equipment fix results from the review. This log is your evidence of good faith during an SMS investigation.

File the completed review in the driver's safety file, not their personnel file.

392.2RG sits in the Unsafe Driving BASIC with a CSA severity weight of 8 — among the higher weights in the category. That score is multiplied by a time weight (citations in the last 6 months carry the highest multiplier) and accumulates against your Unsafe Driving BASIC percentile.

Our inspection records rank this code #17 out of 3,036 FMCSR codes by citation volume, with 59,296 citations in the last 12 months alone. That volume means FMCSA has substantial data against which your fleet's rate is benchmarked. Even a handful of citations can move a smaller fleet's percentile significantly.

For context within the peer group: the parent code 392.2 has accumulated 1,208,164 citations across our database. 392.2RG's 96,652 all-time citations represent a meaningful sub-segment. The combined weight of multiple 392.2-family citations on a single carrier is the fastest path to an elevated Unsafe Driving BASIC and potential intervention. Prioritize keeping this code at zero.

Our inspection records show Freightliner (FRHT) leads all vehicle makes with 25,167 all-time 392.2RG citations, followed by Kenworth (KW) at 13,297 and Peterbilt (PTRB) at 13,136. These three makes dominate long-haul and regional truckload operations, pointing toward over-the-road drivers on extended multi-day runs as the highest-risk population — not local or pickup-and-delivery drivers.

Training priorities for this audience:

• Sleep science fundamentals: Time-zone crossing, circadian disruption, and split-sleep failures specific to OTR operations
• Fatigue recognition: Teaching drivers to self-identify impairment before an inspector does
• Medication safety: A practical guide to OTC and prescription drugs that cause drowsiness, with your approved/prohibited list
• Illness reporting without fear: Build a non-punitive call-in process so drivers don't feel pressure to drive sick
• HOS strategy: How to bank off-duty time on multi-day runs, not just meet the minimum

Deliver this training annually and track completion in your LMS. Carriers with repeat citations in our data — including SELECT DEDICATED SOLUTIONS LLC with 266 all-time citations — illustrate the cost of not embedding this into ongoing driver education.

A DataQs challenge is appropriate when the inspection record contains a verifiable factual error, not simply because you disagree with the inspector's judgment. For 392.2RG specifically, viable challenge grounds include:

• ELD data contradicts the fatigue allegation: The driver had 10+ compliant off-duty hours and the log is uncorrupted — document this with a data extract.
• Citation attributed to wrong driver or vehicle: USDOT number, vehicle ID, or driver CDL number is incorrect on the inspection report.
• Inspection report lacks supporting observations: The narrative contains no specific behavioral indicators; the citation appears written without evidentiary basis.
• Timing inconsistency: The inspection timestamp conflicts with ELD GPS data placing the driver in a rest period.

Do not file a DataQs challenge simply because the driver denies feeling fatigued — that is a credibility dispute the process is not designed to resolve. With 59,296 citations in the last 12 months, enforcement of this code is active and inspectors are trained on documentation. Challenges without hard data backing rarely succeed and consume safety department resources that are better spent on prevention.

Our inspection records show 12,303 citations in the last 90 days against 59,296 in the last 12 months — meaning roughly 20.7% of the annual volume occurred in just the most recent quarter. Monthly data shows the code runs consistently hot: every full month from May 2025 through March 2026 produced between 4,473 and 5,821 citations nationally, with no seasonal lull.

This flat, high-volume pattern means there is no safe off-season. Recommended audit cadence:

• Weekly: Dispatcher spot-check of ELD off-duty data for drivers on multi-day runs. Flag any driver with less than 8 compliant off-duty hours before their next dispatch.
• Monthly: Pull your fleet's 392.2-family violations from your carrier portal. Review any driver with more than one fatigue-adjacent citation in a rolling 60-day window.
• Quarterly: Full pre-trip process audit — shadow a dispatcher for one shift, review the last 90 days of driver release logs, and verify medication disclosure records are current.
• Annually: Comprehensive driver fatigue training completion audit and policy review.

Given Texas's 21,497 citations in 180 days, fleets with significant Texas lane exposure should treat the weekly check as non-negotiable.