This is a good article. Click here for more information.
Listen to this article

I-35W Mississippi River bridge

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

I-35W Mississippi River bridge
picture of the bridge painted green and surrounded by green foliage seen from the Mississippi bank
Bridge 9340 in May 2006
Coordinates Lua error in package.lua at line 80: module 'strict' not found.
Carries 8 lanes of I-35W
Crosses Saint Anthony Falls/Mississippi River
Locale Minneapolis, Minnesota, U.S.
Official name Bridge 9340
Maintained by Minnesota Department of Transportation (Mn/DOT)
ID number 9340
Characteristics
Design Continuous truss bridge
Total length 1,907 ft (581.3 m)
Width 113.3 ft (34.5 m)
Height 115 ft (35.1 m)
Longest span 456 ft (139 m)[1]
Clearance below 64 ft (19.5 m)
History
Construction begin 1964[2]
Opened November 1967
Collapsed August 1, 2007
Statistics
Daily traffic 140,000[3]

The I-35W Mississippi River bridge (officially known as Bridge 9340) was an eight-lane, steel truss arch bridge that carried Interstate 35W across the Saint Anthony Falls of the Mississippi River in Minneapolis, Minnesota, United States. During the evening rush hour on August 1, 2007, it suddenly collapsed, killing 13 people and injuring 145. The bridge was Minnesota's third busiest,[4][5] carrying 140,000 vehicles daily.[3] The NTSB cited a design flaw as the likely cause of the collapse, noting that a too-thin gusset plate ripped along a line of rivets, and asserted that additional weight on the bridge at the time of the collapse contributed to the catastrophic failure.[6]

Immediately after the collapse, help came from mutual aid in the seven-county Minneapolis-Saint Paul metropolitan area and emergency response personnel, charities, and volunteers.[7][8][9] Within a few days of the collapse, the Minnesota Department of Transportation (Mn/DOT) planned a replacement bridge, the I-35W Saint Anthony Falls Bridge. Construction was completed rapidly, and it opened on September 18, 2008.[10][11]

Location and site history

aerial map of the area with the former bridge in red
Bridge location in red

Located in Minneapolis, Minnesota's largest city, the bridge connected the Minneapolis neighborhoods of Downtown East and Marcy-Holmes. The south abutment was northeast of the Metrodome, and the north abutment was northwest of the University of Minnesota East Bank campus. The bridge was the southeastern boundary of the "Mississippi Mile" downtown riverfront parkland.[12] Downstream is the 10th Avenue Bridge, once known as the Cedar Avenue Bridge. Immediately upstream is the lock and dam at Saint Anthony Falls, where Minneapolis began. The first bridge upstream is the historic Stone Arch Bridge, built for the Great Northern Railway and now used for bicycle and pedestrian traffic.[13]

The north foundation pier of the bridge was near a hydroelectric plant, razed in 1988. The south abutment was in an area polluted by a coal-to-gas processing plant[14][15][16][17] and a facility for storing and processing petroleum products.[15] These uses effectively created a toxic waste site under the bridge, leading to a lawsuit and the removal of the contaminated soil.[14][15][18][19][20] No relationship between these prior uses and the bridge failure has been claimed.

Design and construction

External video
I-35W bridge structure before collapse.jpg
video icon When a Bridge Falls, Retro Report[21]
the bridge painted green and the street below it
I-35W bridge south end seen from West River Parkway
aerial photo of the bridge next to the 10th Avenue bridge
I-35W bridge (center left) west of the 10th Avenue Bridge (center right), 2004

The bridge, officially designated "Bridge 9340", was designed by Sverdrup & Parcel to 1961 AASHO (American Association of State Highway Officials, now American Association of State Highway and Transportation Officials) standard specifications. The construction contracts, worth in total more than US$5.2 million at the time, went to Hurcon Inc. and Industrial Construction Company,[22] which built the steel trusses and deck. Construction on the bridge began in 1964 and the structure was completed and opened to traffic in 1967 [23][24] during an era of large-scale projects related to building the Twin Cities freeway system.[25] When the bridge fell, it was still the most recent river crossing built on a new site in Minneapolis.[26] After the building boom ebbed during the 1970s, infrastructure management shifted toward inspection and maintenance.[25][27]

The bridge's fourteen spans extended 1,907 feet (580 m) long. The three main spans were of deck truss construction while all but two of the eleven approach spans were steel multi-girder construction, the two exceptions being concrete slab construction. The piers were not built in the navigation channel; instead, the center span of the bridge consisted of a single 458-foot (140 m) steel arched truss over the 390-foot (119 m) channel. The two support piers for the main trusses, each with two load-bearing concrete pylons at either side of the center main span, were located on opposite banks of the river.[28][29] The center span was connected to the north and south approaches by shorter spans formed by the same main trusses. Each was 266 feet (81 m) in length, and was connected to the approach spans by a 38 foot (11.6 m) cantilever.[23][30] The two main trusses, one on either side, ranged in depth from 60 feet (18.3 m) above their pier and concrete pylon supports, to 36 feet (11 m) at midspan on the central span and 30 feet (9 m) deep at the outer ends of the adjoining spans. At the top of the main trusses were the deck trusses, 12 feet (3.6 m) in depth and integral with the main trusses.[24] The transverse deck beams, part of the deck truss, rested on top of the main trusses. These deck beams supported longitudinal deck stringers 27 inches (69 cm) in depth, and reinforced-concrete pavement.[24][30] The deck was 113 ft 4 in (34.5 m) in breadth and was split longitudinally. It had transverse expansion joints at the centers and ends of each of the three main spans.[24][31] The roadway deck was approximately 115 feet (35 m) above the water level.[32]

Black ice prevention system

On December 19, 1985, the temperature reached −30 °F (−34 °C). Cars coming across the bridge experienced black ice and there was a major pile up on the bridge on the northbound side. In February and December 1996, the bridge was identified as the single most treacherous cold-weather spot in the Twin Cities freeway system, because of the almost frictionless thin layer of black ice that regularly formed when temperatures dropped below freezing. The bridge's proximity to Saint Anthony Falls contributed significantly to the icing problem and the site was noted for frequent spinouts and collisions.[33][34]

By January 1999, Mn/DOT began testing magnesium chloride solutions and a mixture of magnesium chloride and a corn-processing byproduct to see whether either would reduce the black ice that appeared on the bridge during the winter months.[35] In October 1999, the state embedded temperature-activated nozzles in the bridge deck to spray the bridge with potassium acetate solution to keep the area free of winter black ice.[36][37] The system came into operation in 2000.[38][39]

