Prevention FAQ — FMCSR 392.22(b): Warning Device Placement

Inspectors are evaluating whether a driver who has stopped a CMV on or near a roadway has deployed warning devices — triangles, fusees, or equivalent — and placed them at the correct distances ahead of and behind the vehicle. The citation is issued either when devices are missing from the scene entirely or when placement positions are clearly wrong (e.g., all three triangles bunched directly behind the trailer).

Across our 13 million inspection records, this code has accumulated 5,635 all-time citations, ranking it #321 out of 3,036 FMCSR codes by volume — meaningful enough to warrant active prevention but not in the top tier of daily enforcement. Inspectors at breakdown scenes and post-accident reviews are the primary trigger points, so the citation usually compounds an already stressful event. Train drivers that the moment a vehicle becomes disabled, warning device deployment is the first regulatory clock that starts.

Add a dedicated Warning Device Station Check section to your pre-trip form. Drivers must physically confirm:

• Triangle kit present and the case is not damaged or missing reflectors
• All three triangles unfold and stand upright — worn hinges are a common failure point
• Fusees or electric flares (if used) are present and within service date
• The kit is accessible without unloading cargo — stowage behind sealed trailer doors is a root-cause scenario

Our inspection records show Freightliner (FRHT) units lead all cited makes with 969 citations, followed by Utility trailers (UTIL) at 518 and Volvo (VOLV) at 378. Walk the cab-to-trailer connection point on high-volume makes like these and confirm the warning device kit hasn't migrated into an inaccessible compartment during loading. Pre-trip sign-off on the kit should be a line item, not an assumption.

Drivers should carry:

• A completed DVIR or pre-trip checklist showing the warning device kit was inspected that day, signed and dated
• The vehicle's equipment manifest confirming the required number and type of devices

Carriers should retain (minimum 12 months):

• DVIRs or pre-trip records for the cited unit going back at least 30 days prior to the citation date
• Any training records showing the driver completed warning device placement instruction
• The inspection report itself (MCS-63 or equivalent) with the specific sub-violation noted

Because 392.22(b) is not OOS-eligible — our data shows only 1 out of 5,635 citations resulted in an out-of-service order — drivers typically continue their run. That makes post-trip documentation discipline critical: the citation must be logged, reported to safety, and tied to the driver's file before the paper trail goes cold.

Because 392.22(b) has no co-occurring violation data surfaced in our records for this specific code, the root causes we see operationally in breakdown scenarios fall into three categories:

1. Equipment gap — The warning device kit is absent, expired, or broken. This is a pre-trip failure, not a knowledge failure. Fix it with mandatory kit inspection on the DVIR.

2. Training gap — Drivers know devices exist but have never practiced deployment under stress. Night scenarios, highway shoulder simulations, and distance-estimation drills close this gap.

3. Access gap — Devices are technically on the vehicle but inaccessible at the moment of need (locked trailer, sealed load, wrong compartment). This is a load-planning and dispatch problem, not a driver problem. Audit stowage locations fleet-wide.

The top cited makes — FRHT (969), UTIL (518), and VOLV (378) — span tractors and trailers, confirming this is not an equipment-type-specific issue but a process gap that follows the fleet wherever volume is highest.

Since 392.22(b) is not OOS-eligible — our database shows a 0.0% out-of-service rate across 5,634 of 5,635 all-time citations — there is no regulatory hold on the unit. However, returning the vehicle without corrective action embeds the deficiency.

Return-to-service checklist:

1. Replace or repair the warning device kit if the citation involved broken or missing equipment — document the replacement with a parts record
2. Conduct a supervised placement drill with the cited driver before the next dispatch, logged in the training file
3. Confirm stowage location is accessible from outside the vehicle in a disabled scenario
4. Have a terminal safety manager or lead driver sign off on the corrected kit — this creates an audit trail and signals organizational seriousness

This process takes under 30 minutes but creates the documentation layer needed for any future DataQs challenge or CSA review.

Run a structured 48-hour post-citation review covering four areas:

