Prevention FAQ — FMCSR 392.2-HOS: Illness & Fatigue
Fleet safety guidance on 392.2-HOS citations, inspector focus areas, root-cause patterns from 13M+ inspections, and audit cadence based on real enforcement data.
- Code:
- 392.2-HOS
- Code System:
- FMCSR
- BASIC Category:
- Hours of Service
- OOS Eligible:
- No
- Severity Weight:
- 7
- Violation Group:
- Hours
Ranks #1,052 of 3,146 FMCSR codes by citation frequency • OOS rate of 0.6% is below the FMCSR-wide average of 33.3%.
Violation Description
HOS (Local Law) - State/local hour of service violation.
Prevention FAQ for Fleet Managers
Pre-trip discipline, inspector focus, and root-cause fixes
› What exactly do roadside inspectors look for when citing 392.2-HOS?
Across our inspection records, 392.2-HOS citations remain relatively rare—156 in the last 12 months nationally—but they cluster in specific states. Wisconsin, Arizona, and Georgia each logged 8–9 citations in the last 180 days, suggesting those jurisdictions have trained officers to spot and document observable signs of driver impairment: drooping eyes, delayed reactions, slurred speech, inability to perform standard roadside tests, or driver admission of illness or insufficient sleep. Inspectors document the specific observable behavior, not subjective judgment. The 0.6% out-of-service rate (versus 31.4% all-FMCSR average) indicates most citations result from warning-level observations rather than immediate safety removal. Your drivers in high-citation states need explicit training on how fatigue manifests and when self-reporting is safer than pushing through a shift.
› What should be on our pre-trip driver checklist to prevent 392.2-HOS citations?
Build a fatigue-specific pre-trip gate before engine start:
- Sleep attestation: Driver signs off on minimum 8 hours of sleep in the past 24 hours (or last 34-hour restart).
- Illness screen: Driver confirms no fever, vomiting, severe congestion, or medication side effects that impair alertness.
- Meal and hydration check: Driver has eaten and consumed water within the past 2 hours.
- Caffeine/stimulant log (optional): Driver notes any energy drink or medication taken and expected duration.
- Route hazard scan: Driver reviews road conditions and estimated drive time; if exceeding safe limits, dispatch assigns split or rest day.
Make the checklist digital (in your telematics or ELD system) so dispatch sees real-time compliance. Drivers who check "no" on sleep or illness should not be routed. This prevents the root issue before it reaches an inspector's eyes.
› What medical documentation should drivers carry and fleets retain?
Our data shows 392.2-HOS citations frequently co-occur with 391.41APC (missing valid medical certificate), appearing in 3 shared inspections over the last 90 days. This pattern suggests inspectors may cite both simultaneously if a driver appears fatigued and lacks current DOT medical certification—creating compounding liability.
Driver carry requirement:
- Valid FMCSA Form 649-F or state-issued medical certificate (physical copy or digital copy per FMCSA eSignature rule).
- Prescription list if taking medications that affect alertness (antihistamines, benzodiazepines, opioids).
Fleet retain (on file for at least 3 years):
- Copy of driver's medical certification and all renewals.
- Any medical disqualifying conditions self-disclosed during hiring or annual review.
- Physician documentation if driver returns to duty after illness (fever, surgery, etc.).
Review medical files quarterly; flag renewals 60 days before expiry.
› What root-cause patterns are hidden in the co-occurring violation codes?
Our last 90 days of inspection data reveal three co-occurrence signals:
-
392.2-HOS + 395.8A1-HOSP (3 shared inspections): Drivers operating fatigued often lack proper record-of-duty-status documentation. Root cause: no ELD or paper log discipline, masking actual hours driven and rest gaps. Drivers don't see their own fatigue because dispatch doesn't track it.
-
392.2-HOS + 391.41APC (3 shared inspections): Fatigue + missing medical card. Root cause: outdated medical certification or driver unaware of renewal deadline; medical disqualifications (sleep apnea, uncontrolled diabetes) go undetected and untreated, worsening fatigue.
-
392.2-HOS + 396.17C-PI (3 shared inspections): Fatigue + no proof of vehicle inspection. Root cause: trucks in poor maintenance state (rough ride, brake drag, engine noise) amplify driver fatigue. A poorly maintained cab adds stress and reduces sleep quality.
Target prevention at the systems, not just the driver.
› How should we verify a vehicle is fit before it returns to service after fatigue-related breakdown?
A 392.2-HOS citation often signals not just driver fatigue but vehicle or dispatch system failure. Before returning a truck to service:
-
Mechanical audit: Inspect brakes, suspension, steering, seat comfort, and cabin climate control. Poor HVAC, broken seat, or brake lag forces drivers to work harder and tire faster. Review 396.17C-PI (periodic inspection proof) to confirm current maintenance status.
-
Telematics and ELD review: Pull 2 weeks of data prior to the citation. Check: excessive idling, harsh accelerations/braking, and hours-of-service gaps. Did dispatch route a 16-hour drive with no break? Did the ELD record sleep?
-
Dispatch logic check: Verify the load assignment, pick/drop times, and planned rest stops are realistic for the route distance. If a driver can't physically rest between legs, the system is broken, not the driver.
-
Driver interview: Ask the driver what made them unsafe—sleep deprivation, medication, vehicle noise/vibration, unclear dispatch expectations. Use their feedback to retrain dispatch or mechanics.
Return to service only after fixes are confirmed and driver confirms the vehicle feels ready.
› What should our post-citation review process look like?
Within 48 hours of a 392.2-HOS citation, run this review:
Immediate (driver & supervisor):
- Pull the driver's ELD/RODS for 7 days prior. Confirm actual hours driven, sleeper berth use, and any off-duty gaps.
- Interview the driver: Were they sick? Did they sleep? Was dispatch aware of their condition? Did they self-report or did the officer initiate?
- Check medical file: Is their DOT physical current? Any known sleep disorders or medications?
Systemic (fleet safety & dispatch):
- Review the trip assignment: distance, time window, previous load, and rest day. Could dispatch have assigned differently?
- Audit recent ELD data for that driver (4 weeks): Are there patterns of short sleeps, rushed turnarounds, or cycle violations?
- Check vehicle maintenance log: Was the truck's condition adding to driver workload?
Corrective action:
- If driver issue: retraining on fatigue recognition + mandatory 34-hour restart before next assignment.
- If dispatch issue: revise trip planning to include realistic rest windows.
- If vehicle issue: repair documented, driver confirms satisfaction before return to service.
Document findings and actions in your safety management file for CSA audit defense.
› Does 392.2-HOS impact our CSA Vehicle Maintenance BASIC score?
392.2-HOS itself is classified as an Unsafe Driving violation (CSA SEVERITY WEIGHT: 8), not a Vehicle Maintenance violation. However, the co-occurrence pattern matters. Our data shows 392.2-HOS frequently paired with 396.17C-PI (no proof of periodic inspection) and other maintenance gaps, suggesting poorly maintained vehicles amplify driver fatigue.
While a single 392.2-HOS citation does not directly penalize your Vehicle Maintenance BASIC, it signals to auditors that your fleet may lack rigorous pre-trip and preventive maintenance discipline. The citation's severity weight (8 on a scale where higher = worse) and its relative rarity (ranked #1040 of 3,036 FMCSR codes) mean inspectors and auditors take it seriously—it's a red flag, not routine.
Build preventive maintenance and pre-trip documentation into your fatigue prevention program. Link vehicle condition to driver fitness. A well-maintained truck that is inspected and logged reduces variables that compound fatigue.
› What training topics should we add to close the gap for drivers?
Freightliner vehicles account for 61 of all-time 392.2-HOS citations, followed by Ford (24), Kenworth (23), and Peterbilt (22). This distribution reflects the market; it does not indicate a specific truck model problem. Instead, it reveals that drivers piloting large Class 8 long-haul rigs (where Freightliner dominates) are the primary population cited.
Tailor driver training to this segment:
- Fatigue recognition module: Teach drivers the early signs—eye strain, lane drift, repeated yawning, difficulty focusing—before a roadside stop.
- Personal sleep strategy: Different drivers need different sleep. Offer guidance on optimal sleep duration, napping technique (20–90 min windows), and sleep environment (earplugs, blackout curtains in sleeper berth).
- Medication awareness: Review over-the-counter cold/allergy meds, prescription side effects, and why full disclosure to dispatch matters.
- Dispatch communication: Train drivers to tell dispatch if they feel unsafe and how to request a rest day or reduced-mile assignment without penalty.
- ELD/RODS discipline: Show drivers how to log accurately so their rest and fatigue patterns are visible to dispatch and help future trip planning.
Role-play fatigue scenarios in training; do not rely on safety videos alone.
› When should we file a DataQs challenge if we believe a 392.2-HOS citation is inaccurate?
A DataQs challenge is appropriate if:
- No observable impairment documented: The citation states the driver appeared fatigued but provides no detail—no eye drop, speech pattern, test result, or driver admission recorded. Vague citations are challengeable.
- Medical explanation in file: Driver has a sleep disorder diagnosis, medication allergy, or recent surgery documented pre-citation. The appearance attributed to fatigue was a known condition, not unsafe operation.
- ELD/RODS contradiction: The driver's ELD data shows 8+ hours of rest and normal hours-of-service, contradicting the officer's fatigue determination. Request the ELD print from dispatch at the time of stop.
- Procedural error: The officer did not administer standard roadside sobriety/alertness tests or did not document the driver's responses.
Do not challenge if the officer documented specific, observable signs (e.g., "driver's eyes closing at red light," "driver admitted 3 hours of sleep in 24 hours," "driver failed HGN test"). Those are defensible observations.
File within 90 days of citation. Include driver statement, ELD export, medical documentation, and the officer's citation report. FMCSA reviews DataQs challenges; favorable outcomes improve your safety record.
› How often should we self-audit for 392.2-HOS risk in our fleet?
Our 12-month trend shows 156 citations last year, averaging 13 per month. The last 90 days averaged 8.67 per month (26 total), indicating stable but consistent enforcement. Monthly range spans 7–18 citations, with no seasonal spike.
Audit cadence recommendation: quarterly (every 90 days).
Why quarterly? A 90-day window matches the enforcement visibility in our data. It is frequent enough to catch fatigue patterns (driver sleep logs, dispatch trip assignments, vehicle maintenance gaps) before they escalate to a citation, but not so frequent that it burdens your safety team.
Each quarterly audit should include:
- Random ELD/RODS sample (10–15 active drivers): Verify 8+ hours rest, no cycle violations, realistic trip windows.
- Vehicle inspection checklist: Confirm all trucks in your fleet pass 396.17C-PI (proof of periodic inspection) and have no brake, suspension, or HVAC defects.
- Dispatch job assignment review: Audit 20–30 recent trips for realistic distance-to-rest ratios.
- Driver self-report: Anonymous survey asking drivers if they ever felt unsafe due to fatigue or vehicle condition.
Document findings and corrective actions. Use the quarterly results to update training and dispatch policy annually. This cadence aligns with your ELD data retention and CSA audit cycles.
Top Enforcing States
Where 392.2-HOS is most commonly cited (last 180 days)
Often Cited Together
Other violations commonly found on the same inspection (last 90 days)
Related Records
Data sources & freshness
TruckCodex aggregates official public-sector datasets. See the Source registry for dataset-level coverage and the Freshness log for last-import timestamps.
Census, SAFER, SMS, Licensing & Insurance (L&I), roadside inspections, crashes, and authority history.
Vehicle recall campaigns, defect investigations, and consumer safety complaints (SCRS).
Cross-border carrier registry and Canadian recall campaigns where applicable.
TruckCodex is an independent aggregator; it is not affiliated with FMCSA, NHTSA, EIA, or Transport Canada. Always verify compliance-critical information directly with the originating agency.