Wanna rethink that battle plan there Captian Hook?


Recommended Posts

Navy Exchanges Fire With Suspected Pirates

pirates.jpg

Pirates (photo released by Navy after fight)

Cape_st_george.jpg

Navy (U.S.S. Cape St. George in unrelated archive photo)

DUBAI, United Arab Emirates (AP) - Two U.S. Navy warships exchanged gunfire with suspected pirates Saturday off the coast of Somalia, and one suspect was killed and five others were wounded, the navy said.

Seven other suspects were taken into custody after the early-morning shootout, said Lt. Cmdr. Charlie Brown, spokesman for the U.S. Navy's 5th Fleet.

No sailors were wounded in the battle, which occurred at about 5:40 a.m. local time, approximately 25 nautical miles off the Somali coast in international waters.

The battle started after the USS Cape St. George and USS Gonzalez, which were patrolling as part of a Dutch-led task force, spotted a 30-foot fishing boat towing smaller skiffs and prepared to board and inspect the vessels.

(AP) In this photo provided by the U.S. Navy, a Tomahawk Land Attack Missile (TLAM) is launched from the...

Full Image

The suspected pirates were holding what appeared to be rocket-propelled grenade launchers, the navy said. When the suspects began shooting, naval gunners returned fire with mounted machine guns, killing one man and igniting a fire on the vessel.

Three suspects were seriously wounded and being treated on one of the Navy ships, Brown told The Associated Press. A Dutch Navy medical team was en route.

The suspects' nationalities were unknown.

The Navy boarding teams confiscated an RPG launcher and automatic weapons, the statement said.

The Cape St. George, a guided-missile cruiser, and Gonzalez, a guided-missile destroyer, were conducting maritime security operations in the area. They are based in Norfolk, Va.

The International Maritime Organization has warned ships to stay away from the Somali coast because of pirate attacks, which surged to 35 last year from two in 2004.

On March 15, the U.N. Security Council encouraged naval forces operating off Somalia to take action against suspected piracy. Pirate attacks against aid ships have hindered U.N. efforts to provide relief to the victims of a severe drought in the area.

The pirate raids are part of the anarchy wracking Somalia, which has had no effective government since 1991, when warlords ousted a dictatorship and then turned on each other.

EDIT: photo captions edited as per request below)

Edited by Komet

Great way to spend tens of millions of dollars, launch a Tomahawk to scare some stupid pirates.

The navy returned fire with small arms and mounted machine guns. No missiles were used. The pictures there probably aren't of the actual ships involved, just an illustration to show the relative sizes of the vessels.

The navy returned fire with small arms and mounted machine guns. No missiles were used. The pictures there probably aren't of the actual ships involved, just an illustration to show the relative sizes of the vessels.

According to the news story those are the actual ships, err rather the actual ship and boat involved in the fight. the pirates boat was a photo release by the Navy and the image of the U.S.S. Cape St. George is an archive photo.

Edited by Komet

I'm not denying the need to maintain security on the vessel, that pre-empts EVERYTHING. But, doesn't a cruise missle cost over $1 million. So didn't this fight cost US taxpayers over $1 million?

*I'm Canadian so it doesn't effect my pocket book but isn't this absurd?

I'm not denying the need to maintain security on the vessel, that pre-empts EVERYTHING. But, doesn't a cruise missle cost over $1 million. So didn't this fight cost US taxpayers over $1 million?

*I'm Canadian so it doesn't effect my pocket book but isn't this absurd?

If you read the article or the replies below, you would have seen that the picture used in the post was an archive photo; no cruise missiles were ever used. The Navy returned fire with machine guns and small arms fire.

The first post should be edited to show that the image of the Navy warship is an archived photo, and not the photo of it enaging the pirate vessel. There's no need to fire a Tomahawk cruise missile at a small vessel.

The first post should be edited to show that the image of the Navy warship is an archived photo, and not the photo of it enaging the pirate vessel. There's no need to fire a Tomahawk cruise missile at a small vessel.

Its a missle ship! They have one cannon which probably could aim so low! :p

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I bought one of these last year. I really hope I won't have to deal with this crap. My drive is in good condition at the moment.
    • Umm, read my answer again! If you have something to add or contribute, feel free. Otherwise my point was that you apparently dont want faster updates... so you want slower updates by process of elimination. If you have something to contribute, meaningful answers are better.
    • These features described above are good, but far from what developers will like the most. The main feature that developers will care and love the most it's called "Bring Your Own Models". It gives us the ability to connect to LOCAL AI models running on Ollama. The feature it's located on GitHub Copilot tab -> On the model picker where you can select "manage models" instead of paid models and then it will show you the "Bring your own models" window where you can now select Ollama and the endpoint of your local server. So if you have a beefy spec machine you can now use your own model 100% local inside Visual Studio 2026 18.7.0
    • Microsoft Teams is getting a controversial location tracking feature that users may hate by Usama Jawad Image generated with Microsoft Copilot Earlier this year, Microsoft planned to roll out a controversial location tracking feature in Teams, but following customer feedback, it decided to delay its release. The bad news is that the company has decided to launch it later this year, but it's based on roughly the same design that was shared earlier, which means that many users still have good reason to worry. Basically, Microsoft Places and Teams have received workplace check-ins via Wi-Fi. The idea is that if an employee arrives at the office and connects to their enterprise network, their profile status indicator will show them as being present in the office. For example, if you arrive at work, open Teams on your PC, and connect to the "Studio B" company Wi-Fi network, your Teams profile will indicate that you are present in "Studio B", as shown below: Microsoft says that this feature is basically a replacement for physical workplace check-in peripherals, it reduces the need to manually update your status, and it also enables co-workers to know that you're at work so that they can coordinate in-person meetings with you. IT admins can enable this workplace check-in capability at a tenant level, and users have the ability to control whether they want to enable it or not. Of course, all of that sounds great on paper, but naturally, many Teams customers may still have concerns, as they did before. This is because it enables your reporting manager and other members of the organization to track if you are at the office, when you arrive at the office, and where you are right now. This could be problematic for people who work in what they consider to be flexible work environments or hybrid setups, and this kind of location tracking could be considered an invasion of privacy. Microsoft has tried to alleviate some of these concerns by letting users know that they can manually set their location easily, which essentially overrides workplace check-in if they feel uncomfortable with it. However, that doesn't really solve the problem because your organization could enforce a workplace policy that mandates that this feature remains enabled. The Redmond tech giant has also assured users that this capability does not store historical data and is only a real-time indicator of location. Finally, it only generates a signal when you connect to a corporate network, which means that if you are working from home and connect your PC to your personal Wi-Fi, it won't broadcast your location to your employer; you will simply be shown as "Remote". Microsoft has encouraged IT admins to prepare for this change and begin informing users so they know what to expect once it begins rolling out later this year.
  • Recent Achievements

    • Very Popular
      AndrewSteel earned a badge
      Very Popular
    • Veteran
      Taliseian went up a rank
      Veteran
    • One Month Later
      Clizby earned a badge
      One Month Later
    • One Month Later
      Timaximus earned a badge
      One Month Later
    • Week One Done
      Timaximus earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      516
    2. 2
      +Edouard
      162
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      Steven P.
      82
    5. 5
      ATLien_0
      81
  • Tell a friend

    Love Neowin? Tell a friend!