The War Powers Resolution of 1973 and the Veto Congress Overrode

Richard Nixon vetoed the War Powers Resolution on October 24, 1973, and in most years that would have been the end of it. Overriding a veto takes two-thirds of both chambers, and presidents rarely lose those fights over national security. But the autumn of 1973 was not most years. Four days before the veto, Nixon had ordered the firing of the special prosecutor investigating Watergate, and his attorney general and deputy attorney general had resigned rather than carry it out. The country had just learned, months earlier, that the United States had secretly bombed Cambodia in 1969 and 1970 while the public and most of Congress were told otherwise. The last American combat troops had left Vietnam that spring, after a war that had never been declared. On November 7, 1973, the House voted to override, 284 to 135, and the Senate followed the same day, 75 to 18. For the first time, Congress had written into law a procedure meant to stop a president from fighting a war on his own. The fifty-three years since have been a long argument about whether it worked.

In short: The War Powers Resolution requires presidents to report to Congress when they send forces into hostilities and to withdraw them after 60 days unless Congress authorizes the action. It passed over Nixon's veto in 1973, when his power was at its lowest. Presidents of both parties have since reported under it while denying it binds them, and Congress has rarely forced the issue.

The war that was never declared

The Constitution splits war powers on purpose. Article I gives Congress the power to declare war, to raise and support armies, and to make rules for the armed forces. Article II makes the President commander in chief. The framers' notes from the 1787 convention show they changed the draft from giving Congress the power to "make" war to the power to "declare" it, leaving the President room to repel sudden attacks. They did not intend a president to start wars on his own.

The United States last formally declared war in 1942, against Germany's allies in Europe. Korea was fought without a declaration, under the authority of United Nations resolutions and the President's own claims. Vietnam was fought under the Gulf of Tonkin Resolution of August 1964, which Congress passed almost unanimously after reported attacks on American destroyers, one of which did not happen. Johnson's administration later treated that resolution as a blank cheque for a war that grew to more than half a million American troops.

By the early 1970s, many members of Congress who had voted for the Tonkin resolution felt deceived. Congress repealed it in January 1971. But repeal did nothing to stop the war, which Nixon continued on his own authority as commander in chief. The revelations about the Cambodia bombing, and Nixon's 1970 ground incursion into Cambodia, convinced many legislators that the problem was structural. Congress needed a rule that applied before a war began, not after.

Two sponsors and a dissenter

The law had many parents, but two names belong on it. In the Senate the leading sponsor was Jacob Javits, a liberal Republican from New York who had spent years arguing that Congress had surrendered its war powers by inches. In the House the lead was Clement Zablocki, a Democrat from Milwaukee who chaired the foreign affairs subcommittee that handled the bill and who had been, for much of the Vietnam war, a supporter of it. A Republican from Manhattan and a Democrat from industrial Wisconsin made an unlikely pair. Their partnership is a reminder that the 1973 law was not a partisan weapon. It was an institutional one.

The House and Senate versions differed, and the differences mattered. The Senate's bill tried to list the situations in which a president could use force without Congress, such as repelling an attack on the United States or rescuing endangered Americans abroad. The House's bill focused more on procedure: reporting, a clock and a way to end the action. The conference committee settled largely on the House approach.

That compromise cost the bill one of its original champions. Senator Thomas Eagleton of Missouri, a Democrat who had been among the sponsors of the Senate version, voted against the final bill and against the override. His objection was the mirror image of Nixon's. Where Nixon thought the law took too much from the President, Eagleton argued that it handed the President something he had never had under the Constitution: an apparent licence to wage war anywhere, for any reason, for up to 60 days before Congress had to say a word. The history that followed gave his warning more weight than his colleagues expected. Presidents have rarely needed more than 60 days to do what they set out to do.

What the law actually requires

The War Powers Resolution is short, and its main parts are easy to state.

Consultation. The President "in every possible instance" is to consult with Congress before introducing armed forces into hostilities or situations where hostilities are clearly imminent, and to keep consulting while they are there.

Reporting. Within 48 hours of introducing forces into hostilities, or into another country equipped for combat in certain circumstances, the President must send a written report to the Speaker of the House and the President pro tempore of the Senate explaining the circumstances, the legal authority and the expected scope and duration.

The clock. Once a report is submitted, or was required to be, the President has 60 days to end the use of forces unless Congress has declared war, specifically authorized the action, or extended the period, or is physically unable to meet because of an attack. The President may take 30 more days if needed to withdraw safely.

The off switch. Section 5(c) said that Congress could direct the President to remove forces at any time by a concurrent resolution, which passes both chambers but does not go to the President for signature.

The law also says plainly that it does not grant the President any new authority to use force, and that authority may not be inferred from appropriations bills or treaties unless they say so specifically. That was aimed straight at the Vietnam experience, in which continued funding had been treated as continued approval.

Why Nixon called it unconstitutional

Nixon's veto message argued that the resolution tried to take away, by statute, powers the President held under the Constitution. Requiring forces to come home after 60 days unless Congress acted, he said, would let Congress end a military action by doing nothing. He also warned that announcing a deadline in advance would encourage adversaries to wait the United States out.

Those arguments have outlived him. Every administration since, Democratic and Republican, has taken the position that the War Powers Resolution is at least partly unconstitutional, while generally submitting reports "consistent with" it rather than "pursuant to" it, a careful wording that complies in practice without conceding the law binds them.

