Prevention FAQ — FMCSR 173.36: Large Bulk Packages
Fleet safety guidance on 173.36 large bulk package requirements. Based on 3 all-time citations and inspection patterns showing 100% OOS rate when cited.
- Code:
- 173.36
- Code System:
- FMCSR
- BASIC Category:
- Hazardous Materials
- OOS Eligible:
- Yes
- Severity Weight:
- 8
- Violation Group:
- Package Integrity - HM
Ranks #2,567 of 3,146 FMCSR codes by citation frequency • OOS rate of 100.0% is above the FMCSR-wide average of 33.3%.
Violation Description
Large bulk packages general requirements
Prevention FAQ for Fleet Managers
Pre-trip discipline, inspector focus, and root-cause fixes
› What specific items do DOT inspectors focus on when checking 173.36 compliance?
Inspectors examine the structural integrity and configuration of large bulk packages themselves—not the vehicle, but the containment unit. Our inspection records show that across the rare 3 all-time citations for this code, 100% of violations resulted in out-of-service placement, indicating inspectors treat package integrity as a critical safety threshold. In Texas, which accounts for recent enforcement activity, inspectors prioritize verifying that bulk packages meet dimensional and construction standards for safe transport. The violation is infrequent nationally (ranked #2551 of 3,036 codes), which means most bulk carriers operate compliant. When cited, however, the severity is absolute—every citation triggers an OOS decision, compared to the all-FMCSR average OOS rate of 31.4%.
› What should bulk package carriers add to their pre-trip inspection checklist?
Create a dedicated large bulk package section covering: (1) external package shell for dents, cracks, or deformation that might compromise containment; (2) all seams, welds, and closures for integrity; (3) valve and fitting functionality and sealing; (4) package certification and compliance documentation attached to or carried with the unit; (5) weight distribution and securement to ensure the load doesn't shift or stress the package structure during transit. Have drivers photograph the package condition at origin and document any pre-existing damage. Because our data shows only 1 citation in the last 90 days and 2 in the last 12 months, most fleets are compliant—use this as your baseline to maintain that performance through consistent pre-trip validation.
› What documentation must drivers carry for 173.36 compliance?
Drivers must carry or have accessible: (1) the large bulk package's original certification or design specification confirming it meets DOT standards; (2) the shipper's declaration of hazardous materials if applicable; (3) loading records showing date, weight, and inspector initials; (4) maintenance or repair records if the package has been serviced; (5) any waivers or exemptions granted by the carrier or manufacturer. Keep records in the cab or on a tablet accessible at roadside inspection. The co-occurring citation pattern shows 1 shared inspection with code 396.3A1 (maintenance repair records), suggesting that incomplete documentation of prior repairs can trigger secondary violations. Maintain a compliance file at the carrier office for each bulk package unit, retained for at least one year.
› What root causes are driving the rare 173.36 citations we see?
Our inspection records across 13 million roadside stops show only 3 citations for 173.36, but the pattern is telling: when violated, it correlates with code 396.3A1 (inspection, repair, and maintenance of parts and accessories) in 1 shared inspection. This suggests the root cause is deferred or improperly documented maintenance—a bulk package may have developed a defect (stress crack, seal failure) that was not properly repaired, re-certified, or documented before return to service. The carriers cited (MIDTEX OIL LP, ROCKY MOUNTAIN CRUDE OIL LLC, SOUTHMARK AVIATION INC) each had 1 citation, indicating this is not a systemic fleet pattern but an isolated equipment or maintenance oversight. Fleet root-cause analysis should focus on: Was the package last inspected? Was damage repaired by a qualified technician? Was the repair documented and approved by the package manufacturer?
› How should a fleet verify repairs before putting a bulk package back in service?
Establish a formal repair verification protocol: (1) upon discovery of damage, immediately take the package out of service and photograph the defect; (2) engage a manufacturer-authorized repair facility or qualified maintenance contractor; (3) require a written repair report documenting the defect, method of repair, materials used, and re-certification of package integrity; (4) conduct a secondary visual inspection by fleet safety personnel—do not rely on the repair vendor alone; (5) update the package maintenance log with date, repair description, technician name, and authorization signature; (6) retain the repair report in the compliance file. Because 100% of 173.36 citations result in OOS placement, a single failure can halt operations—prevention through rigorous repair verification pays immediate dividends. Before returning to service, have the driver perform the same inspection checklist used for pre-trips, with supervisor sign-off.
› What should a fleet review after receiving a 173.36 citation?
Post-citation review must cover: (1) When was the package last inspected by the manufacturer or certified technician? (2) Had any damage or wear been reported by drivers but not addressed? (3) Was the package repair, if any, done by an authorized vendor and documented? (4) Did the fleet safety manager perform a pre-citation audit of that specific package? (5) Were all co-drivers trained on large bulk package pre-trip checklist items? Run a fleet-wide audit of all large bulk packages in service—compare each unit's inspection records to your internal logs. Because our data shows 2 citations in the last 12 months and 1 in the last 90 days, violations are trending low, but a citation indicates a gap in your maintenance or documentation system. Interview the cited driver on what they observed before the stop and whether they reported concerns. Use findings to refine pre-trip training and repair-authorization procedures.
› How does a 173.36 citation affect my carrier's CSA Vehicle Maintenance BASIC?
A 173.36 citation contributes to your Vehicle Maintenance BASIC score, which is one of seven CSA Basics FMCSA tracks. The violation triggers immediate out-of-service placement (100% OOS rate in our data), signaling to auditors that package integrity failures are catastrophic. While 173.36 itself ranks #2551 nationally by citation frequency and is rare, the weight it carries in CSA scoring is disproportionate because it reflects a fundamental safety failure—large bulk packages contain hazardous materials, and structural failure could result in spill, fire, or environmental contamination. A single citation can elevate your fleet's Vehicle Maintenance BASIC percentile if you have a small inspection count, or flatten an otherwise clean record. Compare this to peer codes: loading/unloading hazmat violations (177.834A-HMC and 177.834(a)) generate thousands of citations and 97–99% OOS rates but are more common. Treat 173.36 as a high-severity issue in your CSA mitigation strategy.
› What training topics should drivers receive to prevent 173.36 violations?
Design driver training covering: (1) How to visually inspect a large bulk package for structural integrity—dents, cracks, weld damage, valve leaks—before accepting a load; (2) How to identify stress points on the package (areas prone to failure during acceleration, braking, or cornering); (3) When and how to report damage to dispatch and refuse transport if safety is compromised; (4) Documentation requirements—how to read package certification labels and where to find maintenance records; (5) How to secure a large bulk package to the vehicle to minimize vibration and stress during transit. Train on the specific vehicle makes cited in our data: HEIL, INTL, KW, and STLG. Each make has different mounting systems and seal configurations—ensure drivers understand their assigned vehicle type. Conduct refresher training annually and after any maintenance event. Because violations are rare (3 all-time, 1 in 90 days), use this as your training talking point: 'Compliance is the norm—here's how we stay that way.'
› When should a fleet file a DataQs challenge for a 173.36 citation?
File a DataQs challenge if: (1) inspection records show the package was certified and compliant at time of stop—the inspection photo or report contradicts the citation; (2) you have documented proof that the package was repaired or re-certified between the last inspection and the cited stop, and the inspector cited a pre-repair defect; (3) the citation document lacks specific detail about the defect (a citation that simply states 'package non-compliant' without describing the structural failure); (4) two independent inspectors or your manufacturer differ on whether the package is still serviceable. Because only 3 all-time citations exist in our database, incorrect citations carry outsized weight on your compliance record. Gather photographic evidence, maintenance records, and manufacturer communications before filing. DataQs challenges require documentation—do not proceed without it. Most 173.36 citations will be accurate given the rarity and severity, but a defensible challenge can correct a false record.
› How often should a fleet audit large bulk packages for 173.36 compliance?
Our inspection records show 1 citation in the last 90 days and 2 in the last 12 months—enforcement is sporadic but absolute when triggered. Establish a quarterly audit cycle for all large bulk packages in your fleet: (1) visually inspect each package for structural damage; (2) verify maintenance records are current and filed; (3) confirm manufacturer certifications are not expired; (4) review driver pre-trip reports for that unit over the past three months. Additionally, perform an immediate inspection after any incident—hard braking, accident, extreme weather, or driver report of unusual sounds or vibration. Because the OOS rate is 100% when citations occur, a single compliance failure can ground an asset. The citation trend (1 in 90 days vs. 2 in 12 months) suggests enforcement activity is low but tightening—anticipate more roadside focus on bulk packages in the coming months. Use quarterly audits as your early-warning system to catch defects before an inspector does.
Top Enforcing States
Where 173.36 is most commonly cited (last 180 days)
Related Records
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.
Vehicle recall campaigns, defect investigations, and consumer safety complaints (SCRS).
Cross-border carrier registry and Canadian recall campaigns where applicable.
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.