What aircraft procurement program was the biggest failure?

If we define “biggest failure” as a combination of sunk cost, institutional damage, and doctrinal confusion, I’d argue the U.S. Navy’s A-12 Avenger II deserves the crown. It wasn’t just a canceled airframe; it became a cautionary tale about concurrency, immature stealth manufacturing, and requirement creep in the post–Cold War transition.

The A-12 was meant to replace A-6 Intruder in the deep strike role off carriers—an operationally serious mission. Instead, weight growth, cost escalation, and unrealistic assumptions about composite/stealth production collided. When it imploded, the Navy had to stretch legacy platforms and then bridge with Super Hornet while waiting for JSF to mature.

Historically, you see this pattern after big strategic inflection points. After WWI, air power visions outran budgets; after WWII, nuclear strategy reshaped procurement; after the Cold War, “peace dividend” pressures punished programs with technical risk. It echoes earlier procurement disasters where politics + technology + doctrine were misaligned.

Lesson: stable requirements and believable tech readiness matter more than PowerPoint promises. (For sources, the GAO reporting and the broader procurement histories by people like Norman Friedman are good starting points.)

I’m gonna answer like I do with kit: what failed at the job it was bought for? VH-71 Kestrel is my pick. It’s “just” a helicopter program, but it’s the perfect example of buying a high-end solution and then customizing it into a money pit.

They took an existing airframe concept and piled on mission equipment, comms, survivability, and bespoke requirements until the weight/performance and cost went sideways. That’s like buying a solid ruck and then sewing on a million pouches until the frame cracks—no longer optimized for anything.

If we’re talking fixed-wing, A-12 is the classic. But VH-71 is the kind of failure that should’ve taught everyone to stop gold-plating and to keep modifications limited unless the mission truly demands it.

Lesson: “nice to have” requirements kill programs. Define what you need, not what sounds cool in a briefing.

From the operator side, the biggest “failure” is the one that leaves units with a gap and a bunch of workarounds. I’d put Comanche (RAH-66) high on the list—not because the aircraft was useless, but because it chased a Cold War scout/attack concept while the Army was getting pulled hard into a very different operational reality.

When programs die, it’s not just money. It’s training plans, tactics development, maintainers’ pipelines, basing assumptions, and all the planning that gets thrown out. You end up leaning harder on legacy airframes and improvising capabilities with add-on sensors, pods, and “good enough” solutions.

Lesson I wish planners internalized: if your mission set is changing fast, build modular capability and upgrade paths, not a single exquisite solution that only makes sense in one forecasted war.

I’ll zig a bit: some of the “biggest failures” are manned programs that ignored the trajectory toward uncrewed ISR/strike and networked targeting. Comanche is an example of a concept getting overtaken by sensors, datalinks, and UAVs.

A-12 and F-111B are classic procurement failures, sure. But what stings is how often we buy an exquisite platform for a role that could be partially disaggregated: uncrewed scouting, stand-off weapons, distributed sensors, and cheaper attritable aircraft.

Lesson: when you’re buying a platform with a 30–50 year lifecycle, you need an architecture mindset. Open systems, upgradeable mission computers, and the ability to integrate autonomous teammates later. Otherwise the “failure” is strategic: you lock in yesterday’s solution.

Not my lane, but I’ll answer with a ground guy’s framing: the worst procurement failures are the ones that distort the whole force structure. When aviation programs collapse, the Army/Navy/Air Force ends up rebalancing money away from other priorities—sometimes including ground modernization.

Comanche is the one I watched from the outside and thought, “that’s a lot of budget gravity.” The cancellation freed funds for helicopters and systems that were immediately relevant (upgrades, UAV integration, better sensors). Whether the aircraft itself would’ve been great is almost beside the point—the program’s opportunity cost became the story.

Lesson: measure programs against what else could’ve been funded. A ‘failed’ aircraft can delay vehicles, comms, and protection systems across the force.

From a Navy perspective, F-111B is hard to ignore. It wasn’t just a canceled airplane; it was a fleet air defense concept tied to carrier operations. The weight/performance issues and inter-service politics (TFX) produced an aircraft that didn’t fit carrier realities, and the Navy had to pivot.

The “failure” still produced downstream success—because it helped push the Navy toward a purpose-built solution: the F-14 with AWG-9/Phoenix for that era’s threat. So was F-111B a failure? Programmatically yes; strategically it forced a correction.

A-12 is more purely destructive because it didn’t generate an immediate clean replacement path; it mostly generated a gap and budget scars.

Lesson: naval aviation is uniquely unforgiving about weight, approach speeds, and deck handling. Jointness is great until it ignores physics and shipboard constraints.

If we’re talking “biggest failure” as in most infamous cancellation: A-12 Avenger II.

But if we’re talking about an aircraft that simply couldn’t be what it was supposed to be: F-111B. A fleet defense fighter that’s too heavy/compromised for carrier ops is basically dead on arrival. It’s a great example of why you can’t just adapt an airframe concept across wildly different missions and basing environments.

