The Constitutional Crisis on Capitol Hill: Senate Democrats Weaponize War Votes to Break GOP Silence on Iran

As Operation Epic Fury enters its second week with seven U.S. service members dead and hundreds of Iranian civilians killed, a group of Senate Democrats is escalating a constitutional confrontation over Congress's role in the war.

A Showdown Over Hearings

Six Senate Democrats delivered an ultimatum to Majority Leader John Thune on Monday afternoon: either greenlight public committee hearings on the war in Iran, or face a sustained campaign of procedural war votes designed to grind the Senate's legislative agenda to a halt [1].

The group — Senators Cory Booker (D-NJ), Tim Kaine (D-VA), Adam Schiff (D-CA), Tammy Baldwin (D-WI), Chris Murphy (D-CT), and Tammy Duckworth (D-IL) — warned that unless Republicans agree to hold open hearings, "they will use the tools of the Senate to hold this public debate and a series of votes on the administration's war powers on the floor of the Senate" [1].

The threat marks a significant escalation in the minority party's pushback against what Democrats have characterized as an illegal war launched without congressional authorization. It also reflects growing frustration with the closed-door briefings that have been the only forum for lawmakers to question the administration's conduct of Operation Epic Fury [2].

"The American public deserves to hear directly from the administration about the scope, duration, cost, and legal basis for this war," Senator Kaine said, calling the closed briefings inadequate for democratic accountability [3].

The Failed War Powers Votes

The Democrats' new strategy follows the failure of two war powers resolutions in the span of 48 hours. On March 4, the Senate rejected a joint resolution co-authored by Kaine and Republican Senator Rand Paul that would have directed the removal of U.S. Armed Forces from hostilities against Iran not authorized by Congress. The vote fell 47-53, almost entirely along party lines [4][5].

Only two senators crossed the aisle: Rand Paul, the lone Republican to support the resolution, and John Fetterman of Pennsylvania, the lone Democrat to vote against it [6]. Paul, a longtime advocate of congressional war powers, excoriated his colleagues afterward, writing that Congress "should be ashamed" for ceding its constitutional authority [7].

The following day, the House of Representatives narrowly rejected a similar resolution by a vote of 212-219 [8]. Only two Republicans — Thomas Massie of Kentucky and Warren Davidson of Ohio — broke with their party, while four Democrats voted against the measure [9].

Source: GDELT Project

Data as of Mar 9, 2026CSV

Operation Epic Fury: Scope and Consequences

The war votes are playing out against the backdrop of a rapidly escalating military campaign. Operation Epic Fury began on February 28, 2026, when U.S. and Israeli forces launched nearly 900 strikes in the first 12 hours, targeting Iranian missile systems, air defenses, military infrastructure, and leadership [10]. The opening salvo killed Supreme Leader Ali Khamenei and dozens of senior officials [10].

In the first 72 hours alone, U.S. forces struck more than 1,700 targets across Iran, and at least 48 top Iranian leaders were killed in the joint U.S.-Israeli operations [11]. As of March 9, seven U.S. service members have been killed in action, with the most recent — Sgt. Benjamin N. Pennington, 26 — succumbing to wounds sustained during a March 1 enemy attack at Prince Sultan Air Base in Saudi Arabia [12].

Iranian civilian casualties have mounted as well. By March 3, the Red Crescent reported over 600 civilians killed, while Human Rights Activists in Iran estimated 742 civilian deaths [10]. These numbers have fueled the congressional pressure for transparency and accountability.

The Minab School Airstrike: A Catalyst for Action

No single event has galvanized the Democratic push for hearings more than the destruction of the Shajareh Tayyebeh girls' elementary school in Minab, Hormozgan province, on the first day of the campaign. The attack killed between 165 and 180 people — most of them girls aged 7 to 12 — making it the deadliest single strike of the war [13][14].

Initial confusion over responsibility gave way to mounting evidence of U.S. involvement. Investigations by The Washington Post, NPR, and other outlets concluded that the United States was likely responsible for the strike [15]. Video footage circulated online showing what munitions experts identified as a U.S. Tomahawk cruise missile striking in the vicinity of the school, which sat adjacent to an Islamic Revolutionary Guard Corps naval complex [16].

A preliminary U.S. assessment acknowledged the country was "likely" responsible but indicated the school was not intentionally targeted and may have been hit due to outdated intelligence that wrongly identified the area as still part of an Iranian military installation [15]. Human Rights Watch called for the attack to be investigated as a war crime [17].

The six Democratic senators issued a joint statement saying they were "horrified" by the bombing: "The killing of school children is appalling and unacceptable under any circumstance" [18]. Their demand for public hearings centers not just on broad war authorization questions but specifically on obtaining answers about how the Minab strike occurred and what steps are being taken to prevent similar incidents.

