Prevention FAQ — FMCSR 180.352B: Rigid IBC Retest Date Marking

Fleet safety guidance on rigid IBC retest date compliance. Based on 2 all-time citations across 13M inspections. Pre-trip checks, documentation, root-cause analysis, and audit cadence.

Severity Weight
7
OOS Eligible
No
BASIC Category
Hazardous Materials
Code System
FMCSR
Code:
180.352B
Code System:
FMCSR
BASIC Category:
Hazardous Materials
OOS Eligible:
No
Severity Weight:
7
Violation Group:
Package Testing - HM

Ranks #2,664 of 3,146 FMCSR codes by citation frequency • OOS rate of 0.0% is below the FMCSR-wide average of 33.3%.

Violation Description

Rigid IBC retest date marking

Prevention FAQ for Fleet Managers

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

What exactly do inspectors look for when checking rigid IBC retest date markings?

Inspectors verify that rigid intermediate bulk containers (IBCs) carry legible, accurate retest date markings that reflect the container's certification status. Our inspection records show 2 all-time citations for this code, with 1 citation in Texas over the last 180 days. When an inspector encounters a hazmat shipment, they examine the IBC's label or stamp to confirm the retest date has not expired and is clearly visible. The marking must be durable enough to survive transport conditions. Focus areas include faded or worn markings, missing dates entirely, and dates that have passed. Even a single unmarked or expired-dated IBC can trigger a citation, so 100% compliance across your fleet is the standard.

What should our pre-trip checklist include for rigid IBCs?

Add a dedicated section to your pre-trip inspection form:

  • Retest date visibility: Driver must confirm the date is legible from at least 1 meter away.
  • Expiration check: Compare marked date against current date; reject any container with a past retest date.
  • Marking condition: Look for peeling, fading, or water damage that obscures the date.
  • Location consistency: Verify the date marking is on the side or top of the container (not hidden).
  • Count and record: Document the number of IBCs loaded and the retest dates observed.

Make this a mandatory stop-point—driver cannot depart until every IBC passes this check. Across 13 million inspections, we see that hazmat compliance failures often cluster; pairing this check with a general IBC condition assessment (external damage, closure integrity) strengthens your program.

What documents must drivers carry, and what should the fleet retain?

Driver carry: A shipping paper or manifest that lists each IBC by retest date. The driver must be able to cross-reference container serial number to retest date in case of inspection. Some shippers provide a retest certificate; keep a copy on the vehicle.

Fleet retention: Maintain records for at least 2 years:

  • Supplier certificates confirming retest dates for every IBC your fleet owns or leases.
  • Pre-trip inspection logs showing the driver's retest date verification signature and date.
  • Photos of IBC markings (optional but recommended for disputed citations).
  • Maintenance records if a container is removed from service for marking repair or retest.

Our data shows 2 all-time citations for this code; neither was placed out of service, but documentation gaps often lead to repeat violations. Digitize these records where possible so you can audit compliance across the fleet in seconds.

What root causes commonly lead to this violation, based on co-occurrence patterns?

Our inspection records show that in the last 90 days, this code was paired 1 time with FMCSR 173.24F1 (closure defects—openings or leaking). This pattern suggests a systemic issue: inadequate container inspection before loading. When drivers or loaders skip the retest date check, they often also miss closure integrity, indicating a single root cause: insufficient hazmat loading procedures or training.

Common contributing factors:

  • Rushed shipping operations: Tight deadlines push loaders to skip checks.
  • Unclear responsibility: Driver assumes the shipper verified retest dates; shipper assumes the carrier will verify.
  • Worn container inventory: Older IBCs have faded markings; fleet hasn't implemented rotation or replacement schedule.
  • Supplier variability: Different shippers mark retest dates differently; drivers don't know where to look.

Address the root cause by centralizing retest verification: make it the carrier's responsibility, not the shipper's. Require your dispatch team to confirm dates before assigning the load.

How should we verify that a repaired or cleaned IBC is ready to return to service?

