Anatomy of a Midwest Corridor Empty Mile Problem: What 18 Months of Load Data Showed Us

Empty miles — miles driven by a truck with no freight generating revenue — are one of the more visible forms of inefficiency in truckload brokerage. The number you hear quoted across the industry is that roughly 35% of all truck miles in the U.S. are empty. In practice, that aggregate hides enormous variation by lane, carrier type, and season. Midwest corridors, in particular, have structural backhaul imbalances that show up repeatedly in load data and that mid-market brokers can exploit if they understand the patterns.

Why the Midwest Generates Chronic Backhaul Imbalances

The Midwest is a net freight exporter on certain lane types and a net importer on others, and the directionality of the imbalance varies by commodity and season. The Chicago metro functions as a major inbound distribution hub for retail goods from both coasts and the Gulf. Freight moves heavily into Chicago from Los Angeles, Memphis (distribution hub), and Savannah — then distributes outbound into the secondary Midwest markets.

The result is that outbound lanes from secondary Midwest cities — Columbus, Indianapolis, Louisville, Kansas City — often have less inbound freight to refill before they need to return. Carriers who deliver into Columbus or Indianapolis from Chicago frequently have two options: deadhead back to Chicago empty, or chase available loads in a market that may not have the rate or lane profile they need. This dynamic creates predictable windows of excess capacity in these markets, which shows up as lower spot rates and higher carrier acceptance rates when a broker posts loads originating in these cities.

Understanding which direction and which day of week amplifies this effect is where the data gets interesting.

Chicago–Detroit: Automotive Freight and the Monday Problem

The Chicago–Detroit corridor runs approximately 280 miles and carries significant automotive parts and components volume. Tier 1 and Tier 2 automotive suppliers in the Chicago suburbs ship components to Detroit-area assembly plants on a just-in-time basis. This creates a heavily directional westbound flow — Chicago to Detroit — with a corresponding capacity surplus on the Detroit-to-Chicago return leg.

The Monday pattern is particularly pronounced. Automotive plants typically receive weekend-restocked component inventory on Monday-Tuesday. Loads tendered Monday morning from Chicago-area suppliers to Detroit show significantly higher carrier acceptance rates and more competitive carrier quotes than midweek loads on the same corridor, because carriers who just delivered to Chicago-area distribution centers over the weekend want loads heading toward Detroit before deadheading back.

In 18 months of load data on this corridor, Monday morning Chicago-origin loads to Detroit show an average of 14% lower carrier rates than the same lane midweek, while acceptance rates on those loads are 22 percentage points higher. This is a real pattern — it's the market clearing mechanism for weekend carrier repositioning. Brokers who understand this can advise shippers on tender timing and can build carrier expectations around the pattern rather than being surprised by it.

Chicago–St. Louis: The Agricultural Overlay

The Chicago–St. Louis corridor, roughly 300 miles, carries a broad commodity mix — general merchandise, food and beverage, retail distribution — overlaid with significant agricultural freight flows tied to grain and processed food shipments from central Illinois. This agricultural overlay creates strong seasonal patterns that affect the entire corridor's capacity dynamics.

During harvest season (September–November), outbound agricultural freight from central Illinois distribution points can pull carrier capacity away from Chicago-originating commercial loads. Carriers who normally run Chicago–St. Louis commercial freight may be running agricultural loads from Decatur or Champaign during peak harvest. The net effect is that the Chicago–St. Louis corridor sees spot rate increases of 8–15% above the annual average during late October and early November as commercial shippers compete with elevated agricultural demand for the same carrier capacity pool.

Brokers running significant commercial volume on this corridor need to plan for this annual pattern. Contracted capacity becomes particularly valuable during the harvest window — spot market rates on this corridor can move fast when an early harvest coincides with strong commercial demand. Carriers who specialize in agricultural freight (refrigerated vans, pneumatic bulk trailers) don't directly compete with dry van commercial freight, but they do draw down the overall capacity pool by pulling owner-operators toward the more lucrative agricultural loads.

Indianapolis–Columbus: The Drayage Connection

