Prevention FAQ — FMCSR 392.22B: Warning Device Placement

Fleet safety managers: reduce 392.22B citations with pre-trip checklists, inspector focus areas, root-cause analysis from co-occurrence patterns, and audit cadence tied to 62 violations in the last 90 days.

Severity Weight
2
OOS Eligible
No
BASIC Category
Vehicle Maintenance
Code System
FMCSR
Code:
392.22B
Code System:
FMCSR
BASIC Category:
Vehicle Maintenance
OOS Eligible:
No
Severity Weight:
2
Violation Group:
Cab Body Frame

Ranks #675 of 3,146 FMCSR codes by citation frequency • OOS rate of 0.0% is below the FMCSR-wide average of 33.3%.

Violation Description

Failure to place or improper placement of warning devices on the road surface

Prevention FAQ for Fleet Managers

Pre-trip discipline, inspector focus, and root-cause fixes

What exactly do inspectors look for when citing 392.22B?

Inspectors focus on whether warning devices are placed on the road surface at the correct distance and angle when a vehicle is disabled or hazard-stopped. Our inspection records show 111 citations in Texas over the last 180 days—the highest enforcement intensity nationally. Inspectors verify: (1) triangles or flares are deployed on the pavement, not just visible from the cab; (2) placement distance matches the FMCSR standard for road type and visibility; (3) devices are upright and facing traffic; (4) all required devices are present, not just one or two. Pay particular attention if your fleet operates heavily in Texas or Iowa, where we recorded 32 citations in Iowa over the same period.

What should the pre-trip checklist include to prevent this violation?

Build a checklist item: 'Warning devices inspection—verify triangle/flare count, condition, and placement in accessible location (not buried under cargo or tools).' Drivers must confirm: (1) all required triangles are present and not cracked or faded; (2) flare containers are not corroded or leaking; (3) devices are stored where they can be deployed within 60 seconds; (4) the vehicle is not missing the required three-piece set. Have drivers physically remove and re-stow one device monthly to muscle-memory the retrieval process. This prevents the common scenario where devices are carried but inaccessible or forgotten during an emergency stop.

What documentation must drivers carry and carriers retain?

Drivers must carry all required warning devices physically on the vehicle—this is not a 'produce a document' code, but inspection of actual hardware. Carriers should retain: (1) purchase records and delivery dates for warning device kits; (2) photos of correctly-staged devices in the vehicle at the time of purchase; (3) driver sign-offs confirming receipt and correct placement during onboarding; (4) maintenance logs showing quarterly device inventory audits; (5) damage or loss reports when devices are replaced. If a citation occurs, document the exact configuration on the cited vehicle, the inspection date, and the replacement or repair action taken within 48 hours. This trail protects you in any subsequent DataQs challenge.

What root causes does co-occurrence data reveal?

Across 62 citations in the last 90 days, 392.22B was frequently paired with: (1) 396.17C (No proof of periodic inspection) in 23 shared inspections—suggesting vehicles lack regular maintenance audits that would catch missing or damaged devices; (2) 392.2RG (Operating while fatigued) in 22 inspections—fatigued drivers skip or rush the emergency device deployment in stressful situations; (3) 393.95B (Warning devices missing) in 11 inspections—a direct pattern indicating systematic failure to stock or maintain the devices. Root cause analysis should focus on: Is your fleet skipping preventive maintenance? Are drivers fatigued during long shifts? Is there no inventory control for consumable safety items?

How should damaged or missing devices be repaired before the vehicle returns to service?

Do not place a vehicle back in service until all warning devices are present and functional. Repair steps: (1) physically verify count (usually three triangles or equivalent flares); (2) inspect each device for visible cracks, fading, or corrosion that would reduce visibility; (3) test flare functionality if applicable; (4) confirm placement in the designated, accessible storage area; (5) have a supervisor or safety manager sign off on the completed repair. If devices were missing due to loss or theft, document the incident and file a new device kit immediately. Drivers should not improvise with homemade or non-compliant alternatives. The repair must be complete before the next road dispatch.

What should a post-citation review process look like?

