Why Calling the F-35 a Failure Misses the Real Scam

Why Calling the F-35 a Failure Misses the Real Scam

Every time the Pentagon signs another multi-year deal for the F-35, the headlines write themselves. Cost overruns. Software delays. Maintenance headaches. Lazy pundits reach for the same dusty playbook and declare the program a trillion-dollar boondoggle.

They are looking at the wrong problem.

Calling the F-35 a failure is the easiest take in defense commentary. It requires zero analytical heavy lifting. You pull a scary lifetime cost figure, cite a stalled software release, and play to the crowd. I have spent years watching defense programs burn cash on vanity specs and political compromises, and I have seen plenty of hardware rot on tarmacs because nobody wanted to admit the premise was broken. The F-35 is not broken in the way its loudest critics claim. It is broken in a much more expensive, much more structural way.

The real issue is not that the jet cannot fly, fight, or survive. The real issue is how the Pentagon structures multi-year procurement around a single, all-purpose airframe—and how contractors turn long-term sustainment into a captive revenue machine that punishes real adaptability.

The Lazy Consensus Around F-35 Headlines

Conventional coverage treats every multi-year F-35 contract as a binary verdict: either the Pentagon is doubling down on a lemon, or it is finally stabilizing a troubled program. Both sides of that argument miss the mechanics driving the deal.

Multi-year procurement exists to give prime contractors production certainty and theoretically lower unit costs through volume commitments and economic ordering quantities. On paper, locking in multi-year batches sounds like smart business. In practice, locking in years of production on a complex, software-heavy platform before sustainment costs and upgrade cycles are truly tamed locks the buyer into a rigid economic dependency.

Critics love to point at sticker price or per-hour operating costs as if those numbers exist in a vacuum. They rarely separate initial build costs from decades of logistics, depot bottlenecks, spare parts scarcity, and proprietary software gatekeeping. Meanwhile, defenders treat every new contract as proof that the program is "on track," ignoring whether the underlying cost structure actually bends in the taxpayer's favor.

When reporters reduce a multi-year F-35 contract to a fight between "expensive boondoggle" and "indispensable fighter," they are asking the wrong question. The right question is not whether the F-35 is a good jet. The right question is why modern airpower procurement keeps buying monolithic platforms on multi-year rails in an era where software, sensors, and attritable systems evolve faster than airframes.

What People Actually Ask About F-35 Contracts

Is locking in a multi-year F-35 contract a smart move for taxpayers?

Not automatically, and certainly not in the way press releases suggest. A multi-year contract can smooth out manufacturing lines and reduce some unit-level friction, which is why procurement officials reach for it. Yet locking in multi-year volume also cements supplier leverage when sustainment, spares, and technical data rights remain tightly controlled.

Calling a multi-year deal an automatic win ignores the difference between buying an airplane and owning a fleet for forty years. If the jet arrives faster or slightly cheaper off the line while long-term maintenance and modernization remain expensive and slow, taxpayers still eat the bill over the aircraft's life. A multi-year contract is a financial tool, not a cure for structural cost growth.

Why does the F-35 stay funded despite constant criticism?

Because sunk cost, allied interoperability, and fleet scale create political and operational gravity that few politicians want to fight. Once dozens of squadrons and partner air forces build their training, doctrine, and supply chains around one core platform, walking away stops looking like fiscal discipline and starts looking like strategic disruption.

There is also a simpler reason critics underappreciate: replacing a multi-role stealth aircraft with a patchwork of older designs or half-baked alternatives carries its own steep costs and capability gaps. The jet survives not because its critics are imagining flaws, but because alternatives carry risks that planners are unwilling to absorb all at once.

Does a multi-year deal fix F-35 maintenance and readiness problems?

A production contract does not magically fix parts shortages, depot throughput, or software integration. Those bottlenecks live in sustainment, supply chains, and configuration management—areas that frequently lag behind assembly-line output.

I have seen organizations sign bigger supply agreements hoping scale alone would fix broken workflows. It rarely works. If repair turnarounds are slow and software updates stack up faster than fleets can absorb them, building more units without fixing the support engine simply expands the backlog.

