F-35B Fighter CRASHES Off HMS Queen Elizabeth Into the Sea, Then THIS Happened…
The morning of November 17, 2021, started like any other aboard HMS Queen Elizabeth as she cut through the Eastern Mediterranean. The Royal Navy’s flagship was operating at the heart of Carrier Strike Group 21, projecting British power across international waters. But within minutes, one of the most expensive military accidents in recent history would unfold, involving a £100 million F-35B Lightning II stealth fighter and a mistake so simple it defied belief.
What happened next would trigger one of the most urgent underwater recovery missions of the modern era, expose critical flaws in military procedures, and force a complete rethinking of how the world’s most advanced fighter jets are operated. The pilot’s miraculous survival was just the beginning of this extraordinary story.
The Day Disaster Struck
Lieutenant ‘Hux’, as he was known to his squadron mates, prepared for what should have been a routine takeoff from HMS Queen Elizabeth‘s ski-jump ramp. The F-35B Lightning II he was about to pilot – tail number ZM152 – represented the pinnacle of modern military aviation technology. This wasn’t just any fighter jet; it was a fifth-generation stealth aircraft packed with classified systems that multiple nations would kill to examine.
As ‘Hux’ throttled up for takeoff, everything initially seemed normal. The Rolls-Royce LiftSystem roared to life, and the aircraft began its roll down the 280-meter flight deck. But then something went catastrophically wrong. Instead of the expected surge of power that would launch him skyward, the engine delivered only 55% of its required thrust.
“I knew immediately something was wrong,” ‘Hux’ later recounted. “The aircraft wasn’t accelerating as it should have been.” With the ski-jump ramp approaching rapidly and insufficient power to achieve flight, he faced every naval aviator’s nightmare – rolling off the edge of an aircraft carrier.
In a split-second decision that saved his life, ‘Hux’ triggered his ejection seat. The advanced Martin-Baker Mk16 ejection system fired him clear of the doomed aircraft at lightning speed. Remarkably, instead of plummeting into the Mediterranean, he landed back on HMS Queen Elizabeth’s flight deck – a stroke of luck that prevented him from being pulled under the 65,000-ton warship. He suffered only minor injuries: cuts to his neck and some bruising.
Meanwhile, his F-35B rolled off the ski ramp, floated briefly on the surface like a massive metallic swan, and then disappeared beneath the waves into waters over 1,000 meters deep.
The Shocking Truth Behind the Crash
Initial reports suggested “foreign object debris” or a “rain cover” might be to blame, but the official Service Inquiry would reveal a truth both simpler and more concerning than anyone anticipated. The F-35B Fighter CRASHES Off HMS Queen Elizabeth Into the Sea had been caused by something as mundane as a protective cover – but the implications were anything but mundane.
The culprit was what military engineers call “red gear” – specifically, an engine intake blank designed to prevent debris from entering the jet’s intake ducts during maintenance or adverse weather conditions. One of these protective covers had been left in the port intake duct, acting like a cork in a wine bottle and choking the engine’s air supply.
A Web of System Failures
The investigation uncovered a cascade of failures that went far beyond a single forgotten cover. The red gear storage and tracking system was fundamentally flawed – engineers had no reliable method to log, track, or immediately flag missing protective equipment. There was no systematic check to ensure all covers were removed before flight operations.
Even more concerning, the red gear itself was poorly designed. The crucial “Remove Before Flight” warnings frequently peeled off, and the pop-pins meant to secure the covers often weren’t used properly. Some covers had even blown off the flight deck during previous operations, yet no comprehensive review had been conducted.
The situation was further complicated by conflicting orders. A Government Special Access Programme Security Officer had directed that red gear be fitted for the ship’s passage through the Suez Canal and port visit to Oman, but provided no clear guidance about when to remove them once at sea.
Perhaps most alarming, this wasn’t the first time red gear had caused F-35 engine problems. US operators had recorded four previous instances of intake covers being sucked into F-35 engines, though none had resulted in aircraft loss. The warning signs had been there, but the lessons hadn’t been learned.
The High-Stakes Race Against Time
The moment F-35B ZM152 disappeared beneath the Mediterranean waves, a different kind of crisis began. This wasn’t just about the loss of a £100 million aircraft – it was about preventing one of America and Britain’s most closely guarded military secrets from falling into enemy hands.
The F-35B contained cutting-edge stealth technology, advanced radar systems, electronic warfare capabilities, and classified software that took decades to develop. If recovered by hostile nations like Russia or China, these technologies could be reverse-engineered, potentially compromising the entire F-35 program and revealing NATO’s tactical advantages.
Intelligence agencies knew that Russian and Chinese naval vessels routinely monitor NATO operations in international waters. Time was critically short – every hour the wreckage sat on the seabed increased the risk of it being located by adversaries with their own deep-sea recovery capabilities.
The Complex Recovery Operation
The recovery mission required unprecedented coordination between British, American, and Italian forces. Specialized salvage vessels equipped with remotely operated vehicles (ROVs) capable of operating at extreme depths were rushed to the crash site. Sonar imaging systems swept the Mediterranean floor, eventually locating the distinctive silhouette of the stealth fighter resting on the seabed.
The technical challenges were immense. Operating over 1,000 meters underwater, recovery teams had to carefully extract the aircraft without damaging its sensitive components or compromising the classified systems they were trying to protect. The operation required precision that bordered on the surgical – one wrong move could scatter debris across the ocean floor or damage the very technology they were racing to secure.
By early December 2021, after weeks of round-the-clock operations, the F-35B was successfully brought to the surface. The recovery prevented a potential intelligence disaster and demonstrated the extraordinary lengths to which allied nations would go to protect their technological advantages.
Lessons Learned and Lasting Changes
The F-35B crash forced an immediate and comprehensive review of carrier strike operations. The incident served as what many described as a “reality check” for the UK’s carrier strike capability, highlighting vulnerabilities that went beyond simple procedural failures.
Immediate Reforms
New protocols for red gear management were implemented immediately across the fleet. Digital tracking systems replaced the previous ad-hoc logging methods, ensuring that every protective cover could be accounted for in real-time. Pre-flight inspection procedures were overhauled to include mandatory verification that all protective equipment had been removed.
Design improvements were fast-tracked for future red gear, including better attachment systems, more durable warning labels, and bright colors that would make forgotten covers immediately obvious to ground crews.
Broader Implications
The crash highlighted the complexity of operating advanced military systems in real-world conditions. While the F-35B represented the cutting edge of aviation technology, it remained vulnerable to the most basic human errors. The incident emphasized the critical importance of robust procedures and systematic thinking in military operations.
The financial cost extended far beyond the lost aircraft. Recovery operations, investigation expenses, and the implementation of new safety protocols added millions to the final bill. But perhaps more importantly, the crash temporarily reduced the UK’s carrier strike capability at a time when global tensions were rising.
A Catalyst for Improvement
Despite the dramatic circumstances, the crash ultimately strengthened British carrier strike operations. The incident forced honest assessments of existing procedures and drove innovations that made future operations safer and more reliable. Every lesson learned from F-35B ZM152’s final flight was immediately applied to prevent similar accidents.
The pilot’s survival story also became a testament to the effectiveness of modern ejection systems and the importance of split-second decision-making under pressure. ‘Hux’s’ experience in the ejection seat and his miraculous landing on the carrier deck provided valuable data for improving pilot safety systems.
The recovery operation itself became a model for international cooperation under pressure. The successful retrieval of the stealth fighter demonstrated that allied nations could rapidly coordinate complex operations to protect shared technological advantages.
Today, HMS Queen Elizabeth continues to operate F-35B Lightning II aircraft around the world, but with enhanced safety protocols born from the hard lessons of November 17, 2021. The crash of F-35B ZM152 may have been a costly mistake, but it ultimately made carrier aviation safer for everyone.
The story of how a simple protective cover nearly compromised national security – and the extraordinary efforts to prevent that outcome – serves as a reminder that in the world of advanced military technology, the smallest details can have the largest consequences. Sometimes, the most expensive lessons are also the most valuable ones.