![\"\"](\"https:\/\/alphadefense.in\/wp-content\/uploads\/2025\/07\/image-62-1024x590.png\")
<\/figure>\n\n\n\nLet’s compile all 15 F-35 crashes in detail to understand how challenging it is to maintain this jet. These incidents highlight the reality behind operating such a complex, over-engineered masterpiece\u2014where cutting-edge performance often comes with increased vulnerability to failure.<\/p>\n\n\n\n
The latest F-35 crash occurred near NAS Lemoore in California, marking the 15th such incident since the jet’s inception.<\/p>\n\n\n\n
14 Previous F-35 Crashes \u2013 Explained with Failure Types<\/strong><\/h2>\n\n\n\n1. June 23, 2014 \u2013 Eglin AFB, Florida, USA<\/strong><\/h3>\n\n\n\nAn F\u201135A (tail number 10\u20115015) caught fire during the takeoff roll from Eglin AFB. Investigators traced the cause to a fractured third\u2011stage rotor arm of the F135 engine\u2019s fan module. That part liberated under excessive rubbing, cutting through the fan case, engine bay, fuel tank, fuel lines, and hydraulic lines. Leaking fuel and hydraulic fluid ignited, burning about the rear two\u2011thirds of the airframe. The pilot aborted takeoff safely and exited without injury. The damage exceeded USD\u202f50\u202fmillion, and the entire F\u201135 fleet grounded shortly afterward. Pratt & Whitney implemented interim \u201crub\u2011in\u201d procedures and redesigns to fix the Rub\u2011failure.<\/p>\n\n\n\n
Failure type:<\/strong> Mechanical failure \u2013 engine rotor damage leading to catastrophic fire.<\/em><\/p>\n\n\n\n2. September 28, 2018 \u2013 Beaufort, South Carolina, USA<\/strong><\/h3>\n\n\n\nA USMC F\u201135B bearing tail number 168719<\/strong> crashed during a routine training flight near Marine Corps Air Station Beaufort. Military confirmed the pilot ejected safely without injury. The engine suffered a catastrophic flameout when a defective fuel tube ruptured mid-flight<\/strong>, cutting off fuel supply and causing immediate loss of power. Investigators traced the rupture to a defective batch supplied during engine production. The incident triggered a fleet-wide inspection of fuel tubes across all F\u201135s. At least 117 jets<\/strong> received replacement parts before further flight. Maintenance crews grounded numerous aircraft temporarily for safety assurance. This was the first-ever loss<\/strong> of an F\u201135 aircraft.<\/p>\n\n\n\nFailure type:<\/strong> Mechanical failure \u2013 fuel tube rupture causing engine shutdown.<\/em><\/p>\n\n\n\n3. April 9, 2019 \u2013 Off Aomori, Japan<\/strong><\/h3>\n\n\n\nA JASDF F\u201135A, tail number 79\u20118705<\/strong> (callsign AX\u20116), took off from Misawa Air Base for aerial training with three other F\u201135s. The pilot, Maj. Akinori Hosomi<\/strong>, flew combat-simulation drills reliably until 7:26 p.m. He reported two simulated kills and acknowledged a descent order. Seconds later the aircraft disappeared from radar, plummeting into the Pacific at over 1,100\u202fkm\/h. Rescuers recovered scattered debris and, in June 2019, recovered pilot remains about 1500\u202fm below the sub surface.<\/p>\n\n\n\nInvestigators ruled out any technical or mechanical issues. They found no signs of engine or system malfunction<\/strong>. Instead, they attributed the crash to spatial disorientation<\/strong>. Hosomi likely experienced vertigo and lost equilibrium. He did not send a distress call, attempt recovery, or eject. The danger overwhelmed instrument readings, and he followed a fatal descent without awareness. However, many believe this needs more study.<\/p>\n\n\n\nFollowing the crash, JASDF grounded all twelve F\u201135As. It mandated retraining focused on spatial orientation and gravity-induced loss of consciousness (G\u2011LOC). Enhanced protocols now accompany each F\u201135 pilot\u2019s training.<\/p>\n\n\n\n
Failure type:<\/strong> Spatial disorientation leading to loss of situational awareness and fatal descent.<\/em><\/p>\n\n\n\n4. May 19, 2020 \u2013 Eglin AFB, Florida, USA<\/strong><\/h3>\n\n\n\nA US Air Force F\u201135A, tail number 12\u2011005053<\/strong>, crashed on landing at runway\u202f30 around 9:26\u202fPM. The pilot ejected safely but sustained non-life-threatening injuries. The jet rolled, caught fire, and was destroyed.<\/p>\n\n\n\nInvestigators determined the aircraft touched down at about 202 knots<\/strong>, approximately 50 knots above target<\/strong> and at a 5.2\u00b0 angle of attack<\/strong>, much shallower than the recommended ~13\u00b0. The aircraft then bounced violently, entering pitch oscillation<\/strong>. The pilot applied aft stick and afterburner to abort, but conflicting control inputs froze the tail surfaces in a nose-down position. Consequently, he could not arrest the oscillations and ejected after about five seconds on the runway.<\/p>\n\n\n\nSeveral contributing factors aggravated the mishap: the pilot landed with Speed Hold engaged<\/strong>, his helmet-mounted display misaligned<\/strong>, he suffered cognitive fatigue<\/strong>, and he lacked sufficient knowledge of the jet\u2019s flight-control logic<\/strong>.<\/p>\n\n\n\nFailure type:<\/strong> Oxygen system fault + HUD display error + pilot error.<\/em><\/p>\n\n\n\n5. September 29, 2020 \u2013 California, USA<\/strong><\/h3>\n\n\n\nAn F\u201135B, tail number 169294 (callsign VOLT\u201193), collided mid-air with KC\u2011130J BuNo\u202f166765 (callsign RAIDER\u202f50) during aerial refueling near El Centro. Both aircraft belonged to the U.S. Marine Corps and participated in the Weapons and Tactics Instructor (WTI) exercise out of MCAS Yuma, Arizona.<\/p>\n\n\n\n
At approximately 1600 local, the F\u201135B clipped the tanker\u2019s starboard wing and fuel pod. The F\u201135B lost lift and crashed into the desert near the Salton Sea. The pilot ejected successfully and sustained minor injuries.<\/p>\n\n\n\n
The KC\u2011130J suffered heavy damage to both right-side engines and propellers. The crew declared emergency and made a belly landing in a cauliflower field near Thermal Airport. All eight crew members walked away safe.<\/p>\n\n\n\n
Investigators linked the crash to wake turbulence and flight-control anomalies during refueling. Sensor transitions produced erratic airdata inputs. The F\u201135B lost stable control before contact.<\/p>\n\n\n\n
6. March 12, 2021 \u2013 Yuma, Arizona, USA<\/strong><\/h3>\n\n\n\nA US Marine Corps F\u201135B (tail number unknown<\/strong>, assigned to VMX\u20111) flew a nighttime close air support mission over the Yuma Range Complex. During gunnery practice, a 25\u202fmm PGU\u201132\/U SAPHEI\u2011T round prematurely exploded as it exited the externally mounted GAU\u201122 gun pod<\/strong>. The resulting blast shredded fuselage panels and left fragmentation damage across the belly and lower aft section. The pilot landed the jet safely back to base and reported no injuries. Navy officials initially classified the event as a Class A mishap\u2014later downgraded to Class C, indicating damage between $60,000 and $600,000.<\/p>\n\n\n\nFailure type:<\/strong> Mechanical failure \u2013 premature ordnance detonation.<\/em><\/p>\n\n\n\n7. November 17, 2021 \u2013 HMS Queen Elizabeth, Mediterranean<\/strong><\/h3>\n\n\n\nAn RAF F\u201135B (tail number ZM152, construction number BK\u201118)<\/strong> crashed into the Mediterranean Sea during takeoff from HMS\u202fQueen\u202fElizabeth. The pilot ejected safely and was recovered onto the carrier deck.<\/p>\n\n\n\nEngine thrust fell significantly below normal\u2014only about 55% of required power\u2014because a plastic protective engine intake blank<\/strong> remained lodged in the intake during launch. That blockage choked airflow, preventing proper engine performance. The jet failed to gain lift and plunged off the ski-jump ramp into the sea.<\/p>\n\n\n\nInvestigators found that technicians had left this \u201cRed Gear\u201d intake cover<\/strong> in place. A systemic failure in removal procedures contributed. The panel linked the mishap to human and organizational error<\/strong> rather than engineering flaws.<\/p>\n\n\n\nThe aircraft was assigned to 617 Squadron, RAF<\/strong>, deployed aboard Queen Elizabeth during Carrier Strike Group\u202f21 operations. After impact, the intake blank floated to the surface and was recovered. All onboard \u201csecurity sensitive equipment\u201d was later salvaged.<\/p>\n\n\n\nFailure type:<\/strong> Engine intake blockage \u2013 foreign object.<\/em><\/p>\n\n\n\n8. January 4, 2022 \u2013 South Korea<\/strong><\/h3>\n\n\n\nA South Korean Air Force F\u201135A \u2014 tail number 20\u2011017 \u2014 made an emergency belly landing at Seosan Air Base after avionic systems failed. The pilot landed safely and walked away without injury.<\/p>\n\n\n\n
The aircraft experienced system-wide electronic anomalies. All flight systems shut down except for engine thrust and manual flight controls. The landing gear failed to deploy due to avionics malfunction. The pilot opted for a gear-up touchdown, guided foam covered the runway, minimizing damage.<\/p>\n\n\n\n
Investigators attributed the incident to sensor system and hydraulic failures, which led to the gear malfunction. Only core controls and propulsion remained functional. The fleet was grounded immediately pending full investigation.<\/p>\n\n\n\n
Failure type:<\/strong> Hydraulic failure + sensor system fault.<\/em><\/p>\n\n\n\n9. January 24, 2022 \u2013 USS Carl Vinson, South China Sea<\/strong><\/h3>\n\n\n\nA U.S. Navy F\u201135C with tail number 169304<\/strong>, assigned to Strike Fighter Squadron 147 \u201cArgonauts\u201d<\/strong>, attempted a skilled “expedited recovery” (Sierra Hotel break)<\/strong> downwind approach over the USS\u202fCarl\u202fVinson. The pilot had more than 370 flight hours in the F\u201135C. As he executed the tight maneuver, multiple critical steps failed. He did not activate two electronic landing assist systems\u2014Approach Power Compensation (APC)<\/strong> and Delta Flight Path (DFP)<\/strong>\u2014intending to maintain proper angle of attack and throttle control. As a result, the aircraft approached at low power, high speed, and excessive descent rate.<\/p>\n\n\n\nAt around 16:30 local time, due to low thrust and sensor issues, the jet struck the aft ramp with its belly. The main landing gear collapsed. The plane caught two arresting wires\u2014a leftover rail snagged the wire and caused the aircraft to spin across the deck before falling into the sea. The pilot safely ejected, but six crew members<\/strong> aboard the flight deck suffered injuries. A nearby EA\u201118G Growler sustained over $2.5 million in damage, and deck repairs cost approximately $120,000. The jet itself was a total loss, valued at over $115 million.<\/p>\n\n\n\nNavy investigators ultimately classified the incident as pilot error<\/strong>. They cited task saturation<\/strong>, incomplete checklist execution, and mismanaged automation as root causes. The pilot\u2019s unfamiliarity with the maneuver compounded the failure to activate the landing aids in the compressed timeline.<\/p>\n\n\n\nFailure type:<\/strong> Flight-control logic error during ramp strike amplified by missed automation activation under task saturation.<\/em><\/p>\n\n\n\n10. October 19, 2022 \u2013 Hill AFB, Utah, USA<\/strong><\/h3>\n\n\n\nOn October 19, 2022, an F-35A Lightning II (tail number 15-5197) belonging to the 421st Fighter Squadron, 388th Fighter Wing, crashed shortly after making the final turn toward runway 14 at Hill Air Force Base, Utah, around 6:08 p.m. local time. The aircraft had just returned from a routine training sortie as part of a four-ship formation. On final approach, the wake turbulence from a preceding jet induced mild airflow disturbances, which fed erroneous data into the aircraft\u2019s air data application (ADA). The ADA rapidly switched between its primary and backup sources, resulting in corrupted altitude and airspeed information. Consequently, the flight-control system responded incorrectly, and manual controls no longer aligned reliably with the pilot’s input. In an attempt to recover, the pilot applied full afterburner, but with insufficient altitude, low airspeed, and increasing sideslip, recovery became impossible. The pilot ejected approximately three seconds after losing control and sustained only minor injuries. The aircraft crashed north of the runway, sparking a brush fire that scorched 8\u201310 acres. The F-35A was a total loss, valued at approximately USD 166 million. The root cause was identified as an air data system failure that fed corrupted sensor information to the flight-control logic, leading to a loss of control.<\/p>\n\n\n\n
Failure type:<\/strong> Air data system failure \u2013 corrupted altitude readings.<\/em><\/p>\n\n\n\n11. December 15, 2022 \u2013 Fort Worth, Texas, USA<\/strong><\/h3>\n\n\n\nAn F\u201135B tail number 170061<\/strong> crashed during vertical landing trials at NAS JRB Fort Worth. The jet descended in STOVL mode, bounced during hover descent, then flipped nose\u2011down and rolled over. The pilot ejected safely and escaped uninjured. The aircraft had not yet transferred from manufacturer to U.S. military. Video footage shows the jet tipping forward after a bounce. Engineers later determined a software glitch in the STOVL flight\u2011control logic misinterpreted sensor inputs. The jet lost balance mid\u2011transition from hover to landing and overturned. The pilot ejected promptly as automated control failed. Failure type:<\/strong> Flight\u2011control logic glitch during STOVL operation.<\/em><\/p>\n\n\n\nFailure type:<\/strong> Flight-control logic glitch during STOVL operation.<\/em><\/p>\n\n\n\n12. September 17, 2023 \u2013 North Charleston, South Carolina, USA<\/strong><\/h3>\n\n\n\nF\u201135B tail number 169591 from VMFAT\u2011501 flew through heavy rain near Joint Base Charleston. The pilot ejected safely over a residential backyard in North Charleston. After ejection, the jet continued flying on autopilot for 64 nautical miles. Eventually, it crashed in rural Williamsburg County. An electrical event disabled the transponder, radios, and navigation systems midflight. Both the helmet-mounted and panoramic cockpit displays failed multiple times during the sortie. <\/p>\n\n\n\n
Investigators later found the pilot misjudged the jet’s behavior and ejected while systems were stabilizing. They traced the crash to a software fault, likely a cascading failure in the navigation system. Due to stealth features and no working transponder, the aircraft remained missing for over 24 hours. Search efforts faced serious delays as a result.<\/p>\n\n\n\n
Failure type:<\/strong> Software fault \u2013 possible cascading failure in navigation system<\/em>.<\/p>\n\n\n\n13. May 28, 2024 \u2013 Albuquerque, New Mexico, USA<\/strong><\/h3>\n\n\n\nSoon after takeoff from Kirtland Air Force Base, developmental F\u201135B tail number 170067 suffered a critical malfunction. The jet had just refueled during its flight from Fort Worth, Texas, to Edwards AFB, California. At low altitude, the pilot ejected safely, though he sustained serious injuries and later stabilized in the hospital. <\/p>\n\n\n\n
The jet slammed into a scrub desert hillside near Albuquerque International Sunport and immediately burst into flames. Firefighters responded quickly and extinguished the blaze before it could spread. The aircraft, fitted with Technology Refresh 2 software, was completely destroyed in the crash. Investigators are still analyzing telemetry data to find the root cause. However, early indications suggest a mechanical issue possibly linked to the engine\u2019s fuel system.<\/p>\n\n\n\n
Failure type:<\/strong> Mechanical failure \u2013 engine or fuel-related malfunction.<\/em><\/p>\n\n\n\n14. January 28, 2025 \u2013 Eielson AFB, Alaska, USA<\/strong><\/h3>\n\n\n\nOn January 28, 2025, at 12:49 p.m. local time, an F\u201135A began malfunctioning during the landing phase at Eielson Air Force Base. The pilot quickly initiated emergency procedures and successfully ejected, avoiding injury. As the jet lost control at low altitude, it crashed within the base perimeter and triggered a large fire. The impact completely destroyed the aircraft. <\/p>\n\n\n\n
Although the pilot required brief medical observation, he suffered no serious harm and was released shortly after. While the official cause remains undisclosed, investigators strongly suspect a failure in the flight-control or air-data systems. The aircraft, assigned to the 354th Fighter Wing, bore the \u201cAK\u201d tail code and was likely flown by the 355th Fighter Squadron. Overall, this incident underscores how even a minor system glitch can lead to a catastrophic failure in modern stealth fighters.<\/p>\n\n\n\n
Failure type:<\/strong> Undisclosed \u2013 suspected flight control or air data glitch.<\/em><\/p>\n\n\n\nApart from these the latest one became memefest for many tracking aviation and defence. In mid-June 2025, a Royal Navy F\u201135B diverted to Thiruvananthapuram International Airport in Kerala due to technical glitch and low fuel amid bad weather. The jet landed safely on June 14 after attempts to return to HMS\u202fPrince of Wales failed. Later it was learnt tha aircraft had hydraulics and APU issues. A UK engineering team arrived, worked through monsoon rain, and moved the jet into an airport hangar. Meanwhile, Kerala\u2019s tourism department embraced the situation with humorous memes, portraying the F\u201135B as a delighted tourist giving the state five stars. Internet users joked it wanted a vacation or lunch of filter coffee. The jet stayed stranded for 37 days under armed guard, attracting global social media attention. It finally departed on July 22, reunited with its Carrier Strike Group en route to Australia. The event underscored how unexpected technical faults can transform a sophisticated stealth fighter into a worldwide meme sensation.<\/p>\n\n\n\n
The F\u201135 is one of the most advanced but also maintenance-intensive aircraft ever fielded. With its tightly integrated stealth features, complex software architecture, and high part-count, it regularly faces technical issues and availability challenges. These problems are not rare, they’re systemic, especially for countries that neither assemble the aircraft nor possess sovereign maintenance capabilities. Operators without full industrial access often face delays in fault diagnosis, spares, and repairs. As the Thiruvananthapuram incident illustrated, even a non-catastrophic glitch can become a global embarrassment when local support infrastructure is lacking.<\/p>\n\n\n\n
References<\/p>\n\n\n\n
\n- June\u00a023,\u00a02014 \u2013 Eglin AFB, Florida, USA – FighterJetsWorld<\/a> <\/li>\n\n\n\n
- September\u202f28,\u202f2018 \u2013 Beaufort, South Carolina, USA – \ud83d\udcce News Link<\/a><\/li>\n\n\n\n
- April\u202f9,\u202f2019 \u2013 Off Aomori Prefecture, Japan (JASDF F\u201135A #79-8705) – \ud83d\udcce CNN<\/a><\/li>\n\n\n\n
- May\u202f19,\u202f2020 \u2013 Eglin AFB, Florida, USA – \ud83d\udcce Air Force Times<\/a>\\<\/li>\n\n\n\n
- September\u202f29,\u202f2020 \u2013 Imperial County, California, USA – \ud83d\udcce Task & Purpose<\/a><\/li>\n\n\n\n
- March\u202f12,\u202f2021 \u2013 Yuma, Arizona, USA – \ud83d\udcce Aviation Geek Club<\/a><\/li>\n\n\n\n
- November\u202f17,\u202f2021 \u2013 Mediterranean (HMS\u202fQueen\u202fElizabeth, UK) \ud83d\udcce BBC<\/a><\/li>\n\n\n\n
- January\u202f4,\u202f2022 \u2013 Seosan Air Base, South Korea (F\u201135A #20\u2011017) – \ud83d\udcce Korea Times<\/a><\/li>\n\n\n\n
- January\u202f24,\u202f2022 \u2013 USS\u00a0Carl Vinson, South China Sea – \ud83d\udcce USNI News<\/a><\/li>\n\n\n\n
- October\u202f19,\u202f2022 \u2013 Hill AFB, Utah, USA (F\u201135A #15\u20115197) – \ud83d\udcce KSL TV<\/a><\/li>\n\n\n\n
- December\u202f15,\u202f2022 \u2013 Fort Worth, Texas, USA (F\u201135B #170061) – \ud83d\udcce Defense News<\/a><\/li>\n\n\n\n
- September 17, 2023 \u2013 North Charleston, South Carolina, USA (F\u201135B #169591) \ud83d\udcce NBC News<\/a><\/li>\n\n\n\n
- May 28, 2024 \u2013 Albuquerque, New Mexico, USA (F\u201135B #170067) – \ud83d\udcce Business Insider<\/a><\/li>\n\n\n\n
- January 28, 2025 \u2013 Eielson AFB, Alaska, USA -\ud83d\udcce NY Post<\/a><\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"
An F35 crash occurred near NAS Lemoore in California. The jet caught fire after impact. California Highway Patrol (CHP) confirmed…<\/p>\n","protected":false},"author":1,"featured_media":1448,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_uag_custom_page_level_css":"","_uf_show_specific_survey":0,"_uf_disable_surveys":false,"fifu_image_url":"","fifu_image_alt":"","_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[6,507,544],"class_list":["post-1445","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","tag-alpha-defense","tag-f35","tag-f35-crash"],"yoast_head":"\n
F35 Crash Near NAS Lemoore \u2013 July 30, 2025 - AlphaDefense.in<\/title>\n<meta name=\"description\" content=\"An F-35 crash near NAS Lemoore reignites safety concerns. Read a detailed list of all past F-35 crashes. Read more details here..\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/alphadefense.in\/index.php\/2025\/07\/31\/f35-crash-history-latest-lemoore\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"F35 Crash Near NAS Lemoore \u2013 July 30, 2025 - AlphaDefense.in\" \/>\n<meta property=\"og:description\" content=\"An F-35 crash near NAS Lemoore reignites safety concerns. Read a detailed list of all past F-35 crashes. Read more details here..\" \/>\n<meta property=\"og:url\" content=\"https:\/\/alphadefense.in\/index.php\/2025\/07\/31\/f35-crash-history-latest-lemoore\/\" \/>\n<meta property=\"og:site_name\" content=\"AlphaDefense.in\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/TheAlphaDefense\/\" \/>\n<meta property=\"article:published_time\" content=\"2025-07-31T06:46:52+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-07-31T06:46:55+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/alphadefense.in\/wp-content\/uploads\/2025\/07\/image-61.png\" \/>\n\t<meta property=\"og:image:width\" content=\"640\" \/>\n\t<meta property=\"og:image:height\" content=\"416\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"alphadefense.in\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@alpha_defense\" \/>\n<meta name=\"twitter:site\" content=\"@alpha_defense\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"alphadefense.in\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"13 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/alphadefense.in\/index.php\/2025\/07\/31\/f35-crash-history-latest-lemoore\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/alphadefense.in\/index.php\/2025\/07\/31\/f35-crash-history-latest-lemoore\/\"},\"author\":{\"name\":\"alphadefense.in\",\"@id\":\"https:\/\/alphadefense.in\/#\/schema\/person\/75f9c8f915691996b14d064fd0060a1c\"},\"headline\":\"F35 Crash Near NAS Lemoore \u2013 July 30, 2025\",\"datePublished\":\"2025-07-31T06:46:52+00:00\",\"dateModified\":\"2025-07-31T06:46:55+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/alphadefense.in\/index.php\/2025\/07\/31\/f35-crash-history-latest-lemoore\/\"},\"wordCount\":2755,\"commentCount\":1,\"publisher\":{\"@id\":\"https:\/\/alphadefense.in\/#organization\"},\"image\":{\"@id\":\"https:\/\/alphadefense.in\/index.php\/2025\/07\/31\/f35-crash-history-latest-lemoore\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/alphadefense.in\/wp-content\/uploads\/2025\/07\/image-61.png\",\"keywords\":[\"Alpha Defense\",\"F35\",\"F35 Crash\"],\"articleSection\":[\"Blog\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/alphadefense.in\/index.php\/2025\/07\/31\/f35-crash-history-latest-lemoore\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/alphadefense.in\/index.php\/2025\/07\/31\/f35-crash-history-latest-lemoore\/\",\"url\":\"https:\/\/alphadefense.in\/index.php\/2025\/07\/31\/f35-crash-history-latest-lemoore\/\",\"name\":\"F35 Crash Near NAS Lemoore \u2013 July 30, 2025 - AlphaDefense.in\",\"isPartOf\":{\"@id\":\"https:\/\/alphadefense.in\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/alphadefense.in\/index.php\/2025\/07\/31\/f35-crash-history-latest-lemoore\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/alphadefense.in\/index.php\/2025\/07\/31\/f35-crash-history-latest-lemoore\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/alphadefense.in\/wp-content\/uploads\/2025\/07\/image-61.png\",\"datePublished\":\"2025-07-31T06:46:52+00:00\",\"dateModified\":\"2025-07-31T06:46:55+00:00\",\"description\":\"An F-35 crash near NAS Lemoore reignites safety concerns. Read a detailed list of all past F-35 crashes. Read more details here..\",\"breadcrumb\":{\"@id\":\"https:\/\/alphadefense.in\/index.php\/2025\/07\/31\/f35-crash-history-latest-lemoore\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/alphadefense.in\/index.php\/2025\/07\/31\/f35-crash-history-latest-lemoore\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/alphadefense.in\/index.php\/2025\/07\/31\/f35-crash-history-latest-lemoore\/#primaryimage\",\"url\":\"https:\/\/alphadefense.in\/wp-content\/uploads\/2025\/07\/image-61.png\",\"contentUrl\":\"https:\/\/alphadefense.in\/wp-content\/uploads\/2025\/07\/image-61.png\",\"width\":4096,\"height\":2660},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/alphadefense.in\/index.php\/2025\/07\/31\/f35-crash-history-latest-lemoore\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/alphadefense.in\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"F35 Crash Near NAS Lemoore \u2013 July 30, 2025\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/alphadefense.in\/#website\",\"url\":\"https:\/\/alphadefense.in\/\",\"name\":\"alphadefense.in\",\"description\":\"Let\u2019s simplify the nuance\",\"publisher\":{\"@id\":\"https:\/\/alphadefense.in\/#organization\"},\"alternateName\":\"Alpha Defense\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/alphadefense.in\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/alphadefense.in\/#organization\",\"name\":\"alphadefense.in\",\"url\":\"https:\/\/alphadefense.in\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/alphadefense.in\/#\/schema\/logo\/image\/\",\"url\":\"http:\/\/alphadefense.in\/wp-content\/uploads\/2024\/07\/AD-Logo.jpeg\",\"contentUrl\":\"http:\/\/alphadefense.in\/wp-content\/uploads\/2024\/07\/AD-Logo.jpeg\",\"width\":400,\"height\":400,\"caption\":\"alphadefense.in\"},\"image\":{\"@id\":\"https:\/\/alphadefense.in\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/TheAlphaDefense\/\",\"https:\/\/x.com\/alpha_defense\",\"https:\/\/www.instagram.com\/alpha.defense_\/\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/alphadefense.in\/#\/schema\/person\/75f9c8f915691996b14d064fd0060a1c\",\"name\":\"alphadefense.in\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/alphadefense.in\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/8d033bcad4fdd8511432f8d34bd0708a063a0e99dba011d037dee5e1cb4dc385?s=96&d=robohash&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/8d033bcad4fdd8511432f8d34bd0708a063a0e99dba011d037dee5e1cb4dc385?s=96&d=robohash&r=g\",\"caption\":\"alphadefense.in\"},\"sameAs\":[\"http:\/\/alphadefense.in\"],\"url\":\"https:\/\/alphadefense.in\/index.php\/author\/alphadefense-in\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"F35 Crash Near NAS Lemoore \u2013 July 30, 2025 - AlphaDefense.in","description":"An F-35 crash near NAS Lemoore reignites safety concerns. Read a detailed list of all past F-35 crashes. Read more details here..","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/alphadefense.in\/index.php\/2025\/07\/31\/f35-crash-history-latest-lemoore\/","og_locale":"en_US","og_type":"article","og_title":"F35 Crash Near NAS Lemoore \u2013 July 30, 2025 - AlphaDefense.in","og_description":"An F-35 crash near NAS Lemoore reignites safety concerns. Read a detailed list of all past F-35 crashes. Read more details here..","og_url":"https:\/\/alphadefense.in\/index.php\/2025\/07\/31\/f35-crash-history-latest-lemoore\/","og_site_name":"AlphaDefense.in","article_publisher":"https:\/\/www.facebook.com\/TheAlphaDefense\/","article_published_time":"2025-07-31T06:46:52+00:00","article_modified_time":"2025-07-31T06:46:55+00:00","og_image":[{"url":"http:\/\/alphadefense.in\/wp-content\/uploads\/2025\/07\/image-61.png","width":640,"height":416,"type":"image\/png"}],"author":"alphadefense.in","twitter_card":"summary_large_image","twitter_creator":"@alpha_defense","twitter_site":"@alpha_defense","twitter_misc":{"Written by":"alphadefense.in","Est. reading time":"13 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/alphadefense.in\/index.php\/2025\/07\/31\/f35-crash-history-latest-lemoore\/#article","isPartOf":{"@id":"https:\/\/alphadefense.in\/index.php\/2025\/07\/31\/f35-crash-history-latest-lemoore\/"},"author":{"name":"alphadefense.in","@id":"https:\/\/alphadefense.in\/#\/schema\/person\/75f9c8f915691996b14d064fd0060a1c"},"headline":"F35 Crash Near NAS Lemoore \u2013 July 30, 2025","datePublished":"2025-07-31T06:46:52+00:00","dateModified":"2025-07-31T06:46:55+00:00","mainEntityOfPage":{"@id":"https:\/\/alphadefense.in\/index.php\/2025\/07\/31\/f35-crash-history-latest-lemoore\/"},"wordCount":2755,"commentCount":1,"publisher":{"@id":"https:\/\/alphadefense.in\/#organization"},"image":{"@id":"https:\/\/alphadefense.in\/index.php\/2025\/07\/31\/f35-crash-history-latest-lemoore\/#primaryimage"},"thumbnailUrl":"https:\/\/alphadefense.in\/wp-content\/uploads\/2025\/07\/image-61.png","keywords":["Alpha Defense","F35","F35 Crash"],"articleSection":["Blog"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/alphadefense.in\/index.php\/2025\/07\/31\/f35-crash-history-latest-lemoore\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/alphadefense.in\/index.php\/2025\/07\/31\/f35-crash-history-latest-lemoore\/","url":"https:\/\/alphadefense.in\/index.php\/2025\/07\/31\/f35-crash-history-latest-lemoore\/","name":"F35 Crash Near NAS Lemoore \u2013 July 30, 2025 - AlphaDefense.in","isPartOf":{"@id":"https:\/\/alphadefense.in\/#website"},"primaryImageOfPage":{"@id":"https:\/\/alphadefense.in\/index.php\/2025\/07\/31\/f35-crash-history-latest-lemoore\/#primaryimage"},"image":{"@id":"https:\/\/alphadefense.in\/index.php\/2025\/07\/31\/f35-crash-history-latest-lemoore\/#primaryimage"},"thumbnailUrl":"https:\/\/alphadefense.in\/wp-content\/uploads\/2025\/07\/image-61.png","datePublished":"2025-07-31T06:46:52+00:00","dateModified":"2025-07-31T06:46:55+00:00","description":"An F-35 crash near NAS Lemoore reignites safety concerns. Read a detailed list of all past F-35 crashes. Read more details here..","breadcrumb":{"@id":"https:\/\/alphadefense.in\/index.php\/2025\/07\/31\/f35-crash-history-latest-lemoore\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/alphadefense.in\/index.php\/2025\/07\/31\/f35-crash-history-latest-lemoore\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/alphadefense.in\/index.php\/2025\/07\/31\/f35-crash-history-latest-lemoore\/#primaryimage","url":"https:\/\/alphadefense.in\/wp-content\/uploads\/2025\/07\/image-61.png","contentUrl":"https:\/\/alphadefense.in\/wp-content\/uploads\/2025\/07\/image-61.png","width":4096,"height":2660},{"@type":"BreadcrumbList","@id":"https:\/\/alphadefense.in\/index.php\/2025\/07\/31\/f35-crash-history-latest-lemoore\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/alphadefense.in\/"},{"@type":"ListItem","position":2,"name":"F35 Crash Near NAS Lemoore \u2013 July 30, 2025"}]},{"@type":"WebSite","@id":"https:\/\/alphadefense.in\/#website","url":"https:\/\/alphadefense.in\/","name":"alphadefense.in","description":"Let\u2019s simplify the nuance","publisher":{"@id":"https:\/\/alphadefense.in\/#organization"},"alternateName":"Alpha Defense","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/alphadefense.in\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/alphadefense.in\/#organization","name":"alphadefense.in","url":"https:\/\/alphadefense.in\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/alphadefense.in\/#\/schema\/logo\/image\/","url":"http:\/\/alphadefense.in\/wp-content\/uploads\/2024\/07\/AD-Logo.jpeg","contentUrl":"http:\/\/alphadefense.in\/wp-content\/uploads\/2024\/07\/AD-Logo.jpeg","width":400,"height":400,"caption":"alphadefense.in"},"image":{"@id":"https:\/\/alphadefense.in\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/TheAlphaDefense\/","https:\/\/x.com\/alpha_defense","https:\/\/www.instagram.com\/alpha.defense_\/"]},{"@type":"Person","@id":"https:\/\/alphadefense.in\/#\/schema\/person\/75f9c8f915691996b14d064fd0060a1c","name":"alphadefense.in","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/alphadefense.in\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/8d033bcad4fdd8511432f8d34bd0708a063a0e99dba011d037dee5e1cb4dc385?s=96&d=robohash&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/8d033bcad4fdd8511432f8d34bd0708a063a0e99dba011d037dee5e1cb4dc385?s=96&d=robohash&r=g","caption":"alphadefense.in"},"sameAs":["http:\/\/alphadefense.in"],"url":"https:\/\/alphadefense.in\/index.php\/author\/alphadefense-in\/"}]}},"jetpack_featured_media_url":"https:\/\/alphadefense.in\/wp-content\/uploads\/2025\/07\/image-61.png","uagb_featured_image_src":{"full":["https:\/\/alphadefense.in\/wp-content\/uploads\/2025\/07\/image-61.png",4096,2660,false],"thumbnail":["https:\/\/alphadefense.in\/wp-content\/uploads\/2025\/07\/image-61.png",150,97,false],"medium":["https:\/\/alphadefense.in\/wp-content\/uploads\/2025\/07\/image-61-300x195.png",300,195,true],"medium_large":["https:\/\/alphadefense.in\/wp-content\/uploads\/2025\/07\/image-61.png",640,416,false],"large":["https:\/\/alphadefense.in\/wp-content\/uploads\/2025\/07\/image-61.png",640,416,false],"1536x1536":["https:\/\/alphadefense.in\/wp-content\/uploads\/2025\/07\/image-61.png",1536,998,false],"2048x2048":["https:\/\/alphadefense.in\/wp-content\/uploads\/2025\/07\/image-61.png",2048,1330,false],"mailpoet_newsletter_max":["https:\/\/alphadefense.in\/wp-content\/uploads\/2025\/07\/image-61.png",1320,857,false],"woocommerce_thumbnail":["https:\/\/alphadefense.in\/wp-content\/uploads\/2025\/07\/image-61-300x300.png",300,300,true],"woocommerce_single":["https:\/\/alphadefense.in\/wp-content\/uploads\/2025\/07\/image-61.png",600,390,false],"woocommerce_gallery_thumbnail":["https:\/\/alphadefense.in\/wp-content\/uploads\/2025\/07\/image-61-100x100.png",100,100,true]},"uagb_author_info":{"display_name":"alphadefense.in","author_link":"https:\/\/alphadefense.in\/index.php\/author\/alphadefense-in\/"},"uagb_comment_info":22,"uagb_excerpt":"An F35 crash occurred near NAS Lemoore in California. The jet caught fire after impact. California Highway Patrol (CHP) confirmed…","jetpack-related-posts":[],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/alphadefense.in\/index.php\/wp-json\/wp\/v2\/posts\/1445","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/alphadefense.in\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/alphadefense.in\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/alphadefense.in\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/alphadefense.in\/index.php\/wp-json\/wp\/v2\/comments?post=1445"}],"version-history":[{"count":1,"href":"https:\/\/alphadefense.in\/index.php\/wp-json\/wp\/v2\/posts\/1445\/revisions"}],"predecessor-version":[{"id":1450,"href":"https:\/\/alphadefense.in\/index.php\/wp-json\/wp\/v2\/posts\/1445\/revisions\/1450"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/alphadefense.in\/index.php\/wp-json\/wp\/v2\/media\/1448"}],"wp:attachment":[{"href":"https:\/\/alphadefense.in\/index.php\/wp-json\/wp\/v2\/media?parent=1445"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/alphadefense.in\/index.php\/wp-json\/wp\/v2\/categories?post=1445"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/alphadefense.in\/index.php\/wp-json\/wp\/v2\/tags?post=1445"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
An F\u201135A (tail number 10\u20115015) caught fire during the takeoff roll from Eglin AFB. Investigators traced the cause to a fractured third\u2011stage rotor arm of the F135 engine\u2019s fan module. That part liberated under excessive rubbing, cutting through the fan case, engine bay, fuel tank, fuel lines, and hydraulic lines. Leaking fuel and hydraulic fluid ignited, burning about the rear two\u2011thirds of the airframe. The pilot aborted takeoff safely and exited without injury. The damage exceeded USD\u202f50\u202fmillion, and the entire F\u201135 fleet grounded shortly afterward. Pratt & Whitney implemented interim \u201crub\u2011in\u201d procedures and redesigns to fix the Rub\u2011failure.<\/p>\n\n\n\n
Failure type:<\/strong> Mechanical failure \u2013 engine rotor damage leading to catastrophic fire.<\/em><\/p>\n\n\n\n A USMC F\u201135B bearing tail number 168719<\/strong> crashed during a routine training flight near Marine Corps Air Station Beaufort. Military confirmed the pilot ejected safely without injury. The engine suffered a catastrophic flameout when a defective fuel tube ruptured mid-flight<\/strong>, cutting off fuel supply and causing immediate loss of power. Investigators traced the rupture to a defective batch supplied during engine production. The incident triggered a fleet-wide inspection of fuel tubes across all F\u201135s. At least 117 jets<\/strong> received replacement parts before further flight. Maintenance crews grounded numerous aircraft temporarily for safety assurance. This was the first-ever loss<\/strong> of an F\u201135 aircraft.<\/p>\n\n\n\n Failure type:<\/strong> Mechanical failure \u2013 fuel tube rupture causing engine shutdown.<\/em><\/p>\n\n\n\n A JASDF F\u201135A, tail number 79\u20118705<\/strong> (callsign AX\u20116), took off from Misawa Air Base for aerial training with three other F\u201135s. The pilot, Maj. Akinori Hosomi<\/strong>, flew combat-simulation drills reliably until 7:26 p.m. He reported two simulated kills and acknowledged a descent order. Seconds later the aircraft disappeared from radar, plummeting into the Pacific at over 1,100\u202fkm\/h. Rescuers recovered scattered debris and, in June 2019, recovered pilot remains about 1500\u202fm below the sub surface.<\/p>\n\n\n\n Investigators ruled out any technical or mechanical issues. They found no signs of engine or system malfunction<\/strong>. Instead, they attributed the crash to spatial disorientation<\/strong>. Hosomi likely experienced vertigo and lost equilibrium. He did not send a distress call, attempt recovery, or eject. The danger overwhelmed instrument readings, and he followed a fatal descent without awareness. However, many believe this needs more study.<\/p>\n\n\n\n Following the crash, JASDF grounded all twelve F\u201135As. It mandated retraining focused on spatial orientation and gravity-induced loss of consciousness (G\u2011LOC). Enhanced protocols now accompany each F\u201135 pilot\u2019s training.<\/p>\n\n\n\n Failure type:<\/strong> Spatial disorientation leading to loss of situational awareness and fatal descent.<\/em><\/p>\n\n\n\n A US Air Force F\u201135A, tail number 12\u2011005053<\/strong>, crashed on landing at runway\u202f30 around 9:26\u202fPM. The pilot ejected safely but sustained non-life-threatening injuries. The jet rolled, caught fire, and was destroyed.<\/p>\n\n\n\n Investigators determined the aircraft touched down at about 202 knots<\/strong>, approximately 50 knots above target<\/strong> and at a 5.2\u00b0 angle of attack<\/strong>, much shallower than the recommended ~13\u00b0. The aircraft then bounced violently, entering pitch oscillation<\/strong>. The pilot applied aft stick and afterburner to abort, but conflicting control inputs froze the tail surfaces in a nose-down position. Consequently, he could not arrest the oscillations and ejected after about five seconds on the runway.<\/p>\n\n\n\n Several contributing factors aggravated the mishap: the pilot landed with Speed Hold engaged<\/strong>, his helmet-mounted display misaligned<\/strong>, he suffered cognitive fatigue<\/strong>, and he lacked sufficient knowledge of the jet\u2019s flight-control logic<\/strong>.<\/p>\n\n\n\n Failure type:<\/strong> Oxygen system fault + HUD display error + pilot error.<\/em><\/p>\n\n\n\n An F\u201135B, tail number 169294 (callsign VOLT\u201193), collided mid-air with KC\u2011130J BuNo\u202f166765 (callsign RAIDER\u202f50) during aerial refueling near El Centro. Both aircraft belonged to the U.S. Marine Corps and participated in the Weapons and Tactics Instructor (WTI) exercise out of MCAS Yuma, Arizona.<\/p>\n\n\n\n At approximately 1600 local, the F\u201135B clipped the tanker\u2019s starboard wing and fuel pod. The F\u201135B lost lift and crashed into the desert near the Salton Sea. The pilot ejected successfully and sustained minor injuries.<\/p>\n\n\n\n The KC\u2011130J suffered heavy damage to both right-side engines and propellers. The crew declared emergency and made a belly landing in a cauliflower field near Thermal Airport. All eight crew members walked away safe.<\/p>\n\n\n\n Investigators linked the crash to wake turbulence and flight-control anomalies during refueling. Sensor transitions produced erratic airdata inputs. The F\u201135B lost stable control before contact.<\/p>\n\n\n\n A US Marine Corps F\u201135B (tail number unknown<\/strong>, assigned to VMX\u20111) flew a nighttime close air support mission over the Yuma Range Complex. During gunnery practice, a 25\u202fmm PGU\u201132\/U SAPHEI\u2011T round prematurely exploded as it exited the externally mounted GAU\u201122 gun pod<\/strong>. The resulting blast shredded fuselage panels and left fragmentation damage across the belly and lower aft section. The pilot landed the jet safely back to base and reported no injuries. Navy officials initially classified the event as a Class A mishap\u2014later downgraded to Class C, indicating damage between $60,000 and $600,000.<\/p>\n\n\n\n Failure type:<\/strong> Mechanical failure \u2013 premature ordnance detonation.<\/em><\/p>\n\n\n\n An RAF F\u201135B (tail number ZM152, construction number BK\u201118)<\/strong> crashed into the Mediterranean Sea during takeoff from HMS\u202fQueen\u202fElizabeth. The pilot ejected safely and was recovered onto the carrier deck.<\/p>\n\n\n\n Engine thrust fell significantly below normal\u2014only about 55% of required power\u2014because a plastic protective engine intake blank<\/strong> remained lodged in the intake during launch. That blockage choked airflow, preventing proper engine performance. The jet failed to gain lift and plunged off the ski-jump ramp into the sea.<\/p>\n\n\n\n Investigators found that technicians had left this \u201cRed Gear\u201d intake cover<\/strong> in place. A systemic failure in removal procedures contributed. The panel linked the mishap to human and organizational error<\/strong> rather than engineering flaws.<\/p>\n\n\n\n The aircraft was assigned to 617 Squadron, RAF<\/strong>, deployed aboard Queen Elizabeth during Carrier Strike Group\u202f21 operations. After impact, the intake blank floated to the surface and was recovered. All onboard \u201csecurity sensitive equipment\u201d was later salvaged.<\/p>\n\n\n\n Failure type:<\/strong> Engine intake blockage \u2013 foreign object.<\/em><\/p>\n\n\n\n A South Korean Air Force F\u201135A \u2014 tail number 20\u2011017 \u2014 made an emergency belly landing at Seosan Air Base after avionic systems failed. The pilot landed safely and walked away without injury.<\/p>\n\n\n\n The aircraft experienced system-wide electronic anomalies. All flight systems shut down except for engine thrust and manual flight controls. The landing gear failed to deploy due to avionics malfunction. The pilot opted for a gear-up touchdown, guided foam covered the runway, minimizing damage.<\/p>\n\n\n\n Investigators attributed the incident to sensor system and hydraulic failures, which led to the gear malfunction. Only core controls and propulsion remained functional. The fleet was grounded immediately pending full investigation.<\/p>\n\n\n\n Failure type:<\/strong> Hydraulic failure + sensor system fault.<\/em><\/p>\n\n\n\n A U.S. Navy F\u201135C with tail number 169304<\/strong>, assigned to Strike Fighter Squadron 147 \u201cArgonauts\u201d<\/strong>, attempted a skilled “expedited recovery” (Sierra Hotel break)<\/strong> downwind approach over the USS\u202fCarl\u202fVinson. The pilot had more than 370 flight hours in the F\u201135C. As he executed the tight maneuver, multiple critical steps failed. He did not activate two electronic landing assist systems\u2014Approach Power Compensation (APC)<\/strong> and Delta Flight Path (DFP)<\/strong>\u2014intending to maintain proper angle of attack and throttle control. As a result, the aircraft approached at low power, high speed, and excessive descent rate.<\/p>\n\n\n\n At around 16:30 local time, due to low thrust and sensor issues, the jet struck the aft ramp with its belly. The main landing gear collapsed. The plane caught two arresting wires\u2014a leftover rail snagged the wire and caused the aircraft to spin across the deck before falling into the sea. The pilot safely ejected, but six crew members<\/strong> aboard the flight deck suffered injuries. A nearby EA\u201118G Growler sustained over $2.5 million in damage, and deck repairs cost approximately $120,000. The jet itself was a total loss, valued at over $115 million.<\/p>\n\n\n\n Navy investigators ultimately classified the incident as pilot error<\/strong>. They cited task saturation<\/strong>, incomplete checklist execution, and mismanaged automation as root causes. The pilot\u2019s unfamiliarity with the maneuver compounded the failure to activate the landing aids in the compressed timeline.<\/p>\n\n\n\n Failure type:<\/strong> Flight-control logic error during ramp strike amplified by missed automation activation under task saturation.<\/em><\/p>\n\n\n\n On October 19, 2022, an F-35A Lightning II (tail number 15-5197) belonging to the 421st Fighter Squadron, 388th Fighter Wing, crashed shortly after making the final turn toward runway 14 at Hill Air Force Base, Utah, around 6:08 p.m. local time. The aircraft had just returned from a routine training sortie as part of a four-ship formation. On final approach, the wake turbulence from a preceding jet induced mild airflow disturbances, which fed erroneous data into the aircraft\u2019s air data application (ADA). The ADA rapidly switched between its primary and backup sources, resulting in corrupted altitude and airspeed information. Consequently, the flight-control system responded incorrectly, and manual controls no longer aligned reliably with the pilot’s input. In an attempt to recover, the pilot applied full afterburner, but with insufficient altitude, low airspeed, and increasing sideslip, recovery became impossible. The pilot ejected approximately three seconds after losing control and sustained only minor injuries. The aircraft crashed north of the runway, sparking a brush fire that scorched 8\u201310 acres. The F-35A was a total loss, valued at approximately USD 166 million. The root cause was identified as an air data system failure that fed corrupted sensor information to the flight-control logic, leading to a loss of control.<\/p>\n\n\n\n Failure type:<\/strong> Air data system failure \u2013 corrupted altitude readings.<\/em><\/p>\n\n\n\n An F\u201135B tail number 170061<\/strong> crashed during vertical landing trials at NAS JRB Fort Worth. The jet descended in STOVL mode, bounced during hover descent, then flipped nose\u2011down and rolled over. The pilot ejected safely and escaped uninjured. The aircraft had not yet transferred from manufacturer to U.S. military. Video footage shows the jet tipping forward after a bounce. Engineers later determined a software glitch in the STOVL flight\u2011control logic misinterpreted sensor inputs. The jet lost balance mid\u2011transition from hover to landing and overturned. The pilot ejected promptly as automated control failed. Failure type:<\/strong> Flight\u2011control logic glitch during STOVL operation.<\/em><\/p>\n\n\n\n Failure type:<\/strong> Flight-control logic glitch during STOVL operation.<\/em><\/p>\n\n\n\n F\u201135B tail number 169591 from VMFAT\u2011501 flew through heavy rain near Joint Base Charleston. The pilot ejected safely over a residential backyard in North Charleston. After ejection, the jet continued flying on autopilot for 64 nautical miles. Eventually, it crashed in rural Williamsburg County. An electrical event disabled the transponder, radios, and navigation systems midflight. Both the helmet-mounted and panoramic cockpit displays failed multiple times during the sortie. <\/p>\n\n\n\n Investigators later found the pilot misjudged the jet’s behavior and ejected while systems were stabilizing. They traced the crash to a software fault, likely a cascading failure in the navigation system. Due to stealth features and no working transponder, the aircraft remained missing for over 24 hours. Search efforts faced serious delays as a result.<\/p>\n\n\n\n Failure type:<\/strong> Software fault \u2013 possible cascading failure in navigation system<\/em>.<\/p>\n\n\n\n Soon after takeoff from Kirtland Air Force Base, developmental F\u201135B tail number 170067 suffered a critical malfunction. The jet had just refueled during its flight from Fort Worth, Texas, to Edwards AFB, California. At low altitude, the pilot ejected safely, though he sustained serious injuries and later stabilized in the hospital. <\/p>\n\n\n\n The jet slammed into a scrub desert hillside near Albuquerque International Sunport and immediately burst into flames. Firefighters responded quickly and extinguished the blaze before it could spread. The aircraft, fitted with Technology Refresh 2 software, was completely destroyed in the crash. Investigators are still analyzing telemetry data to find the root cause. However, early indications suggest a mechanical issue possibly linked to the engine\u2019s fuel system.<\/p>\n\n\n\n Failure type:<\/strong> Mechanical failure \u2013 engine or fuel-related malfunction.<\/em><\/p>\n\n\n\n On January 28, 2025, at 12:49 p.m. local time, an F\u201135A began malfunctioning during the landing phase at Eielson Air Force Base. The pilot quickly initiated emergency procedures and successfully ejected, avoiding injury. As the jet lost control at low altitude, it crashed within the base perimeter and triggered a large fire. The impact completely destroyed the aircraft. <\/p>\n\n\n\n Although the pilot required brief medical observation, he suffered no serious harm and was released shortly after. While the official cause remains undisclosed, investigators strongly suspect a failure in the flight-control or air-data systems. The aircraft, assigned to the 354th Fighter Wing, bore the \u201cAK\u201d tail code and was likely flown by the 355th Fighter Squadron. Overall, this incident underscores how even a minor system glitch can lead to a catastrophic failure in modern stealth fighters.<\/p>\n\n\n\n Failure type:<\/strong> Undisclosed \u2013 suspected flight control or air data glitch.<\/em><\/p>\n\n\n\n Apart from these the latest one became memefest for many tracking aviation and defence. In mid-June 2025, a Royal Navy F\u201135B diverted to Thiruvananthapuram International Airport in Kerala due to technical glitch and low fuel amid bad weather. The jet landed safely on June 14 after attempts to return to HMS\u202fPrince of Wales failed. Later it was learnt tha aircraft had hydraulics and APU issues. A UK engineering team arrived, worked through monsoon rain, and moved the jet into an airport hangar. Meanwhile, Kerala\u2019s tourism department embraced the situation with humorous memes, portraying the F\u201135B as a delighted tourist giving the state five stars. Internet users joked it wanted a vacation or lunch of filter coffee. The jet stayed stranded for 37 days under armed guard, attracting global social media attention. It finally departed on July 22, reunited with its Carrier Strike Group en route to Australia. The event underscored how unexpected technical faults can transform a sophisticated stealth fighter into a worldwide meme sensation.<\/p>\n\n\n\n The F\u201135 is one of the most advanced but also maintenance-intensive aircraft ever fielded. With its tightly integrated stealth features, complex software architecture, and high part-count, it regularly faces technical issues and availability challenges. These problems are not rare, they’re systemic, especially for countries that neither assemble the aircraft nor possess sovereign maintenance capabilities. Operators without full industrial access often face delays in fault diagnosis, spares, and repairs. As the Thiruvananthapuram incident illustrated, even a non-catastrophic glitch can become a global embarrassment when local support infrastructure is lacking.<\/p>\n\n\n\n References<\/p>\n\n\n\n An F35 crash occurred near NAS Lemoore in California. The jet caught fire after impact. California Highway Patrol (CHP) confirmed…<\/p>\n","protected":false},"author":1,"featured_media":1448,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_uag_custom_page_level_css":"","_uf_show_specific_survey":0,"_uf_disable_surveys":false,"fifu_image_url":"","fifu_image_alt":"","_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[6,507,544],"class_list":["post-1445","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","tag-alpha-defense","tag-f35","tag-f35-crash"],"yoast_head":"\n2. September 28, 2018 \u2013 Beaufort, South Carolina, USA<\/strong><\/h3>\n\n\n\n
3. April 9, 2019 \u2013 Off Aomori, Japan<\/strong><\/h3>\n\n\n\n
4. May 19, 2020 \u2013 Eglin AFB, Florida, USA<\/strong><\/h3>\n\n\n\n
5. September 29, 2020 \u2013 California, USA<\/strong><\/h3>\n\n\n\n
6. March 12, 2021 \u2013 Yuma, Arizona, USA<\/strong><\/h3>\n\n\n\n
7. November 17, 2021 \u2013 HMS Queen Elizabeth, Mediterranean<\/strong><\/h3>\n\n\n\n
8. January 4, 2022 \u2013 South Korea<\/strong><\/h3>\n\n\n\n
9. January 24, 2022 \u2013 USS Carl Vinson, South China Sea<\/strong><\/h3>\n\n\n\n
10. October 19, 2022 \u2013 Hill AFB, Utah, USA<\/strong><\/h3>\n\n\n\n
11. December 15, 2022 \u2013 Fort Worth, Texas, USA<\/strong><\/h3>\n\n\n\n
12. September 17, 2023 \u2013 North Charleston, South Carolina, USA<\/strong><\/h3>\n\n\n\n
13. May 28, 2024 \u2013 Albuquerque, New Mexico, USA<\/strong><\/h3>\n\n\n\n
14. January 28, 2025 \u2013 Eielson AFB, Alaska, USA<\/strong><\/h3>\n\n\n\n
\n