Prevention FAQ — FMCSR 392.22(a): Emergency Warning Devices

Fleet safety manager guide to preventing 392.22(a) citations: checklists, documentation, CSA impact, root causes, and audit cadence based on real inspection data.

Severity Weight
1
OOS Eligible
No
BASIC Category
Unsafe Driving
Code System
FMCSR
Code:
392.22(a)
Code System:
FMCSR
BASIC Category:
Unsafe Driving
OOS Eligible:
No
Severity Weight:
1
Violation Group:
Other Driver Violations

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

Violation Description

Failing to use hazard warning flashers

Prevention FAQ for Fleet Managers

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

What do inspectors actually look for when they write a 392.22(a) citation?

Inspectors are checking whether a CMV stopped on a roadway or shoulder has its required warning devices — typically triangles — properly deployed at the required distances, and whether those devices are physically present and usable on the vehicle. The citation is written when either the devices are missing entirely or they exist but weren't displayed when the vehicle was stopped outside a protected area.

Our inspection records show 5,302 all-time citations for this code, with Freightliner (FRHT) vehicles accounting for 907 of them and Utility trailers (UTIL) for another 521 — so inspectors are clearly encountering this across the most common tractor-trailer combinations on the road. Inspectors verify the kit is present during any roadside inspection, not just breakdown scenarios, because possession is part of the requirement. A broken or incomplete triangle set triggers the citation just as a missing one does.

What specific items should appear on our pre-trip checklist to prevent this citation?

Add a dedicated emergency warning device section to your pre-trip checklist with these discrete checkpoints:

  1. Kit present — Confirm the triangle reflector kit (minimum three pieces) is aboard and accessible, not buried under cargo.
  2. Condition check — Inspect each triangle for cracks, missing reflective material, or broken fold-out legs. A damaged triangle fails the deployment test.
  3. Secure storage — Verify the kit is in its holder or bracket, not loose in the cab where it can shift or be overlooked.
  4. Flares/fusees (if carried) — Check expiration dates if the fleet uses fusees as a supplement.
  5. Driver acknowledgment — The checklist entry should require an initials sign-off, not just a box check.

Given that FRHT platforms alone account for 907 of the 5,302 all-time citations in our database, ensure Freightliner-specific storage locations are called out by cab model in your checklist template so drivers know exactly where to look.

What documentation should drivers carry and what should carriers retain to defend against this citation?

Drivers should carry: No separate permit or certificate is required for warning devices, but drivers should retain their completed pre-trip inspection report showing the emergency kit was verified that day. A dated DVIR with the warning device line signed off is your first line of defense.

Carriers should retain:

  • DVIRs for at least 90 days (per 396.11), with the emergency device check clearly documented.
  • Records of any triangle kit replacements or issuances to a specific vehicle, tied to VIN and date.
  • Training records showing the driver was instructed on deployment procedures.

Because 392.22(a) carries a CSA severity weight of 4 and our records show 5,302 citations with a 0.0% out-of-service rate, a well-documented pre-trip DVIR is often sufficient to support a DataQs challenge if the citation was written despite a properly stocked and serviceable kit.

What root causes drive 392.22(a) citations, and what do the co-occurring violation patterns tell us?

Our database doesn't list co-occurring codes for 392.22(a), but the peer codes in the same Vehicle Maintenance category reveal systemic patterns worth addressing in your root-cause analysis:

  • 393.9(a) — Inoperable required lamps (660,737 citations, 15.4% OOS rate): The most-cited peer code suggests fleets that miss lighting inspections also miss emergency equipment checks — both are pre-trip items that get skipped when inspection culture is weak.
  • 396.3(a)(1) — Inspection/repair/maintenance general (236,919 citations, 45.3% OOS rate): A 45.3% OOS rate on this peer code signals that fleets generating maintenance violations broadly are also generating 392.22(a) hits — the root cause is insufficient preventive maintenance discipline, not isolated oversights.
  • 396.17C-PI / 396.17(c) — No proof of periodic inspection (212,081 and 198,331 citations respectively): Vehicles without current annual inspection stickers are frequently also missing or carrying degraded emergency kits, pointing to a documentation and accountability gap at the fleet level.

The corrective action: treat warning device checks as part of your PM cycle, not just driver responsibility.

How should we verify a vehicle is compliant before returning it to service after a 392.22(a) citation?

Follow a three-step return-to-service verification:

  1. Physical confirmation — A shop supervisor or safety staff member (not the cited driver) physically opens the triangle kit, inspects all three reflectors for reflective surface integrity and fold-out functionality, and confirms they re-stow correctly in the case. Document the inspection with a photo attached to the citation record.
  2. DVIR annotation — The corrective action entry on the DVIR should specify kit replaced or kit confirmed serviceable with the verifier's name and date — not just "repaired."
  3. Inventory update — Log the kit serial number or purchase date in your vehicle file so you have a replacement history. Triangle kits degrade from UV exposure and cab heat; a no-cost kit check at each PM interval prevents recurrence.