Within 48 hours of a 392.22B citation, conduct a focused review: (1) verify the cited vehicle's device configuration—ensure it matches the violation description; (2) inspect the driver's training record and last three pre-trip reports; (3) audit 10 similar vehicles in the same fleet for the same issue; (4) review the driver's shift length and fatigue indicators if 392.2RG was also cited; (5) check maintenance records for the past 90 days to confirm periodic inspections occurred; (6) hold a brief toolbox talk with all drivers on emergency device deployment and placement. Document corrective actions taken. This review directly addresses the patterns we see in co-occurring codes and prevents repeat citations in the same driver or vehicle pool.

How does 392.22B affect my carrier's safety rating?

Our inspection database shows 1,241 all-time citations for 392.22B, ranking it #664 of 3,036 FMCSR codes by citation volume. While not an out-of-service violation (0.0% OOS rate in our records), repeated or clustered citations in a short timeframe can signal poor vehicle maintenance oversight to regulators and customers. The code falls in the Unsafe Driving category; accumulation may impact CSA scoring under the Vehicle Maintenance BASIC if citations trend upward month-over-month. Monitor your trend—over the last 12 months we recorded 383 citations nationally, with peak months (July 2025, September 2025) reaching 54 and 43 citations respectively. A spike in your fleet suggests a systemic training or inventory issue requiring immediate attention.

What training topics should drivers receive to prevent this violation?

Deliver hands-on training covering: (1) correct device placement distance (per FMCSR standard for highway vs. street vs. country road); (2) how to deploy devices from your vehicle's storage location in under 60 seconds, even at night or in bad weather; (3) when deployment is required (disabled vehicle, emergency stop, accident); (4) visual inspection—checking for cracks, fading, or corrosion that renders devices non-compliant; (5) accountability—each driver confirms device count at vehicle assignment. Use training videos showing correct and incorrect placements. Have drivers practice deployment quarterly. Focus on the vehicles your fleet operates most: across all-time citations, Freightliner (195 citations), Utility trailers (134 citations), and Wabash National (102 citations) dominate. If your fleet runs these makes, briefing frequency should match the exposure.

When should I consider filing a DataQs challenge?

File a DataQs challenge if: (1) the citation narrative describes device placement that your documentation and driver log contradict—for example, if the driver signed off on device presence and correct placement at the start of shift, but the inspector claimed devices were missing; (2) the vehicle's maintenance record shows a recent device inventory audit completed within 48 hours before citation, contradicting the violation; (3) photographic evidence from your pre-trip checklist app timestamps the correct configuration on the citation date. Do not challenge on the grounds that 'the driver forgot to deploy them'—that is a valid violation. The challenge is strongest when you have physical proof of presence and correct placement at the relevant time.

How often should the fleet self-audit for this issue?

Conduct a self-audit every 30 days. Justification: across the last 90 days, we recorded 62 citations (average 20.7 per month), with July 2025 spiking to 54 citations. This suggests seasonal or operational patterns that a monthly cadence will catch before an inspector does. Each audit should: (1) physically verify device presence and condition on 20% of active vehicles (randomly selected); (2) review 100% of driver pre-trip reports for device sign-offs; (3) check for any loss or replacement incidents reported by drivers; (4) assess storage accessibility on each vehicle. Document all findings. If the audit reveals missing or damaged devices on any vehicle, remove that vehicle from service immediately and repair before dispatch. This proactive approach directly counters the co-occurrence patterns—particularly the link to missed maintenance audits (396.17C)—and reduces citation risk.

Last updated: 2026-04-20T14:07:06.834Z Guidance derived from TruckCodex inspection data Read the full article → Quick Q&A →

Top Enforcing States

Where 392.22B is most commonly cited (last 180 days)

1. Texas
54
OOS 0.0%
2. Iowa
13
OOS 0.0%
3. Illinois
8
OOS 0.0%

Often Cited Together

Other violations commonly found on the same inspection (last 90 days)

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.

Refreshed daily.

Vehicle recall campaigns, defect investigations, and consumer safety complaints (SCRS).

Refreshed daily.
EIA

Retail diesel and gasoline price history and state fuel-tax tables.

Refreshed weekly.

Cross-border carrier registry and Canadian recall campaigns where applicable.

Refreshed weekly.

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.