Behind the stealth coatings, data fusion buzzwords and record-breaking price tags, a colder metric is starting to weigh on defence deals: which jet actually stays in the air, year after year, without ending up in a smoking crater.
When a 100‑million‑euro jet meets the ground
On 30 July 2025, farmers near Naval Air Station Lemoore in California heard a dull thud. Moments earlier, a US Navy F‑35C Lightning II had gone down during a routine training flight.
The pilot managed to eject and survived. The aircraft did not. Around 100 million euros’ worth of fifth‑generation hardware was reduced to scrap in seconds.
This was not an isolated mishap. It was the second F‑35 crash of the year, after an F‑35A went down in Alaska during a training mission in January. In both cases, the pilots escaped, but the pattern raised fresh questions about the jet routinely described as “the fighter of the century”.
F‑35s keep making headlines for their technology. Increasingly, they also make headlines when they fail to complete basic training flights.
On paper, the Lockheed Martin F‑35 is a marvel: stealthy, highly networked, and able to fuse data from sensors and allies into a single tactical picture. It comes in three versions for the US Air Force, Navy and Marine Corps, plus a long list of export customers.
Yet behind the brochure lies a more uncomfortable reality: technical glitches, software delays, demanding maintenance, and an incident record that now sits under the microscope of rival manufacturers and sceptical parliaments.
Incident rates: the metric sales brochures gloss over
Defence ministries rarely buy fighters for their brochure speed or climb rate alone. They care about a more prosaic question: how often do they fail, and why?
From 2018 onwards, as F‑35 numbers grew, so did public reports of accidents and serious incidents. That timeframe also allows a comparison with other modern fighters already in frontline service, including the French Rafale, Europe’s Eurofighter Typhoon, Sweden’s Gripen, and China’s J‑20.
➡️ This haircut adapts well to women over 50 whose hair reacts to humidity
➡️ This old metal accessory from the cupboard that nature lovers now keep protects birds in winter
➡️ This cozy meal feels like something you’d eat by the fire
Rafale vs F‑35: fewer jets, far fewer mishaps
Based on open-source tallies, roughly 900 or more F‑35s are now in service worldwide. Since the type entered operational life, around 18 notable accidents and major incidents have been reported. That produces an approximate incident rate in the 1.6–2% range.
By contrast, the French-built Dassault Rafale has a much cleaner record. With around 150–160 aircraft in service across France, India, Egypt, Qatar and Greece, only two major publicly known crashes appear in recent years.
The Rafale operates with an incident rate below 1%, despite intensive use over Iraq, Syria, the Sahel and the Indo-Pacific.
Part of that difference comes from maturity. The Rafale first flew in the 1980s and entered French service in 2001. Its development arc was long, painful and largely settled before mass export. By the late 2010s, the aircraft was considered technically stable, and the French Air and Space Force had decades of maintenance experience behind it.
The F‑35, in contrast, is still evolving while already delivered in large numbers. Software upgrades, hardware retrofits and configuration changes are constant, which introduces new failure modes and complexity. Each new block of software can fix one issue and uncover two more.
How other fighters compare
Other modern jets sit between these two extremes. The Eurofighter Typhoon, with more than 600 aircraft delivered to European and Gulf air forces, has recorded around ten crashes since entry into service, giving it an incident rate broadly comparable to the F‑35.
Sweden’s Gripen, especially the latest Gripen E, was designed for simplicity and low running costs. Incident numbers remain low, helped by a smaller fleet and a philosophy that prioritises ease of maintenance and pilot-friendly behaviour.
- F‑35: high incident rate, high complexity, high cost
- Rafale: low incident rate, high combat use, strong maintenance culture
- Typhoon: moderate incident rate, mature but complex platform
- Gripen: low cost, relatively low incident count
China’s stealthy J‑20 is harder to assess. Analysts estimate more than 300 aircraft produced, but Beijing releases almost no details on accidents. From the outside, its safety profile is largely guesswork.
The money question: what reliability does to lifetime cost
Crash statistics are only one part of the story. Each lost jet represents not only the sticker price, but years of training, spare parts, and logistical infrastructure gone in an instant.
Across a 30‑year lifespan, the true cost of a fighter includes fuel, maintenance personnel, simulators, software updates and upgrades. Frequent incidents, even non‑fatal ones, usually translate into more inspections, more downtime and higher bills.
| Aircraft | Approximate unit price | Estimated 30‑year cost | Key factors |
| F‑35A | €90–100m | €250–300m | Heavy maintenance, complex logistics, high hourly cost, dependence on US support chain. |
| Rafale F4 | €80–120m | €180–200m | Balanced running costs, strong reliability, support can be localised in customer country. |
| Gripen E | €60–70m | €120–150m | Lightweight design, low fuel burn, simplified maintenance concept. |
Here the Rafale occupies a middle ground. It is not the cheapest to purchase or operate, yet it offers high-end performance without the same level of logistical burden as the F‑35. For countries wary of locking themselves into a single US-controlled software and spares ecosystem, that balance becomes a political asset.
Incident rates feed directly into life‑cycle cost: a jet that spends weeks grounded or, worse, lost in a crash, quickly erodes any upfront “bargain”.
Why the Rafale’s stability matters for export deals
In recent years, France has signed major Rafale contracts with India, the United Arab Emirates, Greece, Egypt and others. Many of these states could have pushed harder for access to the F‑35, backed by the US diplomatic machine.
The choice of Rafale often reflects more than short‑term price. Air forces study availability rates, sortie numbers in real operations, and the rate at which aircraft return safely to base. Paris can point to sustained Rafale deployments over Iraq, Syria, Libya and Africa with tight accident figures.
Defence planners also value predictability. A fighter with modest software needs and a clear upgrade path is easier to keep flying than a machine that behaves like a half‑finished operating system. Each time an F‑35 software block slips, training schedules and maintenance plans have to adapt around it.
From “combat of the century” to “maintenance of the century”
The F‑35 programme has been compared to a constantly updating smartphone: packed with sensors, apps and connectivity, but reliant on patches, reboots and an invisible cloud infrastructure. That comparison is less flattering when talking about a jet travelling at Mach 1.6.
Several US officials, on and off the record, acknowledge that the aircraft’s combat potential is enormous, but only when it is fully operational and supported by the right software version. That conditional phrasing is exactly what makes foreign buyers nervous.
The best fighter jet is rarely the one with the most lines of code. It is the one that takes off when needed and comes back in one piece.
Key notions: incident rate, availability and “sortie generation”
Three technical terms sit behind the numbers that favour the Rafale today.
Incident rate counts accidents and serious malfunctions per number of aircraft or flight hours. A lower rate does not only mean fewer crashes. It usually signals better design margins, simpler systems and lots of accumulated experience.
Availability rate expresses how many jets in a fleet are actually ready to fly at any given time. Air forces quietly track whether they can put, say, 7 or 8 aircraft out of 10 into the sky when called upon. Highly complex stealth jets often struggle here, because their coatings and software demand constant attention.
Sortie generation refers to how many missions a squadron can launch and recover per day during a crisis. An aircraft that is slightly less stealthy but far easier to turn around on the ground can end up delivering more bombs or patrols over a week of combat.
On these three measures, French officials argue that Rafale squadrons can sustain a high tempo with relatively lean support teams, especially from dispersed or improvised airbases.
What this means for future air wars
Imagine a mid-sized European or Asian country facing several days of intense air operations: long-range patrols, precision strikes, and air defence missions. In that scenario, paper performance gives way to practical questions: Which jets are available on the second or third day? Which can absorb a maintenance issue without halving the fleet?
A fleet of Rafales with a low incident rate, robust maintenance chain and high availability might field a larger number of daily sorties than a smaller, more fragile F‑35 contingent. Even if each F‑35 carries more data or has a stealthier profile, the raw count of missions flown matters.
There are also political risks. A series of high‑profile crashes can trigger domestic backlash, media storms and parliamentary inquiries. For buying nations, a jet associated with frequent accidents can quickly become a liability at home, regardless of its battlefield virtues.
On the other hand, a platform like the Rafale that quietly logs thousands of hours without major incident builds a reputation for seriousness. That reputation, backed by numbers rather than slogans, is now shaping tenders from Eastern Europe to the Indo‑Pacific — and tilting the scales against the F‑35 in a field where reliability is starting to speak louder than stealth.
Originally posted 2026-03-05 01:56:16.