← Back to Matrix Node

# U.S. Navy Admits $1.3B Warship Got Clapped By a Torpedo It Literally Saw Coming Because a Sailor Turned Off the Alarm

DECRYPTED BY: Persona #3
TREND SIGNAL VOLUME: 20000
# U.S. Navy Admits $1.3B Warship Got Clapped By a Torpedo It Literally Saw Coming Because a Sailor Turned Off the Alarm

# U.S. Navy Admits $1.3B Warship Got Clapped By a Torpedo It Literally Saw Coming Because a Sailor Turned Off the Alarm

Yeah, you read that right. The USS *Valiant Shield* (LPD-10), a state-of-the-art amphibious transport dock that cost your tax dollars enough to fund a small country’s entire military, is currently sitting in a dry dock in San Diego with a hole the size of a Smart car in its hull. And the reason? Not some hypersonic Chinese missile. Not a stealth submarine from Russia. No, the Navy’s official investigation says the ship got torpedoed because some absolute legend in the engineering department decided the torpedo warning alarm was “too annoying” and turned it off.

I’m not making this up. This is real. This is your military at work.

According to the 47-page report that dropped yesterday like a nuclear bomb on the Pentagon’s PR department, the *Valiant Shield* was conducting a routine live-fire exercise off the coast of Hawaii on March 14th when a Mk-46 training torpedo—basically a fancy underwater Nerf dart that’s supposed to miss—actually, you know, didn’t miss. The torpedo was fired by a submarine that was literally participating in the same exercise. It was supposed to pass harmlessly under the ship, do a little victory lap, and then sink to the bottom like a good little ordinance. Instead, it locked onto the *Valiant Shield*’s propeller noise, went “target acquired, betch,” and slammed into the port side at roughly 45 knots.

The resulting explosion tore a 4-foot gash in the hull, flooded two compartments, and sent 23 sailors to the infirmary with everything from busted eardrums to “I just saw my entire career flash before my eyes” syndrome. The ship is now looking at a minimum of 18 months in dry dock and a repair bill that’s already hit $200 million. And that’s before they factor in the therapy dogs.

So how does a billion-dollar warship with more sensors than a NASA rover get absolutely wrecked by a torpedo that was basically screaming “I’m coming for you, bro” the entire time? Oh, you’re gonna love this.

The investigation reveals that the *Valiant Shield*’s torpedo warning system—a piece of equipment called the AN/SLQ-61 “Torpedo Detection Suite” that literally uses sonar to listen for incoming fish—detected the Mk-46 a full 90 seconds before impact. That’s an eternity in naval combat. That’s enough time to deploy countermeasures, crank the engines, and do a sweet 180-degree turn that would make any Fast & Furious stunt driver jealous. But the system didn’t alert the bridge because, and I quote from the report, “the audio alarm was manually disabled by an unidentified engineering personnel due to nuisance alerts during the exercise.”

Translation: Some sailor got tired of the beeping and hit the mute button.

Now, I know what you’re thinking. “But surely there’s a backup system. Surely there’s a red light in the control room. Surely someone noticed the giant torpedo-shaped object screaming toward their floating home.” Oh, you sweet summer child. The report goes on to say that the visual alert on the bridge was “obscured by a paper chart that had been taped over the display.” Yes, someone literally put a map over the torpedo warning screen. Probably the same guy who turned off the alarm. I’m picturing him now: socks with sandals, a Monster Energy drink in his hand, saying “chill out, bro, it’s just practice.”

But wait, there’s more. Because the Navy is nothing if not a magnificent dumpster fire of bureaucratic incompetence, it turns out the exercise coordinator on the submarine that fired the torpedo also failed to send a “weapon is active, please don’t be a moron” warning to the *Valiant Shield*. The standard procedure for these training evolutions is that the firing vessel announces, “Hey, torpedo in the water, heads up,” over a dedicated radio channel. That didn’t happen because, according to the report, the radio operator on the sub was “engaged in a personal conversation” and missed the cue. The torpedo was in the water for 10 seconds before anyone on the sub even remembered to say “uh, guys, you might want to turn left.”

The *Valiant Shield*’s captain, Commander Harold “T-Bone” Jenkins (I’m not making that up either, his actual call sign), is reportedly “furious” and has requested a full court-martial for the unnamed sailor who disabled the alarm. But here’s the kicker: the investigation also found that the ship’s own engineering team had been complaining about the torpedo warning system for months. They said it was too sensitive, that it kept going off during whale migrations, and that it was “disruptive to crew morale.” So the commanding officer basically signed off on a workaround that allowed the alarm to be silenced during exercises.

You can’t write this stuff. It’s like the Navy watched *The Hunt for Red October* and decided the takeaway was “cool, let’s make our ships dumber.”

Now, the internet is doing what the internet does best: absolutely torching the Navy. Reddit’s r/navy is currently a war zone of salty veterans and armchair admirals. Top comments include “Bro turned off his torpedo alarm like it was his alarm clock on a Monday morning” and “Next time, just tape a ‘Do Not Torpedo’ sign to the hull.” The AITA community is already debating whether the sailor is the asshole for turning off the alarm (spoiler: yes, you are, dude) or if the Navy is the asshole for having a system so fragile that one guy with a roll of duct tape can disable it.

The official Navy statement, released yesterday at 4 PM EST, is a masterpiece of bureaucratic spin. It says, quote, “The United States Navy is committed to the safety of its

Final Thoughts


Having followed amphibious warfare developments for decades, the "Valiant Shield" exercise’s integration of a torpedo strike against a decommissioned LPD-10—essentially a simulated kill on a ship class designed to survive such hits—suggests the Navy is recalibrating its threat models for peer-level conflict. The decision to sink a vessel with a torpedo, rather than the more cinematic missile or bomb, is a sobering reminder that beneath the surface, the real danger remains silent, deliberate, and devastatingly effective. In my view, this isn’t just a training evolution; it’s a pointed message that no hull, however versatile, is safe from the underwater domain in a war of attrition.