Intermodal Drayage Heavy Haul: Tri-Axle Chassis & Federal Bridge Law Compliance

The Regulatory Reality of Overweight Ocean Container Drayage

Ocean shipping containers loaded with dense commodities such as tile, stone, steel coils, heavy machinery, or liquid bulk in tank containers routinely produce gross weights well above the standard 80,000-pound federal highway limit. A typical 20-foot container may have a tare weight of 5,000-6,500 pounds yet carry 50,000-60,000 pounds of payload. A 40-foot high-cube container can easily reach 90,000-110,000 pounds gross when fully loaded with stone or machinery.

Moving these loads on public highways triggers two distinct but overlapping compliance regimes: (1) state overweight permitting and (2) the Federal Bridge Gross Weight Formula (Formula B) codified at 23 CFR 658.17. Failure to satisfy either exposes the carrier, broker, and driver to severe citations, out-of-service orders, and potential civil penalties that can exceed $10,000 per violation.

Federal Bridge Gross Weight Formula (Formula B)

The Federal Bridge Formula is not a simple axle-count rule. It is a sophisticated engineering calculation designed to protect bridge structures from excessive bending moments and shear forces. The formula is expressed as:

For practical intermodal drayage, the relevant axle groups are typically:

• Steer axle (single)
• Tractor drive tandem (two axles, fixed spread)
• Trailer tri-axle group (three axles on a slider chassis with variable spread from 8 ft 0 in to 12 ft 6 in or greater)

The formula must be satisfied for every possible axle group combination on the vehicle, including the entire five-axle configuration. A 40-foot heavy container loaded to 95,000 pounds will almost always require the tri-axle slider to be positioned at or near its maximum spread to remain compliant.

Tri-Axle Slider Chassis: The Specialized Asset Class

Standard 23-foot spread tandem chassis cannot legally carry most heavy 40-foot ocean containers. Carriers serving port terminals with dense cargo must maintain a dedicated fleet of tri-axle slider chassis. These units typically feature:

• Three 22.5-inch or 275/70R22.5 tires per axle
• Air-ride or spring suspension with slider mechanism allowing 4-6 feet of travel
• Reinforced kingpin and bolster plates rated for 70,000+ pound container loads
• Electronic or manual spread indicators that feed data to the TMS

Asset management within the TMS must track each chassis by unique identifier, current slider position, last inspection date, and maximum legal spread. This data becomes critical input for the compliance engine.

Automated Compliance Engine Architecture in Modern Intermodal TMS

Strong Tower Consulting designs and implements rule-based compliance engines inside enterprise TMS platforms used by intermodal drayage operators. The engine follows a deterministic workflow executed at the time of dispatch planning:

1. Weight Ingestion: The system receives container gross weight from the ocean carrier’s EDI 309 or 322 message, subtracts verified tare weight (maintained in a master container database), and calculates true payload.
2. Asset Matching: A constraint solver evaluates available tri-axle chassis within the terminal radius. Only chassis whose current slider setting plus allowable adjustment can satisfy Formula B for the calculated gross weight are presented to the planner.
3. Axle Distribution Modeling: Using the exact axle spacing table for each chassis (stored as a JSON configuration per asset), the engine computes expected weight on each axle group for multiple slider positions. It applies manufacturer load ratings and state-specific tire weight limits.
4. Bridge Formula Validation: Every possible axle group is tested against the 23 CFR 658.17 formula. If no legal slider position satisfies all groups, the load is flagged for overweight permitting and restricted routing.
5. Corridor & Permit Automation: The routing engine is constrained to state-approved heavy-haul corridors. When gross weight exceeds 80,000 lbs, the system auto-generates the state-specific overweight permit application via API integration with permitting portals (where available) or produces a pre-filled PDF for manual filing. Permit numbers are stored against the load and transmitted to the driver via the ELD application.
6. Driver & Chassis Instruction: The dispatch order includes the required slider position (e.g., “Set tri-axle spread to 12 ft 6 in prior to loading”), axle weight targets, and permitted route segments.

Database Schema Considerations for Compliance

A robust compliance engine requires normalized relational data structures. Key tables include:

• chassis_master - chassis_id, type (triaxle_slider), max_spread_feet, axle_spacing_inches JSON, tire_size, last_inspection
• container_master - container_number, size_ft, tare_weight_lbs, owner
• load_weight_profile - load_id, container_gross_lbs, calculated_payload_lbs, required_min_spread
• bridge_formula_rules - state_code, axle_count, distance_feet, max_weight_lbs (materialized lookup table)
• permit_records - load_id, permit_number, issuing_state, expiration_date, corridor_restrictions JSON

Strong Tower Consulting recommends maintaining a materialized view that pre-calculates allowable gross weights for common chassis configurations and corridor combinations. This dramatically reduces real-time computation during dispatch.

Integration Points with Enterprise Systems

The compliance engine must integrate tightly with several other TMS modules and external systems:

• EDI translation layer for 309, 322, 404, and 990 messages
• Asset management and maintenance scheduling
• ELD / mobile driver application for real-time slider position confirmation and route enforcement
• Accounting system for permit cost allocation and recovery (Transportation Accounting Integration)
• Rate management matrix that applies heavy-haul accessorials automatically (Carrier Rate Matrix Optimization)

Strong Tower Consulting has implemented these integrations for multiple intermodal drayage fleets and 3PL operations. Our TMS Implementation practice focuses on configuring these compliance rules without custom coding when possible, preserving upgrade paths and reducing long-term technical debt.