PilotPhotog Podcast

Friendly Fire Crisis: Lessons from the Navy's Red Sea Incident

PilotPhotog Season 4

Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.

0:00 | 5:03

Enjoyed this episode or the podcast in general? Send me a text message:

Support the show


To help support this podcast and become a PilotPhotog ProCast member: https://www.buzzsprout.com/1555784/support

If you enjoy this episode, subscribe to this podcast, you can find links to most podcast streaming services here: 

PilotPhotog Podcast (buzzsprout.com)


Sign up for the free weekly newsletter Hangar Flyingwith Tog here: 

https://hangarflyingwithtog.com

 

You can check out my YouTube channel for many videos on fighter planes here:

https://youtube.com/c/PilotPhotog

 

If you’d like to support this podcast via Patreon:

https://www.patreon.com/PilotPhotog

 

And finally, you can follow me on Twitter here:

https://twitter.com/pilotphotog

Speaker 1

On 22 December 2024 , a US Navy F-A-18 Super Hornet was shot down , not by an enemy , but by a devastating Blue on Blue friendly fire incident . It was a moment that shook one of the most advanced naval and air forces in the world . How could this happen and what can we learn to prevent it from happening again ? This incident occurred during the high-stakes operations in the Red Sea , a region that has become increasingly dangerous . As you know , houthi rebels have frequently been targeting commercial shipping with drones and missiles , making this area a flashpoint for conflict . In response , the US Navy , alongside its allies , have been patrolling these waters to protect vital shipping lanes . Operating in such a tense and confined space demands precision and flawless communication , but on that fateful December night , a series of missteps led to disaster . Here's what we know so far and the lessons we must learn . The USS Harry Truman had just entered the Red Sea in support of Operation Prosperity Guardian and soon began launching precision airstrikes while its escort ships were repelling Houthi attacks . These factors of just entering the area , beginning up-tempo operations while also dealing with incoming fire , likely heavily contributed to the Blue on Blue incident . Still , how did one of the Navy's guided missile cruisers mistake a friendly Super Hornet for a threat , and what happened next may surprise you . This wasn't the only close call that night . The incident as the Super Hornet approached its carrier , the guided missile cruiser USS Gettysburg mistakenly identified it as a threat , despite the jet broadcasting its IFF or Identify Friend or Foe signals . A misclassification in the missile defense system led to a catastrophic error . A surface-to-air missile likely an SM-2 , was fired . Thankfully , the Super Hornet's crew ejected in time but survived with minor injuries . Of course , the aircraft was destroyed , leaving everyone asking the same question how could this happen ? Now here's where it gets even more alarming . We're recently learning that just moments later , a second missile was fired , this time apparently at another Super Hornet flying nearby . This second jet barely escaped , taking evasive maneuvers that caused the missile to miss by only 100 feet . This second close call nearly turned one tragedy into two . There are some reports surfacing now that the USS Gettysburg turned off the guidance system on the second missile , which could explain why it missed .

Speaker 1

The fact that the same cruiser almost shot down two friendly jets raises serious concerns about the reliability of our missile defense systems and communications protocols , and while the Navy's investigation is ongoing , we already know enough to draw some important lessons . The Navy's preliminary report highlights several key failures . First , communications breakdowns Vital information wasn't relayed in time . Second , misclassification by the missile system the jet's IFF signals weren't recognized correctly . And third , lack of redundancy in identification protocols Backup systems failed to prevent the misfire . This chain of errors reveals just how complex and dangerous modern warfare can be , even when fighting an unconventional enemy like the Houthis . Lessons learned In response to this incident ?

Speaker 1

The Navy has announced several steps to ensure this doesn't happen again . Number one enhanced IFF technology Upgrades to ensure friendly aircraft are always correctly identified . Number two stricter communication protocols . Better coordination between air and surface forces to prevent misunderstandings . Number three , and perhaps most important , comprehensive training , new drills that are designed to simulate these exact scenarios , giving crews the skills to respond under pressure . Hopefully , these measures aim to not only address the immediate issues , but also set a higher standard for military aviation and surface warfare . Friendly fire is a tragic reality of warfare and it's not a new problem . From ancient battlefields to today's high-tech military operations . Such incidents remind us of the critical importance of communication technology and training . Hopefully , the downing of the Super Hornet is a wake-up call . Operating in the narrow , volatile waters of the Red Sea is challenging enough without the added risk of friendly fire . By addressing the factors that led to this incident , the Navy can turn this tragedy into an opportunity for growth , making the skies and seas safer for our warfighters . Until then , keep those radar warning receivers powered up . And now you know ? Pilotphotogcom .