Prevention FAQ — FMCSR 393.116 Cargo Securement

Guidance for fleet safety managers on intermodal container securement inspections, pre-trip protocols, documentation, root-cause analysis, and CSA impact based on 13M inspection records.

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

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

Violation Description

No/improper securement of logs

Prevention FAQ for Fleet Managers

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

What exactly do inspectors look for when checking intermodal container securement?

Inspectors verify that intermodal containers are properly secured to the chassis or platform using appropriate devices and fastening methods. Our inspection records show this violation carries a 97.5% out-of-service rate—far above the all-FMCSR average of 31.4%—meaning inspectors enforce it with high severity. In Texas, which accounts for 38 of the last 180 days' citations, and North Carolina with 10 citations, enforcement has been intensive and unforgiving: both states show 100% OOS rates. Inspectors typically check:

  • Twist locks engaged and seated properly
  • Lashing straps or chains free of damage, corrosion, or wear
  • All four corners secured (or all applicable points for the container type)
  • No gaps or movement when the container is manipulated
  • Fastening hardware torqued to specification

Don't assume "looks tight"—document torque values and fastening method at each pre-trip.

What should our pre-trip checklist include to prevent 393.116 citations?

Your checklist must address all securement points before any load departs. Build in these steps:

  1. Verify container type and weight — confirm the chassis/platform is rated for the load
  2. Check all twist locks — engage fully, confirm audible/tactile click at each corner
  3. Inspect lashing hardware — look for bent shackles, cracked welds, rust, or missing pins
  4. Test for movement — manually rock the container side-to-side and front-to-back; it should not shift
  5. Document fastening method — record which lashing points were used and any non-standard config
  6. Verify spare lashing gear onboard — drivers should carry backup straps or chain to address roadside failures
  7. Sign-off by name and date — creates accountability and legal protection

Make this checklist vehicle-specific, especially for tractors (PTRB, TRLR, FRHT dominate citations), and assign it as a required gate-check before dispatch.

What documentation should drivers carry and what should we retain on file?

Drivers must carry:

  • Signed pre-trip inspection form with date, time, driver name, and notation of all securement points checked
  • Load securement diagram showing which twist locks and lashing points were engaged
  • Shipper's weight certificate or bill of lading confirming container weight and contents
  • Maintenance record for the chassis/platform showing the last date lashing hardware was inspected or replaced

Fleets should retain:

  • 12-month rolling file of all pre-trip forms, indexed by vehicle VIN
  • Photos of securement (especially non-standard loads) taken at origin and destination
  • Maintenance logs showing when lashing equipment was last serviced or replaced
  • Accident/incident reports involving container movement or loss

Our inspection records show that missing proof of maintenance (code 396.17C) co-occurs with 393.116 in 9 shared inspections over the last 90 days, indicating inspectors actively check maintenance records during securement audits. Keep everything for at least 24 months.

What root causes does the co-occurrence data suggest we should address in training?

Our inspection records reveal three critical systemic patterns:

Pattern 1: Maintenance gaps — Code 396.17C (no proof of periodic inspection) co-occurs in 9 shared inspections. This suggests drivers or dock personnel are not following a scheduled inspection regimen for twist locks and lashing hardware. Solution: establish a quarterly equipment inspection schedule, require proof of inspection onboard, and flag any chassis that misses it.

Pattern 2: Driver fatigue and inattention — Codes 392.2RG and related fatigue violations co-occur in 4+2+2+2 shared inspections combined. This indicates drivers securing containers under time pressure or while fatigued may skip steps or cut corners. Solution: implement fatigue awareness training tied to pre-trip discipline; consider mandatory rest stops before long hauls.

Pattern 3: Vehicle condition cascades — Inoperable lamps (393.9) and tire defects (393.75C, 393.75A3) co-occur with securement citations, suggesting overall vehicle maintenance culture is weak. Solution: integrate pre-trip signing into a holistic vehicle health check; don't compartmentalize securement.

Address these in your driver and dock supervisor training to prevent recurrence.

How should we verify securement repairs before returning a vehicle to service?

After any securement citation, do not dispatch the vehicle until a certified mechanic has completed and signed off on repairs. Your verification process should include:

  1. Physical inspection — mechanic engages/disengages all twist locks, confirms smooth operation and audible engagement
  2. Hardware replacement — any bent, cracked, or rusted fasteners, shackles, or pins must be replaced with OEM equivalents
  3. Torque testing — all fastening hardware must be re-torqued to manufacturer spec (record the value and tool used)
  4. Load simulation — if possible, have the mechanic simulate a loaded container and rock it to confirm zero movement
  5. Documentation — mechanic signs a repair order noting which components were replaced, torque specs used, and date of inspection
  6. Driver re-checkout — have the driver perform a fresh pre-trip with the mechanic present to confirm understanding

Our top carrier by citation count, J B HUNT TRANSPORT INC, has logged 13 citations across all vehicle types; establishing this verification discipline helps avoid repeat violations. File the repair order with the vehicle's maintenance record.

What post-citation review should we conduct internally?