1. Timeline reconstruction — What was the breakdown sequence? When did the driver deploy (or fail to deploy) devices? Was there a dispatch delay that shortened the window?
2. Equipment audit — Pull the pre-trip DVIR for that unit. Was the warning device kit signed off? If yes and it was still deficient, that's a driver accountability issue. If no check was performed, that's a process issue.
3. Driver debrief — One-on-one, non-punitive conversation focused on what the driver knew about proper placement distances and what made deployment difficult at that scene
4. Fleet-wide spot check — Pull 10 random units within 72 hours and physically inspect warning device kits. Our inspection records show carriers like NEW PRIME INC (50 citations) and J B HUNT TRANSPORT INC (27 citations) accumulate citations across large fleets, suggesting that a single event often signals a systemic gap, not an isolated incident

Document the review outcome and corrective action in your SMS compliance folder.

392.22(b) falls under the Unsafe Driving BASIC in FMCSA's CSA scoring model. Every citation on an inspectable event adds a time-weighted violation point to that BASIC, with more recent events weighted more heavily.

The good news from our data: the 0.0% OOS rate for this code (1 OOS event out of 5,635 citations) means the severity weight assigned is on the lower end of the Unsafe Driving spectrum compared to codes that routinely result in OOS orders. For context, the all-FMCSR average OOS rate is 31.4% — this code runs essentially at zero, reflecting its classification as a procedural rather than immediately dangerous violation.

At #321 out of 3,036 FMCSR codes by citation volume, it is common enough that accumulation across a large fleet will move your BASIC percentile. Ten or more citations in a 24-month window on a mid-size carrier is enough to warrant a targeted intervention before an FMCSA intervention letter arrives.

Based on the make distribution in our inspection records — FRHT (969 citations), UTIL (518), VOLV (378), KW (317), PTRB (283) — this violation spans the full range of tractor and trailer configurations in a typical dry-van or temperature-controlled fleet. Training must therefore be universal, not equipment-specific.

Priority training modules:

• Placement geometry drill — Drivers must know the correct distances for roadways, curves, and hills without looking them up. Practice under timed conditions
• Night and adverse-weather scenario — Most broken-down vehicles sit longer at night; training in daylight only creates a false confidence gap
• Kit inspection as muscle memory — Integrate a 60-second kit check into every pre-trip walkthrough until it requires no reminder
• Stowage access test — Have drivers demonstrate they can retrieve the kit in under 60 seconds from the vehicle's actual stowage location, fully loaded

Carriers with the highest citation counts — NEW PRIME INC at 50 and SWIFT TRANSPORTATION CO OF ARIZONA LLC at 21 — are high-mileage operations where driver turnover makes onboarding training quality the primary control point.

File a DataQs challenge when you have specific, documented evidence that the citation is factually incorrect. Viable grounds include:

• The driver's pre-trip DVIR shows the kit was inspected and present, and the violation narrative conflicts with that record
• The inspection report lists the wrong vehicle unit or USDOT number
• The citation was issued for a vehicle that was not disabled on a roadway in the regulatory sense (e.g., a secured loading dock)
• A supervisor or law enforcement report from the same scene documents that devices were properly placed

Do not file a challenge based on disagreement with the inspector's judgment about placement distance if no contradicting documentation exists — it will not succeed and creates a paper trail of rejected challenges.

Because this code carries a 0.0% OOS rate and lower severity weight, the CSA score impact of a single citation is limited. Reserve DataQs resources for citations where the violation is clearly erroneous and documentation is solid.

Our inspection records show 0 citations in the last 90 days and 0 in the last 12 months for 392.22(b). That zero-recent-activity trend does not mean enforcement has stopped — it reflects the event-driven nature of this citation (it requires a breakdown to occur). Warning device readiness is invisible until a vehicle sits disabled on a shoulder.

Recommended audit cadence:

• Monthly random fleet sample — Inspect warning device kits on 10–15% of active units each month, rotating through the fleet quarterly. Physical inspection, not paperwork review
• Post-incident mandatory check — Any breakdown event, even one that doesn't generate a citation, triggers a same-day kit inspection and DVIR review for that unit
• Onboarding gate — Every new driver demonstrates correct kit retrieval and placement geometry before first solo dispatch

The all-time volume of 5,635 citations across our database confirms this is a persistent industry gap despite relatively low recent enforcement activity. Low citation frequency in recent months means your next one is statistical, not impossible — audit accordingly.