Wednesday, June 19, 2024
More
    HomeWorldAn Attack on a Cargo Ship in the Red Sea Has Caused...

    An Attack on a Cargo Ship in the Red Sea Has Caused a Miles-Long Oil Slick. Things Could Get Worse

    An Attack on a Cargo Ship in the Red Sea Has Caused a Miles-Long Oil Slick. Things Could Get Worse

    CAIRO (AP) — An attack by Yemeni Houthi rebels on a Belize-flagged ship earlier this month caused an 18-mile (29-kilometer) oil slick, the U.S. said Saturday. It also warned of the danger of a spill from the vessel's cargo of fertilizer.

    The Rubymar, a British-registered, Lebanese-operated cargo vessel, was attacked on Feb. 18 while sailing through the Bab el-Mandeb Strait that connects the Red Sea and the Gulf of Aden, U.S. Central Command said.

    The missile attack forced the crew to abandon the vessel, which had been on its way to Bulgaria after leaving Khorfakkan in the United Arab Emirates. It was transporting more than 41,000 tons of fertilizer, said in a statement.

    The vessel suffered significant damage, which led to the slick, said the CENTCOM statement, warning that the ship's cargo “could spill into the Red Sea and worsen this environmental disaster.”

    “The Houthis continue to demonstrate disregard for the regional impact of their indiscriminate attacks, threatening the fishing industry, coastal communities, and imports of food supplies,” it said.

    The Associated Press, relying on satellite images from Planet Labs PBC of the stricken vessel, reported Tuesday that the vessel was leaking oil in the Red Sea.

    's internationally recognized government on Saturday called for other countries and maritime-protection organizations to quickly address the oil slick and avert “a significant…

    Continue Reading This Article At Military.com

    Stay Connected

    34,572FansLike
    4,123FollowersFollow
    1,739FollowersFollow

    Latest articles

    AlphaDog Hosting Ad

    Related articles

    Leave a reply

    Please enter your comment!
    Please enter your name here
    Captcha verification failed!
    CAPTCHA user score failed. Please contact us!