Prevention FAQ — FMCSR 393.130: Heavy Equipment Cargo Securement

Fleet manager guide to preventing 393.130 citations: checklists, documentation, root-cause analysis, and CSA impact based on 6,520 real inspection records.

OOS Eligible
Severity Weight
1
OOS Eligible
Yes
BASIC Category
Vehicle Maintenance
Code System
FMCSR
Code:
393.130
Code System:
FMCSR
BASIC Category:
Vehicle Maintenance
OOS Eligible:
Yes
Severity Weight:
1
Violation Group:
General Securement

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

Violation Description

No/improper heavy vehicle/machine securement

Prevention FAQ for Fleet Managers

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

What exactly do inspectors look for when they cite 393.130, and which enforcement environments are highest-risk?

Inspectors are looking for heavy equipment and machinery on flatbeds or lowboys that isn't adequately tied down — loose chains, missing binders, insufficient tie-down points, or equipment that has shifted in transit. Our inspection records show Texas alone generated 329 citations in the last 180 days with a 97.0% OOS rate, making it by far the highest-risk jurisdiction. Iowa issued 48 citations over the same period, every single one resulting in an OOS order (100.0% rate). North Carolina (49 citations, 91.8% OOS) and Illinois (19 citations, 94.7% OOS) are also active enforcement states. If your fleet runs heavy-haul lanes through any of these states, treat every stop as a high-probability inspection event. Inspectors typically walk the trailer perimeter, test chain tension by hand, check that binders are locked and cotter-pinned, verify tie-down angles, and confirm equipment is blocked or immobilized against forward movement.

What pre-trip checklist items specifically target 393.130 compliance?

Build a dedicated heavy-equipment securement block into your pre-trip form. Required line items:

  • Tie-down count: Confirm the number of chains/straps meets requirements for the equipment weight and length.
  • Working load limit (WLL) markings: Each chain or strap must have a legible WLL tag; flag any faded or missing tags immediately.
  • Binder condition and lock: Every binder must be fully engaged and secured against accidental release — check the latch or cotter pin.
  • Chain condition: No broken links, kinks, or excessive wear.
  • Blocking and chocking: Wheeled equipment must be chocked; tracked equipment must be blocked or secured against all movement axes.
  • Equipment attachment points: Confirm chains connect to the machine's designated lift/tie-down points, not to hydraulic lines or sheet metal.
  • Post-departure re-check at first stop: Chain tension relaxes within the first 50 miles; a mandatory re-check stop should be policy for every load.

Drivers on Peterbilt, Ford, and Kenworth platforms — the top three cited vehicle makes in our database — should treat this checklist as non-negotiable before departure.

What documentation must drivers carry and what must carriers retain to defend a 393.130 inspection?

Drivers should carry:

  • Bill of lading or load manifest listing equipment weight, dimensions, and any special securement instructions from the shipper.
  • Equipment-specific securement plan if the load exceeds standard configurations — especially for asymmetric or unusually shaped machinery.
  • Pre-trip inspection record with the securement checklist completed and signed for that specific load.
  • Tie-down equipment certifications or load ratings if inspectors ask about WLL compliance.

Carriers should retain:

  • Signed pre-trip and post-trip inspection records for each load, minimum 90 days.
  • Maintenance records showing tie-down equipment (chains, binders, straps) is on a replacement schedule.
  • Training records showing drivers completed load securement training, particularly relevant given that 26 of the co-occurring inspections in our last 90 days involved 383.23A2 (operating without a CDL) — a signal that under-credentialed operators are running secured loads.

Retaining these documents gives you the foundation for a DataQs challenge if the citation record is factually inaccurate.

What are the true root causes behind 393.130 citations, based on what else gets cited in the same inspection?

Our inspection records from the last 90 days reveal three systemic patterns through co-occurring violations:

1. Maintenance program breakdown — 396.17C (No proof of periodic inspection) appeared in 54 shared inspections alongside 393.130. This is the top co-occurring code and points to carriers that lack structured maintenance schedules altogether. If periodic inspections aren't being documented, neither are tie-down equipment inspections.

2. Equipment readiness failures — 393.9 (Inoperable Required Lamp) also appeared in 54 shared inspections. Trucks showing up with dead lights are trucks that haven't had a real pre-trip. The same culture that misses lighting misses securement.

3. Driver fitness and compliance gaps — 392.2RG (Operating while ill or fatigued) appeared in 50 shared inspections. A fatigued driver rushing to depart is the driver most likely to skip the load re-check stop and leave loose binders uncorrected. This co-occurrence suggests time pressure and fatigue management are upstream of the securement failure itself.

Address all three root causes — not just the tie-down mechanics.

How should a repair or correction be verified before the vehicle returns to service after an OOS order under 393.130?

An out-of-service order under 393.130 cannot be cleared by the driver alone. Required steps before returning to service:

  1. Re-secure the load: A qualified supervisor or second trained driver — not the same driver who was placed OOS — should independently inspect and correct the securement. Document who performed the correction and at what time.
  2. Inspector sign-off: The vehicle cannot move until the inspecting officer clears the OOS. Do not attempt to move the vehicle to a nearby lot for repair; this is a separate violation.
  3. Photograph the corrected load: Take timestamped photos of all tie-down points after correction. This documentation supports any future DataQs challenge and closes your internal incident record.
  4. Log the correction in the maintenance system: Record the specific deficiency found (e.g., two chains under-tensioned, binder unlocked) alongside the corrective action. This feeds your root-cause analysis.
  5. Notify dispatch and safety manager: The safety manager should receive the full inspection report, not just the citation number, before the next load is assigned to that driver-vehicle combination.