Although there have been no more major multi-vehicle collisions since the automated de-icing system was installed, it has been raised as a possibility that the potassium acetate may have contributed to the collapse of the 35W bridge by corroding the structural supports.[40]

Maintenance and inspection

closeup aerial of a section of the bridge next to a section of the 10th Avenue bridge
I-35W bridge (left) in 2006
bridge painted green seen from the Mississippi bank
The bridge seen from below in 2006

Since 1993, the bridge was inspected annually by Mn/DOT, although no inspection report was completed in 2007, due to the construction work.[22] In the years prior to the collapse, several reports cited problems with the bridge structure. In 1990, the federal government gave the I-35W bridge a rating of "structurally deficient," citing significant corrosion in its bearings. Approximately 75,000 other U.S. bridges had this classification in 2007.[22][41]

According to a 2001 study by the civil engineering department of the University of Minnesota, cracking had been previously discovered in the cross girders at the end of the approach spans. The main trusses connected to these cross girders and resistance to motion at the connection point bearings was leading to unanticipated out-of-plane distortion of the cross girders and subsequent stress cracking. The situation was addressed prior to the study by drilling the cracks to prevent further propagation and adding support struts to the cross girder to prevent further distortion. The report also noted a concern about lack of redundancy in the main truss system, which meant the bridge had a greater risk of collapse in the event of any single structural failure. Although the report concluded that the bridge should not have any problems with fatigue cracking in the foreseeable future, regular inspection, structural health monitoring, and use of strain gauges had been suggested.[23]

In 2005, the bridge was again rated as "structurally deficient" and in possible need of replacement, according to the U.S. Department of Transportation's National Bridge Inventory database.[42] Problems were noted in two subsequent inspection reports.[43][44] The inspection carried out June 15, 2006 found problems of cracking and fatigue.[44] On August 2, 2007, Governor Tim Pawlenty stated that the bridge had been scheduled to be replaced in 2020.[45]

The I-35W bridge ranked near the bottom of federal inspection ratings nationwide. Bridge inspectors use a sufficiency rating that ranges from the highest score, 100, to the lowest score, zero. In 2005, they rated the bridge at 50, indicating that replacement may have been in order. Out of over 100,000 heavily used bridges, only about 4% scored below 50. On a separate measure, the I-35W bridge was rated "structurally deficient," but was deemed to have met "minimum tolerable limits to be left in place as it is."[43][44][46]

In December 2006, a steel reinforcement project was planned for the bridge. However, the project was canceled in January 2007 in favor of periodic safety inspections, after engineers realized that drilling for the retrofitting would, in fact, weaken the bridge. In internal Mn/DOT documents, bridge officials talked about the possibility of the bridge collapsing, and worried that they might have to condemn it.[47]

The construction taking place in the weeks prior to the collapse included joint work and replacing lighting, concrete and guard rails. At the time of the collapse, four of the eight lanes were closed for resurfacing,[48][49][50][51] and there were 575,000 pounds (261,000 kg) of construction supplies and equipment on the bridge.[52]

Collapse

animated GIF of the bridge collapse
Security camera images show the collapse in animation, looking north.
The bridge as seen from above after the collapse
Perhaps a dozen cars in view of the wreckage
Cars that were on the bridge when it collapsed remain on the wreckage. They were numbered as part of the investigation.
R.T. Rybak in a red poncho looking at the collapsed bridge in the water
Mayor R. T. Rybak surveys the collapsed bridge

At 6:05 p.m. CDT on Wednesday, August 1, 2007, with rush hour bridge traffic moving slowly through the limited number of lanes, the central span of the bridge suddenly gave way, followed by the adjoining spans. The structure and deck collapsed into the river and onto the riverbanks below, the south part toppling 81 feet (25 m) eastward in the process.[53] A total of 111 vehicles[54] were involved, sending their occupants and 18[55] construction workers as far as 115 feet (35 m)[32] down to the river or onto its banks. Northern sections fell into a rail yard, landing on three unoccupied and stationary freight cars.[56][57][58][59]

Sequential images of the collapse were taken by an outdoor security camera located at the parking lot entrance of the control facility for the Lower Saint Anthony Falls Lock and Dam.[60][61] The immediate aftermath of the collapse was also captured by a Mn/DOT traffic camera that was facing away from the bridge during the collapse itself.[62] The federal government immediately launched a National Transportation Safety Board (NTSB) investigation. NTSB chairman Mark Rosenker, along with a number of investigators, arrived on scene 9 hours after the collapse. Rosenker remained in Minneapolis for nearly one week, serving as the government's designated primary interface with federal, state and local officials as well as briefing the press on the status of the investigation.

Mayor R. T. Rybak and Governor Tim Pawlenty declared a state of emergency for the city of Minneapolis[63] and for the state of Minnesota[64] on August 2, 2007. Rybak's declaration was approved and extended indefinitely by the Minneapolis City Council the next day.[65] As of the morning following the collapse, according to White House Press Secretary Tony Snow, Minnesota had not requested a federal disaster declaration.[66] President Bush pledged support during a visit to the site on August 4 with Minnesota elected officials and announced that United States Secretary of Transportation (USDOT) Mary Peters would lead the rebuilding effort. Rybak and Pawlenty gave the president detailed requests for aid during a closed-door meeting.[63][67] Local authorities were assisted by the Federal Bureau of Investigation (FBI) evidence team,[68] and by United States Navy divers who began arriving on August 5, 2007.[69]

Victims

Only a few of the vehicles were submerged, but many people were stranded on the collapsed sections of the bridge. Several involved vehicles caught fire, including a semi-trailer truck, from which the driver's body was later pulled. When fire crews arrived, they had to route hoses from several blocks away.[70][71][72]

A school bus carrying 63 children ended up resting precariously against the guardrail of the collapsed structure, near the burning semi-trailer truck. The children were returning from a field trip to a water park as part of the Waite House Neighborhood Center Day Camp based out of the Phillips community. Jeremy Hernandez, a 20-year-old staff member on the bus, assisted many of the children by kicking out the rear emergency exit and escorting or carrying them to safety.[73] One youth worker was severely injured.[74]

