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

Across our 13 million inspection records, 392.2P enforcement is relatively rare—only 151 citations in the last 12 months—but when inspectors cite it, they are documenting observable impairment: weaving, slow reaction time, difficulty following instructions, or clear physical signs of illness. Our data shows Texas, Iowa, and Illinois account for 61 of the 66 citations in the last 180 days, suggesting inspectors in high-traffic corridors are more likely to pull vehicles when driver alertness is visibly compromised. The 0.4% out-of-service rate (versus the FMCSR average of 31.4%) indicates that when cited, the driver is typically not immediately removed from service—but the citation still carries an 8-point CSA severity weight. Focus your driver training on recognizing personal fatigue or illness before it becomes roadside-observable.

Build a driver self-assessment section into your pre-trip checklist. Drivers must document: sleep quality and hours in the past 24 hours, any cold/flu symptoms, medication use (especially sedating drugs), and subjective alertness on a 1–5 scale. Pair this with a supervisor or dispatcher spot-check—at minimum weekly for high-mileage fleets. Our data shows 32 citations in the last 90 days; the spike to 20 in May 2025 and 19 in June suggests seasonal stress (summer loading season) correlates with fatigue citations. Implement a mandatory "go/no-go" rule: if a driver scores below 3 on alertness or reports fewer than 6 hours sleep, that driver does not depart until rest is restored. Document all self-assessments for 12 months to establish a baseline and identify repeat risk patterns.