Because the OOS rate for this code is 0.0% across all 5,302 citations in our records, vehicles are not being pulled from service at the roadside — but the CSA severity weight of 4 means the citation still scores against your BASIC, so verification before next dispatch matters.

What post-event review process should we run internally after a driver receives this citation?

Run a structured five-point review within 48 hours of the citation:

  1. Pull the DVIR — Was the warning device line checked that day? If yes, the kit may have been stolen, lost, or was defective and passed incorrectly. If no, the inspection process failed.
  2. Interview the driver — Was the kit present at dispatch? Was it used and not re-stowed? Was it stored correctly per vehicle-specific placement?
  3. Check the vehicle — Inspect the specific vehicle for kit condition and storage location adequacy.
  4. Review the carrier record — Our database shows carriers like NEW PRIME INC accumulating 53 citations for this code all-time. If your fleet is seeing repeat citations across multiple drivers, it's a systemic equipment or training issue, not a driver-behavior issue.
  5. Document findings — Record the root cause, corrective action, and whether a DataQs challenge is warranted. Retain this with the citation in your CSA file for at least 3 years.
How does a 392.22(a) citation affect our CSA Vehicle Maintenance BASIC score?

This code sits in the Vehicle Maintenance BASIC (Group BASIC 5) and carries a CSA severity weight of 4. That places it in the mid-tier of severity — below codes weighted 7–10 but still enough to move your percentile if citations accumulate.

At national rank #328 out of 3,036 FMCSR codes by all-time citation volume, 392.22(a) is not a fringe code — it's cited often enough that fleets with high-mileage operations see it regularly. With 5,302 all-time citations in our database and a 0.0% OOS rate compared to the all-FMCSR average OOS rate of 31.4%, inspectors are writing this as a citation-only violation rather than a shutdown event — but every severity-4 hit within the rolling 24-month BASIC window counts. For fleets near the intervention threshold, even a small cluster of these citations can push the Vehicle Maintenance BASIC into alert territory.

What training topics should our driver orientation and refresher programs cover to close the gap on this violation?

Focus training on three areas, grounded in what the citation data shows:

1. Vehicle-specific storage locations. Our records show 907 citations on FRHT platforms, 521 on UTIL trailers, 361 on VOLV, and 310 on WANC. Drivers who transition between equipment types often don't know where the triangle kit is stored on each specific cab model. Build a visual guide — photos of storage locations by make — into orientation materials.

2. Kit serviceability standards. Drivers need to know what a failed triangle looks like: cracked base, delaminated reflective surface, broken hinge. A triangle that was serviceable six months ago may not pass today.

3. Deployment scenarios and decision-making. Many citations occur because the driver moved the vehicle before setting up devices, or didn't set them up at all during a short stop. Training should include realistic scenario walk-throughs covering when and how deployment is required, not just that it's required.

Under what circumstances should we file a DataQs challenge for a 392.22(a) citation?

File a DataQs challenge when you have documented evidence that directly contradicts the inspector's finding. Strong grounds include:

  • Signed DVIR from that day showing the warning device kit was checked and confirmed serviceable at pre-trip.
  • Photo evidence (dashcam, driver-submitted) showing devices were deployed correctly at the stop in question.
  • Kit issuance record showing the vehicle was equipped with a serviceable kit before dispatch and the same kit is intact post-inspection.

Avoid filing challenges on the basis of driver statement alone without corroborating documentation. Given the 0.0% OOS rate across all 5,302 citations in our database, this violation is almost never contested at the roadside — which means documentation from before the stop is your primary evidence. A successful DataQs removal eliminates the severity-4 CSA score entirely, making it worth pursuing when the paperwork supports it.

How frequently should our fleet self-audit for 392.22(a) compliance, and what does the recent trend data suggest?

Our database shows 0 citations for 392.22(a) in the last 90 days and 0 in the last 12 months, against an all-time total of 5,302. That pattern does not mean enforcement has stopped — it more likely reflects a reporting lag or reduced inspection activity during the measurement window. Fleets should not interpret recent zeros as clearance to deprioritize this check.

Recommended audit cadence:

  • Per-trip: Warning device kit check on every pre-trip DVIR — no exceptions.
  • Monthly: Shop-level spot-check of 10–15% of fleet vehicles for kit completeness and triangle condition, documented in your maintenance log.
  • Quarterly: Full fleet sweep tied to PM intervals, with kit replacement triggered by age, UV damage, or missing components.

The 5,302 all-time citations confirm this is a real enforcement target. A monthly self-audit cadence keeps the fleet ahead of any renewed inspection focus and provides documentation evidence if a citation needs to be challenged.

Last updated: 2026-04-20T13:08:57.989Z Guidance derived from TruckCodex inspection data Read the full article → Quick Q&A →

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.