In mid-August, challenges continued to mount for the brand-new F-35 aircraft from Lockheed Martin . After the plane was marooned for a month in India, Spain reversed an order (with other countries following suit), and a second breakdown occurred in Japan, it seemed that the series of mishaps was at its peak. However, a recent report emerged highlighting the complexities of the aircraft and its sophisticated software.
An Accident and Its Causes On January 28, 2025, an F-35A from the United States Air Force , assigned to the 354th Combat Wing at Eielson Air Force Base in Alaska, crashed during a training mission involving a group of four planes.
The official report released by Pacific Air Forces revealed that the crash resulted primarily from freezing hydraulic fluid contaminated with water in the landing gear shock absorbers. This contamination hindered the complete extension of the struts and led the weight sensors on the wheels to erroneously interpret that the plane was on the ground while it was still airborne.
Kamikaze Mode This false signal activated the “ on-ground ” control mode during flight, rendering the aircraft uncontrollable. Fortunately, the pilot managed to eject and survived with only minor injuries, but the plane, valued at $196.5 million , was entirely lost.
Emergency in Flight Immediately upon discovering the issue, the front landing gear was misaligned at 17 degrees and could not retract. After consulting with engineers from Lockheed Martin and a flight supervisor, the pilot attempted to reactivate the landing gear using two “ touch-and-go ” maneuvers. However, ice further blocked the primary landing gear, and during the second attempt, the sensors indicated that the aircraft had landed.
This situation led to an automatic switch to Operation Mode on Land, drastically reducing the control capabilities of the aircraft. The pilot, identified in the “MP” report, managed to eject just before the plane went into a stall and fell uncontrollably. The aircraft ascended more than 1,000 meters after the ejection, only to plummet vertically, a sequence captured in a video that quickly went viral.
Technical and Maintenance Factors The investigation concluded that ice accumulation on the struts, in combination with the misalignment of the front landing gear’s blocking hook, damaged metal components and inhibited proper system coupling. Additionally, the Weight on Wheels (WoW) sensors, critical to the F-35 Flight Control Logic (CLAWs) , displayed vulnerabilities under extreme cold conditions, a concern Lockheed Martin had previously warned about in maintenance bulletins. In essence, the ice “fooled” the software.
The report emphasized that hydraulic fluid contamination resulted from poor management of hazardous materials and lapses in service protocols, which were considered contributing factors in the accident.
Implications and Lessons This incident underscored the complexity inherent in the advanced automation of the F-35, where a sensor failure can trigger a *domino effect* in the control software. Although another F-35A successfully landed nine days later despite facing a similar issue, the research board stated that given the available information, the safest choice would have been an immediate landing order or a controlled ejection rather than risking another maneuver attempt.
While the report did not issue formal recommendations for policy changes, it stressed the necessity for strict compliance with maintenance protocols, oversight of hydraulic fluid usage, and preparation for operations in Arctic climates.
Strategic Repercussions Ultimately, this accident, despite no fatalities, highlights the operational challenges associated with fifth-generation fighters in extreme environments like Alaska, where temperatures can plummet to –17 ºC , exacerbating technical vulnerabilities.
Moreover, it serves as a cautionary tale for future operators in cold climates, such as Canada and Finland , which must carefully evaluate the reliability of sensors and resilience of control systems under severe conditions. Beyond technical aspects, this incident illustrates how the complexity of the F-35, dependent on sophisticated algorithms and automation, can become a significant risk in unforeseen emergencies, prompting a re-evaluation of the balance between human intervention and software in next-generation military aircraft.