All cases

Federal

Air Force Expeditionary Combat Support System

The Air Force spent more than $1 billion on a logistics system that was cancelled without delivering usable capability. A Senate investigation documented the failure.

Spent on cancelled logistics softwareOver $1 billion
Evidence finding

Investigation found failed delivery

Source documents3View sources ↗

Ask Impact Analyst

Ask about the numbers or evidence. Keep the conversation going with follow-up questions.

By sending, you agree to share your question and this case’s notes with Google Gemini and save the conversation privately for review. Privacy

Impact Analyst

Air Force Expeditionary Combat Support System

What would you like to understand?

Answers use this case’s sources and notes. They do not search the web.

AI answers can be wrong. Check the sources. Enter to send; Shift+Enter for a new line.

Privacy and sharing

By sending, you agree that Google Gemini can process your question and this case’s public notes. We save the conversation privately for review. Leave out private personal details.

Nothing is published automatically. Keep the saved reference if you want to request deletion. Read the privacy policy.

What was the money for?

Modernize the Air Force’s logistics computer systems.

Amount discussed in this caseOver $1 billion

More than $1 billion was spent over the eight years from 2004 to 2012, before cancellation.

Exact amount, time period and source wording

Over $1 billion spent before 2012 cancellation; rounded lower threshold

Period: 2012

Putting the amount in context

More than $125 million a year

average yearly spending over eight years

More than $1 billion divided by eight years is more than $125 million a year, on average.

What this comparison means: The average does not show spending in each year. No usable system was fielded, but that alone does not value every remaining asset.

How we calculated this and where it comes from

more than 1,000,000,000 / 8 years

This is a simple annual average, not the expenditure in every year. No usable capability does not establish zero salvage value.

What actually happened?

The program was cancelled in 2012 without usable capability being put into service. The Air Force continued relying on its older systems.

Keep in mind: Failure to deliver a usable system does not by itself prove criminal fraud or that every asset was worthless.

Read the detailed findings

The Senate report documents a failed logistics modernization effort and continued reliance on legacy systems.

Reported status: Cancelled after eight years without fielding usable capability, according to the Senate investigation.

Cancellation and unusable delivery alone do not establish criminal fraud.

Can we follow the payments?

A report can tell us the total. To follow the money, we also need to connect each bill to a payment and to what was received.

Early-intervention illustration · estimated timing

What could earlier intervention have changed?

The Senate investigation reports more than $1 billion spent over eight years from 2004 to 2012. This uses the rounded $1 billion floor as project spending, with no finding that it was all fraud.

Modeled gross payments avoided$968.75 million

Assumes action after 3 months could prevent 100% of the remaining amount. Effectiveness remains unmeasured. This uses equal monthly amounts because actual payment dates are missing.

A failed-project spending scenario, kept separate from the convicted-scheme and program-wide fraud estimates.

See the calculation, dates and evidence limits

2004 through 2012 · 96 months

$1 billion × 93 / 96 × 100%

Uses the source’s eight-year duration, or 96 months. The exact first and last payment months are not known. Spending is spread evenly for this illustration, and obligations or retained work are not valued.

Net savings require evidence of the costs actually avoidable, recoveries, repayment obligations and the cost of oversight. Essential services and payments legally owed must remain protected.

Publish the payment trail, independently check progress and pause future unearned releases when the evidence warrants it.

See the Receipts Act proposal ↗

Complete invoice-to-payment links

Whole amount shownOver $1 billion
Invoice
What was charged.
Payment record
What was paid.
Delivery record
What was received.
0% traced to invoices and payments in this file0% of the stated Over $1 billion is linked here to an invoice and payment record. $0 is linked to invoices and payments; $0 also has delivery acceptance. $1,000,000,000 has no matched invoice and payment in this case file.

Invoice + payment record

$0 linked here

No matching invoice and payment records have been added to this file.

The circle shows the share of the displayed total with those records. Blue means linked here; gray means not linked here.

0% means no matching records are linked in this file. It does not describe every record the government holds or prove that money was lost or stolen.

Help make invoices, payments and proof of delivery public.

Support the Receipts Act
How this is measured and which records are linked

This file currently links summary-level sources, with no itemized invoice-to-payment records registered against this amount. The pie measures this collection only. Over $1 billion spent before 2012 cancellation; rounded lower threshold. Preserve the source qualifier: this is not an exact spending denominator.

Only invoice and payment records tied to this same amount and scope count. Delivery coverage also requires a linked acceptance record. A report showing a total does not count as an individual receipt.

Invoice, payment and delivery linked
$0
Invoice and payment linked; delivery not linked
$0
No matched invoice and payment in this file
$1,000,000,000

0 matching invoice/payment records; 0 also link to delivery.

No individual invoice-to-payment records are registered in this file yet. This does not establish that those records do not exist elsewhere.

What is still missing?

Which tested software or equipment did each payment buy, and was any of it reused?

Which records would help answer this?

An investigation can explain failure without establishing a complete public ledger linking every vendor payment to tested software and asset reuse.

  • Link each contract change and payment to tested software, accepted functionality and deployment milestones.
  • Publish independent acceptance-test results, unresolved defects and service impacts, with sensitive details protected.
  • Reconcile termination costs, recoveries and reused software or equipment.

These records have not all been assembled here. They may exist elsewhere. Personal details should stay protected.

Can we estimate how much was wasted or stolen?

This file does not establish an independent value for everything delivered. Subtracting a guessed value from a headline amount would not establish fraud. A sound estimate needs matching costs, delivered results and evidence about why any money was lost.

Sources and research notes (3 documents)

These documents support the case. A source document can describe many payments; it is not itself an itemized receipt.

  1. Senate Permanent Subcommittee investigation of ECSS

    govinfo.gov · 2014

  2. GAO-11-53 DOD business system oversight

    gao.gov · 2010-10-07

  3. Senate Homeland Security and Governmental Affairs Committee, bipartisan ECSS investigation

    hsgac.senate.gov · 2014-07-07

Research cutoff: November 9, 2026. Older reports may not include later changes. Read our methodology.