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

Inspectors cite 392.2IRP when a driver's ability or alertness appears impaired to the point of making continued operation unsafe — not just when a driver reports feeling tired. In practice, inspectors are watching for slurred speech, bloodshot or glassy eyes, slow reaction to questions, inability to locate documents, erratic lane positioning observed before the stop, or an admission of illness. Our inspection records show 2,837 citations in the last 12 months alone, with NC generating 419 citations in just the last 180 days — the highest of any state — suggesting aggressive enforcement at fixed and mobile inspection sites along high-volume freight corridors. TX (212) and IA (198) follow closely. Train drivers never to volunteer fatigue to an inspector and to report genuine impairment to dispatch before reaching a checkpoint so the fleet can arrange a swap rather than a citation.

Add a self-certification block to your pre-trip form with the following driver-completed fields:

• Sleep logged: At least 8 consecutive hours in the last 24 hours (yes/no)
• Illness declaration: Any fever, dizziness, medication with sedating effects, or GI symptoms (yes/no — if yes, contact dispatch before departure)
• Hours since last reset: Calculated and entered by the driver
• Medication check: OTC and prescription drugs reviewed against FMCSA-prohibited or caution-flagged medication list
• Dispatcher acknowledgment timestamp: Dispatch confirms driver status before releasing the load

This creates a contemporaneous record that the carrier exercised due diligence. A driver who signs this form and then receives a 392.2IRP citation gives the fleet a defensible paper trail. Make the form digital if possible so the timestamp is system-generated and tamper-evident.

Drivers should carry or have electronic access to:

1. Current ELD log or paper RODS — 395.8A-ELD (failing to keep RODS) appeared in 35 shared inspections in our last-90-days co-occurrence data, meaning carriers that lack clean HOS records face a compounding documentation problem during the same inspection.
2. Signed pre-trip self-certification (see checklist item above).
3. Any DOT medical examiner certificate relevant to a disclosed condition.

Carriers must retain:

• Dispatch release records with timestamps
• Pre-trip forms for at least 12 months
• Any internal fitness-for-duty communications (text, app, or email) involving that driver on the day of the citation

These records become critical if you file a DataQs challenge or if the citation escalates to an investigation.

Our database's last-90-days co-occurrence data reveals three systemic patterns:

1. CDL/credential failures (392.2FT: 150 shared inspections; 383.23A2: 146 shared inspections): When fatigue-coded violations and CDL violations cluster together, it suggests drivers who are operating outside their authorized scope — potentially misassigned routes, owner-operators with lapsed credentials, or borrowed equipment — and who may also be running harder schedules without HOS protection.

2. Inspection documentation gaps (396.17C: 104 shared inspections): No proof of periodic inspection appearing alongside 392.2IRP points to carriers where compliance culture is broadly weak — the driver condition problem is not isolated, it's part of a systemic oversight failure.

3. Equipment deficiencies (393.9 inoperable lamps: 75; 393.95A missing fire extinguisher: 67): When equipment violations pair with driver condition violations, inspectors are typically responding to a vehicle that drew attention before the driver interaction. Fix the equipment, reduce the inspection trigger.

392.2IRP is OOS-eligible, and while our database shows the all-time OOS rate is only 0.2% (14 of 6,173 citations resulted in OOS), the standard for return to service when an OOS is issued is that the driver must be rested or medically cleared before resuming operation. Build this into your post-citation protocol regardless of whether the driver was actually placed OOS:

1. Mandatory rest hold: No dispatch release for at least 8 hours after any 392.2IRP citation, OOS or not.
2. Supervisor call: Direct conversation with the driver to understand whether illness or fatigue was the trigger.
3. Medical clearance: If illness was cited, require a clinic visit and written clearance before the next dispatch.
4. ELD audit: Pull the driver's HOS logs for the prior 72 hours and confirm there was no pre-existing pattern of abbreviated rest periods.

Run a five-part review within 72 hours of receiving the inspection report:

