An FA-18E Super Hornet launches from the deck of the USS Eisenhower in the Red Sea. Image Credit: DoD
In a startling error made on December 22, 2024, two U.S. Navy pilots narrowly escaped disaster when their F/A-18 Super Hornet was inadvertently shot down by the guided-missile cruiser USS Gettysburg over the Red Sea. Both aviators ejected safely; one sustained minor injuries.
What Happened?
In the early morning hours of December 22, 2024, a U.S. Navy F/A-18F Super Hornet from the “Red Rippers” of Strike Fighter Squadron 11 (VFA-11) was mistakenly shot down by friendly fire over the Red Sea. The two-seat fighter jet had just launched from the USS Harry S. Truman aircraft carrier when it was misidentified as a threat by the guided-missile cruiser USS Gettysburg.
Serving as the air defense commander for the carrier strike group, the Gettysburg is responsible for detecting and neutralizing threats to the carrier and its escorts. At approximately 3 AM local time, the Gettysburg fired on the aircraft, successfully hitting it.
While the exact weapon used has not been disclosed, the cruiser is equipped with advanced missile systems designed to counter a variety of threats. Both pilots aboard the F/A-18 ejected safely and were quickly rescued, though one sustained minor injuries.
The incident occurred amid ongoing U.S. military operations in the region, including airstrikes targeting Yemen‘s Houthi rebels. However, this particular aircraft was not involved in those missions. U.S. Central Command (CENTCOM) confirmed that the mishap was not the result of hostile action and has launched a full investigation.
The event underscores the complexities and dangers of conducting military operations in the volatile Red Sea region, where multiple threats and allied forces often operate in close proximity.
Operational Context
The friendly fire incident involving a U.S. Navy F/A-18 Super Hornet over the Red Sea unfolded within a highly complex operational context. The USS Harry S. Truman Carrier Strike Group entered the U.S. Central Command area of responsibility on December 14, 2024, with the mission of ensuring regional stability and security. Operating in the Red Sea, the strike group faced ongoing tensions and attacks from Houthi rebels, who had targeted approximately 100 merchant vessels since November 2023, sinking two ships and damaging others.
In response, the U.S. and its allies launched Operation Prosperity Guardian in December to safeguard vital shipping routes. Just hours before the incident, on December 21, U.S. forces conducted airstrikes against Houthi targets in Yemen, including F/A-18s launched from the Harry S. Truman. Around the same time, U.S. forces intercepted multiple Houthi drones and an anti-ship cruise missile over the Red Sea, further heightening the state of alert.
In a startling error made on December 22, 2024, two U.S. Navy pilots narrowly escaped disaster when their F/A-18 Super Hornet was inadvertently shot down by the guided-missile cruiser USS Gettysburg over the Red Sea. Both aviators ejected safely; one sustained minor injuries.
What Happened?
In the early morning hours of December 22, 2024, a U.S. Navy F/A-18F Super Hornet from the “Red Rippers” of Strike Fighter Squadron 11 (VFA-11) was mistakenly shot down by friendly fire over the Red Sea. The two-seat fighter jet had just launched from the USS Harry S. Truman aircraft carrier when it was misidentified as a threat by the guided-missile cruiser USS Gettysburg.
Serving as the air defense commander for the carrier strike group, the Gettysburg is responsible for detecting and neutralizing threats to the carrier and its escorts. At approximately 3 AM local time, the Gettysburg fired on the aircraft, successfully hitting it.
While the exact weapon used has not been disclosed, the cruiser is equipped with advanced missile systems designed to counter a variety of threats. Both pilots aboard the F/A-18 ejected safely and were quickly rescued, though one sustained minor injuries.
The incident occurred amid ongoing U.S. military operations in the region, including airstrikes targeting Yemen‘s Houthi rebels. However, this particular aircraft was not involved in those missions. U.S. Central Command (CENTCOM) confirmed that the mishap was not the result of hostile action and has launched a full investigation.
The event underscores the complexities and dangers of conducting military operations in the volatile Red Sea region, where multiple threats and allied forces often operate in close proximity.
Operational Context
The friendly fire incident involving a U.S. Navy F/A-18 Super Hornet over the Red Sea unfolded within a highly complex operational context. The USS Harry S. Truman Carrier Strike Group entered the U.S. Central Command area of responsibility on December 14, 2024, with the mission of ensuring regional stability and security. Operating in the Red Sea, the strike group faced ongoing tensions and attacks from Houthi rebels, who had targeted approximately 100 merchant vessels since November 2023, sinking two ships and damaging others.
In response, the U.S. and its allies launched Operation Prosperity Guardian in December to safeguard vital shipping routes. Just hours before the incident, on December 21, U.S. forces conducted airstrikes against Houthi targets in Yemen, including F/A-18s launched from the Harry S. Truman. Around the same time, U.S. forces intercepted multiple Houthi drones and an anti-ship cruise missile over the Red Sea, further heightening the state of alert.
In the early morning hours of December 22, as tensions remained high, the guided-missile cruiser USS Gettysburg, part of the same strike group, mistakenly fired upon the F/A-18 after it took off from the Harry S. Truman.
The incident occurred amid an operational environment filled with overlapping threats and fast-paced decision-making, underscoring the challenges of maintaining precision and coordination under such conditions. This context sheds light on the heightened alert status and the complexities that contributed to the tragic friendly fire event.
Investigating the Mishap
The U.S. Central Command (CENTCOM) has announced a full investigation into the recent friendly fire incident over the Red Sea. The investigation will focus on several critical areas, including the circumstances that led to the misidentification of the aircraft, the effectiveness of radar and communication systems within the carrier strike group, and the operational procedures in place at the time. Investigators will also examine the role of the heightened state of alert caused by recent Houthi attacks, which had prompted U.S. forces to intercept multiple incoming drones and anti-ship cruise missiles shortly before the incident.
The “fog of war” conditions surrounding the incident are also expected to be a key focus, as the rapid pace of operations and overlapping threats may have contributed to the tragic mistake. At this time, CENTCOM has not released any preliminary findings or specific details beyond the initial statement. The results of this investigation will be critical in identifying potential failures and ensuring that future operations within carrier strike groups are better coordinated to prevent similar incidents.
Historical Perspective on Friendly Fire
Friendly fire has been a tragic aspect of warfare throughout history, with the most recent example noted above reminding us of its persistent risks. During World War II, friendly fire accounted for an estimated 2% to 20% of all casualties in battle. Similarly, during the Gulf War, 35 Americans and nine British troops were killed by friendly fire, representing nearly one-quarter of the total U.S. deaths.
Even in the American Civil War, notable incidents occurred, such as the fatal wounding of Confederate General “Stonewall” Jackson by his own troops. In naval warfare, World War II saw 53 instances where U.S. vessels were damaged or sunk by friendly fire, with destroyers being the most frequently affected ships. Needless to say, this doesn’t even begin to scratch the surface regarding all of the friendly fire instances in US military history. War is an inherently dangerous business.
Friendly fire incidents often arise from factors such as poor visibility, chaotic battle conditions, misidentification of targets, or technological failures in identification systems. While modern technology and training aim to reduce these occurrences, the rate of friendly fire has remained relatively stable over the past 200 years.
These incidents not only lead to comprehensive investigations to prevent future mistakes but also take a psychological toll on troops and affect morale. The F/A-18 incident serves as a sobering reminder of the complexities of modern warfare and the importance of continuous efforts to minimize friendly fire in military operations.
Summation
As the investigation into this friendly fire incident continues, the U.S. Navy will undoubtedly scrutinize existing procedures to identify and rectify any shortcomings. The goal remains to ensure the safety of military personnel while effectively addressing threats in the region. The resilience and training of the downed pilots, coupled with prompt recovery efforts, prevented a potential tragedy, serving as proof positive of the professionalism of U.S. naval forces.
As someone who’s seen what happens when the truth is distorted, I know how unfair it feels when those who’ve sacrificed the most lose their voice. At SOFREP, our veteran journalists, who once fought for freedom, now fight to bring you unfiltered, real-world intel. But without your support, we risk losing this vital source of truth. By subscribing, you’re not just leveling the playing field—you’re standing with those who’ve already given so much, ensuring they continue to serve by delivering stories that matter. Every subscription means we can hire more veterans and keep their hard-earned knowledge in the fight. Don’t let their voices be silenced. Please consider subscribing now.
One team, one fight,
Brandon Webb former Navy SEAL, Bestselling Author and Editor-in-Chief
COMMENTS
There are
on this article.
You must become a subscriber or login to view or post comments on this article.