It is worth taking the executive's case seriously. Modern threats can move faster than Congress. Rescues, evacuations and responses to attacks on Americans may need to happen in hours. A rigid clock could, in some circumstances, hand adversaries a tactical gift. And Congress has its own incentives to avoid votes on war, preferring to criticize afterward rather than take responsibility beforehand.

The answer is that the law already allows for all of that. It requires only a report within 48 hours and gives 60 to 90 days before Congress must act. A president who believes in a mission has two months to persuade the country's elected legislators. If he cannot, the Constitution's design suggests the mission should not continue. The trouble has been less the law's design than both branches' willingness to work around it.

Fifty years of tests

The record since 1973 is a catalogue of creative interpretation.

In 1983, after American Marines were deployed to Lebanon as part of a multinational peacekeeping force, Congress passed a law authorizing their presence for 18 months, finding that the War Powers clock had started. President Reagan signed it while saying he did not accept that the clock applied. Less than two weeks later, the bombing of the Marine barracks in Beirut killed 241 American service members, and the force was withdrawn the following year.

The same year, the Supreme Court decided INS v. Chadha, which struck down "legislative vetoes," arrangements that let Congress overrule executive actions without presenting a bill to the President. That decision put the War Powers Resolution's concurrent-resolution provision in grave doubt. Congress responded by adding a procedure for expedited consideration of joint resolutions, which do go to the President and can be vetoed.

In 1999, the bombing campaign over Kosovo ran past 60 days without congressional authorization. Members of Congress sued, and the courts dismissed their case without reaching the merits, as courts have done in nearly every War Powers dispute.

In 2011, the Obama administration argued that the American role in the NATO air campaign over Libya, after the initial weeks, did not amount to "hostilities" under the law, because American forces were mostly supporting allies, faced little risk of casualties and were not engaged in sustained fighting with ground troops. Many legal scholars, including some within the administration, disagreed. The argument let the operation continue past the clock.

In 2019, Congress for the first time passed a joint resolution under the War Powers framework directing the removal of American forces from hostilities, in this case American support for the Saudi-led coalition in Yemen's civil war. President Trump vetoed it, and the Senate failed to override. In 2020, after the killing of the Iranian general Qassem Soleimani, Congress passed a resolution sponsored by Senator Tim Kaine of Virginia directing an end to hostilities against Iran not authorized by Congress. Trump vetoed that too.

Since then, presidents have continued to strike targets abroad on their own authority, including the June 2025 strikes on Iranian nuclear sites, after which the Senate rejected another Kaine resolution. Both parties have been in the White House for these episodes. Both parties have defended presidential power when it was their president.

What the law got right anyway

It would be easy to call the War Powers Resolution a failure, and many have. But that verdict misses some things.

The reporting requirement is honoured. Presidents file reports, which means Congress and the public learn officially when forces enter hostilities. More than a hundred such reports have been filed over the decades.

The law also gives Congress a ready tool, a privileged resolution that can force a floor vote, which a single member can use to make colleagues go on the record. The Yemen and Iran votes would have been much harder to bring about without it. Those votes passed with support from both parties, a coalition of progressive Democrats and Republicans skeptical of foreign entanglements. A law that makes such coalitions possible is doing something.

And the 60-day clock, even when evaded, shapes planning. Administrations design operations and legal theories around it. That is not the same as obedience, but it is not nothing. Lawyers in the Pentagon and the White House spend real time asking whether an operation will last past the deadline, and that question alone has shaped how some missions were designed and how long they ran.

The repair Congress keeps not making

The deeper problem is that the War Powers Resolution depends on Congress wanting to use it. Members who prefer not to vote on war can let a president act and complain later. Members of the president's party usually defend him. Courts stay out.

Proposals to fix this have come from across the spectrum. Some would define "hostilities" in the statute so that a remote air or drone campaign could not be called something else. Some would cut off funds automatically when the clock runs out. Some would replace open-ended authorizations for the use of military force with ones that expire and must be renewed. A bipartisan group of senators introduced a broad rewrite, the National Security Powers Act, in 2021; it did not advance.

The new Congress that takes office in January 2027 will inherit the same choice its predecessors faced. I think the case for acting is strong, and it does not depend on which party holds the White House. A rule that binds only presidents you oppose is not a rule. We follow these questions on our Pentagon and militarism page and on our democracy and the rule of law page.

The men and women who voted to override Nixon in 1973 were not all doves, and they were not all Democrats. Many had supported the Vietnam war at first. What united them was a conviction that the decision to send Americans to kill and die should be made in the open, by the branch closest to the people. That conviction is still worth defending, by whoever holds power.

What you can do

• Ask your members of Congress where they stand. Enter your address at find your representatives for the phone numbers and contact forms of your representative and senators, and see their latest votes. Ask whether they would support defining "hostilities" in law and sunsetting open-ended war authorizations.
• Look at how your representatives voted on war powers. The Congress votes and bills page shows recent roll calls, and the common-ground page shows bills both parties passed together, where war-powers coalitions sometimes appear.
• Connect with groups working on this. Veterans' organizations, peace groups and civil-liberties groups all work on war powers; you can find them by cause and state in our organizations directory.