"The cruiser almost shot down two friendly jets."
The second hornet was forced to make maneuvers in order to avoid the friendly fire that took out the first Hornet on Sunday, according to Fox News. The missile fired at the second jet, which narrowly avoided the same fate, was confirmed to have been fired off by a Naval officer. The officer added that the military is investigating to see if the missile targeted the second Hornet.
Both pilots in the first jet shot down were able to eject in time and were recovered alive after the incident with one suffering "minor injuries." The US had been conducting strikes that were "deliberate" in order to disrupt the Houthis' operations. The jet that was shot down had just taken off the Harry S. Truman aircraft carrier at the time.
CENTCOM said in a statement about the jet which was shot down at the time, "The guided-missile cruiser USS Gettysburg, which is part of the USS Harry S. Truman Carrier Strike Group, mistakenly fired on and hit the F/A-18."
However, the source who spoke to Fox News said the statement is inaccurate, and added, "It was a tanker crew returning to land on the carrier about 10 miles out. They recognized the missile was guiding and punched out about three seconds before the missile hit the jet."
"The cruiser almost shot down two friendly jets," the source reportedly added when speaking to the outlet.
Powered by The Post Millennial CMS™ Comments
Join and support independent free thinkers!
We’re independent and can’t be cancelled. The establishment media is increasingly dedicated to divisive cancel culture, corporate wokeism, and political correctness, all while covering up corruption from the corridors of power. The need for fact-based journalism and thoughtful analysis has never been greater. When you support The Post Millennial, you support freedom of the press at a time when it's under direct attack. Join the ranks of independent, free thinkers by supporting us today for as little as $1.
Remind me next month
To find out what personal data we collect and how we use it, please visit our Privacy Policy
Comments