Thirteen people were killed.[75] Triage centers at the ends of the bridge routed 50 victims to area hospitals, some in trucks, as ambulances were in short supply.[76] Many of the injured had blunt trauma injuries. Those near the south end were taken to Hennepin County Medical Center (HCMC) — those near the north end, to the Fairview University Medical Center and other hospitals. At least 22 children were injured. Thirteen children were treated at Children's Hospitals and Clinics of Minnesota,[77] five at HCMC and four or five at North Memorial Medical Center in Robbinsdale, Minnesota.[78] During the first 40 hours, 11 area hospitals treated 98 victims.[77]

About 1,400 people gathered for an interfaith service of healing held at St. Mark's Episcopal Cathedral on August 5, 2007, when many of the victims were still missing. Among the presenters were representatives of the Christian, Islamic, Jewish, Hindu, Native American and Hispanic communities, police, fire and emergency responders, the governor, the mayor, a choir and several musicians.[79] Minnesotans held a minute of silence during National Night Out, on August 7, 2007, at 6:05 pm.[80] On August 8, 2007, the Twin Cities chapter of the American Red Cross lowered the flags of the United States, the state of Minnesota and the American Red Cross in remembrance of the victims of the tragedy.[81] Gold Medal Park near the Guthrie Theater was a gathering place for those who wished to leave flowers or remembrances for those who died.[82] During an address to the city council on August 15, 2007, Rybak remembered each of the victims and "the details of their lives."[83]

The families of the deceased, survivors, and first responders who were directly impacted by the bridge collapse—together estimated at at least several hundred people—did not have United States disaster insurance for individuals. Sandy Vargas, president and CEO of the Minneapolis Foundation, one of seven foundations that form Minnesota Helps, believes the Minnesota Helps Bridge Disaster Fund cannot cover the uninsured medical costs for the victims of the bridge collapse. The fund may be able to make small grants as a gesture of acknowledgment.[84]

Pawlenty and his office, during the last week of November, announced a "$1 million plan" for the victims. State law has limits that may limit awards to below that amount. No legislative action was needed for this step. "The administration wanted approval from the Joint House-Senate Subcommittee on Claims as a sign of bipartisan support"—which it received.[85] On May 2, 2008, the state of Minnesota reached a $38 million agreement to compensate victims of the bridge collapse.[86]

Nearly a decade after the incident, Mohamed Roble, one of the victims of the Minnesota River bridge collapse, is believed to be a member of ISIS according to court testimony.[87]

Rescue

Four persons running and about four police cars from various services
University of Minnesota Police and Minnesota State Patrol, day of the collapse

Civilians immediately took part in the rescue efforts. Minneapolis and Hennepin County received mutual aid from neighboring cities and counties throughout the metropolitan area.[88] The Minneapolis Fire Department (MFD) arrived in six minutes[89] and responded quickly, helping people who were trapped in their vehicles. They took 81 minutes to triage and transport 145 patients with the help of Hennepin County Medical Center (HCMC), North Memorial and Allina paramedics. By the next morning, they had shifted their focus to the recovery of bodies, with several vehicles known to be trapped under the debris and several people still unaccounted for. Twenty divers organized by the Hennepin County Sheriff's Office (HCSO) used side-scan sonar to locate vehicles submerged in the murky water. Their efforts were hampered by debris and challenging currents. The United States Army Corps of Engineers (USACE) lowered the river level by two feet (60 cm) downriver at Ford Dam to allow easier access to vehicles in the water.[59][90][91][92] Carl Bolander & Sons, a Saint Paul-based earthworks and demolition company, brought in several cranes and other heavy machinery to assist in clearing debris for rescue workers.

Emergency personnel running on the collapsed bridge and two Minneapolis Fire Department boats in the water with dozens of observers on the bank of the Mississippi
Ninety-three people were rescued from the collapsed bridge. Minneapolis Fire Department boats on the Mississippi River took about twenty people. The rescue lasted about three hours.[76]

The Minneapolis Fire Department[89] (MFD) created the National Incident Management System command center in the parking lot of the American Red Cross and an adjacent printing company[8] on the west bank. The Minneapolis Police Department (MPD) secured the area, MFD managed the ground operations, and HCSO was in charge of the water operation.[93] The city provided 75 firefighters and 75 law enforcement units.[63]

Rescue of victims stranded on the bridge was complete in three hours.[76] "We had a state bridge, in a county river, between two banks of a city. ... But we didn't have one problem with any of these issues, because we knew who was in charge of the assets," said Rocco Forte, city Emergency Preparedness Director.[8] City, metropolitan area, county and state employees at all levels knew their roles and had practiced them since the city received FEMA emergency management training the year following 9/11.[94] Their rapid response time is also credited to the Minnesota and United States Department of Homeland Security (DHS) investment in 800 MHz mobile radio communications that were operating in Minneapolis and three of the responding counties,[7][95] the city of Minneapolis collapsed-structures rescue and dive team,[63] and the Emergency Operations Center established at 6:20 p.m. in Minneapolis City Hall.[8][89]

Recovery

Navy recovery operation on the bank of the Mississippi with the twisted wreckage
United States Navy divers in the recovery operation, diving from a United States Army Corps of Engineers barge
emergency landing of a helicopter on the 10th Avenue bridge seen from the bank amid green foliage
Helicopter and airboat on the 10th Avenue Bridge

Recovery of victims took over three weeks. At the request of the NTSB Chairman Mark Rosenker, the Navy sent 17 divers and a five-person command-and-control element from their Mobile Diving and Salvage Unit (MDSU) 2 (TWO).[69] Divers and Underwater Search Evidence Response Team from the FBI joined the response efforts on August 7, bringing with them "truck-loads" of specialized equipment including FBI-provided side-scan sonar and two submarines.

The Navy team started looking in the river at 2 a.m.. The FBI teams had planned to search with an unmanned submarine, but had to abandon this plan after they found it was too big to maneuver in the debris field and cloudy water. Minneapolis Police Captain Mike Martin stated that, "The public safety divers are trained up to a level where they can kind of pick the low-hanging fruit. They can do the stuff that's easy. The bodies that are in the areas where they can sweep shore to shore, the vehicles that they can get into and search that weren't crushed. They were able to remove some of those. Now what we're looking at is the vehicles that are under the bridge deck and the structural pieces."[96][97][98]

