America is at war with a country it says it wants a deal with, and on the same Tuesday it refused negotiations, it dropped a bomb on a wedding.
"The U.S. military never targets civilians, unlike the IRGC."
โ Capt. Tim Hawkins, U.S. Central Command, on the strike that killed at least five people, two of them children, at an Iranian wedding
On Tuesday the United States carried out its second consecutive night of attacks on Iran, and the headline target in the American accounting was the Islamic Revolutionary Guard Corps. But in the city of Kuhestak, in southern Hormozgan province, the bomb landed on a house where a wedding was underway.
At least five people were killed. Two of them were children: Amir-Ali Karimi, four years old, and Mohammad Mollahi, sixteen. More than 68 others, women and children among them, were wounded. The Iranian Red Crescent released footage of a building with its walls and windows blown outward, debris scattered across the street, and children being treated in a hospital in nearby Sirik.
In the space of a few hours, this became a war-crime case. Iran's foreign ministry spokesman called it a "war crime" and part of an "unlawful war of choice." The Red Crescent formally asked the International Criminal Court to open an investigation. Yemen's National Human Rights Commission called it "a full-fledged war crime" and a violation of the four Geneva Conventions, which forbid deliberately targeting civilians and safe residential areas.
The official American line did not wobble, because the official American line is not built to wobble. Central Command's spokesperson, Capt. Tim Hawkins, told the Associated Press that the military was "aware of the reports of civilian casualties," then added that those reports "originated from Iranian state media."
He did not explain what military purpose a wedding ceremony served. He did not name a target inside the home. He did not account for the sixteen-year-old.
Translation: the strike is real, the video is real, and the denial is a script, not an answer. When a government's response to a bombing of a wedding is "we never target civilians, unlike the IRGC," it has stopped distinguishing between a military objective and a body on a hospital bed.
That deflection is the point. It is the same reflex the war has run on since the opening salvo in late February: name an enemy, describe a precision strike, then treat the civilian dead as an inconvenient annotation to be attributed to the other side's "state media."
The strikes were framed as retaliation for Iranian attacks on shipping and U.S. personnel near the Strait of Hormuz, the chokepoint through which roughly a fifth of the world's oil normally flows. That strait remains under what Tehran calls a blockade and what it treats as leverage. Washington, in other words, is jostling for control of the waterway while hitting the coast around it, and the coastal cities hit on Tuesday included Bandar Abbas, Jask, Konarak, Asaluyeh, and Qeshm Island, along with a civilian airport and, per Iranian reports, a fishing pier and parts of the regional power grid.
Trita Parsi, executive vice president of the Quincy Institute for Responsible Statecraft, made the arithmetic uncomfortable. The United States had bombed the wedding, he noted, roughly ten days after the administration claimed its new sanctions on Iran would make military action unnecessary.
The sanctions were the promise. The bombs were the follow-through. Both cannot be the plan, but the government has never had to be internally consistent, only loud.
The threat followed within hours. On Truth Social, Trump wrote that if the "failed Nation of Iran" retaliates, "it will not be the biggest attack of them all, that is waiting in the wings." Later that night he repeated a version for Fox News: if Iran responds, "they'll be hit much harder" and "they'll be no longer." He dismissed returning to talks, saying an agreement with Tehran "isn't worth the paper it's written on."
Iran, for its part, did not back down. Foreign ministry spokesman Esmaeil Baghaei vowed that Tehran would "respond to these savage crimes with firmness," and described the attacks as part of a "catalog of atrocities" that includes a February school strike that killed around 150 people, most of them children.
More than 1,700 Iranian civilians, per the U.S.-based Human Rights Activists News Agency, were killed in the war's opening phase between late February and mid-April. That is before this week.
The retaliation came overnight. Iran said its Revolutionary Guard fired ballistic missiles at U.S. bases in Kuwait, Bahrain, Jordan, and Iraq's Kurdish region, and claimed strikes that killed U.S. personnel and destroyed drones at Ali Al Salem Air Base in Kuwait. Kuwait said it intercepted the drones and missiles and reported no casualties. Jordan said it shot down ten of the missiles and that the remaining three landed in unpopulated areas. As of Wednesday morning, the United States had not confirmed or denied any American deaths.
The exchange is now a loop: strike, threat, counter-strike, new threat, a bigger one "waiting in the wings." Each side holds the Strait of Hormuz's economy hostage to the other's next move, and the civilians on the southern coast keep absorbing the difference.
Baghaei put the danger in a sentence that deserved to be printed larger than the news ticker it appeared on: "More dangerous than the bomb itself is the normalization of bombing. And more dangerous than silence is the conversion of silence into legitimacy."
The wedding in Kuhestak is the clearest example yet of that normalization. Not the targeting of a general, not a drone base, not a missile site. A family, a celebration, a house. Five dead, two of them small enough to be carried. And the response from the country that did it is a boilerplate that a marketing department would reject.
The question is not whether this was a war crime. The question is why anyone still thinks the word means something, when the government that dropped the bomb gets to be the first to deny it.
Comments (0)
No comments yet. Be the first to speak up.
Join the Riot
Login with Google to leave a comment.
Login to Comment