Anonymous wrote:

Anonymous wrote:

Anonymous wrote:I live on the ESMD on the Bay and according to my navy and coast guard friends out here: the boat was experiencing repeated power failures from the short time it was released from the tugs after it left the port. Without power the navigation system won’t work and you cannot steer it and hence the boat will drift. The crew then tried to force the throttle to get it back on course and avoid a collision which is why there is thick black smoke seen coming from the boat before it gets to the bridge. The boat did contact MTA/the bridge which has its headquarters at the north end of the bridge in Dundalk to indicate they believed it would collide with the bridge but there wasn’t enough time IRT to then close the bridge to traffic before it was struck.

The ship was FULL of thousands (yes, thousands) of containers. The weight is incredible. You cannot do sharp turns or sudden stops on this. It also is so heavy it would do this to almost any bridge if collided.

Every single container ship that sails on the Bay, anywhere from Virginia Beach to Baltimore, must have a local bay captain on board while it’s on the bay to navigate the ship. There was one on this ship as well.

Ships are being re-routed to the port of Philadelphia.

This is helpful. thank you.

+2 That was an informative post. But what us EMSD?

Anonymous wrote:I live on the ESMD on the Bay and according to my navy and coast guard friends out here: the boat was experiencing repeated power failures from the short time it was released from the tugs after it left the port. Without power the navigation system won’t work and you cannot steer it and hence the boat will drift. The crew then tried to force the throttle to get it back on course and avoid a collision which is why there is thick black smoke seen coming from the boat before it gets to the bridge. The boat did contact MTA/the bridge which has its headquarters at the north end of the bridge in Dundalk to indicate they believed it would collide with the bridge but there wasn’t enough time IRT to then close the bridge to traffic before it was struck.

The ship was FULL of thousands (yes, thousands) of containers. The weight is incredible. You cannot do sharp turns or sudden stops on this. It also is so heavy it would do this to almost any bridge if collided.

Every single container ship that sails on the Bay, anywhere from Virginia Beach to Baltimore, must have a local bay captain on board while it’s on the bay to navigate the ship. There was one on this ship as well.

Ships are being re-routed to the port of Philadelphia.

Anonymous wrote:I live on the ESMD on the Bay and according to my navy and coast guard friends out here: the boat was experiencing repeated power failures from the short time it was released from the tugs after it left the port. Without power the navigation system won’t work and you cannot steer it and hence the boat will drift. The crew then tried to force the throttle to get it back on course and avoid a collision which is why there is thick black smoke seen coming from the boat before it gets to the bridge. The boat did contact MTA/the bridge which has its headquarters at the north end of the bridge in Dundalk to indicate they believed it would collide with the bridge but there wasn’t enough time IRT to then close the bridge to traffic before it was struck.

The ship was FULL of thousands (yes, thousands) of containers. The weight is incredible. You cannot do sharp turns or sudden stops on this. It also is so heavy it would do this to almost any bridge if collided.

Every single container ship that sails on the Bay, anywhere from Virginia Beach to Baltimore, must have a local bay captain on board while it’s on the bay to navigate the ship. There was one on this ship as well.

Ships are being re-routed to the port of Philadelphia.

Anonymous wrote:I live on the ESMD on the Bay and according to my navy and coast guard friends out here: the boat was experiencing repeated power failures from the short time it was released from the tugs after it left the port. Without power the navigation system won’t work and you cannot steer it and hence the boat will drift. The crew then tried to force the throttle to get it back on course and avoid a collision which is why there is thick black smoke seen coming from the boat before it gets to the bridge. The boat did contact MTA/the bridge which has its headquarters at the north end of the bridge in Dundalk to indicate they believed it would collide with the bridge but there wasn’t enough time IRT to then close the bridge to traffic before it was struck.

The ship was FULL of thousands (yes, thousands) of containers. The weight is incredible. You cannot do sharp turns or sudden stops on this. It also is so heavy it would do this to almost any bridge if collided.

Every single container ship that sails on the Bay, anywhere from Virginia Beach to Baltimore, must have a local bay captain on board while it’s on the bay to navigate the ship. There was one on this ship as well.

Ships are being re-routed to the port of Philadelphia.

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:I live on the ESMD on the Bay and according to my navy and coast guard friends out here: the boat was experiencing repeated power failures from the short time it was released from the tugs after it left the port. Without power the navigation system won’t work and you cannot steer it and hence the boat will drift. The crew then tried to force the throttle to get it back on course and avoid a collision which is why there is thick black smoke seen coming from the boat before it gets to the bridge. The boat did contact MTA/the bridge which has its headquarters at the north end of the bridge in Dundalk to indicate they believed it would collide with the bridge but there wasn’t enough time IRT to then close the bridge to traffic before it was struck.

The ship was FULL of thousands (yes, thousands) of containers. The weight is incredible. You cannot do sharp turns or sudden stops on this. It also is so heavy it would do this to almost any bridge if collided.

Every single container ship that sails on the Bay, anywhere from Virginia Beach to Baltimore, must have a local bay captain on board while it’s on the bay to navigate the ship. There was one on this ship as well.

Ships are being re-routed to the port of Philadelphia.

This is helpful. thank you.

