← Back to Blog

The Expeditionary Fighting Vehicle: roughly $3.3 billion spent on a Marine vehicle that never fielded

· 12 min read The Expeditionary Fighting Vehicle: roughly $3.3 billion spent on a Marine vehicle that never fielded

The Marine Corps spent more than two decades and roughly $3.3 billion trying to build a single vehicle that could do two very hard things at once: swim across open ocean at high speed like a boat, then climb ashore and fight inland like an armored personnel carrier. When Secretary of Defense Robert Gates recommended cancelling the Expeditionary Fighting Vehicle on January 6, 2011, not one of those vehicles had ever been fielded to a Marine unit. The money was spent. The capability was not delivered.

That sentence is the whole story in miniature, and it is worth sitting with before the qualifiers arrive, because the qualifiers matter in both directions. This was not a pointless vehicle chasing a pointless mission. It was a real and enduring Marine Corps need paired with a single technical requirement so demanding that it drove the cost, the complexity, and the reliability failures that eventually killed the program. The Corps did not walk away from the mission. It replaced the EFV with a more modest wheeled vehicle that actually reached the fleet. Both of those things are true at the same time, and the honest version of this episode holds them together.

What the EFV was, and what it was for

The Expeditionary Fighting Vehicle began life in 1988 under a different name, the Advanced Amphibious Assault Vehicle, or AAAV. The program was renamed the Expeditionary Fighting Vehicle in September 2003. The prime contractor throughout was General Dynamics Land Systems. According to the Congressional Research Service and corroborating secondary sources, the vehicle was meant to replace the AAV-7A1 Assault Amphibious Vehicle, a platform that had entered Marine Corps service in 1972 and was, by the 2000s, decades past its design life.

The mission the EFV was built to serve is core to what the Marine Corps exists to do: move Marines from ships at sea onto a hostile shore, under fire, and keep fighting once they land. The EFV was designed to carry 3 crew and 17 embarked Marines. Where the older AAV-7 launched from ships only a couple of miles offshore, the EFV was conceived to launch from over the horizon, roughly 20 to 25 miles out, so that the amphibious ships themselves could stand off farther from coastal defences. That "over the horizon" launch distance was the entire point of the design, and it was also the source of the trouble.

To cross that distance in a reasonable time, the EFV had to plane across the water, meaning it had to lift its hull up and skim the surface like a fast boat rather than plough through it like a barge. Sources differ on the exact water-speed figures. The threshold requirement is usually described as roughly 20 knots, while the specification top speed was around 24.9 knots, or about 28.6 miles per hour. The safest way to state it is a range: the EFV was required to plane across open water at roughly 20 to 25 knots. For a vehicle that also had to weigh in the neighbourhood of 80,000 pounds and carry armour, a turret, and 17 combat-loaded Marines, that is an extraordinary thing to ask.

Making it work meant retractable appendages, water jets, and a hull that had to transform between a fast planing boat and a heavily armoured land fighting vehicle. CRS and defence press describe this high-water-speed requirement as the root of the program's engineering complexity. This is a root-cause analysis widely shared across those sources, not a story about one broken part. The vehicle was asked to be two fundamentally different machines, optimised for two incompatible physics problems, in one hull.

Timeline

  • 1988: Concept work begins on the Advanced Amphibious Assault Vehicle (AAAV).
  • September 2003: The program is renamed the Expeditionary Fighting Vehicle (EFV).
  • 2006: An operational assessment finds the vehicle failing on average about once every four and a half hours of operation. The program later enters a second System Design and Development phase specifically to address reliability.
  • 2007: Estimated unit cost is reported at about $22.3 million per vehicle.
  • March 2010: GAO and CRS figures put the remaining cost to complete the program at roughly $11.163 billion, and the planned buy has been cut sharply from earlier quantities.
  • January 6, 2011: Secretary of Defense Robert Gates recommends cancelling the EFV as part of the Fiscal Year 2012 efficiencies package. Marine Corps Commandant General James Amos supports the decision. Congress subsequently ends program funding.

It is worth being precise about that last date. Gates did not unilaterally destroy the program with a single instantaneous order. He recommended and announced cancellation on January 6, 2011, as part of a broader package of proposed defence efficiencies, and Congress then followed by ending the money. Commandant Amos, who had every institutional reason to defend a signature Marine Corps program, instead backed the cancellation. His stated reasoning, as recorded by CRS, was affordability: the program was not affordable given the Marine Corps' likely procurement budgets.

The money, kept straight

This episode is a minefield of similar-looking numbers, and the honest account depends on keeping three of them distinct. They measure three different things.

