Prevention FAQ — FMCSR 392.2DIM: Fatigue & Illness

Across our inspection records, 392.2DIM citations concentrate heavily in Iowa (247 in the last 180 days), Illinois (66), and North Carolina (40). Inspectors are observing driver behavior at scale—swerving, lane departures, delayed responses at weigh stations, or explicit driver admission of illness or fatigue during roadside interaction. Iowa's enforcement intensity suggests state-level focus on this violation. The 0.8% out-of-service rate (vs. the all-FMCSR average of 31.4%) indicates most citations are warnings or minor infractions, not immediate removal. However, inspectors are still writing citations regularly: 178 in the last 90 days nationally. Your pre-trip and during-trip observation protocols should train supervisors to catch early warning signs before they reach a roadside scale.

Build a dedicated fatigue-readiness section into your pre-trip form:

• Driver sleep log attestation: Driver confirms ≥6 hours of uninterrupted sleep in past 24 hours before signing off.
• Medication check: Driver discloses any new or changed medications affecting alertness.
• Physical condition: Driver self-reports fever, pain, dizziness, or other acute illness.
• Caffeine/stimulant use: Document baseline vs. overreliance (multiple energy drinks signal fatigue masking).
• Dispatch timing: Prevent back-to-back runs; build in minimum 6-hour reset windows.
• Environmental factors: Note extreme heat, cold, or recent time-zone changes that compound fatigue.

Make this section mandatory and timestamped. A paper or digital signature commits the driver to truthfulness. Supervisors should spot-check 10% of logs monthly to reinforce accountability.

Drivers should carry a personal logbook or mobile app record showing:

• HOS compliance (FMCSA rules)
• Sleep time, location, and quality (self-reported, dated)
• Any illness episodes or medication taken during the trip
• Pre-trip fatigue attestations

Fleets must retain centrally:

• Pre-trip checklists (digital or scanned) with driver signature and date
• HOS records synchronized with dispatch data
• Any incident reports or near-miss reports mentioning fatigue or illness
• Training records showing when fatigue-prevention modules were completed
• Medical certifications (FMCSA-compliant)

If cited, this paper trail demonstrates due diligence and helps defend against elevated CSA scores. Keep records for ≥3 years. Digital archiving (cloud with audit trail) is preferable to paper.

Our 90-day data shows 392.2DIM paired most often with:

1. Other fatigue codes (392.2RG, 392.2-SLLEWA1/2/3): 29, 23, 26, 22, 16 shared inspections. This pattern indicates systemic scheduling or dispatch pressure—when fatigue is cited, it often appears alongside related violations on the same inspection, suggesting the driver was running consecutive or overlapping shifts without proper rest.

2. 396.17C (No proof of periodic inspection): 18 shared inspections. Fatigued drivers are skipping or deferring vehicle maintenance checks. This creates a cascade: tired driver → missed pre-trips → maintenance defects → more citations.

3. 395.24C2III (Failed to add shipping document number) and 393.9 (Inoperable lamp): 16, 15 shared inspections. Administrative slip and equipment oversights correlate with mental fatigue. Drivers too tired to notice burned-out lamps or document details properly.

Target root-cause analysis: audit dispatch schedules for excessive back-to-back runs, strengthen pre-trip enforcement, and implement fatigue-risk assessment training.

A 392.2DIM citation is not a mechanical defect—it's a fitness-to-operate citation. Your remediation workflow:

