I-5 Skagit River Bridge collapse

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
I-5 Skagit River Bridge
280px
Boats in the water and a helicopter overhead about an hour and a half after the bridge collapse.
Coordinates Lua error in package.lua at line 80: module 'strict' not found.
Carries I‑5
Crosses Skagit River
Locale Mount Vernon, Washington
Maintained by Washington State Department of Transportation
ID number 0004794A0000000
Characteristics
Design Through-truss bridge
Material Steel
Total length 1,112 feet (339 m)
Width 72 feet (22 m)
Number of spans 4
History
Opened 1955
Collapsed May 23, 2013
Statistics
Daily traffic 70925
References
[1]
File:I-5 Skagit River Bridge 32086.JPG
The bridge before the collapse.
File:I-5 Skagit River bridge southbound pre-collapse.jpg
The bridge pre-collapse as seen from the roadbed, showing curved trusswork.

The I-5 Skagit River Bridge collapse occurred on May 23, 2013 in the state of Washington, in the northwestern United States. At approximately 7:00 pm PDT, one bridge span carrying Interstate 5 over the Skagit River collapsed into the river below. Three people in two different vehicles fell with the span; they were rescued by boat and did not sustain serious injury. The cause of the collapse was determined to be an oversize load striking several overhead support beams on the bridge, which led to an immediate collapse of the northernmost span.[2]

The through-truss bridge was built in 1955 and connects the Skagit County cities of Mount Vernon and Burlington. It had recently been evaluated as safe and though not structurally deficient, it was considered "functionally obsolete", meaning it did not meet current design standards. The bridge's design was "fracture-critical"; i.e., it did not have redundant structural members to protect its structural integrity in the event of a failure of one of the bridge's support members. The overhead support structure was known to have been struck by a truck as recently as October 2012. From an engineering standpoint, the bridge actually consists of four consecutive spans which are structurally independent. Only the deck and overhead superstructure of the northernmost span collapsed into the river; the span south of the collapsed span also sustained damage from being struck by the same truck, though not severe enough to result in a collapse. Also, the piers below the deck were not damaged.

Because the bridge collapse severed a vital transportation link between Vancouver, British Columbia and Seattle, replacing the collapsed span became a high priority for the Washington state government. In June 2013 two temporary bridges were erected and placed on the collapsed span's support columns while the permanent bridge was built. In September 2013 the permanent bridges were installed and work began to prevent similar failure of the remaining three spans.

Background

The bridge crosses between Mount Vernon and Burlington, in Washington State, about 60 miles (97 km) north of Seattle. It is part of the primary road transportation route between the metropolitan areas of Seattle and Vancouver, British Columbia. Before the collapse, approximately 71,000 vehicles crossed the bridge every day.[3]

The bridge was built in 1955, a year before the Interstate Highway System was begun. The bridge carries four lanes of traffic, two lanes in each direction. The portions over the river are four consecutive spans, each 160 feet (49 m) long. The spans are built from triangulated steel girders, using a through-truss design where the roadway passes in an open tunnel between the left and right trusses and between the lower and upper truss work. The roadway has relatively limited vertical clearance for tall vehicles due to the upper truss members. The abutted spans share pier footings and appear to be one continuous bridge, but the four spans are actually independent.

The bridge was recently evaluated as safe and in good condition despite being 58 years old; it was not listed as structurally deficient. The bridge was classified as functionally obsolete, in this case because the bridge does not meet current design standards for lane widths and vertical clearance in new highway bridges.[1][4] The bridge was not a candidate for any significant upgrades or replacement and was well-maintained.

Through-truss design

