Tuesday, 7 April 2026

Trump declared it a triumph at midnight: "WE GOT HIM!" But does the scale of what was sent in match the story?

 Collective Evolution


By Joe Martino, founder of CE

The story of the F-15E shoot-down over Iran and the subsequent "rescue mission" is one of those stories that may not at all be what we're told. But before we throw way the official narrative, let's look at some details closely.
First, the story we were given is that On April 3rd, an F-15E Strike Eagle was shot down over southwestern Iran, both crew members ejected, one was recovered quickly, and the other, the weapons systems officer, spent more than 24 hours evading capture in the rugged Zagros Mountains before being extracted by Navy SEAL Team 6 in what the Pentagon itself described as "one of the most challenging and complex" special operations missions in American history.
Two MC-130J Commando II aircraft were destroyed on the ground inside Iran, four MH-6 Little Bird helicopters were destroyed, a temporary forward base was established inside a nation the U.S. is actively in conflict with, hundreds of special operators were deployed, Israel provided intelligence and air support, and the official explanation for why two of the most sophisticated covert insertion aircraft in the U.S. military inventory ended up destroyed on an abandoned agricultural airstrip shifted, depending on which briefing you read, between "stuck in the mud," "sandy soil," and "mechanical issues."
Trump declared it a triumph at midnight: "WE GOT HIM!"
But does the scale of what was sent in match the story?
One of the things I've come to understand from years of trying to make sense of how power actually operates is that when the scale of a response doesn't match the stated objective, that gap is almost always worth examining carefully, because systems don't waste resources without reason, and the people who plan these operations are not careless with either money or lives.
You don't deploy two of the most sophisticated covert insertion aircraft in the U.S. military inventory - aircraft specifically engineered for clandestine special operations in denied territory, built to insert and extract Tier 1 forces from places that don't have runways - to recover one injured airman whose location had already been pinpointed by satellite and CIA technology.
You don't send SEAL Team 6 with Delta Force on standby, hundreds of operators, dozens of warplanes, and establish a temporary military base inside a hostile nation for a single rescue, and then describe that rescue as one of the most complex operations in American military history, because those two things simply don't add up together - either the operation was genuinely that complex, which means the stated objective wasn't the only objective, or the Pentagon is wildly overstating the difficulty of recovering one man, which would be its own kind of dishonesty worth examining.
The Pentagon called this "one of the most challenging and complex" missions in American history, and I think we need to sit with that claim for a moment because if that's true, then the question of why it was that complex is important.
The location of the 'rescue' is not incidental. Open-source analysts geolocated the wreckage almost immediately after Iranian state media published footage of the destroyed aircraft, and what they found is that the forward base was established approximately 35KM's from Isfahan's nuclear complex - the site where Iran's near-weapons-grade highly enriched uranium is believed to be stored in tunnels that survived last year's U.S.-Israeli strikes on Iran's nuclear infrastructure.
Before those strikes, the IAEA estimated Iran held roughly 440KG's of uranium enriched to 60%, which is a short technical step from the 90% weapons-grade threshold, and while the strikes damaged facilities, the uranium itself wasn't destroyed - with subsequent intelligence assessments suggesting a stockpile of roughly 200KG's remains accessible through a narrow access point in the rubble near Isfahan. Trump himself threatened in late March, just days before this operation: "They're going to give us the nuclear dust. If they don't do that, they're not going to have a country."
And then, days later, hundreds of U.S. special operators landed 35KM's from that uranium, with the kind of force you'd need not for a rescue but for what former defense officials described to the Washington Post as a "temporary occupation" - planes taking off from a commandeered runway, heavy equipment, civilian nuclear specialists, a slow and meticulous process that one former special operator called "an extremely deadly" undertaking.
I'm not telling you that's what happened, because I don't know that with certainty, and intellectual honesty requires me to hold that clearly. What I am telling you is that the proximity is not incidental, the force package is not consistent with the stated mission, and the combination of those two facts demands a more serious answer than we've been given.
Let's look further, the MC-130J Commando II is not a general-purpose transport plane that happened to be available, it is purposely built for unimproved airstrips in denied areas, engineered specifically for the conditions that allegedly disabled it, and the idea that not one but two of them simultaneously suffered disabling malfunctions on a mission to recover a single airman strains the kind of credibility that should matter to anyone paying attention.
Former CIA officer Larry C. Johnson, writing in the hours after the operation, offered a more technically grounded explanation, that the aircraft likely took hits upon entry and while on the ground. Of course, this is not a fringe theory; it's from a former intelligence professional applying basic operational logic to the physical evidence that Iran's state media made publicly available almost immediately.
What's telling is not just the explanation itself but the way it kept changing, because when an official story shifts from "stuck in the mud" to "sandy soil" to "mechanical issues," that's usually not a sign that the truth is getting clearer, it's a sign that the original story didn't hold up to the first round of scrutiny, and the people managing the narrative are adjusting in real time. This is exactly the same as the rhetoric coming out of the U.S. about WHY they were going to ar with Iran to begin with, remember that?
I've written before about the mechanics of how we get misled, and the important thing to understand is that it's rarely through outright fabrication. More often it works through selective framing, through what gets left out, through the questions that never get asked by the people with the loudest microphones, and through a reductionist lens that finds the one angle supporting the preferred narrative while making no effort to examine the full picture.
Holding The Uncertainty Without Collapsing It
Iran's military compared the operation directly to Eagle Claw, the catastrophic 1980 attempt to rescue American hostages in Tehran that ended in disaster at the Desert One staging site, with C-130s, sandy terrain, and burning American wreckage left behind on Iranian soil displayed as a trophy, and Iran's Khatam al-Anbiya spokesman said explicitly that the operation was "planned as a deception and escape mission at an abandoned airport in southern Isfahan under the pretext of recovering the pilot of a downed aircraft" and was "completely foiled."
Now, I want to be careful here, because this is precisely where critical thinking matters most and where people tend to make the error I've spent years trying to help others avoid. Iran has its own incentives to shape this narrative, state media is not a neutral source, and the fact that Iran's version fits the physical evidence more consistently than Washington's version does not automatically make it true.
What it does mean is that the alternative explanation deserves serious engagement rather than reflexive dismissal, and that the honest intellectual position is to hold both possibilities with genuine openness rather than collapsing the uncertainty in either direction because one version feels more comfortable. We want to always follow where the best evidence leads, not think in terms of who is potentially more bias than the other or thinking in terms of what in in-group thinks.
What we can say with confidence is this: the scale of the operation was far beyond what a single-airman rescue requires, the forward base was established near one of the most strategically sensitive nuclear sites on Earth, two purpose-built covert insertion aircraft were destroyed under circumstances whose explanation keeps shifting, multiple former intelligence and military professionals have publicly raised the possibility of a dual mission, and the administration maintained a 36-hour media blackout before presenting its version of events.
That's not a conspiracy theory, that's a set of documented facts that don't cohere around the official explanation, and they deserve a serious answer.
What I keep returning to is something I've been exploring for a long time in my work - the idea that our systems are not designed to serve the public interest, but are instead shaped by incentives that reward narrative control, perception management, and the protection of power. Understanding this isn't about labelling anyone as 'evil' but about developing the clarity to see the game that's being played so you can stop being an unwitting participant in it.
A public that can only process the emotionally satisfying version of events, the brave soldier, the daring rescue, the midnight declaration of victory, is a public that can be led almost anywhere, not only because the people leading them are necessarily malicious but because the system rewards the story that generates compliance and punishes the story that generates questions.
This is what I've called Breaking the Illusion. It's about not arriving at a new set of certainties to replace the old ones, but developing the capacity to sit with complexity, to ask better questions, and to resist the pull of the tidy narrative long enough to actually look at what the evidence says.
-----
By Joe Martino, founder of CE




0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]

<< Home