1. Driver medical review: If the citation mentions illness, require a fitness-for-duty medical exam (may be simple checklist signed by the driver's primary care provider).
2. HOS audit: Pull the driver's HOS records for 14 days prior to citation. Identify scheduling violations or missed mandatory breaks.
3. Supervised return to service: Before the driver's next long haul, require a supervisor ride-along for 2–4 hours to observe behavior and compliance with rest intervals.
4. Refresh training: Complete a fatigue-recognition and HOS-compliance module within 5 business days.
5. Dispatch reassignment (temporary): If possible, assign shorter runs for 30 days to reduce fatigue stressors.
6. Document all steps with dates and signatures. This record protects you if the driver is cited again and shows escalating intervention.

Do not return the driver to service until training is complete and dispatch confirms the next run is ≤8 hours.

Within 48 hours of a 392.2DIM citation, convene a brief root-cause session with:

• Driver: Why were you fatigued/ill? Was there dispatch pressure? Personal issues (sick family, poor sleep at home)?
• Dispatcher: What was the run length, preceding run duration, and time between loads?
• Safety manager: Review HOS data, pre-trip checklist compliance, and any previous fatigue warnings.

Document findings:

• Was the citation justified (honest fatigue/illness) or possibly a false positive (driver was alert, inspector made an assumption)?
• Was dispatch a contributing factor?
• Did pre-trip checklists flag anything (medication, sleep deprivation)?

Action items:

• Retrain driver on fatigue self-assessment (no shame, just safety).
• Adjust dispatch routing if applicable.
• Flag any patterns (same driver, time of week, route type) for trend analysis.

Escalation: If the driver has 2+ fatigue citations in 12 months, move to a 30-day fitness-for-duty probation with mandatory 8-hour-max runs and supervisor check-ins.

392.2DIM carries a CSA severity weight of 8—moderate impact. Nationally, it ranks #536 of 3,036 FMCSR codes by citation volume (2,019 all-time), so it is not among the highest-frequency violations, but it is active and monitored.

Directly, 392.2DIM does not belong to the Vehicle Maintenance BASIC. However, the co-occurrence pattern is important: 18 of our 178 recent 392.2DIM citations appeared alongside 396.17C (No proof of periodic inspection), and 15 appeared with 393.9 (Inoperable lamp). This suggests fatigued drivers neglect vehicle checks, indirectly driving up your Vehicle Maintenance BASIC score over time.

Fleet implication: A single 392.2DIM citation contributes directly to your Unsafe Driving BASIC. Multiple citations (you received 826 in the last 12 months nationally) will elevate that BASIC noticeably. Monitor your fleet's 392.2DIM trend; if you exceed your peer average, proactive fatigue training and dispatch redesign are high-ROI investments in CSA improvement.

Design a focused driver training module covering:

1. Recognizing early fatigue signs: Yawning, lane drift, delayed reactions, eye strain. Teach drivers to pull over and rest rather than push through.
2. Sleep hygiene on the road: Sleeping in trucks, minimizing noise/light, maintaining sleep schedules across time zones.
3. Medication and supplement awareness: Over-the-counter cold medicine, energy drinks, and their effects on alertness. When to disclose to dispatch.
4. HOS rules and mandatory breaks: Make it clear: 30-minute break in first 8 hours is mandatory, not optional. Violations protect no one.
5. Illness reporting protocol: If you're sick (fever, pain, dizziness), call dispatch before departure. Do not hide it.
6. Dispatch communication: Empower drivers to tell dispatch "I am fatigued, I need a 1-hour rest" without penalty or retaliation.

Deliver this annually and mandate a refresher after any fatigue-related incident. Our data shows 178 citations in 90 days—a small percentage of your fleet, but each is preventable with early awareness.

Consider a DataQs challenge if:

1. The citation is inconsistent with observed driver behavior. You have video (dashcam), HOS logs, and pre-trip checklists all showing the driver was alert and compliant, but the inspector noted fatigue without specific behavioral cues (swerving, slow response).
2. Medical evidence contradicts the citation. The driver had a valid reason (recent medication causing drowsiness) that was disclosed and documented, yet was still cited.
3. The citation lacks specificity. The narrative does not detail what fatigue signs the inspector observed (lane drift, slow weigh-station response, slurred speech). Generic "driver appeared fatigued" without evidence is weak.
4. Environmental factors affected driver perception. The inspection occurred during extreme heat, at a confusing weigh station, or at an unusual time that the driver can explain.

Success rate is low, so challenge only when you have strong documentary evidence. A dashcam video showing alert driving or a physician's note is much stronger than "the driver says they were fine." DataQs challenges take 30–60 days; prioritize only when the citation will materially harm your CSA score or carrier rating.

Self-audit monthly based on trends in our inspection data:

• Last 90 days: 178 citations nationally, averaging ~59 per month.
• Last 12 months: 826 citations, averaging ~69 per month.
• March 2026: 98 citations (highest recent month); April 2026 dropped to 1 (data cutoff).

This volatility suggests seasonal or dispatch-cycle patterns. Your fleet should audit on a 30-day rolling basis to catch upswings early.

Monthly audit checklist:

1. Count internal 392.2DIM citations or warnings (yours, not just FMCSA data).
2. Map them to drivers, routes, and time of month (end-of-month rush? seasonal freight?).
3. Cross-reference HOS logs: were any drivers approaching maximum hours?
4. Review dispatch patterns: any consecutive long runs or short turn-arounds?
5. Sample 5–10 pre-trip checklists: are fatigue attestations genuine or rote?

If you see 2+ citations in a month or a trend emerging, escalate to dispatch management and run a focused training burst. The volatility in our national data suggests small operational changes (one extra 2-hour rest window per route, or one fewer run per week) can shift outcomes significantly.