Also, I’d separate “development pain” from “failure.” The F-35 had ugly early years, but it’s producing combat-coded squadrons and getting real upgrades. That’s not the same category as a program that never becomes operational.

Lesson: test early with realistic carrier/operational constraints and don’t assume performance margins exist—they never do.

I’m not an engineer, but I’ve seen how these programs trickle down to people decisions. When a big aircraft program gets canceled or delayed, it affects training slots, career fields, and retention—because units don’t know what they’re transitioning to.

My vote for “biggest failure” would still be A-12 because it’s the cleanest example of huge investment with no fleet capability to show for it.

Lesson for anyone joining: military plans change. If you’re picking a career around one platform, keep your skills broad (maintenance fundamentals, avionics basics, systems thinking). That makes you more resilient when the Pentagon pivots.

I’m looking at this through the lens of the missions that end up on SOF plates: time-sensitive strike, ISR, comms, and getting in/out reliably. When procurement fails, the community ends up improvising with whatever works and fielding stopgap mods.

VH-71 is the one that screams “requirements pile-on.” It was supposed to deliver a secure, survivable, modern transport platform and ended up as a symbol of gold-plating.

Fixed wing? A-12 is the textbook case. But the more interesting lesson is cultural: if a program is being treated like a prestige project instead of a tool for a mission, it’s already in danger.

Lesson: mission-first procurement and ruthless simplicity beat exquisite one-off solutions.

Not an aviation engineer, but I think the “failure” metric that matters is resilience: what happens to the force when the plan collapses?

A-12 looks bad because it didn’t yield an operational capability, so everyone had to keep older aircraft relevant longer. In the fieldcraft world, that’s like planning a route with one water source and then finding it dry—you survive by adapting, but it’s avoidable if you plan for redundancy.

Lesson: build procurement like you build survival plans—assume something will go wrong, keep fallback options, and avoid single points of failure in timelines and assumptions.

“Biggest failure” depends heavily on what you value: fiscal stewardship, deterrence signaling, alliance impacts, or industrial base health.

A-12 is a clean fiscal/program management failure story. Comanche is a strategic mismatch story: the world changed, and the program couldn’t justify itself against urgent needs. VH-71 is a governance story: requirements, oversight, and customization ran away.

I’d pick A-12 for the combination of: large sunk cost, cancellation, litigation/contract fallout, and the way it reinforced post–Cold War skepticism about defense spending.

Lesson: programs need governance that can say “stop” early, plus transparent metrics that Congress and the public can understand—otherwise you get years of drift and then a headline cancellation.

I’ll come at it from systems engineering and logistics. A procurement failure isn’t only the prototype—it’s the sustainment plan, the production realism, and the supply chain.

A-12 failed hard on manufacturability and weight growth realities. Those aren’t just “engineering problems,” they’re integration problems between design, production processes, and what the fleet can actually support.

Also, when programs are late/canceled, logistics has to keep legacy fleets alive: sourcing parts, reverse engineering, depot capacity, corrosion control—stuff nobody budgets for at the start.

Lesson: don’t treat production and sustainment as afterthoughts. If you can’t build it repeatedly and maintain it at scale, it’s not a real capability.

I’m still learning this stuff, so maybe a basic question: when people say A-12 was a failure, is it mainly because it got canceled, or because the stealth tech/manufacturing wasn’t ready yet?

Also how do you compare something like F-111B (cancelled) to something like F-35 (super expensive but actually in service)? Is “failure” about the original requirement, or the end result?

If anyone has a good book/article list for procurement history that isn’t too dense, I’d appreciate it.

In wargame terms, the biggest procurement failures are the ones that break your force design assumptions. If your carrier air wing plan assumes a stealthy deep strike aircraft and it disappears, you either accept higher attrition, reduce the mission, or delay operations until other capabilities arrive.

A-12 is therefore a major failure because it disrupted a specific concept of operations and forced compensating moves: reliance on upgraded legacy aircraft, stand-off weapons, and later, a different mix of strike/fighter platforms.

Comanche is interesting because the “failure” might have been avoided by modularizing: field a baseline airframe earlier, spiral in sensors, and integrate unmanned scouts as teammates. Instead, it stayed in the lab while the battlefield changed.

Lesson: design for graceful degradation. A program that slips shouldn’t collapse your strategy.

I’ll nominate a category rather than one airframe: programs that tried to build a single exquisite platform instead of a manned-unmanned team. That mindset is what keeps repeating.

If I must pick: Comanche. It aimed to be a very advanced manned scout/attack helicopter, but scouting is increasingly an uncrewed/robotic problem—small UAVs, loitering sensors, autonomous route planning, and attritable systems that don’t risk pilots.

A-12 is the biggest “traditional” procurement failure, no doubt. But Comanche feels like the bigger missed opportunity in terms of future force design.

Lesson: build aircraft as nodes in a system. If autonomy and uncrewed sensors can take the riskiest tasks, your procurement strategy should reflect that from day one.