Democrats voiced concern that the United States is becoming further entrenched in another lengthy conflict in the Middle East. They promised to keep raising the issue through more war powers votes in the coming weeks.

The 213-214 vote came one day after a similar effort failed in the Senate. The U.S. and Israel struck Iran on Feb. 28, and a fragile ceasefire is now in its second week.

Democrats overwhelmingly supported the attempt to rein in Trump’s use of military force.

“We’re standing at the edge of a cliff and Congress must act before the president pushes off,” said New York Rep. Gregory Meeks, the ranking Democrat on the House Committee on Foreign Affairs. “Every day we delay, we inch closer to a conflict with no exit ramp.”

Republicans tried to cast the effort as hypocritical.

Florida Rep. Brian Mast, the committee chairman, said Congress never voted on a war powers resolution when the U.S. attacked Iranian-backed Houthis in Yemen in 2024 while Democrat Joe Biden was president.

“When Joe Biden was responding to merchant marine vessels being attacked, it was OK. No war power needed. It went on for about a year,” Mast said. “President Trump responds — war power, war power, war power. … That’s the hypocrisy.”

Under the War Powers Act of 1973, Congress must declare war or authorize use of force within 60 days — a deadline in the Iran war that will arrive at the end of April. The law provides for a potential 30-day extension, but lawmakers have made clear that they want the Republican administration to soon lay out a plan for the war’s end.

While the House vote failed, it gave Democrats an opportunity to highlight some of the most negative effects of the war: the billions of dollars spent, the death of at least 13 service members, the soaring gas prices and fissures with long-standing allies who do not support Trump’s actions.

“Gas prices at home are up to $7 in my home state, and families are hurting,” said Rep. Pramila Jayapal, D-Wash. “Another 10,000 U.S. troops are being sent in to join 50,000 already stationed in the Middle East with absolutely no strategy, no plan and no exit.”

Republicans defended Trump as taking decisive action against an Iranian government that has long terrorized the Middle East and its own people.

“President Donald Trump has sent a message that those who threaten the United States and our partners will be ultimately held accountable,” said Rep. Joe Wilson, R-S.C.

In Thursday’s vote, Rep. Thomas Massie of Kentucky was the only Republican to cross party lines and vote for removing U.S. forces from the war. Rep. Jared Golden of Maine was the only Democrat to vote against the measure.

The first House vote to curb Trump’s miliary action with Iran failed in early March, 212-219.

The post House rejects effort to withdraw US forces from the Iran war as Republicans stick with Trump appeared first on The Hemet & San Jacinto Chronicle.

A U.S. missile strike. An initial statement emphasizing precision. Then, later, reports that civilians — including many children — were among the dead. In Afghanistan, through the early and mid-2000s, these reports came so often they formed a grim pattern. Each incident is explained as an anomaly, but over time, the pattern itself became the story.

Now similar reports are emerging from Iran. A new investigation alleges that a Feb. 28 strike by the U.S. hit an elementary school and sports hall in the southern city of Lamerd, with children once again among the dead. U.S. Central Command has since denied carrying out any strike in or near Lamerd that day, calling the reports false.

Independent verification is difficult because Iran shut down its internet, but Americans should nevertheless be concerned, especially after at least 175 people including many children were reported killed in a U.S. strike on a different school in Minab that same day. The cycle is familiar, with allegations of civilian harm followed by official denials, and no independent access to quickly verify the facts.

I was a civilian protection advisor to the chairman of the Joint Chiefs during the first Trump administration. I worked inside the Pentagon with military professionals who took the issue of civilian harm seriously. They saw avoiding civilian casualties as a matter of military discipline and their own humanity. I know what it looks like when civilian protection works. This isn’t it.

Over more than two decades of armed conflict, U.S. efforts to reduce civilian harm have moved in fits and starts, with periods of progress followed by setbacks and recurring mass casualty events. Pressure often came from civil society, public outrage and negative headlines, but also from within the armed forces. Senior commanders came to see civilian casualties not just as “collateral damage,” but also as operationally counterproductive.

That recognition led to real changes including tighter rules, better intelligence practices and eventually the creation of systems within the Pentagon meant to track, investigate and learn lessons to reduce harm. By the time U.S. troops were withdrawing from Kabul in 2021, those lessons were just beginning to be institutionalized across the armed forces.

What is happening now is undoing that progress. Safeguards built over years are being torn down, and it is unclear whether senior military leaders are willing to push back.

One major incident of harm to civilians can be a mistake. But when reports come in about multiple strikes on a variety of places where families and children gather, it raises a question about whether something larger is at work. It could be failures of intelligence or targeting decisions, or that the level of risk to civilians now being accepted has risen.

There are warning signs that in this policy environment, the U.S. military will not be led to correct its course. Defense Secretary Pete Hegseth publicly dismissed what he calls “stupid rules of engagement” and emphasized making the military “more lethal.” At the same time, Hegseth has weakened or sidelined efforts designed to reduce civilian harm in war. Those signals matter because they shape what military lawyers, analysts and commanders understand to be expected of them. In short, they shape the military’s culture.

