The story of the I-5 collapse continues to evolve. Currently the focus seems to be on the fact that I-5 (not to mention I-35W) was classified as “fracture-critical”, and the danger it and other fracture critical bridges pose. As there’s a great deal of misinformation being spread about the nature of fracture-critical bridges, an explanation of what it actually means is in order.
Information is still limited, but based on the facts available, it looks as if it was caused by a truck carrying a heavy piece of mining machinery striking a cross member. The 50 year old bridge wasn’t classified as “structurally deficient“, but it was “functionally obsolete”, indicating it probably had less clearance height than a modern bridge.
First off, despite what some news outlets are reporting, there are no indications that the bridge was “unsafe”. Functionally obsolete means things like lane width, approach curvature, clearance, and other nonstructural aspects aren’t up to modern bridge code standards. However, none of this has anything to do with the load carrying capacity of the bridge, or the status of the structural members.
So is this just another example of why we need more infrastructure spending? I’m not so sure.
Consider the failure of the I-35W Bridge from several years ago:
During the wreckage recovery, investigators discovered that gusset plates at eight different joint locations in the main center span were fractured. The Board, with assistance from the FHWA, conducted a thorough review of the design of the bridge, with an emphasis on the design of the gusset plates. This review discovered that the original design process of the I-35W bridge led to a serious error in sizing some of the gusset plates in the main truss…On November 13, 2008, the NTSB released the findings of its investigation. The primary cause was the under-sized gusset plates, at 0.5 inches (13 mm) thick.
Or the infamous Hyatt Regency walkway collapse:
…someone looking at the original details of the connection must have said he had a better idea or an easier way to hang one skywalk beneath the other…But no matter how much more convenient to assemble, the new rod configuration effectively doubled the push of the washer on the box beam supporting the upper walkway’s floor, and this made the already under-designed skywalks barely able to support their own weight.
Or the partial collapse of the Centergy parking deck in Atlanta:
First, the connection holding the fourth floor spandrel beam to the column broke. This caused the beam to slide away from the column. The beam moved away from the garage far enough that the T-beams composing the main floor of the parking deck were bearing on a very thin edge on the ledge of the beam. The concrete of the ledge spalled and as the t-beam fell it pushed the spandrel off of the structure. The fourth floor of the deck fell on top of the floor beneath. The weight of the falling floor overwhelmed the capacity of the floor beneath, and initiated a progressive collapse of the entire bay beneath.
Once you move beyond basic statically determinate cases, engineering problems rapidly become very difficult to solve (leading to some creative solutions in the days before computers). An exact solution often requires the aid of either expensive software packages or extensive calculus training. However, while it might be difficult to, say, calculate the exact bending moment in a beam, it’s often easier to put an upper bound on it’s value. And sometimes, a reasonable upper bound is all you really need.
Here’s a real life example I faced recently. A single-story building has a room dedicated to file storage. In this case, the files are stored in large shelves that can be moved along tracks mounted to the floor. I had to design the concrete slab to support the weight of the files.
As I’ve mentioned before, building codes are highly technical documents, reflecting the latest research in structural behavior. As such, building codes are generally authored by private organizations of engineers, architects, and other experts, rather than by the government. If a jurisdiction wishes to adopt one of these codes, they do so by reference (passing a law which states which code will apply) or by obtaining a license. This method goes back to 1905, when the National Board of Fire Underwriters created the first National Building Code.
These organizations, such as the International Code Council (ICC) or the American Society of Civil Engineers (ASCE), fund their operations by selling copies of the codes they develop. However, common sense (and legal precedent) says that you can’t copyright a law – that if someone wants to pass out photocopies of the code, or host it for free on their website, there’s no legal means of stopping them. Someone suing someone else over the issue thus seems almost inevitable. Surprisingly, it took almost 80 years for that to happen, until the case of BOCA v. Code Tech.