1. Driver interview: Was fatigue, illness, or medication the actual cause? Document the answer.
2. 72-hour HOS reconstruction: Pull ELD data and confirm actual rest periods against the log. Flag any discrepancy.
3. Dispatch record audit: Did dispatch have any indication of impairment before releasing the load? Review all communications.
4. Co-citation sweep: 392.2IRP frequently co-occurs with 396.17C (104 shared inspections in 90 days) and equipment codes. Inspect the cited vehicle for all co-occurring deficiencies before it returns to service.
5. Root cause classification: Categorize as driver behavior, scheduling pressure, medical, or documentation failure — each requires a different corrective action. Log the classification in your SMS/CSA tracking system so trend patterns are visible across your fleet.

392.2IRP carries a CSA severity weight of 8 out of 10, placing it among the highest-impact codes in the Unsafe Driving BASIC. Our inspection records rank it #304 out of 3,036 FMCSR codes by citation volume, with 6,173 all-time citations — this is not a rare or niche enforcement action. The severity weight of 8 means each citation multiplied by time-weight factors contributes significantly to Unsafe Driving BASIC percentile. Peer codes in the same category such as 392.2 (1,208,164 citations) and 392.2-SLLSR (191,232 citations) dominate citation volume across the Unsafe Driving BASIC, so carriers in high-enforcement states like NC and TX are operating in environments where inspectors are actively applying the full family of 392.2 codes. A cluster of 392.2IRP citations — even without OOS actions — can push a carrier's Unsafe Driving percentile above intervention thresholds. Prevention is far cheaper than a Compliance Review triggered by BASIC deterioration.

Our database shows Freightliner (FRHT) accounts for 1,526 of all-time 392.2IRP citations — more than double the next closest make (Peterbilt/PTRB at 641, Kenworth/KW at 567). This likely reflects fleet composition as much as anything else, but it means your FRHT operators should be the first cohort through any fatigue-management training rollout.

Core training topics:

• Fatigue physiology: Sleep debt, circadian rhythm disruption, and why drivers underestimate impairment
• Medication awareness: Common OTC medications (antihistamines, cough suppressants) that impair alertness
• Self-reporting culture: Create a no-fault reporting pathway so drivers call in before departure rather than push through
• HOS as a floor, not a ceiling: ELD compliance does not equal fitness for duty — train drivers to understand the difference
• Inspector interaction: What not to say, how to respond professionally, and when to contact dispatch from the inspection site

Challenge when the documented facts do not support the citation. Grounds include:

• No observable impairment: Inspector notes are absent or generic and the driver's pre-trip self-certification and ELD logs show adequate rest with no anomalies.
• Misidentification: The citation was written against the wrong USDOT number or vehicle.
• Co-citation inaccuracy: One of the co-occurring violations (e.g., 396.17C, 393.9) was contested successfully, and removing it materially changes the context of the 392.2IRP charge.

Do not challenge citations where the driver acknowledged fatigue or illness to the inspector — that admission is in the inspection narrative and will defeat the challenge. The 0.2% OOS rate on this code means the vast majority of citations (6,159 of 6,173 all-time) did not result in OOS, which suggests inspectors are applying a relatively low threshold. That same low threshold is often the strongest argument in a DataQs submission: document what threshold the inspector used versus what the regulation actually requires.

Our inspection records show a clear seasonal spike: citations peaked at 358 in June 2026 and 344 in May 2026, then declined through fall and winter before rising again to 227 in March 2026. The last 90 days produced 491 citations, which annualizes above the 12-month total of 2,837 — suggesting enforcement is accelerating into spring and summer.

Recommended audit cadence:

• Monthly: Pull your fleet's 392.2-family citations from your CSA dashboard and trend against the prior month. Cross-reference against dispatch scheduling data to identify routes or drivers with repeated exposure.
• Quarterly deep dive: Review all pre-trip self-certification records, ELD logs for drivers with any fatigue-adjacent citation, and dispatcher release practices.
• Pre-summer surge prep (April–May): Given the May–June citation peaks in our database, run a targeted driver refresher and auditor spot-check of your highest-mileage FRHT and PTRB operators before the heavy enforcement window opens each year.