Seventy-five local, state and federal agencies[93] were involved in the rescue and recovery including emergency personnel and volunteers from the counties of Anoka; Carver; Dakota; Hennepin; Olmsted; Ramsey; Scott; Washington; Winona and Wright in Minnesota; and St. Croix County, Wisconsin, St. Croix EMS & Rescue Dive Team, and others standing by.[99][100][101] Federal assistance came from the United States Department of Defense, DHS, USACE and the United States Coast Guard. Adventure Divers of Minot, North Dakota, is a private firm who assisted local authorities.[99]

Local businesses donated wireless Internet, ice, drinks and meals for first responders.[102] Teams of officers were sent to hospitals to follow up with the injured, who had been transported to eight different medical facilities.

The Minneapolis Police Chaplain Corps Chaplain Director, Dr. Jeffrey Stewart, arrived and was asked to work on arrangements for the Family Assistance Center. He coordinated site location and staffing arrangements with the City’s Department of Health and Family support and relevant Hennepin County offices.[103] When Chaplain Supervisor John LeMay and Lead Chaplain Linda Koelman arrived on the scene, they assisted in setting up the FAC at the Holiday Inn by 2000hrs. As additional Minneapolis Police Chaplains arrived, they began providing services to the victim families, assisting them in locating family members, and providing a calm presence. On August 20, the last victim was recovered from the river.[104]

The Salvation Army canteens served food and water to rescue workers.

A Mayo Clinic transport helicopter was standing by at Flying Cloud Airport.[101] The Minnesota National Guard launched a MEDEVAC helicopter and had up to 10,000 guard members ready to help.[93]

As of August 8, 2007, more than 500 Red Cross volunteers and staff persons counseled 2,000 people with grief, trauma, missing persons, and medical issues, and served 7,000 meals to first responders.[81]

Mary Peters and escort and Sheriff Richard Stanek looking
Col. Michael Chesney, Transportation Secretary Mary Peters, Hennepin County Sheriff Richard Stanek

Following the initial rescue, Mn/DOT retained Carl Bolander & Sons, an earthworks and demolition contractor of Saint Paul, Minnesota, to remove the collapsed bridge and demolish the remaining spans that did not fall. Divers left the water briefly on August 18 while the company's crew used cranes, excavation drills and cutting torches to remove parts of the bridge deck, beams and girders, hoping to improve access for the divers.[105] After the last person's remains were pulled from the wreckage on August 21, the company's crews began dismantling the bridge's remnants.[106] Crews first removed the vehicles stranded on the bridge. By August 18, 80 of the 88 stranded cars and trucks had been moved to the MPD impound lot[107] where owners could claim their vehicles.[105][108] Then workers shifted to removing the bridge deck using cranes and excavators equipped with hoe rams to break the concrete. Structural steel was then disassembled by cranes, and the concrete piers were removed by excavators. National Transportation Safety Board (NTSB) officials asked demolition crews to use extreme care in removing the bridge remnants to preserve as much of the bridge materials as possible for later analysis. By the end of October 2007, the demolition operation was substantially complete, enabling construction to begin on the new I-35W bridge on November 1, 2007. Much of the bridge debris was temporarily stored at the nearby Bohemian Flats as part of the ongoing investigation of the collapse; it was removed to a storage facility in Afton, Minnesota, in the fall of 2010.[109] Federal officials planned to bring some of the bridge steel and concrete to the NTSB Material Laboratory in Washington, D.C., for analysis toward determining the cause of the collapse on behalf of FHWA, Mn/DOT and Progressive Construction, Inc. NTSB also interviewed eyewitnesses.[110]

In the center Donald C. Winter former Secretary of the Navy viewing the I-35W Bridge Collapse site. To the left, one can also see Governor Tim Pawlenty.

Peters announced that USDOT had granted Minnesota US$5 million the day following the collapse.[111] On August 10, Peters announced an additional US$5 million "for Minneapolis", or "the state", "to reimburse Minneapolis for increased transit operations to serve commuters in the wake of last week’s bridge collapse".[112] U.S. Congress removed the US$100 million per-incident cap on emergency appropriations. The United States House of Representatives and United States Senate each voted unanimously for US$250 million in emergency funding for Minnesota that President Bush signed into law on August 6.[113][114] On August 10, 2007 Peters announced US$50 million in immediate emergency relief. The Associated Press clarified that the US$50 million was a downpayment on the US$250 million that has yet to be approved by appropriations committees.[114][115] Minnesota could use the immediate relief for "clean-up and recovery work, including clearing debris and re-routing traffic, as well as for design work on a new bridge".[112] "On behalf of Minnesota, we are grateful for all of this help," Pawlenty said.[116]

Investigation

FBI and Hennepin County recovery operations lowering sonar into the river
FBI evidence team and Hennepin County sheriff's deputies lowering sonar
fracture seen in part of the bridge
This image, from the National Transportation Safety Board's Office of Research and Engineering, shows a fracture in a gusset plate that played a key role in the collapse of the Interstate 35W bridge. (National Transportation Safety Board photo)
Picture taken in June 2003, released by the National Transportation Safety Board, showing bowed gusset plates

The National Transportation Safety Board immediately began a comprehensive investigation that was expected to take up to eighteen months.[117][118] Immediately following the collapse, Governor Pawlenty and Mn/DOT announced that the Illinois-based engineering firm of Wiss, Janney, Elstner Associates, Inc. had also been selected to provide essential analysis that would parallel the investigation being conducted by the NTSB.[119] One week after the collapse, workers were just beginning to move debris and vehicles to further the process of recovering victims. Cameras and motion detectors were added to the site around the bridge to ward off intruders who, officials said, were hindering the investigation.[120] Hennepin County Sheriff Richard W. Stanek stated, "We are treating this as a crime scene at this point. There's no indication there was any foul play involved, [but] it's a crime scene until we can determine what was the cause of the collapse."[121]

An employee of the NTSB had written his doctoral thesis on possible failure scenarios of this specific bridge while he was a student at the nearby University of Minnesota. That thesis, including his computer model of the bridge for failure mode analysis, was used by the NTSB to aid in its investigation.[58][122] The Federal Highway Administration (FHWA) built a computer model of the bridge at the Turner Fairbank Highway Research Center in McLean, Virginia.[110] NTSB investigators were particularly interested in learning why a part of the bridge's southern end shifted eastward as it collapsed,[123] but soon ruled that out as a starting point, and shifted focus to the north end of the structure.[53]

