How many F-35s have crashed and what does that say about the stealth jet’s safety?
August 1, 2025
A US Navy F-35C jet with the “Rough Raiders” squadron crashed near Naval Air Station Lemoore on 30 July 2025, marking the 12th major crash of an F-35 since records began. The pilot ejected safely, and no injuries were reported.
The first flight of the F-35 occurred on 15 December 2006, and by 2011, the US Air Force accepted its first production model. It wasn’t until 2016 that the F-35A variant reached initial operational capability.
F-35B accident at Forth Worth airbase in the U.S.
— Clash Report (@clashreport) December 15, 2022
The pilot was able to eject. pic.twitter.com/gZvLWqiWtE
Since then, more than 600 aircraft have entered military service, and over 2,400 more are on order for the US alone. Yet its journey has been punctuated by recurring incidents, many resulting in the total loss of the aircraft.
Notable F-35 crashes: A timeline
Between 2014 and 2016, three F-35s suffered fire damage in the US, with two of the three deemed damaged beyond repair. But the first F-35 crash came in 2018.
- 28 Sept 2018 – F‑35B (USMC), first crash near MCAS Beaufort, SC. Attributed to a faulty fuel line
- 9 Apr 2019 – F‑35A (Japan), crashed into the Pacific Ocean. Attributed to pilot error
- 19 May 2020 – F‑35A (USAF), landing accident at Eglin AFB, FL. Attributed to technical faults
- 29 Sept 2020 – F‑35B (USMC), mid-air collision with KC-130 during air-to-air refueling in CA. Attributed to pilot error
- 17 Nov 2021 – F‑35B (RAF), crashed into the Mediterranean Sea. Attributed to a maintenance error
- 24 Jan 2022 – F‑35C (US Navy), ramp strike and loss overboard from USS Carl Vinson. Attributed to pilot error
- 19 Oct 2022 – F‑35A (USAF), crash on approach to Hill AFB, UT. Attributed to a technical error
- 15 Dec 2022 – F‑35B, failed vertical landing at NAS Fort Worth, TX. Attributed to an engine fault
- 17 Sep 2023 – F‑35B (USMC), crashed near North Charleston, SC. Attributed to an electrical malfunction
- 28 May 2024 – Test F‑35B crashed after take‑off from Kirtland AFB, NM. Cause unknown
- 28 Jan 2025 – F‑35A (USAF), near Eielson AFB, AK. Cause unknown
- 30 Jul 2025 – F‑35C (US Navy), near NAS Lemoore, CA. Cause unknown
#BREAKING A F-35 fighter jet just crashed during takeoff at Albuquerque International, New Mexico.
— Clash Report (@clashreport) May 28, 2024
Pilot reportedly ejected. pic.twitter.com/eAFSmgWJ00
With the latest incident this week, that brings the total number of F-35 crashes to 12 since the programme launched. Crucially, only one accident – the 2019 JASDF crash – ended in a fatality. In all other cases, pilots successfully ejected, although some were injured in the incidents.
Is the F-35 safe?
While 12 F-35 crashes in seven years sounds like an alarming statistic, it’s important to apply some context around the statistics.
A Sandboxx analysis found that the F-35 averages just 1.6 crashes for every 100,000 flying hours. That’s less than half of the F-16’s lifetime average of 3.55 crashes per 100,000 flight hours.
The article points out that, in the Viper’s troubled early years between 1988 and 1994, an average of 17 F-16 airframes were lost per year, for an average of 4.21 airframes lost per 100,000 flight hours.
Some militaries, including the UK’s RAF, have flagged issues with the F-35’s readiness. Defence News says that, for the US, the F-35 was ‘ready’ 51.1% of the time. The RAF hasn’t specified a rate, only that the F-35’s mission capable rate was approximately half that of the MoD’s target.
The Pratt & Whitney F135 engine, the sole powerplant for the F-35, has also had its problems. It was not originally designed to handle the expanded electrical and cooling demands of upgrades, especially the TR-3 (Technology Refresh-3) and Block 4 modernisation packages.
From a safety perspective, the F-35 is performing well, even better than legacy platforms. But from a fleet perspective, persistent technical issues and high sustainment costs continue to undermine confidence in its reliability and readiness.