Drivers must carry any medical documentation related to current illness or treatment (doctor's note, prescription label) if they are medicated. Carriers must retain: (1) driver's electronic logbook records showing sleep/rest compliance; (2) any driver-reported fatigue or illness incidents in the past 24 months; (3) medical fitness certifications (Commercial Driver's License medical exam); and (4) records of any coaching, retraining, or fitness-for-duty evaluations. If a 392.2P citation occurs, preserve the roadside inspection report, driver's statement, and any dash-cam or safety footage. This documentation protects against unfounded DataQs challenges and helps your safety team root-cause the event. Retention window: minimum 3 years for active drivers, 1 year after driver termination.

Our 90-day data shows 392.2P most frequently paired with 392.2RG (3 shared inspections), another fatigue variant, suggesting some inspectors are applying multiple fatigue-related codes to the same event—not a root-cause issue but a citation categorization difference. More actionable: 2 co-occurrences with 392.2-SLLS2 (speeding 6–10 mph over limit) and 2 with English language proficiency issues (391.11B2-Z). The speed pairing hints at driver overconfidence or rushing to make up lost time due to rest deficit. The language barrier correlation suggests non-English-speaking drivers may not understand fatigue-management guidance in company materials. Root-cause actions: (1) audit your fatigue-management training materials for readability at the 6th-grade level; (2) provide translations in languages spoken by your driver pool; (3) enforce no-speed-run policies and tie run planning to realistic rest windows, not compressed schedules.

Do not return the cited driver to active duty until: (1) the driver has completed 8 uninterrupted hours of sleep and been observed by a supervisor or wellness coordinator as alert and coherent; (2) if illness was the cause, obtain a medical clearance (doctor's note or telehealth visit) confirming the driver is fit to operate; (3) require the driver to complete a 30-minute refresher on fatigue recognition and HOS rules; and (4) have the driver re-certify their understanding via a written acknowledgment signed and filed. For the vehicle itself, a 392.2P citation is about driver state, not equipment—no repairs needed. However, if the citation co-occurred with vehicle defects (our 90-day data shows 1 instance each of tire damage and inoperable headlamps paired with 392.2P), correct those before return to service. Document all clearance steps in the driver's file.

Within 48 hours of a 392.2P citation, convene a safety review with the driver, dispatcher, and safety manager. Ask: (1) How many hours of sleep did the driver have in the 24 hours before the stop? (2) Was the run scheduled realistically, or was the driver rushing? (3) Was illness reported to dispatch beforehand? (4) Did the driver take any medications? (5) Were there personal stressors (family emergency, financial stress)? Document answers in an incident report. Then audit: Did the driver's logbook show compliant hours-of-service? Was the dispatch plan aligned with the 10-hour rule? Did the driver use the company fatigue self-check tool? If the answer to any is "no," that's a process gap your program must close. Track all 392.2P reviews in a quarterly aggregate report to identify fleet-wide patterns (e.g., a specific lane or dispatch center that consistently creates fatigue risk).

392.2P is an Unsafe Driving violation with an 8-point CSA severity weight, not a Vehicle Maintenance violation, so it does not directly impact the Vehicle Maintenance BASIC. However, it does affect your Unsafe Driving BASIC and your overall Safety event score. At 151 citations in the last 12 months across all carriers nationally, 392.2P ranks #1141 of 3,036 FMCSR codes—a low-frequency violation overall. This means a single citation will be noticed in your CSA profile; if your fleet accrues 3+ in a 12-month period, it signals a systemic fatigue-management failure to FMCSA. Prioritize reducing repeat occurrences through the documented prevention steps (rest verification, logbook audits, training) rather than attempting a DataQs challenge, which succeeds only if the roadside observation was factually incorrect.

Core training must cover: (1) Fatigue recognition: how to identify early signs (yawning, difficulty focusing, lane drifting) before they become roadside-observable; (2) Sleep physiology: why 6 hours is insufficient; circadian rhythm impacts on night driving; (3) Logbook planning: working backward from delivery time to ensure adequate rest, not shortcutting hours-of-service; (4) Medication awareness: which over-the-counter cold/allergy drugs impair alertness and when to notify dispatch; (5) Dispatch communication: drivers must feel safe reporting fatigue or illness without fear of run cancellation or pay loss. Deliver training in multiple formats (classroom, e-learning, video, one-on-one coaching). Our vehicle-make data shows Freightliners dominate your cited fleet (76 all-time citations), followed by Peterbilt (37); ensure training references these cab ergonomics and fatigue risks specific to long-haul comfort. Refresh annually; require signature acknowledgment.

Challenge a 392.2P citation only if the factual roadside observations are provably false. Examples: (1) the driver's logbook and supporting documentation (fuel receipts, geolocation data) prove the driver had 10+ hours of rest immediately before the stop; (2) dash-cam or witness testimony shows the driver was driving normally, not weaving or drifting; (3) the driver has a medical condition (e.g., medication side effect, diagnosed sleep disorder being managed) that explains the observed behavior—and medical records predate the citation. DataQs challenges succeed rarely for fatigue citations because inspector observations (weaving, slow response, physical signs) are subjective but difficult to disprove after the fact. Our data shows only 1 out-of-service placement in 257 all-time citations (0.4% OOS rate), meaning inspectors rarely cite 392.2P unless confident. Invest in prevention and process documentation instead. Use the citation as a catalyst for internal safety review, not a target for appeal.

Audit monthly—not because 392.2P is high-volume (only 32 citations in the last 90 days nationally), but because fatigue and illness are persistent risks. Our 12-month trend shows citations ranged from 1 to 20 per month, with peaks in May (20) and June (19), suggesting seasonal or operational pressure points. Your monthly audit should sample: (1) HOS compliance: 20% random check of logbook entries for the previous month, flagging any compressed rest periods or consecutive long days; (2) fatigue self-check completion: 100% of drivers must complete pre-trip alertness assessment; missing entries trigger coaching; (3) dispatch-run alignment: verify that run lengths match realistic rest windows at each terminal; (4) driver incident reports: any driver-reported fatigue or illness within the month. Escalate if any driver is flagged twice in a rolling 12-month period. Quarterly, roll monthly metrics into a fleet-wide trend report and brief dispatch leadership on systemic gaps (e.g., chronic understaffing forcing drivers to rush routes, or seasonal work surges).