Prevention FAQ — FMCSR 392.9: Load Securement

Fleet safety managers: inspector focus areas, pre-trip checklists, root-cause analysis, and audit cadence for FMCSR 392.9 citations.

Severity Weight
N/A
OOS Eligible
No
BASIC Category
Unsafe Driving
Code System
FMCSR
Code:
392.9
Code System:
FMCSR
BASIC Category:
Unsafe Driving
OOS Eligible:
No
Severity Weight:
N/A

Ranks #405 of 3,146 FMCSR codes by citation frequency • OOS rate of 77.8% is above the FMCSR-wide average of 33.3%.

Violation Description

Driver may not operate a CMV without proper load securement

Prevention FAQ for Fleet Managers

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

What exactly do inspectors look for during a 392.9 inspection, and which states are highest risk?

Inspectors are looking at whether cargo is secured against forward, rearward, and lateral movement — checking tie-downs for proper count, condition, and anchor-point integrity, as well as whether cargo is contained, immobilized, or blocked. Our inspection records show Texas is by far the highest-risk state, with 176 citations in the last 180 days and an 88.1% OOS rate on those stops. Kentucky and New Mexico each ran 100% OOS rates in the same window, meaning every cited vehicle was parked. Illinois had 59 citations but only a 22.0% OOS rate, suggesting inspectors there often write the violation without parking the truck. Fleet managers routing heavy-commodity vehicles through Texas should treat every stop as a potential securement audit and brief drivers accordingly before departure.

What specific items must appear on the driver's pre-trip securement checklist?

Build the checklist around the failure points inspectors actually cite. Drivers should verify:

  • Tie-down count matches load type and weight distribution before wheels roll.
  • Working condition of all tie-downs — no cuts, fraying, broken hooks, or missing tensioners.
  • Anchor points are intact on the trailer floor and walls with no visible damage.
  • Front-of-load blocking or header board is in place where required.
  • Load is flush or within legal overhang limits and flagged if overhanging.
  • Tarps and covers are tight with no billowing sections that could mask a securement gap.
  • Post-first-stop re-inspection — securement should be re-checked after the first 50 miles and at each subsequent stop.

The co-occurrence data (detailed in the root-cause FAQ below) shows that lighting defects appear on 42 of the same inspections as 392.9, so add a lamp walk-around to the same pre-trip pass.

What documentation must drivers carry and carriers retain to defend against or reduce 392.9 exposure?

Drivers should carry and be prepared to show:

  • Pre-trip inspection report with a securement line item signed and dated.
  • Bill of lading or shipping manifest that describes the cargo type — this establishes which securement standard applies.
  • Commodity-specific securement method documentation (laminated card or digital reference) matching the cargo on board.

At the carrier level, retain:

  • Driver training records showing securement instruction, including date and content covered.
  • Equipment maintenance logs for tie-downs, chains, binders, and anchor points — these are separate from vehicle DVIR and must show periodic inspection and replacement cycles.
  • Post-citation corrective action records, including what was found deficient and what was replaced or repaired.

Retain all records for at least 12 months to support any DataQs challenge (see related FAQ).

What are the most common root causes, based on what else gets cited in the same inspection?

Our database shows three dominant co-occurrence patterns over the last 90 days:

  1. 393.9 — Inoperable Required Lamp (42 shared inspections): Drivers who skip or rush the pre-trip are missing both lighting defects and securement defects in the same walk-around. The root cause is an insufficient or unverified pre-trip process.

  2. 392.2RG — Operating while ill or fatigued (35 shared inspections): A fatigued driver is more likely to shortcut a securement check. If fatigue violations are pairing with load securement at this rate, your HOS compliance and dispatch scheduling practices need direct review.

  3. 396.17C — No proof of periodic inspection (26 shared inspections): Vehicles missing their annual inspection documentation tend to have broader maintenance gaps. The tie-downs, anchor rails, and bulkheads that secure cargo are maintenance items — if the vehicle isn't being inspected systematically, securement hardware is likely degrading undetected.

Fix the pre-trip process, address HOS pressure from dispatch, and bring periodic inspection documentation current.

What must happen before a vehicle cited under 392.9 returns to service?

Because 392.9 carries a 78.1% OOS rate across all-time citations — more than double the all-FMCSR average of 31.4% — most vehicles cited under this code are already parked at the roadside. Before the vehicle moves:

  • Physical re-securement must be completed by a qualified person at the roadside or a nearby terminal, not just the driver self-certifying.
  • An inspector or law enforcement officer must release the vehicle — do not assume the driver can simply re-secure and go.
  • Document the corrective action: photograph the re-secured load, note the tie-down method used, and have the driver sign off.
  • Report the release condition back to dispatch and the safety department in writing before the driver departs.
  • Update the DVIR to reflect the deficiency and the corrective action taken.

