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

Across our inspection records, 392.2T citations are concentrated in Texas (56 citations in the last 180 days), Iowa (15), and Illinois (8). Inspectors are observing driver behavior and statements that indicate impaired alertness—drowsy eye contact, delayed responses to questions, slurred speech, or inability to follow instructions. In Texas specifically, the high citation volume suggests aggressive roadside observation during safety interrogations. Inspectors also correlate observed behavior with vehicle defects; when they spot mechanical issues alongside behavioral concerns, they're more likely to cite. Document your driver's condition at every stop, and train officers to recognize the difference between normal fatigue from a long day and unsafe impairment that warrants pulling a driver off the road immediately.

Build a driver self-assessment component into your pre-trip process. Have drivers explicitly sign off on: (1) hours slept in the last 24 hours, (2) any medication taken (decongestants, antihistamines, pain relievers), (3) any illness symptoms, and (4) overall fitness to operate. This creates a documented decision point and trains drivers to self-monitor. Pair this with mandatory breaks—your data shows Freightliner units (169 citations) dominate the violation list, suggesting high-mileage fleets are at risk. Institute a policy that any driver reporting fewer than 5 hours of sleep or active illness symptoms is not cleared to depart. Include a line-item check for vehicle lighting and turn signals too, since 393.9 (inoperable lamps) appears in 6 co-occurring inspections with 392.2T—drivers operating tired also miss vehicle defects.

Retain signed pre-trip attestations (driver condition self-assessment) in your safety file for a minimum of 12 months. Record any incident where a driver self-reported fatigue or illness and was stood down; this demonstrates a safety-first culture if challenged. Keep copies of driver communication logs if you have a dispatch system—show that you were not forcing drivers into unsafe conditions. Maintain records of any fatigue-management training completed, including dates and content. If a citation is issued, capture the inspector's narrative and any dashcam footage from that date. Courts and CSA reviewers value contemporaneous, unambiguous records showing the driver made an unsafe decision despite available options to rest or seek medical care—not that the carrier mandated unsafe operation.

Our last 90 days show 392.2T paired most often with 393.9 (inoperable required lamps, 6 shared inspections) and 392.2C (another fatigue variant, 4 shared inspections). The lamp co-occurrence indicates fatigue leading to missed pre-trips and inadequate vehicle inspection—a training gap. The second fatigue code overlap suggests borderline enforcement calls; ensure your drivers and dispatchers understand the distinction and log it. Third, 393.95A (missing fire extinguisher, 4 shared) and 390.21(a) (vehicle marking, 4 shared) point to a broader neglect pattern—tired drivers and under-maintained fleets travel together. Root-cause analysis: audit which drivers are receiving inadequate rest between loads, whether your dispatch system respects HOS limits, and whether vehicle maintenance backlogs are forcing drivers to operate substandard equipment. Fatigue is often the symptom, not the disease.

If a driver was cited for 392.2T, the vehicle itself likely passed the roadside inspection (only 3 out of 528 total citations resulted in OOS status). However, the co-occurrence data shows lamps and brake hoses are frequently defective in the same inspection. Conduct a full pre-service inspection: test all lighting circuits, check brake tubing integrity, verify windshield condition (393.78 co-occurred 3 times). Do not return the vehicle to service until you've confirmed 100% operational status. More importantly, verify the driver's fitness: require a medical exam if illness was cited, or proof of adequate rest if fatigue was the issue. Document the clearance. A citation without OOS status does not mean the underlying condition is resolved—it means the inspector did not deem it immediately unsafe to the public. Your standard should be higher.

Within 48 hours of a 392.2T citation, convene a call with the driver, dispatcher, and safety manager. Review the citation narrative and ask: (1) What was the driver's actual hours-worked and hours-rested in the 72 hours prior? (2) Was the driver medicated, ill, or injured? (3) Did the dispatcher know? (4) Why was the vehicle not pre-tripped sufficiently to catch the co-occurring defects (if any)? (5) What policy or coaching gap allowed this to happen? Then, analyze your dispatch logs for that week—did other drivers run similar lanes under similar fatigue? Treat one citation as a leading indicator of systemic fatigue across your fleet. Implement a corrective action: extra rest-day enforcement, additional fatigue-awareness training, or dispatch system changes. Document the review and action in the driver's file. This demonstrates due diligence if the citation is challenged.

392.2T carries a severity weight of 8 out of 10, making it a significant CSA event despite only 528 all-time citations (ranked #896 out of 3,036 FMCSR codes). It does not generate an out-of-service status (0.6% OOS rate versus 31.4% fleet average), meaning FMCSA views it as a driver behavior violation, not primarily a maintenance failure. However, the co-occurring lamp and brake hose defects—both Vehicle Maintenance—can drag your BASIC score. Focus your CSA mitigation on preventing the co-occurring codes: ensure your fleet's pre-trip and in-service inspections catch lighting and brake issues before an inspector does. If you accumulate multiple 392.2T citations tied to the same driver or vehicle, FMCSA may infer your maintenance program is failing to support driver alertness (e.g., broken air conditioning forcing driver fatigue in summer). Proactively close maintenance backlogs.

Mandatory training modules: (1) Fatigue Recognition, including how drowsiness progresses and when to pull over—make it concrete, not generic. (2) Medication Impact, covering common OTC drugs (decongestants, antihistamines) that impair alertness; tie this to pre-trip disclosure. (3) Illness Decision-Making, teaching drivers to self-report and request dispatch support rather than hide symptoms. (4) Pre-Trip Inspection Discipline, since co-occurring lamp and brake defects indicate rushed or inattentive inspections—Freightliners, Volvos, and Kenworths (169, 72, and 68 citations respectively) need extra scrutiny. Conduct annual refresher training and document attendance. Use real citations from your fleet (anonymized) as case studies. Include a role-play scenario: "Your eyes feel heavy at mile 300 of a 600-mile run. What do you do?" Correct answer: notify dispatch, find a safe rest stop, and rest. Incorrect answer: turn up the radio and push through. Reinforce the correct answer monthly.

DataQs (the FMCSA's public challenge system) is appropriate if: (1) the citation narrative is vague or contradicts your records (e.g., inspector claims driver was drowsy, but your dashcam shows alert behavior and driver had 8+ hours of rest), (2) the driver's HOS log demonstrates compliance and adequate rest, (3) the vehicle was properly maintained and all co-cited defects were pre-trip-inspected that morning, or (4) the inspector's observation was based on a single interaction without corroborating detail. However, do not challenge merely because the citation is burdensome. If your driver was genuinely fatigued or ill, accept it, document your corrective action, and move forward. DataQs is high-effort for fleet safety managers; reserve it for clear factual errors or inspector overreach. Track your challenge outcomes—if you challenge and lose, it signals to FMCSA that your program may not be rigorous.

Our data shows 36 citations in the last 90 days (4 per week average) and 228 in the last 12 months (4.4 per week average). Monthly variation peaked at 37 citations in June and 34 in July (summer heat and peak season fatigue), then stabilized at 12–20 per month. Conduct a quarterly fatigue audit: sample 5–10% of your active driver base, review their HOS logs for pattern violations (late-night hours, minimal rest windows, back-to-back long days), and conduct brief one-on-ones asking how they feel and whether they're resting adequately. Run your self-audit before peak summer months (April–August) when citations spike. If you operate Freightliners, Volvos, or Kenworths (the top three makes cited), prioritize those fleets in your audit. After any 392.2T citation in your fleet, spike your audit cadence to monthly for 90 days on similar routes or driver profiles.