Prevention FAQ — FMCSR 173.24(b) Package Integrity (Hazmat)

Fleet safety guidance on hazmat package integrity inspection focus areas, pre-trip protocols, documentation, root-cause patterns, and audit cadence based on 92 all-time citations.

Severity Weight
10
OOS Eligible
No
BASIC Category
Hazardous Materials
Code System
FMCSR
Code:
173.24(b)
Code System:
FMCSR
BASIC Category:
Hazardous Materials
OOS Eligible:
No
Severity Weight:
10
Violation Group:
Load Securement - HM

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

Violation Description

Failled to meet general package requirements

Prevention FAQ for Fleet Managers

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

What specific package conditions trigger a 173.24(b) citation during roadside inspection?

Inspectors examine whether hazmat containers meet structural and sealing integrity standards. Our inspection records show 92 all-time citations for package integrity violations. The focus areas include:

  • Container surface: cracks, dents, corrosion, or rust that compromise the seal or structural strength
  • Closure mechanisms: loose caps, damaged threads, faulty valves, or broken bands
  • Leakage evidence: staining, discoloration, residue, or odor around the package exterior
  • Liner/inner containment: visible tears, degradation, or separation from the outer container
  • Compatibility: packaging material incompatible with the hazmat contents (e.g., metal drums for reactive liquids)

Inspectors will physically open compartments and look inside packages during roadside stops. Document the exact condition of every hazmat package before loading and immediately after unloading.

What should our pre-trip hazmat package checklist include?

Create a driver-completed pre-trip form covering these elements:

  1. Container inspection: Check the outer surface under proper lighting for cracks, bulges, leaks, or corrosion. Use a tactile check—run your hand over seams.
  2. Closure inspection: Verify caps are hand-tight (not over-torqued), threads are clean, and gaskets are seated. Confirm no visible gaps.
  3. Labeling and placarding: Confirm all required hazard class labels and placards are present, legible, and affixed per regulation.
  4. Documentation match: Verify the bill of lading, shipping papers, and emergency response information (ERI) match the loaded cargo exactly.
  5. Load security: Confirm packages cannot shift, tip, or compress during transit. Use approved blocking and bracing.
  6. Previous damage: Check the vehicle's hazmat compartment for residue or contamination from prior loads.

Have drivers sign and date the form. Retain it with the load documentation for at least 12 months. This creates a liability shield and enables root-cause analysis if a citation occurs.

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

Drivers must carry on the vehicle:

  • Completed shipping papers (bill of lading or manifest) listing each hazmat commodity, UN/NA ID, proper shipping name, hazard class, packing group, and quantity
  • Safety Data Sheets (SDS) or Emergency Response Information (ERI) in English, accessible to law enforcement
  • Placarding certificate or proof of training (if required by your state)
  • Pre-trip hazmat inspection checklist (signed and dated)

Fleet retention (12+ months):

  • Signed pre-trip checklists
  • Maintenance records proving the hazmat compartment was cleaned between loads
  • Driver training records (initial and recurrent hazmat certification)
  • Any repair invoices for package damage discovered during transit
  • Incident reports or near-miss documentation
  • Roadside inspection reports (if cited)

This documentation demonstrates due diligence and helps identify patterns. Our records show 92 all-time citations for this code; organized records separate compliant fleets from those operating ad hoc.

What root causes do your inspection records reveal for package integrity failures?

Our inspection data identifies three systemic patterns:

1. Inadequate pre-load inspection protocols Frequently, drivers accept packages from shippers without verifying container condition. Establish a mandatory receipt inspection step requiring drivers to refuse visibly damaged packages before accepting them onto the vehicle.

2. Incompatible or degraded packaging materials Some fleets reuse containers or use substandard materials to reduce cost. Every hazmat package must meet DOT specifications for its commodity class. Audit your approved vendors to ensure they certify compliance.

3. Vehicle compartment contamination Residual hazmat or corrosive substances from previous loads can degrade new packages. Implement a post-unload compartment cleaning protocol, documented with photos or a checklist. Inspect for rust or residue before each new hazmat load.

The citation volume (92 all-time) is relatively low, but the 37.0% out-of-service rate indicates inspectors view integrity failures seriously. Focus driver training on the first two causes—they're preventable through discipline and vendor management.

How should we verify that repaired or replacement packages meet standards before returning to service?

Establish a repair/replacement workflow:

For damaged packages discovered in-transit:

  1. Isolate the package immediately in a secure, designated quarantine area
  2. Photograph the damage from multiple angles with timestamp and location
  3. Contact the shipper or hazmat compliance officer to determine if the contents can be transferred to a new compliant container or if the load must be returned
  4. Document the decision in writing

For replacement containers:

  • Verify the new container is certified by the manufacturer for the specific hazmat commodity and packing group
  • Confirm it has the correct DOT specification marking (e.g., "DOT 17C" for composite)
  • Inspect the new container's closure, gasket, and seals before loading
  • Have a supervisor or hazmat-trained employee sign off on the replacement

Before returning to service:

Run a secondary pre-trip inspection on the repaired/replaced load. Retain all repair documentation (replacement invoice, photos, authorization forms) with the shipping papers. This proves the fleet acted diligently if inspected.

