Prevention FAQ — FMCSR 392.2DIB: Operating While Ill or Fatigued

Our inspection records show 67 citations in the last 180 days across NY, PA, and GA alone—the top three enforcement states. Inspectors document observable indicators: driver unable to maintain lane position, delayed reaction to instructions, slurred speech, bloodshot or glazed eyes, unkempt appearance, or explicit driver admission of illness or insufficient sleep. They also note context: extreme HOS violations, sequential citations for the same driver, or vehicle control issues that correlate with impairment. The citation is discretionary and severity-dependent; not every tired driver triggers enforcement, but pattern violations and safety-critical moments (near-miss incidents, traffic stops for unsafe operation) elevate scrutiny. In your roadside interactions, expect inspectors to ask targeted questions about sleep duration, medical conditions, and recent medication use before deciding whether to cite.

Embed these three checkpoints into your mandatory pre-trip protocol:

1. Fitness assessment: Driver self-certifies sleep duration (≥7 hours) and states any active illness, pain, or medication side effects affecting alertness.

2. Medical certificate review: Confirm on-file medical card and note any restrictions or conditions that require tracking (diabetes, sleep apnea, medication regimen). Our data shows 5 co-occurring violations for 391.41APC (missing valid medical certificate), suggesting incomplete compliance tracking.

3. HOS alignment: Cross-reference the dispatch log with RODS to confirm recorded duty hours match planned route and driver statement. Across our records, 5 co-occurring HOS violations (395.8A1-HOSP) indicate that fatigue citations cluster with incomplete or falsified logbooks.

Require drivers to initial or electronically acknowledge all three before vehicle release. Document daily.

Driver carry:

• Valid medical certificate (4x6 card, on file with state DLA)
• Current logbook or ELD records showing 7+ hours off-duty preceding the cited drive
• Any prescription bottles or OTC medication packaging (if relevant to cited incident)

Fleet retain (minimum 3 years):

• Signed pre-trip checklists or ELD attestations
• RODS snapshots confirming HOS compliance for the cited date
• Driver training records (fatigue/alertness modules)
• Any reported illness or medical leave dates
• Dispatch notes and communication logs for the cited trip
• Medical certificate expiration calendar with renewal reminders

Our data shows 60 citations in the last 90 days. Thorough documentation is critical because the citation is subjective; you cannot automatically overturn it, but complete records allow you to challenge it via DataQs if the inspector's narrative contradicts driver HOS compliance or documented illness reporting.

Our inspection records show three dominant co-occurrence patterns:

Pattern 1 – Medical Compliance Gap (8 inspections, 392.2-SLLTCD code pairing): When fatigue is cited alongside periodic inspection lapses, it often signals inadequate medical monitoring. Investigate whether the driver's medical certificate is expired, incomplete, or reflects unmanaged conditions (sleep apnea, uncontrolled diabetes) that impair alertness.

Pattern 2 – HOS/Documentation Breakdown (5 inspections, 395.8A1-HOSP pairing): Fatigue + missing logbook records suggests drivers are not accurately recording rest periods or management is not verifying them. Audit recent RODS submissions for gaps or vague duty-status entries.

Pattern 3 – Medical Certificate Absence (5 inspections, 391.41APC pairing): Co-citation of fatigue with missing valid medical certificates indicates your fleet lacks proactive renewal tracking. Implement automated alerts 90 days before expiry.

For each citation, pull the inspection narrative and compare it against your pre-trip logs and HOS records for that date. If the driver's documented rest contradicts the citation, file a DataQs challenge within 90 days.

Post-citation protocol:

1. Immediate stand-down: Driver cannot resume operation until cleared by management review and, if cited during a shift, a 10-hour off-duty break is confirmed in writing.

2. Medical assessment: If the citation involved illness, require a note from the driver's healthcare provider confirming fitness to operate or identifying restrictions. For medication-related incidents, confirm no sedating side effects.

3. HOS audit: Pull the driver's last 14 days of logbook/ELD records. Verify no pattern of short sleep nights or HOS violations that correlate with the incident. If you see repeated short off-duty periods, investigate scheduling or route planning.

4. Retraining sign-off: Document completion of a fatigue-awareness module (e.g., circadian rhythm, medication impacts, when to refuse dispatch). Driver signs acknowledgment.

5. Vehicle inspection: Confirm no defects (worn tires, brake issues) that might have caused the unsafe operation cited alongside fatigue.

All documents—medical clearance, logbook audit, training completion, vehicle inspection report—go into the driver file.

Within 48 hours of a citation, convene: dispatcher, driver, and safety manager.

Key questions:

