Keep Factually independent

Whether you agree or disagree with our analysis, these conversations matter for democracy. We don't take money from political groups - even a $5 donation helps us keep it that way.

Loading...Goal: 1,000 supporters
Loading...

How do maintenance, upgrade cycles, and lifecycle costs compare between Gripen E’s modular systems and F-35’s software-dependent architecture?

Checked on November 22, 2025
Disclaimer: Factually can make mistakes. Please verify important info or breaking news. Learn more.

Executive summary

Gripen E’s design and Saab’s messaging emphasise lower lifecycle and flight-hour costs and easier field maintenance compared with the F‑35, with published Gripen E/F flight‑hour figures around $22,100 and older Gripen C/D around $20,600 per Saab/Defense Express reporting (and Czech government analyses that estimate per‑aircraft annual operating costs of ~$7.25M for Gripen vs. ~$9.6M for F‑35) [1]. Multiple sources in the provided set assert that Gripen’s modular, simpler systems reduce maintenance burden and operating costs relative to the software‑centric F‑35 architecture [2] [3] [1].

1. Design philosophies: modular simplicity vs. software‑centric integration

Saab markets the Gripen family as a pragmatic, low life‑cycle cost fighter built for simple maintenance, exportability and dispersed basing; blogs and comparison pieces reiterate that the Gripen was “designed for minimal life cycle costs” and “cheaper to maintain than other comparable fighters” [3]. By contrast, reporting in these sources frames the F‑35 as a more complex, software‑dependent 5th‑generation aircraft whose stealth and sensor fusion capabilities drive higher maintenance and sustainment needs — a point used to explain higher operating costs versus Gripen [2] [3].

2. Published cost figures and what they cover

Saab‑linked figures cited by Defense Express give a Gripen C/D flight‑hour cost of ~$20,600 and Gripen E/F ~$22,100, figures said to include maintenance, fuel, crew and logistics [1]. Czech government comparisons cited in the same reporting translate program costs into annual per‑aircraft figures — about $7.25M/year for 24 Gripens and $9.6M/year for 24 F‑35s — and derive per‑flight‑hour estimates (at 200 hours/year) of roughly $36,200 for Gripen E/F versus $48,000 for F‑35 [1]. These numbers illustrate relative scale but depend heavily on assumptions (flight hours, basing, national support arrangements) that the sourced reporting highlights as controversial [1].

3. Maintenance posture and sortie generation

Multiple sources stress that Gripen’s single‑engine, simpler systems and modularity produce lower routine maintenance burdens and faster turnaround — “unparalleled ease of maintenance” compared with the F‑35’s “relatively high” maintenance requirements and lower uptime cited in commentary [2] [3]. Saab and national advocates emphasise Gripen’s ability to operate from austere or dispersed facilities with small crews (an argument used in Canadian commentary) which would reduce infrastructure and depot costs in some basing scenarios [4] [3]. The provided sources present this as an operational advantage rather than as a universal rule.

4. Software dependence, upgrades and long‑term sustainment

The F‑35’s advanced capabilities rely on frequent software updates, sensor‑fusion development and lifecycle modernization — elements that can raise sustainment complexity and cost, according to the comparative framing in these sources [2] [3]. None of the supplied results, however, quantify the full long‑term software upgrade bill or the value of continuous upgrades to capability; the sources instead use the software dependency as a rationale for higher routine maintenance and lower uptime in practice [2] [3]. Available sources do not mention detailed program‑level cost breakdowns (e.g., ITAR/contractor support fees, COTS vs bespoke software licensing) beyond the high‑level operating‑cost comparisons (not found in current reporting).

5. Caveats, competing perspectives and contested assumptions

The sources repeatedly note the cost comparisons are “controversial” and sensitive to national assumptions: flight hours per year, what’s included in “operating cost,” and national industrial arrangements can swing results [1]. Proponents of Gripen emphasise lower cost and simpler logistics [4] [3]. Proponents of the F‑35 argue that its 5th‑generation capabilities (stealth, sensor fusion, networking) provide operational value not captured by simple flight‑hour metrics — this value claim is mentioned or implied when sources “relativise” Gripen’s cost advantages by noting F‑35 capabilities [2]. The provided material does not include direct, sourced rebuttals from Lockheed Martin or official F‑35 sustainment offices, so those perspectives are not present in current reporting (available sources do not mention Lockheed Martin or U.S. DoD rebuttals in these search results).

6. Practical implications for procurement and lifecycle planning

For nations prioritising low total‑cost‑of‑ownership, dispersed operations and controllable national sustainment, the cited material argues Gripen E offers attractive maintenance, upgrade-cycle simplicity and lower per‑hour costs [3] [1]. For nations prioritising stealth, integrated battlespace networking and continual capability growth through software, the F‑35’s software‑driven upgrade path — though costlier to sustain — is presented as delivering operational advantages some countries accept despite higher lifecycle costs [2]. Decision‑makers must therefore weigh measured, auditable sustainment estimates against the strategic value of capabilities that are harder to monetise.

If you want, I can: (a) extract the quoted cost numbers into a side‑by‑side table from these sources; (b) list what specific cost categories different reports include or exclude; or (c) search for official F‑35 sustainment replies and more recent national cost studies to broaden the source set.

Want to dive deeper?
How do mean time between failures and sortie rates differ for Gripen E vs F-35 over a 20-year lifecycle?
What are the typical upgrade timelines and costs for modular hardware swaps in Gripen E compared with F-35 software/firmware-driven upgrades?
How do sustainment models (depot vs operator-level maintenance) and required personnel training differ between Gripen E and F-35 operators?
What role do proprietary software, cybersecurity patches, and classified firmware play in the long-term sustainment costs of the F-35 compared to Gripen E?
How do international procurement patterns, logistics chains, and spare-parts availability affect lifecycle readiness and total cost of ownership for Gripen E versus F-35?