Friday, January 31, 2020

Summary Draft #2

In the article, “I-5 and the Physics of Bridge Collapse,” Hartsfield (2013) has stated that most bridges including the I-5 bridge failed due to inevitable design flaws. The author implies the possibilities that can cause a bridge to collapse including construction errors or miscalculations for cantilever, and high external force for suspension bridges. According to Hartsfield (2013), “A truss bridge holds as long as the beams themselves don’t break and the joints stay together.” In this regard, a truss bridge can collapse once a part of the structural beam fails. He further states that the unfortunate tragedy of the I-5 truss bridge might have been due to the impact caused by a truck, as it crashed into one of the beams. Hartsfield also mentions that nevertheless, it is critical to understand the underlying problem to determine the actual cause of unpredicted collapse in bridges.

While truck collision contributed to the collapse of I-5 truss bridge, four main negligence factor had played the key role to this catastrophe.  First of all, Washington State Department of Transportation(WSDOT) should have ensure that every permit given out has oblige to the minimum vertical height clearance level. As WSDOT is responsible of acknowledging the proposed routes for company’s oversized vehicles; they should have checked that all registered vehicles are suitable to utilise the I-5 bridge before granting permission. According to a website from National Transportation Safety Board(NTSB), companies were not prompt to perform route surveys since WSDOT did not technically review permits.

Reference:
Tom.H (2013, May 28). I-5 and the physics of bridge collapse. RealClear Science.com. Retrieved from https://www.realclearscience.com/articles/2013/05/29/i-5_and_the_physics_of_bridge_collapses_106544.html

National Transportation Safety Board. (2014). Washington State I-5 Bridge Collapse Abstract. Retrieved July 15, 2011 from https://www.ntsb.gov/news/events/Pages/2014_I5_Bridge_BMG-Abstract.aspx

No comments:

Post a Comment