Officials with DHS said there was no indication that terrorism was involved.[124] Although officials emphasized that the cause of the collapse had not yet been determined, Peters cautioned states to "remain mindful of the extra weight construction projects place on bridges."[125] Within days, bridge inspections were stepped up throughout the United States.[126]

FHWA advised states to inspect the 700 U.S. bridges of similar construction[127] after identifying a possible design flaw related to large steel sheets called gusset plates, which connect girders in the truss structure.[128][129] Officials raised questions as to why such a flaw would not have been discovered in over 40 years of inspections.[129] The flaw was first discovered by Wiss, Janney, Elstner Associates, Inc., an independent consulting firm hired by Mn/DOT to investigate the cause of the collapse.[129]

On January 15, 2008, the NTSB announced it had determined that the bridge's design specified steel gusset plates that were undersized and inadequate to support the intended load of the bridge,[130] a load that had increased over time.[131] This assertion was based on an interim report that calculated the demand-to-capacity ratio for the gusset plates.[130] The NTSB recommended that similar bridge designs be reviewed for this problem.[130][132][133]

"Although the Board's investigation is still on-going and no determination of probable cause has been reached, interim findings in the investigation have revealed a safety issue that warrants attention," said NTSB Chairman Mark Rosenker. "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."[6]

On March 17, 2008, the NTSB announced an update on the investigation relating to load capacity, design issues, computer analysis and modeling, digital image analysis and analysis of the undersized and corroded gusset plates. The investigation revealed that photos from a June 2003 inspection of the bridge showed gusset-plate bowing.[134][135]

On November 13, 2008, the NTSB released the findings of its investigation. The primary cause was the undersized gusset plates, at 0.5 inches (13 mm) thick. Contributing to that design or construction error was the fact that 2 inches (51 mm) of concrete were added to the road surface over the years, increasing the static load by 20%. Also contributing was the extraordinary weight of construction equipment and material resting on the bridge just above its weakest point at the time of the collapse. That load was estimated at 578,000 pounds (262,000 kg), consisting of sand, water and vehicles. The NTSB determined that corrosion was not a significant factor, but that inspectors did not routinely check that safety features were functional.[136]

Lawsuits

In August 2010, the last of the lawsuits against URS Corporation were settled for $52.4M to avoid prolonged litigation. The cases were handled via a novel consortium of legal entities that worked on a pro-bono basis.[137][138] URS had performed fatigue analysis consulting on the bridge for the Mn/DOT.

As of August 1, 2011, the lawsuit brought by the state of Minnesota against Jacobs Engineering Group, the successor of Sverdrup & Parcel, the firm that designed the bridge, was still pending.[139] In May 2012, the United States Supreme Court turned down an appeal by Jacobs who argued too much time had passed since the 1960s design work, allowing the state of Minnesota suit to proceed.[140] To avoid protracted litigation, Jacobs paid $8.9 million in Nov. 2012 to settle the suit without admitting wrongdoing.[141]

Impacts on business, traffic, and transportation funding

overhead road closed sign over freeway
Closure sign on Interstate 35W

The collapse of the bridge affected river, rail, road, bicycle and pedestrian, and air transit. Pool 1, created by Ford Dam, was closed to river navigation between mile markers 847 and 854.5.[142][143] A rail spur switched by the Minnesota Commercial Railway was blocked by the collapse.[144] The Grand Rounds National Scenic Byway bike path was disrupted as well as two roads, West River Parkway and 2nd Street SE. The 10th Avenue Bridge, which parallels this bridge about a block downstream, was closed to both vehicle and pedestrian traffic until August 31. The Federal Aviation Administration restricted pilots in the 3-nautical-mile (5.6 km) radius of the rescue and recovery.[145]

Thirty-five people lost their jobs when Aggregate Industries of Leicestershire, UK, a company that delivered construction materials by barge, cut production in the area.[146]

dejected looking young men and crowd in front of a section of the collapsed bridge
A section of the collapsed bridge

Small businesses in metropolitan area counties that were harmed by the bridge collapse could apply beginning August 27, 2007 for loans of up to US$1.5 million at 4% interest over up to 30 years from the U.S. Small Business Administration.[147] The agency's disaster declaration for Hennepin and contiguous counties came two days after Pawlenty's request to the SBA on August 20, 2007.[148] Open for business and unsure they could repay loans, owners near the collapse in some cases lost 25% or 50% of their income. Large retailers in a mall of chain stores lost about the same.[149] As of early January 2008, at least one business closed, one announced it was closing, seven of eight SBA applications had not been approved and merchants continued to explain how they are unable to shoulder more debt.[150]

Seventy percent of the traffic served by the bridge was downtown-bound.[151] Mn/DOT published detour information, and made real-time traffic information available for callers to 5-1-1. The designated alternate route in the area was Trunk Highway 280, which was converted to a temporary controlled-access highway with all at-grade access points closed. Other traffic was diverted to Interstates 694, 494, and 35E. The number of lanes was increased on several of the highways by repainting traffic lines to eliminate wide shoulders, and by widening various "choke-points".

Extra Metro Transit buses were added from park-and-ride locations in the northern suburbs during the rush hours.[152] Abandoned vehicles on I-35W and 280 were towed immediately. On August 6, I-35W was opened to local traffic at the access ramps on each side of the missing section; some on-ramps remained closed.[153]

In the aftermath, pressure was exerted on the state legislature to increase the state fuel tax to provide adequate maintenance funding for Mn/DOT.[154] Ultimately the tax was increased by $0.055 per gallon via an override of Governor Pawlenty's veto of the legislation.[155]

Public events and media

dozens of observers in front of downtown
Observers on the Stone Arch Bridge

The Minnesota Twins played their home game as scheduled, against the Kansas City Royals at the Hubert H. Humphrey Metrodome just west of I-35W, on the evening of the accident. Public safety officials told the team that postponing the game could hamper rescue and recovery efforts, since a postponement would send up to 25,000 people back into traffic only blocks from the collapsed bridge. Before the game, a moment of silence was held for the victims of the collapse. The Twins postponed their August 2 game as well as the traditional groundbreaking ceremonies for Target Field also located in downtown Minneapolis.[156] The Twins and Minnesota Vikings would honor the victims of the collapse by placing a decal of a simulated I-35W shield sign with the date "8-1-07" on the backstop wall within the Metrodome, which was always visible in the typical behind-the-pitcher viewpoint on televised games. The decal would remain for the rest of the 2007 season.[157]