This steel through-truss bridge had a "fracture-critical" design with non-redundant load-bearing beams and joints that are each essential to the whole structure staying intact. An initial failure (perhaps by cracking) of a single essential part can sometimes overload other parts and make them fail, which quickly triggers a chain reaction of even more failures and causes the entire bridge span to collapse. In 2007 the I-35W Mississippi River bridge in Minneapolis collapsed suddenly from slow cracking of a single undersized and over-stressed gusset plate. In steel these initial fractures begin small and take years to grow large enough to become dangerous. Following the Minneapolis incident, such age-related disasters in fracture-critical bridges are now avoided by finding and repairing cracks in a required thorough inspection every two years. Eighteen thousand bridges in the United States are labelled fracture-critical (from their design) and require crack inspections.[5] The Skagit bridge was last inspected for cracks in August and November 2012 with only minor work needed.[6]

Besides fracturing, some bridges with critical non-redundant parts can also suddenly fail from buckling of compressive members, the opposite of tension and cracking. In through-truss bridges the critical compressive parts are the top-chord beams running horizontally along the top of the bridge, parallel to the roadway edges. They carry most of the weight of the bridge and traffic. The chords are normally kept aligned and held in place by vertical posts, diagonals, and sideways sway struts. Top chords will quickly fold if their joints somehow become misaligned. Buckling damage is cumulative, but mostly happens from collision damage or overstresses rather than from age and corrosion.[7]

The vertical clearance for vehicles is limited by the portals and sideways sway structs. These are relatively low in older bridges. In Washington State bridges, the sway struts are often curved downwards at the outer ends, with less clearance above the outer lanes and outer shoulders. Tall loads then need to use the inner lanes for maximal clearance. These bridges are vulnerable to impacts by overheight vehicles, and such impacts were common. There was a known strike on this bridge that occurred on October 22, 2012, and investigators found evidence of several other impacts in years past.[8] Bridge inspection reports dating back to 1979 frequently note damage caused by over-height vehicles, and an inspection report from late 2012 noted a three-inch gash in the steel.[9]

According to Charles Roeder, a professor of civil engineering at the University of Washington in Seattle, through-truss bridges were a common bridge design 50 years ago (there are 10,200 through-truss bridges in the US), but "[i]f you take out some of the top framing, you set that bridge up for a stability failure."[10] Before computers, bridge engineers analyzed truss forces by slide rule, with each calculation being time-consuming. Although the finite element method and plastic design theory, both capable of analyzing redundant structures, had recently been formulated and had seen occasional use, they required significantly more calculation than the simple calculation methods for statically determinate structures, which precluded the use of redundant structural members. A great number of bridges were being designed at that time, and there were insufficient design engineers available to design many bridges as indeterminate structures.[11]

Nowadays, through-truss and other fracture-critical designs are avoided in most new bridges for moderate-sized spans. Using three or more parallel main beams or trusses allows the structure to survive a single component failure.

Incident

File:Skagit River Bridge Collapse.jpg
Crews work at the scene of the collapse on the day following the accident.

The collapse was caused by a southbound semi-trailer truck from Canada hauling an oversize load to Vancouver, Washington, directly damaging sway struts and, indirectly, the compression chords in the overhead steel frame (trusswork) on the northernmost span of the bridge.[12] The vertical clearance from the roadway to the upper arched beam in the outer lane is 14 feet 7 inches (4.45 m), and all trucks with oversize loads are expected to travel in the inside lane where the clearance is around 17 feet (5.2 m). The oversize truck instead entered the bridge in the outer lane, while a second semi-truck and a BMW were passing it in the inner lane.[13] The oversize truck was traveling with a wide and 15 feet 9 inches (4.80 m) tall load, and after the collapse a "dented upper corner and a scrape along the upper side [were] visible on the 'oversize load' equipment casing being hauled on the truck."[14] A pilot car was hired to ensure the load could pass safely. The pilot car never signalled the truck driver that there would be a problem crossing the Skagit bridge[15] and did not warn the trucker to use an inside lane.[16]

The oversize truck completed crossing the bridge while the first span immediately collapsed behind it. Both the driver of the oversized load and the pilot vehicle remained at the scene and cooperated with investigators.[17]

There were no fatalities, but three people were transported to local hospitals[18] after being rescued from their cars. The cars remained on the flooded bridge deck after it fell into the river.[19][20]