Indianapolis and Columbus are both major distribution hub markets. Indianapolis serves as a central distribution point for several large retail and e-commerce fulfillment networks; Columbus houses a significant concentration of retail distribution centers. Freight flows between these two markets are relatively balanced, which sounds like a good thing — but balanced volume doesn't mean balanced rates.

The issue is drayage. Both Indianapolis and Columbus have active intermodal facilities. Drayage moves — short hauls between intermodal facilities and warehouses — generate a significant volume of short-distance truck trips that consume local carrier capacity. When intermodal volume spikes (typically with Asian import surges in Q4 pre-holiday), drayage demand in both markets tightens the available carrier pool for over-the-road loads on the Indianapolis–Columbus corridor. Spot rates on this corridor during peak drayage periods can run 10–18% above the corridor average.

This is the kind of granular pattern that doesn't show up in corridor-level rate benchmarks but is plainly visible in load-level data when you look at rate variance by week and correlate it with intermodal container arrival rates at the Indianapolis and Columbus intermodal terminals. It's also the pattern that makes carrier relationship management valuable — carriers who run both drayage and OTR can be steered toward OTR loads during drayage peak periods if you have the relationship capital to ask and offer competitive rates.

Using Backhaul Patterns in Carrier Matching

The practical application of backhaul pattern data in carrier matching is straightforward in concept but requires structured data to execute. The question is: given this load's origin, what carriers are likely to have just delivered nearby and are now repositioning? If a carrier delivered a load to Indianapolis yesterday and needs to get back toward Chicago, a Chicago-origin load tendered today isn't just a business transaction — it's solving the carrier's repositioning problem. That carrier has a higher probability of accepting at or below market because the alternative is deadheading.

ELD location data makes this more tractable. Carriers with active ELD feeds publish location data that allows a carrier matching system to identify trucks that are currently positioned near a load's origin and have recent history suggesting they're in a repositioning mode. This isn't perfect — not all carriers provide location visibility, and the data has latency — but the combination of historical backhaul patterns and real-time location signals improves carrier matching efficiency meaningfully on corridors with well-understood backhaul dynamics.

As we've noted in our article on using ELD data for carrier matching, the coverage and reliability of location feeds vary significantly by carrier size and ELD provider. For small owner-operators who dominate the Midwest backhaul market, location data availability is often the limiting factor rather than the algorithm's sophistication.

What the Data Shows About Rate Floor Opportunities

One of the more counterintuitive findings in Midwest corridor analysis is that brokers who aggressively use backhaul pattern data to tender into excess-capacity windows can achieve better rates on low-volume lanes than on high-volume lanes. The high-volume lanes have more data but also more carrier familiarity with the market — carriers on Chicago–Detroit know their leverage and price accordingly. Low-volume lanes with predictable backhaul surpluses are priced less efficiently because fewer carriers are watching them closely.

A broker who consistently tenders loads on the Indianapolis–Louisville corridor on Wednesday afternoons — a window when carriers who delivered Tuesday from Chicago-area shippers are often positioned in Indianapolis and looking for loads toward the Southeast — can build a rate position on that lane that's 8–12% below the spot market average for similar loads. This advantage compounds over time as the broker builds a carrier panel that knows to watch for those loads at those times. It requires data infrastructure to identify and the discipline to execute against the pattern rather than defaulting to the most familiar carrier at any rate.

Applying This at the Brokerage Level

The brokerages that are capturing these patterns most effectively have built or deployed lane optimization models that treat backhaul availability as a primary input in carrier selection. They're not just asking "which carrier is available?" They're asking "which carriers are likely to be in surplus capacity positions on this lane right now, and what's the market-clearing rate for those carriers today?"

This requires integrating at least three data sources: historical load data showing carrier movement patterns, current DAT load-to-truck ratios for the relevant origin and destination markets, and carrier location signals from ELD integrations. Most mid-market brokerages have access to historical load data in their TMS. The DAT integration is straightforward for platforms that support it. Carrier location data is the gap that requires either direct ELD API integrations or a visibility provider aggregator.

HaulCortex's lane optimization engine incorporates backhaul pattern modeling for Midwest corridors into its carrier matching recommendations. The system identifies which carriers have recent delivery history near load origins and surfaces them ahead of carriers with no location signal, enabling dispatchers to call the highest-probability match first instead of working down a static list.