waist high portrait of a TV cameraman and reporter
The disaster site was used as a backdrop by many TV crews. Contessa Brewer is shown here, reporting for MSNBC.

The collapse was of interest to national and international news organizations. On the evening of the collapse, CNN, MSNBC, and Fox News Channel stayed live with its coverage during the overnight hours, along with local stations WCCO-AM (830) and KSTP (1500),[158] with most of the coverage in the opening hours coming via satellite from Twin Cities news operations WCCO-TV, KSTP-TV, KMSP-TV, KARE-TV and Minnesota Public Radio. National TV networks sent CBS anchor Katie Couric, NBC's Brian Williams and Matt Lauer, MSNBC's Contessa Brewer, ABC's Charles Gibson, CNN's Soledad O'Brien and Anderson Cooper, and Fox News Channel's Greta Van Susteren and Shepard Smith to broadcast from the Twin Cities.[159] U.S. news organizations interested in national and local bridge safety made a record number of requests for bridge information from Investigative Reporters and Editors, an organization that maintains several databases of federal information. News media made more inquiries for National Bridge Inventory data in the first 24 hours after the Minneapolis bridge collapse than for any previous data in the past 20 years.[160]

Disaster declarations

The Hennepin County Board of Commissioners voted on August 7, 2007 to request that Governor Pawlenty petition President George W. Bush to declare the city of Minneapolis and Hennepin County a major disaster area.[161] About two weeks later, Pawlenty requested major disaster designation on August 20.[162] In a subsequent press release for a separate disaster declaration that month, he said, "Ordinarily, preliminary damage assessments are completed before the emergency disaster declaration is requested."[163] During a press conference and briefing with Bush at the Minneapolis/St.Paul Air Reserve Station base for the 934th Airlift Wing on Tuesday, August 21,[164] Pawlenty estimated the total cost of emergency response at over US$8 million including Hennepin County's cost at US$7.3 million for rescue and recovery and US$1.2 million for other state agencies.[165] He estimated the cost of the collapse to the state at US$400,000 to US$1 million per day.[166]

That day, Bush gave an emergency rather than major disaster declaration for the state of Minnesota, allowing local and state agencies to recover costs incurred August 1 to 15 from the Federal Emergency Management Agency (FEMA).[166][167] FEMA can provide payment as required for emergency protective measures (part of FEMA Category B) at no less than 75% federal funding to Hennepin County, the designated county, up to the initial limit of US$5 million.[168] Pawlenty planned to ask that the date restriction and monetary cap be lifted.[166] FEMA aid can compensate the county for the saving of lives, protection of public safety and health, and lessening damage to improved property, but not for the disaster-related needs of the victims nor for removing debris and restoration of the bridge and riverfront nor many other categories of needs.[169]

Replacement bridge

A view of the new bridge from directly underneath it, looking across the river
A view of the pillars of the replacement Saint Anthony Falls bridge

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

The replacement of the collapsed I-35W Mississippi River bridge crosses the Mississippi River at the same location as the original bridge, and carries north–south traffic on I-35W. It was constructed on an accelerated schedule, because of the highway's function as a vital link for carrying commuters and truck freight.[170]

Mn/DOT announced on September 19, 2007, that Flatiron Constructors and Manson Construction Company would build the replacement bridge for $234 million.[171] The I-35W Saint Anthony Falls Bridge was opened to the public on September 18, 2008, at 5 a.m.[172] Using the innovative design-build project delivery method, the replacement bridge opened over three months ahead of schedule, and was awarded the "Best Overall Design-Build Project Award" for 2009 from the Design-Build Institute of America.[173]

Memorial garden

The 35W Bridge Remembrance Garden is a memorial commemorating the victims and survivors of the I-35W bridge collapse.[174] The memorial is located off West River Parkway, in Minneapolis.[175] The memorial was revealed to the public on August 1, 2011, the four-year anniversary of the collapse.[175] Minnesota Governor, Mark Dayton and Minneapolis Mayor R. T. Rybak were present, and both spoke at the reveal. The ceremony included reading the names of the 13 victims, followed by a moment of silence held at exactly 6:05 p.m., the time of the collapse four years prior. Afterwards, there was the release of 13 doves in memory of the people who died.[176]

This $900,000 memorial was funded by the Minneapolis Foundation,[177] and the park land was provided by the Minneapolis Park and Recreation Board.[178] The design of the remembrance garden was created by Tom Oslund, alongside survivors and relatives of the victims. [179]

The design was meant to incorporate symbolic natural elements, including:

  • Stone, for stability and immortality[180]
  • Arborvitae trees, for strength and to live for centuries[180]
  • Water, able to purify and regenerate[180]
  • Darkness and Light, the transition between tragedy and new life[180]

A prime feature in the garden includes 13 steel I-beam and opaque glass columns. Each column has a name engraved of someone lost, along with their story, some even written in their native language.[180] These 13 columns' linear length totals 81 feet (25 m), signifying the date of the collapse (08/01/07).[175] Behind the 13 columns is a black granite water wall. On the wall, stainless steel words form the quote, "Our lives are not only defined by what happens, but by how we act in the face of it, not only by what life brings us, but by what we bring to life. Selfless actions and compassion create enduring community out of tragic events."[181] Along with the quote, the names of the 171 survivors are etched into the black stone. Another part of the memorial includes a path leading to the bluff, overlooking the Mississippi River and the new I-35W Bridge. At night, the columns, pathway and water wall are illuminated by LED lights.

See also

References

