Prevention FAQ — FMCSR 393.110: Cargo Securement (Logs)

Inspectors evaluate whether logs are secured using the correct combination of tiedowns, stakes, and wrapper chains (or equivalent) in accordance with the commodity-specific rules for logs. Key checkpoints include:

• Front-end containment: Is there a proper front bolster, stakes, or equivalent structure that prevents forward log movement?
• Tiedown count and placement: Are enough tiedowns present for the load length and log diameter, distributed per the required spacing?
• Tiedown condition: Are chains, binders, and straps free of visible damage, kinks, or improper hook placement?
• Load stability: Do logs show visible shifting or stacking irregularities that suggest movement en route?

Our inspection records show Texas generated 146 citations in the last 180 days alone — more than all other tracked states combined — making Lone Star weigh stations and mobile enforcement teams a high-priority checkpoint for fleets running timber corridors. North Carolina and New Mexico each recorded 100% OOS rates in the same window, meaning every log-load stop in those states resulted in a vehicle being pulled from service.

Build a dedicated log-securement section into the pre-trip, separate from general cargo. Minimum line items:

1. Front containment integrity — stakes, bolsters, or bunks seated and undamaged.
2. Tiedown count verified — count matches load length and log diameter requirements before departure.
3. Binder/chain condition — each binder opens and locks fully; no bent hooks, cracked links, or kinking.
4. Wrapper chain (if used) — seated low on the load, not riding on bark or a single log.
5. Load profile — no logs protruding beyond the rearmost tiedown by more than the allowable overhang.
6. Post-loading re-check — a second walk-around after the driver has moved 50–100 miles (the first natural settling point).
7. Stake/bunk pocket condition — inspect for cracked welds or bent pockets that prevent stakes from seating fully.

With a 95.1% out-of-service rate across 2,839 all-time citations, inspectors who cite this code almost always park the truck. A robust pre-trip checklist is the only cost-effective way to prevent that outcome.

Drivers must carry:

• A completed pre-trip inspection report that includes the log-securement section, signed and dated.
• The bill of lading or shipping document confirming commodity type (logs), which helps establish the applicable securement standard during an inspection.

Carriers must retain (recommended minimum):

• Signed pre-trip and post-trip inspection reports for at least 90 days.
• Equipment maintenance records documenting tiedown, binder, and stake/bunk inspections and replacements.
• Training records showing driver completion of log-securement training.
• Any post-citation corrective action documentation, including who remediated the load and how it was re-secured before the vehicle returned to service.

Our database shows 11 shared inspections in the last 90 days where 396.17C (no proof of periodic inspection) appeared alongside 393.110. Carriers that can't produce maintenance documentation during an inspection make themselves vulnerable to compounding violations — keep records accessible and organized.

The co-occurrence data in our database points to three distinct systemic failure patterns:

1. Equipment neglect culture (393.104B — tiedown damaged, 17 shared inspections): The most operationally direct pairing. When tiedowns are worn or damaged, the securement system fails as a whole. Root cause: inadequate periodic equipment inspection and no replacement threshold for binders and chains.

2. General maintenance breakdown (393.9 — inoperable required lamp, 19 shared inspections): A truck with a dead lamp and an unsecured log load is a truck where pre-trip inspections are not being performed or acted on. Root cause: drivers are dispatched without completing or enforcing the pre-trip, or defects are noted but not repaired before dispatch.

3. Driver condition/compliance breakdown (392.2RG — operating while fatigued, 21 shared inspections — the top co-occurring code): This pairing is the most systemic. A fatigued driver is less likely to execute a proper pre-trip or post-50-mile re-check. Root cause: dispatch pressure overriding rest requirements, creating a cascade of compliance failures across both HOS and cargo securement.

Because 95.1% of all 393.110 citations result in an out-of-service order, 'return to service' should be treated as a formal process, not an informal call to the driver:

1. On-site remediation documentation: The driver or roadside assist technician who re-secures the load must document exactly what was corrected — which tiedowns were replaced, how many were added, and the final configuration.
2. Physical inspection by a second person: A supervisor, safety coordinator, or shop mechanic — not the cited driver — should verify the load before movement resumes.
3. Equipment replacement, not repair: Damaged binders or chains found during the OOS event should be discarded and replaced, not reused on the re-secured load.
4. Maintenance record entry: Log the event in the equipment file for the trailer or truck involved, including the date, citation number, and corrective action taken.
5. Cleared by enforcement: Confirm the OOS order has been formally lifted before the vehicle moves — do not assume re-securing the load automatically clears the order.

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