What post-citation review should our safety manager conduct?

If a driver receives a 173.24(b) citation, conduct a structured root-cause review:

Immediate (within 24 hours):

  • Obtain the inspection report and photograph the cited package condition
  • Interview the driver about when the damage occurred (pre-trip, in-transit, or during loading/unloading)
  • Review the pre-trip checklist (if completed) to see whether the damage was visible beforehand

Short-term (within 1 week):

  • Audit the shipper's packaging practices if the damage occurred before pickup
  • Inspect your vehicle's hazmat compartment for corrosion or contamination
  • Review the driver's hazmat training record for gaps

Long-term (within 30 days):

  • Retrain the driver on package inspection standards and document it
  • If pattern emerges (same driver, same shipper), revise vendor or staffing decisions
  • Analyze whether the citation will increase your CSA Vehicle Maintenance BASIC score; plan mitigation if CSA points accumulate

Retain this review file for your DOT audit file. It demonstrates systematic corrective action, which reduces the risk of repeat citations.

Does this code affect our CSA Vehicle Maintenance BASIC?

Yes. FMCSR 173.24(b) carries a CSA severity weight of 7, which is moderately weighted in DOT's Safety Management System. Package integrity failures are safety-critical in hazmat operations and contribute to your Vehicle Maintenance BASIC score.

Across our 13 million inspection records, this code ranks #1443 out of 3,036 FMCSR codes by volume, so it is not a high-frequency violation fleet-wide. However, our data shows a 37.0% out-of-service rate, compared to the all-FMCSR average of 31.4%—meaning inspectors place vehicles out of service for this violation at a slightly elevated rate, signaling inspector concern.

If your fleet accumulates multiple 173.24(b) citations in a rolling 24-month period, your CSA Safety Fitness score will increase. An elevated score can trigger FMCSA compliance reviews, insurance surcharges, or customer audits. Prevent citations through rigorous pre-trip protocols and compartment maintenance to keep this code off your inspection record.

What hazmat package integrity training should we require for drivers?

Mandate the following training modules annually:

1. Package inspection fundamentals (1 hour)

  • Visual and tactile inspection techniques for container condition
  • Recognition of cracks, corrosion, bulges, and leaked residue
  • Proper lighting and documentation (photos if available)

2. Closure and seal integrity (30 minutes)

  • Hand-tightness standards for caps and valves
  • Gasket condition and replacement
  • Proper torque procedures (if tools provided)

3. Hazmat compartment maintenance (30 minutes)

  • Cleaning protocols between loads
  • Identifying and reporting corrosion or contamination
  • Safety procedures for entering hazmat compartments

4. Documentation compliance (30 minutes)

  • Matching shipping papers to loaded cargo
  • Pre-trip checklist completion and retention
  • When to refuse a package and escalation procedures

Our inspection records show RAM vehicles account for 18 of the 92 all-time citations, suggesting certain vehicle designs may have compartment or closure issues. During training, focus on the specific vehicle types in your fleet and their known vulnerabilities.

Document all training with sign-in sheets and knowledge checks. Tie training to performance evaluations.

Should we consider a DataQs challenge if cited?

A DataQs challenge may be appropriate if:

  • The inspector did not physically inspect the package. If the citation was issued based on appearance alone without opening or testing the container, request the inspection report and photograph evidence.
  • The package was compliant at time of inspection but degraded in-transit. If damage occurred after the pre-trip, provide timestamped photos or maintenance records proving the package was sound at dispatch.
  • Documentation error. If the shipping papers were mislabeled but the container itself met standards, challenge the citation as a paperwork issue rather than package integrity.
  • Shipper responsibility. If the package arrived pre-damaged and your pre-trip checklist shows the driver correctly refused or documented it, a challenge may succeed.

DataQs challenges are time-consuming. Given the relatively low citation count (92 all-time), challenge only when you have clear documentary evidence of inspector error or shipper fault. Prioritize prevention over litigation.

How often should we self-audit for package integrity compliance?

Our inspection records show zero citations in the last 90 days and zero in the last 12 months, despite 92 all-time citations. This pattern suggests the violation occurs sporadically rather than as a systemic fleet issue for most operators.

Recommended audit cadence:

  • Monthly self-audit: Observe 3–5 hazmat loads during pre-trip and post-unload. Inspect packages, compartments, and documentation. Document findings and correct deficiencies on the spot.
  • Quarterly deep-dive audit: Audit all hazmat drivers' training records, compartment photographs, and pre-trip checklist completion rates. Identify patterns.
  • Annual comprehensive review: Audit all hazmat vendors and packaging suppliers. Verify compliance certificates, conduct sample inspections of purchased containers, and evaluate compartment maintenance costs.

The absence of recent citations in our database does not mean your fleet is immune. Monthly audits keep hazmat operations visible to management and catch defects before inspectors do. Retain audit reports with your CSA compliance file to demonstrate proactive safety culture if FMCSA requests records.

Last updated: 2026-04-20T15:31:04.915Z Guidance derived from TruckCodex inspection data Read the full article → Quick Q&A →

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.