+2 That was an informative post. But what us EMSD?

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:I live on the ESMD on the Bay and according to my navy and coast guard friends out here: the boat was experiencing repeated power failures from the short time it was released from the tugs after it left the port. Without power the navigation system won’t work and you cannot steer it and hence the boat will drift. The crew then tried to force the throttle to get it back on course and avoid a collision which is why there is thick black smoke seen coming from the boat before it gets to the bridge. The boat did contact MTA/the bridge which has its headquarters at the north end of the bridge in Dundalk to indicate they believed it would collide with the bridge but there wasn’t enough time IRT to then close the bridge to traffic before it was struck.

The ship was FULL of thousands (yes, thousands) of containers. The weight is incredible. You cannot do sharp turns or sudden stops on this. It also is so heavy it would do this to almost any bridge if collided.

Every single container ship that sails on the Bay, anywhere from Virginia Beach to Baltimore, must have a local bay captain on board while it’s on the bay to navigate the ship. There was one on this ship as well.

Ships are being re-routed to the port of Philadelphia.

This is helpful. thank you.

+2 That was an informative post. But what us EMSD?

Anonymous wrote:

Anonymous wrote:Where will the cruise ships go?

Norfolk or Newark. Or it might be cheaper to fly the passengers home from another port of call.

Anonymous wrote:

Anonymous wrote:I live on the ESMD on the Bay and according to my navy and coast guard friends out here: the boat was experiencing repeated power failures from the short time it was released from the tugs after it left the port. Without power the navigation system won’t work and you cannot steer it and hence the boat will drift. The crew then tried to force the throttle to get it back on course and avoid a collision which is why there is thick black smoke seen coming from the boat before it gets to the bridge. The boat did contact MTA/the bridge which has its headquarters at the north end of the bridge in Dundalk to indicate they believed it would collide with the bridge but there wasn’t enough time IRT to then close the bridge to traffic before it was struck.

The ship was FULL of thousands (yes, thousands) of containers. The weight is incredible. You cannot do sharp turns or sudden stops on this. It also is so heavy it would do this to almost any bridge if collided.

Every single container ship that sails on the Bay, anywhere from Virginia Beach to Baltimore, must have a local bay captain on board while it’s on the bay to navigate the ship. There was one on this ship as well.

Ships are being re-routed to the port of Philadelphia.

This is helpful. thank you.

Anonymous wrote:More info about the ship and it's owners + operators. The shipping world is very weird when it comes to responsibility for the ship.

https://www.vesselfinder.com/vessels/details/9697428

https://www.tradewindsnews.com/casualties/-mass-casualty-event-as-maersk-container-ship-destroys-vital-bridge-in-baltimore/2-1-1617658

The ship is owned by Mitsui & Co subsidiary Grace Ocean of Singapore and operated by Maersk between the East Coast of the US and East Asia, according to Clarksons data.

A Grace Ocean official confirmed to TradeWinds that the vessel involved was the Dali.

“We can confirm that this is correct,” he said, adding that the company was working with the ship’s technical manager, Synergy Marine, to determine what happened.

“At this time we are still trying to get information,” he said.
...
Maersk said: “We are horrified by what has happened in Baltimore, and our thoughts are with all of those affected.”

The group said the ship was operated by Synergy and time-chartered by Maersk, with Maersk cargo on board.

No Maersk crew or personnel were on the vessel.

I predict a lot of finger pointing when it comes to liability. It sounds like Maersk "rents" the ship from the ownership company and then subcontracted to a company called Synergy to actually operate the ship, with all of Maersk's cargo on the ship. Whose insurance is actually responsible?

It's going to be a debacle. I hope the Feds start freezing assets.

Anonymous wrote:I live on the ESMD on the Bay and according to my navy and coast guard friends out here: the boat was experiencing repeated power failures from the short time it was released from the tugs after it left the port. Without power the navigation system won’t work and you cannot steer it and hence the boat will drift. The crew then tried to force the throttle to get it back on course and avoid a collision which is why there is thick black smoke seen coming from the boat before it gets to the bridge. The boat did contact MTA/the bridge which has its headquarters at the north end of the bridge in Dundalk to indicate they believed it would collide with the bridge but there wasn’t enough time IRT to then close the bridge to traffic before it was struck.

The ship was FULL of thousands (yes, thousands) of containers. The weight is incredible. You cannot do sharp turns or sudden stops on this. It also is so heavy it would do this to almost any bridge if collided.

Every single container ship that sails on the Bay, anywhere from Virginia Beach to Baltimore, must have a local bay captain on board while it’s on the bay to navigate the ship. There was one on this ship as well.

Ships are being re-routed to the port of Philadelphia.

The ship is owned by Mitsui & Co subsidiary Grace Ocean of Singapore and operated by Maersk between the East Coast of the US and East Asia, according to Clarksons data.

A Grace Ocean official confirmed to TradeWinds that the vessel involved was the Dali.

“We can confirm that this is correct,” he said, adding that the company was working with the ship’s technical manager, Synergy Marine, to determine what happened.

“At this time we are still trying to get information,” he said.
...
Maersk said: “We are horrified by what has happened in Baltimore, and our thoughts are with all of those affected.”

The group said the ship was operated by Synergy and time-chartered by Maersk, with Maersk cargo on board.

No Maersk crew or personnel were on the vessel.