The Constitutional Fault Line

The confrontation over Iran hearings is the latest chapter in a decades-long tug-of-war between the executive and legislative branches over the power to wage war. Article I, Section 8 of the Constitution grants Congress the sole authority to declare war, but presidents of both parties have repeatedly initiated military action unilaterally, citing their authority as commander in chief [19].

The War Powers Resolution of 1973, passed over President Nixon's veto in the aftermath of the Vietnam War and the secret bombing of Cambodia, was designed to reassert congressional control. It requires presidents to notify Congress within 48 hours of deploying forces into hostilities and mandates withdrawal within 60 days absent congressional authorization [19][20].

In practice, the resolution has been a paper tiger. Presidents from both parties have routinely circumvented its provisions, launching operations they describe as "consistent with" rather than "pursuant to" the War Powers Act [20]. The Iran campaign is the latest and most dramatic example: a full-scale military operation launched without a congressional vote, declaration of war, or specific authorization for the use of military force.

Senator Kaine, who has championed war powers reform across three administrations, called the situation "the most brazen violation of the War Powers Resolution since its passage" [3]. The resolution he introduced would not have prevented the U.S. from defending itself against an imminent attack — it merely required that offensive hostilities against Iran be explicitly authorized by Congress [3].

Source: FRED / U.S. Energy Information Administration

Data as of Mar 4, 2026CSV

The Republican Position

Senate Republicans have largely rallied behind the administration, arguing that the president has inherent authority as commander in chief to respond to threats and that congressional micromanagement of military operations would endanger troops. The 52 Republicans who voted to block the war powers resolution contend that Operation Epic Fury falls within the president's executive authority, particularly given Iran's nuclear program and its support for proxy forces that have attacked U.S. interests [5].

Fox News reported that the operation "survived its Senate challenge" as "Republicans close ranks behind Trump," framing the vote as a show of party unity behind the president's national security strategy [21].

Senator Thune has not publicly responded to the Democrats' demand for hearings, but Republican leaders have pointed to the classified briefings as sufficient oversight. The disconnect between the two parties' views on what constitutes adequate congressional engagement has become a central fault line in the debate.

The Fetterman Factor

Senator John Fetterman's decision to vote with Republicans against the war powers resolution was perhaps the most politically significant crossover in the vote. The Pennsylvania Democrat — who has increasingly broken with his party on Israel-related matters — joined 52 Republicans in opposing the measure, denying Democrats even a simple majority [6].

Progressive groups responded with fury. Common Dreams ran a headline declaring that "Fetterman and Senate GOP Block War Powers Resolution on Iran," putting the Democratic senator's name alongside the Republican majority [22]. His vote underscored the difficulty Democrats face in assembling a coalition broad enough to constrain the president's war-making authority, even within their own caucus.

What Comes Next

The Democrats' procedural threat carries real weight. Under Senate rules, the minority can force votes on privileged resolutions under the War Powers Act, requiring the majority to repeatedly spend floor time defeating them rather than advancing its own agenda. If the six Democrats follow through, they could trigger a series of disruptive votes that would consume days of Senate floor time [1].

The strategy echoes tactics used by war powers advocates in previous conflicts, including during the debate over U.S. involvement in Yemen, when a bipartisan coalition eventually forced votes that passed both chambers — only to be vetoed by President Trump during his first term [19].

But the political landscape is different now. With American troops actively in harm's way and the operation still in its early stages, some Democrats worry that forcing repeated votes could be seen as undermining the military. Others argue that the constitutional principle at stake — whether Congress has any meaningful role in decisions about war and peace — transcends political optics.

Senator Murphy framed the stakes bluntly: "If Congress doesn't assert its authority now, during an active war launched without our consent, then the War Powers Resolution is dead and the Constitution's grant of war powers to Congress is meaningless" [1].

The Broader Implications

The Iran confrontation is testing the boundaries of executive war-making authority in ways not seen since the 2003 invasion of Iraq — the last time Congress explicitly voted to authorize a major military campaign. Every subsequent military operation, from Libya to Syria to the ongoing campaign in Iran, has been conducted under expansive interpretations of presidential authority that have progressively marginalized Congress's constitutional role.

The Council on Foreign Relations noted that "Congress Declines to Demand a Say in the Iran War" after the failed votes, calling it a continuation of a pattern in which "lawmakers express concern about executive overreach but ultimately decline to use their constitutional tools to constrain it" [23].

Whether the Democrats' latest gambit breaks that pattern — or becomes another footnote in the long retreat of congressional war powers — may depend on whether public pressure, amplified by the Minab school tragedy and mounting American casualties, forces Republican leaders to the negotiating table.

For now, the constitutional standoff on Capitol Hill mirrors the military one in the Persian Gulf: both sides are escalating, and neither shows signs of backing down.