What post-event review process should the fleet run after any 393.130 citation?

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

  • Pull the full inspection report: Identify exactly which tie-down points failed, what the inspector noted, and whether an OOS was issued. Our database shows a 97.7% OOS rate for this code all-time — if your driver wasn't placed OOS, that's still a citation that carries a CSA severity weight of 7.
  • Interview the driver: Was the pre-trip checklist completed? Was a re-check stop made? Was there time pressure from dispatch?
  • Review the load origin: Did the shipper or yard provide a securement plan? Was the load pre-staged incorrectly before the driver accepted it?
  • Audit co-occurring violations: If your citation came with 396.17C or 393.9 violations, the maintenance program needs review, not just the driver.
  • Identify the carrier pattern: United Rentals North America, EquipmentShare, and Sunbelt Rentals are the top three cited carriers in our records — all equipment rental operations. If your fleet handles similar freight, compare your securement procedures against what's generating their repeat citations.
  • Update training records and document completion.
How does a 393.130 citation hit the carrier's CSA score, and how serious is the exposure?

This code carries a CSA severity weight of 7, which places it in the serious-violation tier. Combined with its 97.7% OOS rate — more than three times the all-FMCSR average OOS rate of 31.4% — nearly every citation also generates an out-of-service event, which adds further weight to the Vehicle Maintenance BASIC score. The code ranks #298 out of 3,036 FMCSR codes by citation volume, meaning it's not a rare edge-case violation; inspectors know it and write it regularly. Within the Vehicle Maintenance BASIC category, peer codes like 393.9(a) generate 660,737 citations but carry only a 15.4% OOS rate — a fraction of 393.130's impact per event. One 393.130 OOS citation effectively counts as both a violation and a driver/vehicle OOS event in the CSA calculation. Carriers receiving multiple citations in a rolling 24-month window will see compounding score increases. The 1,068 citations recorded in the last 12 months across the industry confirm that FMCSA enforcement is active on this code year-round.

What driver training topics most directly close the compliance gap for 393.130?

Our citation data shows that Peterbilt (601 all-time citations), Ford (507), and Kenworth (480) are the top three cited vehicle makes — a spread that covers both Class 8 OTR platforms and medium-duty pickups hauling equipment on goosenecks. Training must reach both populations. Key curriculum topics:

  • Load-specific securement calculations: Drivers need to calculate minimum aggregate WLL for the actual equipment weight, not estimate by habit.
  • Binder and chain inspection: Hands-on identification of worn chain, cracked binders, and degraded straps — not just a visual pass.
  • Securement point identification by equipment type: Excavators, skid steers, forklifts, and rollers each have manufacturer-designated tie-down points. Generic chaining to bucket edges or boom arms is a recurring failure mode.
  • Re-check stop discipline: Training should make the 50-mile re-check stop a reflex, not an option.
  • Fatigue and time pressure: Given that 392.2RG appeared in 50 co-occurring inspections in the last 90 days, include a module on recognizing when fatigue is driving shortcuts in the securement process.
Under what circumstances should the fleet file a DataQs challenge on a 393.130 citation?

A DataQs challenge is appropriate when the inspection record contains a factual error — not simply because the citation feels unfair. Grounds worth pursuing:

  • Incorrect vehicle or driver assignment: If the DOT number, license plate, or driver ID on the report doesn't match your records, file immediately.
  • Load was correctly secured and documented: If your driver completed a signed securement checklist, has timestamped photos of the load before departure, and the inspection report contradicts that evidence, the challenge has a factual basis.
  • OOS designation applied incorrectly: At a 97.7% all-time OOS rate, inspectors almost always issue OOS on this code — but if the record shows OOS and your documentation shows the load met all requirements, that's challengeable.
  • Co-occurring violations were cleared but 393.130 was not: If paired violations like 396.17C were resolved on re-inspection, ensure the record reflects that.

Do not file a DataQs challenge simply to delay CSA score impact. Challenges without supporting documentation are routinely denied and consume safety staff time. Retain pre-trip checklists, photographs, and load manifests for every heavy-equipment move as your first line of defense.

How frequently should the fleet self-audit for 393.130 exposure, and what does the trend data say about timing?

Our inspection records show 173 citations in the last 90 days and 1,068 in the last 12 months, indicating sustained enforcement pressure with no off-season. Monthly citation counts peaked at 124 in July 2025 and have not dropped below 60 in any month through early 2026. There is no quiet period to relax on.

Recommended audit cadence:

  • Monthly securement equipment audit: Inspect all chains, binders, straps, and blocking equipment in the fleet for wear, WLL legibility, and quantity. The consistent monthly volume (72–124 citations per month across the industry) justifies monthly, not quarterly, reviews.
  • Quarterly driver records audit: Pull pre-trip inspection logs for all heavy-equipment moves and verify securement checklist completion rates. Cross-reference against any near-miss reports.
  • Post-season haul review: July 2025's spike to 124 citations suggests construction-season volume drives enforcement. Run a focused audit entering spring and again entering summer when haul frequency increases.
  • Immediate audit after any co-occurring violation: If your fleet receives a 396.17C or 393.9 citation — the two codes each tied to 54 co-occurring 393.130 inspections in our last 90 days — treat it as a leading indicator and audit securement practices before the next load moves.
Last updated: 2026-04-20T13:01:57.874Z Guidance derived from TruckCodex inspection data Read the full article → Quick Q&A →

Top Enforcing States

Where 393.130 is most commonly cited (last 180 days)

1. Texas
190
OOS 93.7%
2. North Carolina
29
OOS 93.1%
3. Iowa
27
OOS 100.0%
4. Illinois
23
OOS 91.3%
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.