If an IBC's retest date marking is damaged (faded, worn, or illegible), it must be repaired or replaced before loading. Use this verification workflow:

  1. Visual inspection: Confirm the new marking is legible, permanent, and placed in a standard location (side panel or top).
  2. Retest certification: Obtain a current retest certificate from an approved facility (if the container's certification has expired, it must be retested, not just re-marked).
  3. Date match: Verify the retest date on the certificate matches the marking applied to the container.
  4. Photo documentation: Photograph the repaired marking and file the retest certificate with the vehicle maintenance records.
  5. Quarantine cleared: Update your fleet management system to show the container is cleared for service.

Our data shows 0 out-of-service placements for this code across 2 all-time citations, but preventive re-marking avoids citations entirely. Document every repair so auditors see a clear maintenance trail.

What should the fleet review after receiving a citation for this code?

Immediately after a citation:

  1. Identify the container: Locate the specific IBC cited by serial number or description. Document the retest date it was carrying and where the marking was found to be deficient.
  2. Audit affected loads: Cross-reference the citation date and truck ID to identify all similar loads the driver or vehicle carried in the 30 days prior. Inspect every IBC from those loads.
  3. Supplier audit: Contact the shipper to confirm whether retest dates were marked at origin and why the marking became illegible (shipper issue or carrier handling issue).
  4. Driver interview: Review the driver's pre-trip log. Was the retest date check completed? Did the driver note the date in writing? This reveals training gaps.
  5. Preventive action: If the issue is faded markings on fleet-owned IBCs, inspect your entire inventory for wear and schedule re-marking or replacement.
  6. Trend check: Our inspection records show 1 citation in the last 90 days and 2 in the last 12 months; if your fleet receives a second citation, escalate this to a hazmat training initiative.

Document all findings and corrective actions for CSA and audit readiness.

Does this violation affect our CSA Vehicle Maintenance BASIC score?

FMCSR 180.352B is ranked #2651 of 3,036 codes by citation volume, indicating very low enforcement frequency. Our data shows only 2 all-time citations nationally and 0 out-of-service placements. In contrast, peer hazmat codes like 177.834A-HMC (general loading/unloading) carry 3,954 citations and a 99.2% out-of-service rate, showing the severity gap.

While 180.352B itself does not trigger immediate CSA alerts due to rarity, it is a hazmat compliance marker. A single citation suggests gaps in hazmat procedures. Inspectors often escalate hazmat inspections after spotting one defect, so the real risk is that one 180.352B citation leads to deeper scrutiny of your entire hazmat operation. This can expose additional violations in placarding, documentation, or vehicle maintenance—codes that do heavily impact CSA Vehicle Maintenance and Hazmat BASIC scores.

Prevent the cascade: perfect execution on retest date marking demonstrates hazmat discipline and reduces audit exposure.

What training topics should our drivers and loaders complete?

Design a hazmat IBC refresher covering:

  1. Retest date identification: Show drivers where dates appear on real containers (side panels, top, stamped, or labeled). Use photos from your fleet's inventory.
  2. Expiration concept: Explain what an expired retest date means (container may not be structurally sound; cannot be shipped).
  3. Pre-trip checklist walkthrough: Walk through your form with live containers so drivers practice the 10-second check.
  4. Responsibility clarity: Clarify that the carrier (your fleet) is liable if an IBC with an expired or illegible date is loaded, regardless of shipper confirmation.
  5. Reporting procedure: Teach drivers to refuse loads with unmarked or expired IBCs and to document the refusal in writing to dispatch.
  6. Common mistakes: Show examples of faded markings, misplaced dates, or containers with multiple dates (only the latest retest date is valid).

Our vehicle make data shows FRHT and UTIL tractors with citations; ensure training covers all vehicle types and loader stations. Conduct the refresher annually and when any citation is received.

When should we consider filing a DataQs challenge for this citation?

File a DataQs challenge if any of the following apply:

  • Documentation exists proving compliance: If your pre-trip log and photos show the retest date was legible and current on the inspection date, challenge the citation for factual error.
  • Shipper-supplied container: If the IBC was supplied by the shipper already loaded, and your records show you did not repack or modify it, the shipper bears liability; you may challenge based on carrier responsibility limits.
  • Inspector error in identification: If the citation references an IBC serial number that was not on your vehicle, or if the date cited as expired was actually current, file with supporting documentation.
  • Ambiguous marking interpretation: If the retest date marking is genuinely unclear in the photo or report, and industry standards allow multiple interpretation formats, challenge on clarity grounds.

Our data shows 2 all-time citations with 0 out-of-service placements, suggesting citations may not be ironclad. If you have strong documentation, challenge promptly. However, do not challenge to avoid training—use every citation as a process improvement trigger.

How often should we audit our fleet for rigid IBC retest date compliance?

Recommended audit cadence: Monthly for fleet-owned IBCs; per-load for shipper-supplied IBCs.

Justification from our data: In the last 90 days, 1 citation was recorded; in the last 12 months, 2 citations. This low but steady volume suggests the violation is not widespread but occurs when oversight lapses. A monthly audit catches gradual marking deterioration before it triggers a citation.

Fleet-owned IBC audit:

  • First Tuesday of each month: inspect 100% of stored IBCs for retest date legibility.
  • Photograph markings; flag any date within 3 months of expiration for pre-emptive retest.
  • Record findings in a spreadsheet tied to container serial number.

Per-load audit:

  • Pre-dispatch: every IBC scheduled for a load is verified by dispatch (not just the driver) against the shipping manifest.
  • Post-delivery: driver submits photos of loaded IBCs with visible dates as proof of compliance.

This dual approach—inventory maintenance plus transaction verification—closes the gap that led to the 2 citations. If your fleet receives a citation, escalate to weekly audits for 90 days, then return to monthly.

Last updated: 2026-04-20T17:42:33.476Z Guidance derived from TruckCodex inspection data Read the full article → Quick Q&A →

Top Enforcing States

Where 180.352B is most commonly cited (last 180 days)

1. Texas
1
OOS 0.0%

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.