We don’t know all the facts yet about the Minab school strike or the disputed one at the sports complex in Lamerd, but we’ve seen enough to know that the attacks can’t be written off as isolated mistakes. Before and since the start of the U.S. war on Iran in February, there has been little sustained public debate and no congressional hearings about the risks of American military action in Iran, including the inevitable civilian casualties that result from using powerful explosive weapons in populated areas. During the war in Afghanistan, each deadly strike on a wedding party or family compound did more than take civilian lives. It fueled anger at the U.S. and magnified skepticism that our military was trying to minimize civilian harm in any way.

Americans are entitled to clear answers about who and what is being targeted, what its military is doing to protect Iranian civilians and how possible violations of the laws of war are being investigated. This is basic public oversight that should accompany the use of military force. When incidents are openly disputed, as in the Lamerd strike, the need for impartial and transparent investigations becomes more, not less, important. If the U.S. military was acting lawfully, it should show it. But if it wasn’t, the public deserves to know that too.

The United States has long claimed to fight according to international law and to benefit from doing so. But that means little if the rules are mocked and actions don’t match reality. Waiting to recognize these patterns of civilian harm, and to correct them, will once again cost lives.

The post Americans deserve answers about civilian casualties in Iran appeared first on The Hemet & San Jacinto Chronicle.

WASHINGTON (AP) — A Pentagon police officer died after being stabbed Tuesday during a burst of violence at a transit center outside the building, and a suspect was shot by law enforcement and died at the scene, the Pentagon said Tuesday.

The Pentagon, the headquarters of the U.S. military, was temporarily placed on lockdown after someone attacked the officer on a bus platform shortly after 10:30 a.m. The ensuing violence, which included a volley of gunshots, resulted in “several casualties,” said Woodrow Kusse, the chief of the Pentagon Force Protection Agency, which is responsible for security in the facility.

The deaths of the officer and the suspect were first confirmed by officials who were not authorized to discuss the matter and spoke to The Associated Press on condition of anonymity. The Fairfax County Police Department also tweeted condolences about the officer’s death. Officials said they believe two bystanders were injured.

The suspect was identified by multiple law enforcement officials as Austin William Lanz, 27, of Georgia.

The officer was ambushed by Lanz, who ran at him and stabbed him in the neck, according to two of the law enforcement officials. Responding officers then shot and killed Lanz. Investigators were still trying to determine a motive for the attack and were digging into Lanz’s background, including any potential history of mental illness or any reason he might want to target the Pentagon or police officers.

The officials could not discuss the investigation publicly and spoke to AP on condition of anonymity.

Lanz had enlisted in the U.S. Marine Corps in October 2012 but was “administratively separated” less than a month later and never earned the title Marine, the Corps said in a statement.

The episode on a busy stretch of the Washington area’s transportation system jangled the nerves of a region already primed to be on high alert for violence and potential intruders outside federal government buildings, particularly following the Jan. 6 riot at the Capitol.

At a Pentagon news conference, Kusse declined to confirm that the officer had been killed or provide even basic information about how the violence had unfolded or how many might be dead. He would only say that an officer had been attacked and that “gunfire was exchanged.”

Kusse and other officials declined to rule out terrorism or provide any other potential motive. But, Kusse said the Pentagon complex was secure and “we are not actively looking for another suspect at this time.” He said the FBI was leading the investigation.

“I can’t compromise the ongoing investigation,” Kusse said.

The FBI confirmed only that it was investigating and there was “no ongoing threat to the public” but declined to offer details or a possible motive.

Later Tuesday, the Pentagon Force Protection Agency issued a statement confirming the loss of the officer, and Defense Secretary Lloyd Austin expressed his condolences and said flags at the Pentagon will be flown at half-staff.

“This fallen officer died in the line of duty, helping protect the tens of thousands of people who work in — and who visit — the Pentagon on a daily basis,” Austin said in a statement. “This tragic death today is a stark reminder of the dangers they face and the sacrifices they make. We are forever grateful for that service and the courage with which it is rendered.”

Tuesday’s violence occurred on a Metro bus platform that is part of the Pentagon Transit Center, a hub for subway and bus lines. The station is steps from the Pentagon building, which is in Arlington County, Virginia, just across the Potomac River from Washington.

An Associated Press reporter near the building heard multiple gunshots, then a pause, then at least one additional shot. Another AP journalist heard police yelling “shooter.”

A Pentagon announcement said the facility was on lockdown, but that was lifted after noon, except for the area around the crime scene.

Austin and Gen. Mark Milley, chairman of the Joint Chiefs of Staff, were at the White House meeting with President Joe Biden at the time of the shooting. Pentagon spokesman John Kirby said Austin returned to the building and went to the Pentagon police operations center to speak to the officers there.

It was not immediately clear whether any additional security measures might be instituted in the area.

In 2010, two officers with the Pentagon Force Protection Agency were wounded when a gunman approached them at a security screening area. The officers, who survived, returned fire, fatally wounding the gunman, identified as John Patrick Bedell.

Find your latest news here at the Hemet & San Jacinto Chronicle

The post Officer dead, suspect killed in violence outside Pentagon appeared first on The Hemet & San Jacinto Chronicle.