When your fleet receives a 393.116 citation, follow this post-event protocol:

  1. Gather the inspection report — obtain the DVIR and any photos or notes the inspector documented
  2. Interview the driver — ask what they checked pre-trip, whether they felt the container was secure, and whether they heard/felt movement during transit
  3. Review the load sheet — confirm the shipper's weight and any special loading instructions; heavy or unevenly distributed loads increase securement failure
  4. Inspect the vehicle — examine the actual twist locks, lashing hardware, and chassis for defects that may have been the root cause
  5. Cross-check maintenance records — verify whether the vehicle's securement hardware was last inspected and when
  6. Root-cause categorization — classify the citation as driver error, equipment failure, shipper error (wrong container weight), or process gap
  7. Corrective action plan — assign retraining, equipment replacement, or process change; document and track to completion
  8. Share results — brief all drivers and dock supervisors on the specific failure mode to prevent imitation

This systematic review turns a citation into actionable fleet intelligence.

How does a 393.116 citation impact our CSA Vehicle Maintenance BASIC score?

A 393.116 citation carries a CSA severity weight of 7, placing it in the upper tier of enforcement impact. Across our inspection database, this code ranks #573 out of 3,036 FMCSR codes by citation volume, meaning it is relatively less frequent than some other maintenance violations—but when cited, it almost always results in an out-of-service order (97.5% OOS rate vs. the all-FMCSR average of 31.4%).

This combination means:

  • High severity per occurrence — each citation counts heavily in CSA scoring
  • Imminent hazard perception — regulators and CSA algorithms view unsecured containers as safety-critical
  • Fleet impact — even a single citation can flag your Vehicle Maintenance BASIC and trigger a compliance investigation
  • Insurance and customer implications — many shippers and brokers audit CSA scores; a rising Vehicle Maintenance BASIC can cost you loads

Our last 90 days show 21 citations nationally with a 97.5% OOS rate, indicating consistent high-severity enforcement. Prevent citations aggressively via the pre-trip and maintenance protocols outlined in this FAQ.

What driver and dock training topics close the knowledge gap on this violation?

Target these training modules to your workforce:

For Drivers:

  • Twist lock mechanics — hands-on walkthrough of how each type engages and disengages; many drivers have never been shown what "fully seated" feels and sounds like
  • Lashing strap and chain condition — teach recognition of fraying, corrosion, bent shackles, and missing keeper pins
  • Load stability in transit — explain that a container that seems tight at dock may shift if lashing is incomplete, especially on curves and during braking
  • Roadside troubleshooting — what to do if a twist lock fails mid-haul (stop, do not continue; use spare lashing gear; notify dispatch)
  • Load weight awareness — understand how an overweight or unevenly distributed container affects securement stress

For Dock Supervisors:

  • Shipper communication — confirm container weight and contents before accepting; flag discrepancies
  • Chassis assignment — match container size/weight to rated chassis capacity
  • Spare equipment inventory — maintain an on-site stock of replacement twist locks, straps, and shackles

Our citation data spans multiple vehicle makes (PTRB, TRLR, FRHT leading); ensure training is equipment-agnostic but chassis-specific where needed.

When should we consider filing a DataQs challenge on a citation?

DataQs challenges are appropriate in limited, specific circumstances. Consider challenging only if:

  1. Inspector error is documented — e.g., you have photos or witness statements showing the container was fully secured at time of inspection, but the inspector's DVIR claims otherwise
  2. Equipment malfunction was not the driver's fault — e.g., a twist lock mechanically failed despite proper pre-trip, driver immediately pulled over, and the failure is observable and documented
  3. Procedural violation in inspection conduct — e.g., the inspector did not allow you time to verify the securement or did not follow DOT inspection protocols

Do not challenge simply because:

  • You believe the OOS decision was harsh
  • The driver says they checked it
  • The container seemed tight when you eyeballed it

Our data shows a 97.5% OOS rate on 393.116, indicating consistent, well-documented enforcement. Frivolous challenges waste compliance resources and may damage your carrier profile. Focus instead on the prevention, maintenance, and training measures in this FAQ. If you have a credible challenge, work with your compliance counsel and file within the DataQs window (typically 45 days).

How often should we self-audit for securement compliance?

Our inspection records over the last 90 days show 21 citations; over the last 12 months, 127 citations. This is a relatively low-frequency violation nationally, but the severity (97.5% OOS rate) and concentration in specific states (Texas 38 citations, North Carolina 10) suggest seasonal or operational clustering.

Recommended audit cadence:

  • Monthly spot-checks — randomly select 10–15 outbound loads at each terminal; verify pre-trip paperwork, physically check 2–3 twist locks per container, and observe driver securement behavior
  • Quarterly deep audits — inspect all active intermodal chassis/platforms for twist lock function, lashing hardware condition, and maintenance records; document findings
  • After any citation — immediately inspect the cited vehicle and all similar units in your fleet; don't wait for the next scheduled audit
  • After any accident or load loss — investigate root cause and adjust audit frequency upward if securement was a factor

The uptick from April (2 citations) to July (20 citations) in our last 12-month trend suggests summer or peak-season operational stress increases risk. Schedule heavier audits during your high-volume periods. Log all audits to demonstrate due diligence if you are ever inspected.

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

Top Enforcing States

Where 393.116 is most commonly cited (last 180 days)

1. Texas
36
OOS 100.0%
2. North Carolina
3
OOS 100.0%
3. Iowa
2
OOS 100.0%
4. Illinois
2
OOS 50.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.