Stealth, Sensors, and the Misunderstood Airframe

To judge the F-35 fairly, you have to define what it actually is rather than what internet debates pretend it is. It is not a retro dogfighter built to win turning contests at low altitude while ignoring everything else. It is a sensor-rich, stealthy multi-role combat aircraft designed to find, track, share data on, and strike targets in contested airspace while surviving threats that would chew up legacy non-stealth jets.

In modern air warfare, information dominance and low observability matter long before a visual merge ever happens. A platform that can gather data across the battlespace, fuse it, and pass targeting information to other forces changes the math of a fight. Analysts who judge a fifth-generation aircraft purely by nostalgic dogfighting metrics or isolated flight-hour numbers are grading a quarterback on how well he punts.

At the same time, defenders go too far when they act as if stealth and sensor fusion erase every operational trade-off. A single airframe asked to serve multiple variants—conventional takeoff and landing, carrier launch, and short takeoff/vertical landing—inherits design compromises. Weight, internal volume, thermal management, and maintenance complexity are real physics constraints, not talking points.

Consider a thought experiment to see the trade-off clearly. Imagine a scenario where an air force faces a high-intensity conflict with tight budgets and heavy attrition risks. If it puts too much of its combat mass into a small number of ultra-complex, high-cost manned jets, losing even a handful hurts deeply, and keeping every airframe mission-ready becomes a logistics grind. Conversely, if it relies solely on older, easily detected aircraft against modern air defenses, survivability drops sharply. The tension is real, and pretending the F-35 solves every side of that equation without friction is just another form of spin.

The Trap of Monolithic Procurement

Here is where the real critique lands. The deeper flaw exposed by multi-year F-35 contracts is the Pentagon's habit of treating complex defense hardware like permanent monuments instead of modular, adaptable systems.

Historically, defense thinkers like John Boyd argued for speed, adaptability, and getting inside an adversary's decision loop rather than building bloated, slow-moving systems. Modern defense reformers and military strategists—people like Dan Ward, who has written extensively on how overly complex, gold-plated programs drive up cost and schedule risk, or analysts studying distributed, attritable force design—have pointed to the same core danger: when a single platform tries to do everything for everyone over decades, complexity compounds.

Locking in multi-year contracts on a massive program reinforces that monolith. It rewards predictable scale on legacy assumptions while making rapid pivot—toward cheaper autonomous systems, distributed sensors, faster software iteration, or contested-logistics resilience—harder to execute at speed.

Even my own contrarian argument carries downsides that I will not sugarcoat. Pushing hard for modular, distributed, or cheaper alternatives sounds great in theory, yet rushing immature technologies into frontline service can leave forces with under-tested gear when real threats show up. Likewise, cutting back too aggressively on proven high-end platforms before affordable replacements scale can create capability valleys during a crisis. There is no free lunch in defense planning—only different kinds of risk.

What Smart Buyers and Analysts Should Do Instead

If you want to understand what a multi-year F-35 contract actually means, stop cheering or jeering at the headline number and start checking the mechanics underneath.

  1. Separate flyaway price from lifecycle ownership. Look at sustainment costs, depot capacity, spare parts availability, and upgrade timelines alongside unit price. A lower unit cost means far less if keeping the fleet flying remains slow and expensive.
  2. Audit software and data leverage. In modern aircraft, whoever controls the code, diagnostics, and mission data controls much of the real cost and pace of improvement. Watch how much autonomy and transparency the buyer actually gets.
  3. Measure readiness, not just deliveries. Delivery milestones make great press releases. Mission-capable rates, parts turnaround times, and pilot training throughput tell you what the force can actually put in the sky.
  4. Pair high-end platforms with adaptable mass. Do not treat any single manned jet as a silver bullet that excuses ignoring cheaper, faster-evolving unmanned systems, munitions depth, and dispersed logistics.

Stop arguing over whether the F-35 is a miracle or a mistake. Start demanding procurement contracts that buy real operational readiness and adaptability instead of multi-year lock-in.

KF

Kenji Flores

Kenji Flores has built a reputation for clear, engaging writing that transforms complex subjects into stories readers can connect with and understand.