House Narrowly Defeats Iran War Powers Resolution as Thousands More US Troops Head to Middle East

The bill failed in a vote of 213-214, with just one Democrat voting against it and one Republican supporting it

The House on Thursday just barely defeated a War Powers Resolution that would have directed President Trump to end hostilities against Iran that haven’t been authorized by Congress, as the US military is enforcing a blockade on Iranian ports and is deploying thousands more troops to the region to prepare for potential ground operations.

The bill failed in a vote of 213-214, with just one Democrat, Rep. Jared Golden (ME), joining Republicans to kill the legislation. Only one Republican, Rep. Thomas Massie (R-KY), voted in favor, while Rep. Warren Davidson (R-OH), who supported a previous War Powers Resolution, voted “present.” Rep. Nancy Mace (R-SC), who previously suggested she might support the bill, didn’t vote.

A day earlier, the Senate voted on a similar War Powers Resolution, which failed 52 to 47, with just one Republican, Sen. Rand Paul (R-KY), supporting it and one Democrat, Sen. John Fetterman (PA), voting against it.

The failure of Congress to reassert its war powers over President Trump, who launched the war without any congressional authorization, a violation of the Constitution, comes amid a very fragile truce between the US and Iran, and as the Trump administration is threatening to restart the bombing campaign if a deal isn’t reached.

Polling has shown that the war against Iran is extremely unpopular among Americans, and the fuel crisis sparked by the conflict has led to rising gas prices in the US. Since the US and Israel launched the war on February 28, the price Americans have to pay for gas at the pump has increased by more than 30%.

Dave DeCamp is the news editor of Antiwar.com, follow him on Twitter @decampdave.

Join the Discussion!

We welcome thoughtful and respectful comments. Hateful language, illegal content, or attacks against Antiwar.com will be removed.

For more details, please see our Comment Policy.