1. Dispatch decision: Who approved this trip? Did the system flag the driver's consecutive days, HOS utilization, or medical restrictions?
2. Driver reporting: Did the driver inform dispatch of fatigue or illness before departure? If not, why not? (Fear of economic loss? Unclear policy?)
3. HOS accuracy: Pull RODS. Does the recorded log match reality? Are rest periods documented? Our data shows 5 co-occurring HOS violations, indicating logbook inflation is common in these cases.
4. Medical status: Is the medical certificate current? Any undisclosed conditions or medications affecting alertness?
5. Vehicle condition: Were there maintenance issues (rough idle, poor braking) that compounded fatigue?
6. Training gap: Has the driver completed fatigue-management training? What was the topic and when?

Document findings and corrective actions (retraining, schedule adjustment, medical follow-up, equipment repair). Use this to refine your pre-trip protocol and dispatcher guidance.

Yes. FMCSR 392.2DIB has a CSA Severity Weight of 8—a moderate-to-high score reflecting the safety risk. Nationally, 392.2DIB ranks #986 of 3,036 FMCSR codes by citation volume; while not in the top 50, each citation carries real weight in your Unsafe Driving BASIC category.

Compare the context: across our database, the all-FMCSR average out-of-service rate is 31.4%, but 392.2DIB has a 0.0% OOS rate (409 all-time citations, zero placements). This means inspectors are citing fatigue/illness primarily as a warning or minor violation, not as an immediate emergency. However, for CSA scoring purposes, treat it seriously: a cluster of 3+ 392.2DIB citations within 24 months will elevate your Unsafe Driving percentile and trigger increased scrutiny from FMCSA.

Prioritize prevention and robust documentation. If you receive a citation, initiate the post-event review and retraining outlined above—it demonstrates proactive safety culture if FMCSA audits your file.

Tailor training to three core areas:

1. Circadian Rhythm & Sleep Quality (not just hours): Teach drivers that 7 hours of uninterrupted sleep is the floor. Explain how fragmented sleep, early morning starts, and irregular schedules damage alertness even if total hours seem adequate. Use real-world scenarios (long haul into unfamiliar time zones, split shifts).

2. Medication & Illness Disclosure: Cover common OTC drugs that impair (antihistamines, cold meds, pain relievers) and prescription risks. Clarify your policy: drivers must report illness or new meds to dispatch before accepting a load. Make it clear this is a safety requirement, not a economic penalty.

3. When to Refuse Dispatch: Empower drivers to say "no" if they are too tired, too sick, or on new medication. Explain that FMCSA will not penalize a driver for a safety refusal and that your fleet supports that decision. Reinforce with dispatch: no retaliatory communication.

4. Medical Certificate Importance: Explain that conditions disclosed to the medical examiner (sleep apnea, diabetes) can be managed; surprises on a roadside inspection are expensive and dangerous.

Conduct this training annually and after every 392.2DIB citation.

File a DataQs challenge within 90 days of the citation if your evidence contradicts the inspector's narrative. Strongest grounds:

1. HOS compliance: RODS snapshot or ELD data proving the driver had 7+ hours off-duty immediately before the cited operation. Fatigue citations are subjective; documented rest is objective.

2. Medical clearance: Healthcare provider's note confirming the driver was fit to operate on the cited date (e.g., "Patient was not ill on [date]" or "Medication does not cause drowsiness").

3. No observed impairment: Inspector narrative vague or lacks specific behavior observation (e.g., cites "driver appeared tired" without lane-weaving, slurred speech, or crash/near-miss).

4. Pre-trip documentation: Your signed driver checklist or ELD attestation showing the driver confirmed adequate sleep and no illness at dispatch time.

Weak grounds: "Driver says he was fine" or generalized disputes. You need corroborating records. Our data shows 409 all-time citations; most stand because documentation is absent or vague. Build your case file during your post-citation review (see prior question), then submit via FMCSA's SafetyData portal with all supporting documents.

Audit frequency: Monthly (minimum).

Justification: Our monthly trend shows volatility—82 citations in May–August 2025, then a drop to 1 citation in April 2026. This suggests seasonal or dispatch-driven risk spikes (summer peak season, higher load pressure, new routes). Monthly audits catch emerging patterns before they cluster into a BASIC score spike.

Key metrics to track:

1. Citation rate per 100 drivers: Benchmark your fleet against your own history. One 392.2DIB per 100 drivers per year is manageable; 3+ is a red flag.
2. Co-occurrence patterns: Count how many cited drivers also had HOS violations, expired medical certificates, or maintenance issues in the same inspection. Use this to target training.
3. Seasonal/seasonal variation: Map citations by month, day of week, route, or load type. If fatigue citations spike on dedicated lanes or during harvest season, adjust scheduling or add relief drivers.
4. Driver repeat offenders: Any driver cited twice in 24 months requires immediate retraining or reassignment.
5. Dispatcher decision audit: Randomly review 10 dispatch decisions per month. Were HOS, medical status, and driver fatigue factors checked?

Document findings in a monthly safety report. Share with drivers, management, and medical reviewers to close the loop.