The trucker, employed by Mullen Trucking, was hauling an oversize load containing a housing for drilling equipment.[21] The company's vice-president, Ed Sherbinski, said permits were issued from Washington State that included clearance for all bridge crossings on the route.[21] The truck had been led over the bridge by a pilot escort vehicle.[22][23] A spokesman for the Washington State Department of Transportation said there are no warning signs leading up to the bridge regarding its clearance height.[24] In Washington, only overcrossings of less than 14 feet (4.3 m) (the normal legal height limit) are required to have advance postings of height restrictions.[25]

The oversize truck also damaged a sway strut of the second span, but not enough to initiate a collapse. That span was repaired.

Investigation

An NTSB investigator examines the truck that struck the bridge.

This accident was investigated by the Washington State Patrol and the National Transportation Safety Board. NTSB's Preliminary Report[26] attributes the collision to the tall-load truck being in the wrong, outside lane, and being crowded further into the shoulder by the passing truck. It attributes the bridge collapse to the collision taking out multiple sway braces, which destabilized the critical load-bearing (upper chord) members.

Aftermath

Governor Jay Inslee declared an economic "state of emergency" for three surrounding counties (Skagit County, Snohomish County, and Whatcom County) in order to cope with disruption to traffic and the local economy.[27] Traffic on I-5 was detoured around the scene of the collapse on an adjacent bridge upstream. State trooper Sean O'Connell died while directing traffic through the detour when his motorcycle hit a truck.[28] Shortly after the accident, three state lawmakers proposed a bill that would rename the repaired bridge after him.[29]

The collapsed span was temporarily replaced by a pair of two-lane ACROW bridges rolled onto the existing bridge piers. It went into service on June 19.[30] Inspections on the temporary span near the end of July 2013 uncovered that part of an "L" joint that holds the asphalt in place between the temporary bridge and permanent roadway had come loose.[citation needed] The right lane of the bridge was closed for about two hours while crews welded the joint back into place and spread new asphalt.[citation needed]

A $6.87 million contract was awarded to contractor Max J. Kuney Construction of Spokane to design and build a permanent replacement span.[31] It was built alongside the temporary span without interrupting traffic, and moved into place during an overnight closure on September 14–15, 2013.[32] Planned changes to the three remaining overhead spans should allow overheight vehicles to operate in the outer lanes.[33]

The collapse raised questions about how Washington State Department of Transportation regulates oversize vehicles. The department leaves it up to drivers to determine a safe route to their destination, unlike in many other states where routes are assigned. The permit for Mullen Trucking's trip did not specifically note the Skagit River Bridge as a hazard on the route, even though the outer trusses were a full foot lower than the truck; this contrasts with an earlier permit to the same company that included numerous clearance warnings. State lawmakers are exploring making changes to the state's oversize vehicle laws.[9]

The bridge constructed to replace the collapsed bridge has been named the Trooper Sean M. O'Connell Jr. Memorial Bridge.[34]

Washington's infrastructure

Prior to the bridge collapse the Seattle Section of the American Society of Civil Engineers (ASCE) issued the 2013 Report Card for the State of Washington's infrastructure. The state's bridges were given a grade of "C−" (an average score among states). There were 400 structurally deficient bridges in Washington. Thirty-six percent of all bridges are more than 50 years old. The oldest bridges were designed for an expected life of only 50 years; keeping them safe is increasingly difficult and expensive.[35] The advocacy group Transportation for America reports that only 5.10 percent of Washington's bridges are structurally deficient, which is the sixth best in the country.[36]

See also

References

  1. 1.0 1.1 Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. 9.0 9.1 Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. 21.0 21.1 Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  25. http://www.wsdot.wa.gov/NR/rdonlyres/337A7006-8808-4790-85EA-167C8AC39F2E/0/OverheightLoads.pdf
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. 2013 Report Card for Washington's Infrastructure
  36. Lua error in package.lua at line 80: module 'strict' not found.

External links