The Pentagon and Congress Must Stop Raiding the Afghan War Fund

House Budget Committee member Rep. Mick Mulvaney, R-S.C., listens to testimony from Budget Director Jack Lew, Feb. 15, 2011, on Capitol Hill.

J. Scott Applewhite/AP

AA Font size + Print

House Budget Committee member Rep. Mick Mulvaney, R-S.C., listens to testimony from Budget Director Jack Lew, Feb. 15, 2011, on Capitol Hill.

New legislation just passed the House that prevents Congress and the Pentagon from using war funds to pay for things that have nothing to do with war. By William D. Hartung

Last week’s House action on the National Defense Authorization Act was largely an exercise in fantasy budgeting and pork barrel politics. Virtually all of the Pentagon’s major cost saving initiatives were rejected, and key issues like when to bring U.S. troops home from Afghanistan were not even brought up for debate. 

This otherwise dismal showing was partially redeemed by the House’s passage of an amendment that would take the first step towards ending the use of the war budget – formally known as the Overseas Contingency Operations (OCO) account – to pay for items that have nothing to do with the war in Afghanistan. The amendment, co-sponsored by Reps. Mick Mulvaney, R-S.C., and Patrick Murphy, D-Fla., proposes using standards developed by the Office of Management and Budget to clarify which items can properly be included in the OCO budget.

This measure is long overdue. In recent years, the OCO budget has been saddled with tens of billions of dollars in expenditures that are unrelated to the war in Afghanistan or any other overseas contingency. Fiscal year 2014 is a good example. Even as troop levels in Afghanistan went down by 39 percent, the total OCO budget remained virtually unchanged. This was partly due to an excessive request from the administration, and partly due to billions in congressional add-ons.

Because the OCO account includes less detail than the Pentagon’s base budget, it’s hard to know exactly how much of the OCO funding authorized in the 2000s was unrelated to the Afghan conflict. But it is certainly in the tens of billions of dollars. Independent analyses by the Center for Strategic and Budgetary Assessments and the Project on Government Oversight suggest that roughly $30 billion of the FY2014 OCO budget involved items that belonged in the Pentagon’s base budget.

The main fight over the war budget will come once the Obama administration puts forward a realistic number for that account later this year, after the administration and the new Afghan government agree on what kind of ongoing presence the United States will have there.

In addition to the challenge of keeping inappropriate expenditures out of the OCO account, there is the question of how long it should continue. Several U.S. military leaders have suggested that the fund should continue for an additional 3 to 4 years, continuing even after  the number of U.S. troops in Afghanistan drops to zero .. 

The stated rationales for keeping a war fund even after there is no war to fund is that the U.S. military needs money to bring troops and equipment home, as well as to “reset the force” by replacing or refurbishing equipment damaged or lost in the war. Neither of these arguments hold up to scrutiny.

Just as the OCO budget during the war included money to move personnel and equipment to Afghanistan as needed, there have already been some funds spent on bringing them home. Future allocations will need to supplement these amounts, but doing so should not cost tens of billions of dollars. For example, some equipment will be left for Afghan forces or destroyed in place, obviating the need to transport it back to the United States. All of this suggests the possibility of devising a smaller, more tightly crafted OCO budget for FY2015, with funds for future years premised on what U.S. presence remains.. But if once war ends, the OCO fund should end as well.

The call for large amounts of funding for reset also rests on shaky ground. As a 2011 study by the Stimson Center has shown, the $1 trillion in procurement funding contained in the Pentagon budget in the decade after 2001 was more than ample to provide the Army with a full inventory of new and/or upgraded vehicles, over and above any equipment that may have been lost in Afghanistan.  Similar trends hold for the Air Force, Navy and Marines.  Given this reality, Congress should carefully scrutinize any funding justified on the grounds of “resetting the force.”

In the name of budget discipline and sound planning, the use of the OCO account as an all-purpose slush fund must end.

William D. Hartung is the director of the Arms and Security Project at the Center for International Policy.

Close [ x ] More from DefenseOne

Thank you for subscribing to newsletters from
We think these reports might interest you:

  • Federal IT Applications: Assessing Government's Core Drivers

    In order to better understand the current state of external and internal-facing agency workplace applications, Government Business Council (GBC) and Riverbed undertook an in-depth research study of federal employees. Overall, survey findings indicate that federal IT applications still face a gamut of challenges with regard to quality, reliability, and performance management.

  • PIV- I And Multifactor Authentication: The Best Defense for Federal Government Contractors

    This white paper explores NIST SP 800-171 and why compliance is critical to federal government contractors, especially those that work with the Department of Defense, as well as how leveraging PIV-I credentialing with multifactor authentication can be used as a defense against cyberattacks

  • GBC Issue Brief: Supply Chain Insecurity

    Federal organizations rely on state-of-the-art IT tools and systems to deliver services efficiently and effectively, and it takes a vast ecosystem of organizations, individuals, information, and resources to successfully deliver these products. This issue brief discusses the current threats to the vulnerable supply chain - and how agencies can prevent these threats to produce a more secure IT supply chain process.

  • Data-Centric Security vs. Database-Level Security

    Database-level encryption had its origins in the 1990s and early 2000s in response to very basic risks which largely revolved around the theft of servers, backup tapes and other physical-layer assets. As noted in Verizon’s 2014, Data Breach Investigations Report (DBIR)1, threats today are far more advanced and dangerous.

  • Information Operations: Retaking the High Ground

    Today's threats are fluent in rapidly evolving areas of the Internet, especially social media. Learn how military organizations can secure an advantage in this developing arena.


When you download a report, your information may be shared with the underwriters of that document.