For carriers running construction materials — the heaviest-cited commodity segment in our data — establish a regional contact list of certified load securement crews who can respond to OOS events.

What should a fleet's post-citation review process look like after a 392.9 write-up?

Run a structured event review within 48 hours of the citation:

  1. Pull the inspection report and identify the exact securement deficiency noted by the inspector.
  2. Interview the driver — was the pre-trip completed? What was secured, and how? Was there dispatch pressure to depart before the load was ready?
  3. Review the prior 30 days of DVIRs for that vehicle — look for any mention of tie-down or anchor-point condition.
  4. Check the co-occurring violations on the same inspection. If 393.45B2UV (brake hose inadequacy) or 396.3A1BOS (brakes out of service) also appear — both show up in our 90-day co-occurrence data — this is a maintenance program failure, not just a driver error.
  5. Classify root cause as driver behavior, equipment condition, dispatch practice, or training gap — each requires a different corrective action.
  6. Document all findings and corrective actions with dates. This record is your defense in a CSA review and any DataQs challenge.
How does a 392.9 citation affect the carrier's CSA scores?

392.9 sits in the Unsafe Driving BASIC, which is one of the most visible BASIC categories to shippers, brokers, and FMCSA safety investigators. With 3,878 all-time citations in our database, this code ranks #396 out of 3,036 FMCSR codes by volume — it is not a rare violation, and FMCSA weights it accordingly. The 78.1% OOS rate is particularly damaging because OOS events carry higher severity weights in the SMS algorithm than non-OOS violations. Every OOS event elevates the carrier's Unsafe Driving percentile faster than a standard citation. Carriers whose names appear in our top-carrier data — some with 9 or 10 citations each — are at elevated risk of intervention thresholds if citations cluster within a 24-month window. Fleet managers should monitor their SMS dashboard monthly and flag any 392.9 entries for immediate root-cause review rather than treating them as isolated incidents.

What training topics should close the gap for drivers, given the vehicle make data?

Our inspection records show Freightliner (FRHT) leads all makes with 485 all-time citations under 392.9, followed by Kenworth (290), Peterbilt (245), Mack (228), and International (181). These are predominantly Class 8 tractors paired with flatbed, dump, and construction-body trailers — not straight trucks doing light-freight work. Training should be built around the actual load types these combinations carry:

  • Flatbed securement using chains, binders, and straps — including working load limit calculations.
  • Construction material loads (concrete, aggregate, pipe, steel) with commodity-specific securement methods.
  • Practical yard exercises — have drivers secure a load under time pressure, then have a safety manager inspect it before it's released.
  • Re-inspection requirements after the first 50 miles.
  • What inspectors look for: include actual 392.9 inspection report examples in training materials.

Annual classroom review is insufficient. Build hands-on securement drills into quarterly safety meetings.

When should a fleet file a DataQs challenge on a 392.9 citation?

File a DataQs challenge when the inspection record contains a factual error — not simply because the outcome was unfavorable. Strong grounds include:

  • The inspection report identifies a securement method that was not present on the vehicle (wrong cargo type recorded, wrong tie-down count).
  • The citation was issued to the wrong carrier USDOT number.
  • The driver's pre-trip documentation and load photos contradict the specific deficiency cited.
  • A co-occurring violation on the same inspection was already successfully challenged and removed — a 392.9 attached to a corrected record may also be eligible for review.

Note that a DataQs challenge does not remove a valid citation — it corrects factual inaccuracies. Given the 78.1% OOS rate on this code, inspectors are confident in their findings the vast majority of the time. Only challenge when your documentation clearly contradicts the record. Retain all pre-trip reports, load photos, and driver statements for at least 12 months to preserve your ability to file.

How often should the fleet run internal self-audits specifically for 392.9 exposure, and why?

Our 12-month trend data shows consistent monthly citation volume — ranging from 41 to 81 citations per month nationally — with no clear seasonal drop-off. The last 90 days produced 107 citations, which aligns with the elevated monthly pace seen in mid-2025 (81 citations in a single month). This is not a cyclical problem with a safe period; enforcement is steady year-round.

Recommended cadence:

  • Monthly: Pull your fleet's SMS Unsafe Driving BASIC data and cross-reference any 392.9 entries against your internal pre-trip records.
  • Quarterly: Conduct unannounced yard audits — inspect secured loads on 10–15% of outbound vehicles before they leave the terminal.
  • After every citation: Treat the event as a trigger for an immediate fleet-wide securement review, not just a driver counseling session.

Given that Texas alone produced 176 citations in the last 180 days, fleets with significant Texas operations should increase audit frequency to bi-monthly at minimum.

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

Top Enforcing States

Where 392.9 is most commonly cited (last 180 days)

1. Texas
82
OOS 85.4%
2. Illinois
48
OOS 25.0%
3. Iowa
5
OOS 0.0%
4. North Carolina
5
OOS 60.0%
5. New Mexico
1
OOS 100.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.