1. Pull the inspection report: Identify exactly which element of log securement failed — tiedown count, condition, front containment, or load configuration.
2. Review the full co-occurring citation list: Our records show citations for 393.110 frequently appear alongside 383.23A2 (operating without a CDL, 7 shared inspections in the last 90 days). Verify the cited driver's credential status independently.
3. Interview the driver: Was the pre-trip completed? Was the load re-checked after initial miles? Were there dispatch pressures that shortened the pre-trip?
4. Trace to equipment: Which trailer and tractor combination was involved? Pull their maintenance history for bunk, stake, and tiedown condition.
5. Correct the systemic gap: If the root cause is equipment, set a replacement schedule. If it's training, schedule remediation within 30 days and document it.
6. Document everything: Post-event review records support DataQs challenges if the citation was improperly written and demonstrate good faith during DOT compliance reviews.

393.110 carries a CSA severity weight of 7 — one of the higher weights within the Vehicle Maintenance BASIC. The severity weight multiplies against a time weight (most recent violations score higher) and is then normalized against your peers.

In our inspection database, 393.110 ranks #455 out of 3,036 FMCSR codes by all-time citation volume. That's a relatively specialized violation, but the 95.1% OOS rate means almost every citation also adds an OOS indicator, which applies an additional multiplier to the BASIC calculation.

For context: the all-FMCSR average OOS rate is 31.4%. At 95.1%, this code sits at three times that average. A single citation isn't just a severity-7 hit — it's also a near-certain OOS event, compounding score impact. Carriers in the top 10 cited list — including J B Hunt Transport (USDOT 80806) with 7 all-time citations and Ryder Transportation Solutions (USDOT 299073) with 7 — demonstrate that even large, professional fleets accumulate exposure. Fleets running regular log hauls should treat every citation as a material BASIC risk.

Our vehicle make data shows FRHT (Freightliner) accounts for 254 all-time 393.110 citations, followed by FORD (137) and PTRB (Peterbilt, 133). These are not exclusively dedicated log trucks — FORD and DODG (64 citations) appearances suggest smaller vocational and medium-duty units are involved, not just Class 8 semis. That means training must reach drivers of medium-duty trucks and not just CDL long-haul operators.

Core training modules to build:

1. Log-specific securement standards — how the rules for logs differ from general freight, including front containment requirements and tiedown spacing by log diameter.
2. Tiedown inspection and rejection criteria — what wear, corrosion, or deformation warrants replacement before the load is built.
3. Mid-trip re-check procedure — when and how to re-tighten or re-configure after initial load settling.
4. Pre-trip checklist execution — not just completing the form, but knowing what a failed item looks like on a log trailer specifically.
5. HOS awareness — given the 21 shared inspections pairing 393.110 with fatigued-driving violations, integrate rest compliance into securement culture training.

File a DataQs challenge when you have documented evidence that the inspection record is factually incorrect. Common grounds for 393.110:

• Load configuration was compliant: If you have pre-trip photos, driver-signed inspection sheets, or shipper documentation showing the load met the securement standard and the inspector incorrectly applied the violation, that's challengeable.
• Wrong code applied: If the load involved strapped lumber or bundled product rather than individual logs, and the inspector cited the log-specific code in error, that's a factual dispute.
• Tiedown count dispute: If the inspection report lists fewer tiedowns than were present and you have photographic evidence from the load origin.

Do not file if the deficiency was real and the load was genuinely non-compliant — a failed challenge wastes time and leaves the violation intact. Given the 95.1% OOS rate across 2,701 out-of-service placements, inspectors who write this code are almost always doing so after observing a clear securement failure. Challenge when the facts support it, not as a default response to any citation.

Our 12-month trend data justifies a monthly audit cadence at minimum, with increased intensity in the second half of the calendar year. Citation volume rose from 7 in April 2025 to a peak of 36 in December 2025 — a more than fivefold increase over eight months. The last 90 days produced 71 citations, which is nearly a quarter of the full prior-year total of 304.

Recommended audit structure:

• Monthly: Review all pre-trip inspection logs for log-haul routes. Flag any incomplete securement sections.
• Quarterly: Pull a sample of 10–15 pre-departure load photos (if your fleet uses them) and compare against tiedown requirements.
• Annually: Conduct a full equipment inspection of all log trailers — bunks, stakes, pockets, and tiedown inventory — before the fall ramp-up when citation frequency historically climbs.
• Triggered audit: Any citation or near-miss triggers an immediate audit of all active log-haul units, not just the cited vehicle.

The December 2025 spike to 36 citations with 34 OOS placements in a single month illustrates how quickly exposure can accumulate if audits lag enforcement trends.