Footnotes

  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. 3.0 3.1 Lua error in package.lua at line 80: module 'strict' not found. This map shows average daily traffic volumes for downtown Minneapolis. Trunk highway and Interstate volumes are from 2006.
  4. Lua error in package.lua at line 80: module 'strict' not found. Index map for Mn/DOT's 2006 traffic volumes; relevant maps showing the highest river bridge traffic volumes are Maps 2E, 3E, and 3F.
  5. Lua error in package.lua at line 80: module 'strict' not found.[self-published source]
  6. 6.0 6.1 Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 Lua error in package.lua at line 80: module 'strict' not found.
  8. 8.0 8.1 8.2 8.3 Lua error in package.lua at line 80: module 'strict' not found.
  9. 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. Flanagan, Barbara. "Sheba the donkey is off Nicollet Island, but on pictorial map of it", Star Tribune, August 26, 1988, Section:News; page 3B
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. 14.0 14.1 Lua error in package.lua at line 80: module 'strict' not found.
  15. 15.0 15.1 15.2 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.[page needed]
  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. Lua error in package.lua at line 80: module 'strict' not found.
  22. 22.0 22.1 22.2 Lua error in package.lua at line 80: module 'strict' not found.
  23. 23.0 23.1 23.2 Lua error in package.lua at line 80: module 'strict' not found.
  24. 24.0 24.1 24.2 24.3 Lua error in package.lua at line 80: module 'strict' not found.
  25. 25.0 25.1 Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found. Since then however several older bridges have been replaced.
  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. 30.0 30.1 Lua error in package.lua at line 80: module 'strict' not found.. These contract plans contain dimensions and elevations at Figures 1.1 and 1.2.
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. 32.0 32.1 Lua error in package.lua at line 80: module 'strict' not found. Sheets 1 and 86 of these plans (pp. 2 and 87) show a finished grade profile at an elevation of approximately 840 feet (260 m) over the main span, which is 115 feet (35 m) over the pool elevation of 725 feet (221 m). This is consistent with a later inspection report, Bridge Inspection Report Bridge No. 9340, published online by Minnesota Department of Transportation in 2007. The Road Inventory Bridge Sheet (p. 4) shows a height of 132 feet (40 m) from river bottom to superstructure and a river depth of 15 feet (4.6 m), correlating to a height of 117 feet (36 m) over the water.
  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. Lua error in package.lua at line 80: module 'strict' not found.
  36. Lua error in package.lua at line 80: module 'strict' not found.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. Lua error in package.lua at line 80: module 'strict' not found..
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. Lua error in package.lua at line 80: module 'strict' not found.
  42. Lua error in package.lua at line 80: module 'strict' not found.
  43. 43.0 43.1 Lua error in package.lua at line 80: module 'strict' not found.
  44. 44.0 44.1 44.2 Lua error in package.lua at line 80: module 'strict' not found.
  45. Lua error in package.lua at line 80: module 'strict' not found.
  46. Lua error in package.lua at line 80: module 'strict' not found.
  47. Lua error in package.lua at line 80: module 'strict' not found.
  48. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  49. Lua error in package.lua at line 80: module 'strict' not found.
  50. Lua error in package.lua at line 80: module 'strict' not found.
  51. Lua error in package.lua at line 80: module 'strict' not found.
  52. Lua error in package.lua at line 80: module 'strict' not found.
  53. 53.0 53.1 Lua error in package.lua at line 80: module 'strict' not found.
  54. Lua error in package.lua at line 80: module 'strict' not found.
  55. Lua error in package.lua at line 80: module 'strict' not found.
  56. Lua error in package.lua at line 80: module 'strict' not found.
  57. Lua error in package.lua at line 80: module 'strict' not found.
  58. 58.0 58.1 Lua error in package.lua at line 80: module 'strict' not found.[full citation needed]
  59. 59.0 59.1 Lua error in package.lua at line 80: module 'strict' not found.
  60. Lua error in package.lua at line 80: module 'strict' not found.
  61. Lua error in package.lua at line 80: module 'strict' not found.
  62. Lua error in package.lua at line 80: module 'strict' not found.[dead link] August 8, 2007
  63. 63.0 63.1 63.2 63.3 Lua error in package.lua at line 80: module 'strict' not found.
  64. Lua error in package.lua at line 80: module 'strict' not found.
  65. Lua error in package.lua at line 80: module 'strict' not found.
  66. Lua error in package.lua at line 80: module 'strict' not found.
  67. Lua error in package.lua at line 80: module 'strict' not found.
  68. Lua error in package.lua at line 80: module 'strict' not found.
  69. 69.0 69.1 Lua error in package.lua at line 80: module 'strict' not found.
  70. Lua error in package.lua at line 80: module 'strict' not found.
  71. Lua error in package.lua at line 80: module 'strict' not found.
  72. Lua error in package.lua at line 80: module 'strict' not found.
  73. Lua error in package.lua at line 80: module 'strict' not found.
  74. Lua error in package.lua at line 80: module 'strict' not found.
  75. Lua error in package.lua at line 80: module 'strict' not found.
  76. 76.0 76.1 76.2 Lua error in package.lua at line 80: module 'strict' not found.
  77. 77.0 77.1 Lua error in package.lua at line 80: module 'strict' not found. Lua error in package.lua at line 80: module 'strict' not found.
  78. Lua error in package.lua at line 80: module 'strict' not found.
  79. Lua error in package.lua at line 80: module 'strict' not found.
  80. Lua error in package.lua at line 80: module 'strict' not found.
  81. 81.0 81.1 Lua error in package.lua at line 80: module 'strict' not found.
  82. Lua error in package.lua at line 80: module 'strict' not found.
  83. Lua error in package.lua at line 80: module 'strict' not found.
  84. Lua error in package.lua at line 80: module 'strict' not found.
  85. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  86. Lua error in package.lua at line 80: module 'strict' not found.
  87. Lua error in package.lua at line 80: module 'strict' not found.
  88. Lua error in package.lua at line 80: module 'strict' not found. Lua error in package.lua at line 80: module 'strict' not found.
  89. 89.0 89.1 89.2 Lua error in package.lua at line 80: module 'strict' not found.
  90. Lua error in package.lua at line 80: module 'strict' not found.
  91. Lua error in package.lua at line 80: module 'strict' not found.
  92. Lua error in package.lua at line 80: module 'strict' not found.
  93. 93.0 93.1 93.2 Lua error in package.lua at line 80: module 'strict' not found. Lua error in package.lua at line 80: module 'strict' not found.
  94. Lua error in package.lua at line 80: module 'strict' not found. Lua error in package.lua at line 80: module 'strict' not found.
  95. Lua error in package.lua at line 80: module 'strict' not found.
  96. Lua error in package.lua at line 80: module 'strict' not found.
  97. Lua error in package.lua at line 80: module 'strict' not found.
  98. Lua error in package.lua at line 80: module 'strict' not found.
  99. 99.0 99.1 Lua error in package.lua at line 80: module 'strict' not found.
  100. Lua error in package.lua at line 80: module 'strict' not found. Lua error in package.lua at line 80: module 'strict' not found.
  101. 101.0 101.1 Lua error in package.lua at line 80: module 'strict' not found.
  102. Lua error in package.lua at line 80: module 'strict' not found. Lua error in package.lua at line 80: module 'strict' not found. Lua error in package.lua at line 80: module 'strict' not found.
  103. U.S. Fire Administration/Technical Report Series I-35W Bridge Collapse and ResponseMinneapolis, Minnesota USFA-TR-166/August 2007, page 18
  104. A Newsletter of the Police Executive Research Forum, Vol. 21, No. 10 | October 2007, Minneapolis Area Police Officials Describe, “Lessons Learned” from Bridge Collapse
  105. 105.0 105.1 Lua error in package.lua at line 80: module 'strict' not found.
  106. Lua error in package.lua at line 80: module 'strict' not found.
  107. Lua error in package.lua at line 80: module 'strict' not found.
  108. Lua error in package.lua at line 80: module 'strict' not found.
  109. Lua error in package.lua at line 80: module 'strict' not found.
  110. 110.0 110.1 Lua error in package.lua at line 80: module 'strict' not found.
  111. Lua error in package.lua at line 80: module 'strict' not found. Lua error in package.lua at line 80: module 'strict' not found.
  112. 112.0 112.1 Lua error in package.lua at line 80: module 'strict' not found.
  113. Lua error in package.lua at line 80: module 'strict' not found.
  114. 114.0 114.1 Lua error in package.lua at line 80: module 'strict' not found.
  115. Lua error in package.lua at line 80: module 'strict' not found.
  116. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  117. Lua error in package.lua at line 80: module 'strict' not found.
  118. Lua error in package.lua at line 80: module 'strict' not found.
  119. Lua error in package.lua at line 80: module 'strict' not found.
  120. Lua error in package.lua at line 80: module 'strict' not found.
  121. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  122. NTSB press conference, August 2, 2007[full citation needed]
  123. Lua error in package.lua at line 80: module 'strict' not found.
  124. Lua error in package.lua at line 80: module 'strict' not found.
  125. Lua error in package.lua at line 80: module 'strict' not found.
  126. Lua error in package.lua at line 80: module 'strict' not found.
  127. Lua error in package.lua at line 80: module 'strict' not found.
  128. Lua error in package.lua at line 80: module 'strict' not found.
  129. 129.0 129.1 129.2 Lua error in package.lua at line 80: module 'strict' not found.
  130. 130.0 130.1 130.2 Lua error in package.lua at line 80: module 'strict' not found.
  131. Lua error in package.lua at line 80: module 'strict' not found.
  132. Lua error in package.lua at line 80: module 'strict' not found.
  133. Lua error in package.lua at line 80: module 'strict' not found.
  134. Lua error in package.lua at line 80: module 'strict' not found.
  135. Lua error in package.lua at line 80: module 'strict' not found.
  136. Lua error in package.lua at line 80: module 'strict' not found.
  137. Lua error in package.lua at line 80: module 'strict' not found.
  138. Lua error in package.lua at line 80: module 'strict' not found.
  139. Lua error in package.lua at line 80: module 'strict' not found.
  140. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  141. http://www.mprnews.org/story/2012/11/14/law/i35w-bridge-settlement-jacobs-engineering
  142. Lua error in package.lua at line 80: module 'strict' not found.
  143. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  144. Lua error in package.lua at line 80: module 'strict' not found.
  145. Lua error in package.lua at line 80: module 'strict' not found. Lua error in package.lua at line 80: module 'strict' not found.
  146. Lua error in package.lua at line 80: module 'strict' not found.
  147. Lua error in package.lua at line 80: module 'strict' not found.
  148. Lua error in package.lua at line 80: module 'strict' not found. Lua error in package.lua at line 80: module 'strict' not found.
  149. Lua error in package.lua at line 80: module 'strict' not found.
  150. Lua error in package.lua at line 80: module 'strict' not found.
  151. Lua error in package.lua at line 80: module 'strict' not found.
  152. Lua error in package.lua at line 80: module 'strict' not found.
  153. Lua error in package.lua at line 80: module 'strict' not found.
  154. Lua error in package.lua at line 80: module 'strict' not found.[self-published source]
  155. Lua error in package.lua at line 80: module 'strict' not found.
  156. Lua error in package.lua at line 80: module 'strict' not found.
  157. Lua error in package.lua at line 80: module 'strict' not found.
  158. Lua error in package.lua at line 80: module 'strict' not found.
  159. Lua error in package.lua at line 80: module 'strict' not found.
  160. Lua error in package.lua at line 80: module 'strict' not found.
  161. Lua error in package.lua at line 80: module 'strict' not found.
  162. Lua error in package.lua at line 80: module 'strict' not found.[full citation needed]
  163. Lua error in package.lua at line 80: module 'strict' not found.
  164. Lua error in package.lua at line 80: module 'strict' not found.
  165. Lua error in package.lua at line 80: module 'strict' not found.
  166. 166.0 166.1 166.2 Lua error in package.lua at line 80: module 'strict' not found.
  167. Lua error in package.lua at line 80: module 'strict' not found. Lua error in package.lua at line 80: module 'strict' not found.
  168. Lua error in package.lua at line 80: module 'strict' not found. Lua error in package.lua at line 80: module 'strict' not found.
  169. Lua error in package.lua at line 80: module 'strict' not found.
  170. Lua error in package.lua at line 80: module 'strict' not found.
  171. Lua error in package.lua at line 80: module 'strict' not found.
  172. Lua error in package.lua at line 80: module 'strict' not found.
  173. Lua error in package.lua at line 80: module 'strict' not found.
  174. Lua error in package.lua at line 80: module 'strict' not found.
  175. 175.0 175.1 175.2 Lua error in package.lua at line 80: module 'strict' not found.
  176. Lua error in package.lua at line 80: module 'strict' not found.
  177. Lua error in package.lua at line 80: module 'strict' not found.
  178. Lua error in package.lua at line 80: module 'strict' not found.
  179. Lua error in package.lua at line 80: module 'strict' not found.
  180. 180.0 180.1 180.2 180.3 180.4 Lua error in package.lua at line 80: module 'strict' not found.
  181. Lua error in package.lua at line 80: module 'strict' not found.

Works cited

  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.

Further reading

  • Lua error in package.lua at line 80: module 'strict' not found. studies by civil engineers, geographers, and others on the events and aftermath of the collapse of the bridge
  • Lua error in package.lua at line 80: module 'strict' not found.

External links