Money actually spent: roughly $3.3 billion. By the time the EFV was cancelled, the program had consumed a large sum in development. CRS phrases this carefully as "more than $3 billion" in development funding. The specific figure of $3.3 billion comes from press reporting rather than from CRS. The most accurate way to state it on the page is therefore: roughly $3.3 billion spent, with CRS describing it as more than $3 billion in development. Whatever the exact rounding, this is money that was already gone when the program ended. It is a sunk figure, not a forecast.

Projected full-program total: on the order of $15 billion. Completing the EFV and fielding it in quantity was projected to cost far more than what had been spent. Sources cite a full-program total on the order of $15 billion, with some estimates running toward roughly $15.9 billion. This is a rounded projection, not a hard invoice, and it should be read as an order-of-magnitude figure: the program's finish line was several times more expensive than the distance already travelled.

Remaining cost to complete: roughly $11 to $12 billion. As of March 2010, GAO and CRS figures put the remaining cost to field 573 vehicles at about $11.163 billion, composed of roughly $866.7 million in remaining research and development and about $10.226 billion in procurement. Press accounts cited roughly $12 billion more still needed to actually produce the vehicles. This is the cost-to-complete, distinct from both the money already spent and the projected grand total.

To say it plainly: roughly $3.3 billion had already been spent, finishing the program was estimated to require another $11 to $12 billion, and the full life of the program was projected on the order of $15 billion. Those are not three ways of describing one number. They are three different measurements, and conflating them is the most common way this story gets told wrong.

Underneath the totals sits the per-unit story, which is the mechanism that drove them. The estimated cost per vehicle escalated from about $22.3 million in 2007 toward roughly $24 million by 2010. As the unit price climbed, the planned quantity was cut, from more than 1,000 vehicles, roughly 1,013 in earlier plans, down to 573. That is the classic acquisition death spiral: rising per-unit cost forces a smaller buy, and a smaller buy spreads fixed development costs across fewer units, which raises the per-unit cost again. Sources also cite termination costs of roughly $185 million to wind the program down, though that particular sub-figure is less firmly corroborated than the others and should be attributed to CRS if used.

The reliability problem

Cost was only half of the case for cancellation. The other half was whether the vehicle worked. A 2006 operational assessment found the EFV failing, on average, about once every four and a half hours of operation. For a combat vehicle that Marines would ride into a contested landing, a mean time between failures measured in single-digit hours is not a rounding error. It is a fundamental problem. The program subsequently entered a second System Design and Development phase specifically to attack the reliability shortfalls, which is itself a signal of how deep those problems ran.

Reliability and the high-water-speed requirement are not separate stories. They are the same story. The demand to plane across open water at high speed forced the retractable appendages, the water jets, and the transforming hull, and that complexity is precisely what made a rugged, reliable vehicle so hard to build. The requirement that made the EFV special is the requirement that made it fragile and expensive.

The honest critique and the honest defence, side by side

The critique

By the plain measures that oversight bodies apply, the EFV was a failure. Roughly $3.3 billion of public money went into it across more than two decades, and it was cancelled in January 2011 without a single vehicle ever fielded to an operational Marine unit. Per-unit cost had roughly doubled the plausibility of the program out of existence, climbing toward $24 million each and forcing the planned buy to be cut nearly in half, from more than 1,000 vehicles to 573. A 2006 assessment found it breaking down about once every four and a half hours. And finishing it would have cost another $11 to $12 billion, against a full-program projection on the order of $15 billion. This is the textbook shape of a defence acquisition death spiral: cost growth, quantity cuts, reliability shortfalls, and finally cancellation, with money spent and no capability delivered. Commandant Amos' own stated basis for supporting the cancellation, affordability, is the critique in the words of the service that wanted the vehicle most.

The defence

The mission was never the problem. The AAV-7 the EFV was meant to replace dated to 1972, and moving Marines from ship to shore under fire is not an optional capability for the Corps. The need was real, and it did not disappear when the EFV did. What failed was one overreaching requirement: the demand that a heavy armoured fighting vehicle also transform into a fast planing boat capable of self-deploying from ships some 20 to 25 miles offshore. That single requirement, widely identified in CRS and defence press as the root cause, drove the complexity, the cost growth, and the poor reliability that killed the program.

Crucially, the Marine Corps did not respond by abandoning amphibious assault. It responded by scaling the requirement down to something buildable. The successor is the Amphibious Combat Vehicle, an 8x8 wheeled vehicle that deliberately trades the EFV's extreme water speed for affordability and survivability. It self-deploys over much shorter distances and moves through the water far more slowly, roughly 8 knots in three-foot seas rather than planing at 20-plus. And it worked. The ACV was approved for Initial Operational Capability on November 13, 2020, and moved to a full-rate production decision in December 2020, with a roughly $184 million contract for an initial batch of 36 vehicles.

