Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations waross on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

Baltimore Bridge collapse after ship collision 125

Replies continue below

Recommended for you

From gCaptain, about the tugboats:

According to Marine Traffic the ship departed the Seagirt Marine Terminal in the Port of Baltimore at approximately 00:30 local time, sailed northwest past the Nuclear Ship Savanah then turned southeast to depart the harbor, released the tugboats, and collided with the bridge at approximately 01:38.

Full article:
Forum members say many harbors require tugs until the ships are past the bridges.
 
I'm surprised not to see a bumper system around the piers given the traffic under it. The power-line towers before the bridge look better protected.
 
Selection_212_jta3kc.png

This photo depicts the deck was sinking in a straight line over the demolished pier. This is important as it could only occur if the pier was pushed away or knocked out underneath the bearings. Thus the pier structure has almost zero resistance against such impact. After the collapse the bridge and the broken concrete columns all resting on top of the bow of the container ship.
 
There are a few reasons they might not have used tugs. My guess is the bridge has a narrow navigable channel based on the after collapse photos showing the bridge pieces sitting on the bottom. That's no more than speculation though.
 
Some basic information: "The Francis Scott Key Bridge, known originally as the Outer Harbor Crossing until it was renamed in 1976, while still under construction, or simply as the Key Bridge or Beltway Bridge, was a steel arch continuous through truss bridge spanning the lower Patapsco River and outer Baltimore Harbor / Port carrying Maryland Route 695 in Baltimore, Maryland, United States. The main span of 1,200 feet (366 m) was the third longest span of any continuous truss in the world.[2] It was the second-longest bridge in the Baltimore metropolitan area, after the Chesapeake Bay Bridge."

Steel was expensive in the 1970s and interest rates were high. I'm sure budgets were stretched to even build this continuous truss bridge. Not an excuse, but redundancy was not a prime consideration in bridge design in the 70s. In any event, this was not a case of a single member failure leading to progressive collapse.
 
According to Wikipedia it was initially supposed to be a tunnel but was too expensive.

Wikipedia said:
Bids for constructing the proposed Outer Harbor Tunnel were opened in July 1970, but price proposals were substantially higher than the engineering estimates.[11] Officials drafted alternative plans, including a four-lane bridge, which the General Assembly approved in April 1971.[12][13]

At an estimated cost of $110 million, the bridge would have more traffic lanes and lower operating and maintenance costs than a tunnel.[citation needed] A bridge would provide a route across the Baltimore Harbor for vehicles transporting hazardous materials, which are prohibited from both the Baltimore Harbor and Fort McHenry tunnels.[14] The United States Coast Guard issued its bridge permit in June 1972, replacing an earlier approval of the tunnel from the Army Corps of Engineers.[10] Construction of the Outer Harbor Bridge began in 1972,[15] several years behind schedule and $33 million over budget.[16]

 
Ship size and mass has increased tremendously in the last few decades. Perhaps this will trigger a re-evaluation of all bridges and protections. For example, even if substantial pilings are used, if the overhang of the ships increases enough they can still reach the primary bridge structure. Likewise if the height and width of cargo is high enough they can still reach areas of the bridge previously thought safe.
 
In the video, a short while after the lights come back on the first time, there is a smoke plume out of the ship's stack, and it continues right up to the strike. I suspect the engine stopped, causing the lights to go out. Then it was restarted, with the plume signifying it had not settled down to a proper running state yet. The second "lights out" is also of interest--did the engine stop again? Was there another restart?

The opening under the bridge is about 1114 feet wide. The ship is about 157 feet wide. The normal route under the San Francisco Bay bridge is 2171 feet wide. In 2007, a container ship hit one of the piers, with no significant damage to the bridge or its supports.

Strikes me that the bridge fenders on the Baltimore bridge were inadequate (as mentioned by others). And the ship got a "lucky" strike, being almost headlong. I also think the clear span of the Baltimore bridge is pretty skimpy, but real bridge folks likely know more than I about it.

The NTSB will issue a report in a year or two, and it will likely be pretty good. Ship has massive failure(s) at exactly the wrong time and hits an inadequately protected bridge.


spsalso
 
I'm not sure how reply directly to someone. But Spsalso's comment the first time the lights went off the main powerplant went. When the lights kicked back on it was the backup system. Then the second time the lights went off it was the backup power switching back over to main power, hence the plume. Backup power does not provide power to thrusters. Usually only rudder, navigation, and emergency systems.
 
But the plume started before the second time the lights went off.

The lights came back on, the first time, at 2:23

The smoke plume started at 2:35

The lights went off the second time at 3:29

The plume was emitted until impact, or thereabouts.


By the way, Sal's doing his usual great job of covering this event:



spsalso
 
Right but the backup power stays on until the main power is up and ready.

The sequence is typically

Power goes out - backup automatically kicks in - crew attempts to restart main - main fires back up - crew checks to make sure its holding - crew manually turns off the backup and makes the switch.
 
Found a drawing of the bridge fender design.

Screenshot_20240326_144244_hbrci8.png


There is a report which analysed the impact resistance of the bridge which I've not been able to find.

Knott said:
Guide Specification and Commentary for Vessel Collision Design of Highway Bridges”, US Department of Transportation, Federal Highway Administration, Publ. No. FHWA-RD-9 1-006, Dec. 1990
 
Looks like it just missed a dolphin:

Selection_210_r9mhwb_prhqyl.png


After the Sunshine Skyway Bridge disaster they went all out on the protective dolphins on the new span:

CnRFnUOWgAATgz6_mkaq47.jpg
 
Lots of smoke and brownout indicates a failing service generator set. The failing unit should have tripped on reverse power and then automatic load shedding should have taken care of the rest. Maybe it's power output was significantly reduced but never went below zero. Perhaps they were trying to bring an additional unit online instead of tripping the failed unit to avoid the hassle of restoring the plant after load shedding.

The safest option could have been tripping all generators and letting the emergency diesel so it's thing. This would have restored steering and engine power within 30 seconds. However, it is a lot of work to bring the plant back to normal after this.

As for tugs, there isn't much we can do if the ship is going more than 6 knots. It takes all of our horsepower to keep up and we don't have any left for maneuvering.
 
Ship tracking showed 8.5kn when the power failed and slowing to 7.5kn just before impact. There are not many structures that could withstand that kind of direct impact.
 
This marine traffic video shows the location of the tugs after leaving the Dali. It appears that no attempt is made to reach the ship until just moments before impact. This implies no mayday call was made until late in the process.

Link
 
I regret even bringing this up, but could the power failure be due to a cyber attack? Hope the authorities are recovering and analyzing the software logs.
 

Part and Inventory Search

Sponsor

Back
Top