Bridge load rating vs. span length for abnormal load crossings

A permit comes back with a bridge posted at 40 tons. Your transporter, loaded with a nacelle, is pushing well past that with the trailer and dollies included. Someone on the team pulls up the span length on the county GIS site and says it looks fine, it's only a 60-foot single span, plenty of structure under it. That's the moment a route gets committed to on the wrong read, because span length and load rating are answering two different questions.

What each number actually tells you

Span length is a distance. It's how far the bridge deck runs between supports, whether that's abutment to abutment or pier to pier. It tells you nothing on its own about what the structure can carry. A short span over a culvert can be rated lower than a long span over a river, because the rating comes from a structural analysis of that specific deck, girders, and substructure, done against a known design vehicle, not from how far it stretches.

Load rating is the output of that analysis, usually expressed as the heaviest legal or permit vehicle the bridge can carry safely, under a given configuration. State DOTs run these ratings (often through an AASHTO-based method) and keep them on file per structure, cross-referenced to an NBI number. That rating assumes a specific axle spread and gross weight distribution, which is exactly what an abnormal load configuration doesn't match. A nine-axle trailer spreads weight very differently than the two-axle design truck the rating was built around, and in some cases that works in the haul's favor; in others it doesn't.

So a planner reading span length as a proxy for capacity is reading the wrong column. The number that matters for a structural rating check on a haul route is the posted or calculated rating itself, matched against the actual axle configuration and gross combination weight of the loaded transporter, not a guess based on how long the bridge looks on a map.

Why a culvert can stop a haul before the interstate does

Most abnormal load routes to a wind or solar site don't fail on the big crossings. State-maintained bridges on primary routes tend to have current ratings on file and get checked as a matter of course during permitting. What catches planners out is the small stuff: a county culvert, a private bridge on an old logging road, a rail overpass with a rating sheet last updated before the turbine models being hauled today existed. These structures often carry thin documentation, and a posted weight limit sign at the approach may be the only rating information available in the field.

This is where a pilot-car survey earns its cost or wastes it. Sending a survey crew and a transporter down a route to discover a 15-ton culvert that a records check would have flagged is a mobilization cost nobody budgeted for, and a schedule slip that lands on the project manager's desk, not the logistics planner's. The fix is ordering the checks in the right sequence: confirm the structures and their rated capacity on paper first, then send the crew to verify geometry and clearance on the ground.

Where a desk check fits before the engineer gets a call

A VHR imagery pass over a route reads the physical geometry of a crossing: span count, deck width against the transporter's track width, approach grade at the abutments, and whether a laydown or cribbing area sits nearby if load spreading ends up part of the plan. The rating figure itself lives elsewhere, held by the owner of record and filed against the structure's NBI or county bridge ID, built from an inspection and a load analysis nobody reruns for each permit request. Pairing that imagery read with the DOT's or county's rating sheet, before committing a route to the haul plan, is what a route-and-site constructability read is built to do.

If a bridge, culvert, or approach on your route needs that kind of look before the pilot car goes out, that's the gap Constructability Screening is built to close.