One correction matters here and is easy to get wrong: the ACV is built by BAE Systems, together with Iveco, not by General Dynamics. General Dynamics, the EFV's prime contractor, competed for the ACV and lost. So the redemption arc is not the same company getting a second chance. It is the Marine Corps keeping the mission, discarding the impossible requirement, and buying a more modest vehicle from a different manufacturer that actually reached the fleet.

Read that way, the roughly $3.3 billion was spent on a cancelled vehicle, but not on a discarded idea. The hard lesson about what a single heroic requirement can do to an entire program informed a scaled-back successor that delivered a real, fielded capability. That does not undo the sunk cost. It does complicate the simplest version of the story, which is exactly why it belongs in the honest one.

Fact-check notes and sources

  • Program history, contractor, and 2003 rename. The EFV began as the Advanced Amphibious Assault Vehicle (AAAV), with prime contractor General Dynamics Land Systems, and was renamed the Expeditionary Fighting Vehicle in September 2003. Wikipedia: Expeditionary Fighting Vehicle; corroborated by CRS RS22947.
  • Intended to replace the 1972-era AAV-7A1. The AAV-7A1 entered service in 1972; the EFV was its intended replacement. Wikipedia: Expeditionary Fighting Vehicle.
  • Capacity and over-the-horizon concept. Designed to carry 3 crew plus 17 Marines and launch roughly 20 to 25 miles offshore. Wikipedia: Expeditionary Fighting Vehicle; GlobalSecurity.org: AAAV.
  • Water speed as a range, not a single figure. The threshold requirement was roughly 20 knots; the specification top speed was about 24.9 knots (roughly 28.6 mph). Stated here as "roughly 20 to 25 knots" to avoid false precision. Wikipedia: Expeditionary Fighting Vehicle.
  • Cancellation on January 6, 2011, with Amos' support. Gates recommended cancellation as part of the FY2012 efficiencies package; Commandant General James Amos supported the decision on affordability grounds; Congress subsequently ended funding. CRS RS22947.
  • Roughly $3.3 billion spent. CRS phrases the spend as "more than $3 billion" in development funding; the specific $3.3 billion figure comes from press reporting, not CRS. CRS RS22947.
  • Projected total and cost-to-complete, kept distinct. GAO and CRS figures (March 2010) put the remaining cost to field 573 vehicles at about $11.163 billion ($866.7 million R&D plus $10.226 billion procurement); the full-program total was projected on the order of $15 billion. CRS RS22947.
  • Unit cost and quantity cut. Estimated unit cost rose from about $22.3 million (2007) toward roughly $24 million, and the planned buy was cut from more than 1,000 vehicles to 573. Termination costs of roughly $185 million are cited but less firmly corroborated. Wikipedia: Expeditionary Fighting Vehicle; CRS RS22947.
  • Reliability. A 2006 operational assessment found roughly one failure every four and a half hours of operation. Wikipedia: Expeditionary Fighting Vehicle.
  • High-water-speed requirement as root cause. The demand to plane across water at high speed drove the complexity, cost, and reliability problems, per CRS and defence analysis. CRS R42723 (ACV report).
  • The ACV successor, built by BAE Systems, reached the fleet. The wheeled 8x8 Amphibious Combat Vehicle, built by BAE Systems with Iveco (not General Dynamics), reached Initial Operational Capability on November 13, 2020, and a full-rate production decision in December 2020 with a roughly $184 million contract. Wikipedia: Amphibious Combat Vehicle; CRS IF11755; Defense News; Naval News.

Related reading

This post is informational and journalistic, not legal or financial advice. It describes public programs and documented events; mentions of third parties are nominative fair use and no affiliation is implied.

← Back to Blog

Accessibility Options

Text Size
High Contrast
Reduce Motion
Reading Guide
Link Highlighting
Accessibility Statement

J.A. Watte is committed to ensuring digital accessibility for people with disabilities. This site conforms to WCAG 2.1 and 2.2 Level AA guidelines.

Measures Taken

  • Semantic HTML with proper heading hierarchy
  • ARIA labels and roles for interactive components
  • Color contrast ratios meeting WCAG AA (4.5:1)
  • Full keyboard navigation support
  • Skip navigation link
  • Visible focus indicators (3:1 contrast)
  • 44px minimum touch/click targets
  • Dark/light theme with system preference detection
  • Responsive design for all devices
  • Reduced motion support (CSS + toggle)
  • Text size customization (14px–20px)
  • Print stylesheet

Feedback

Contact: jwatte.com/contact

Full Accessibility StatementPrivacy Policy

Last updated: April 2026