How SEALs were caught in ‘ferocious’ firefight during Yemen counter-terrorism raid

WE ARE THE MIGHTY:


New details have emerged about the Jan. 28 raid on a compound used by al-Qaeda in the Arabian Peninsula that resulted in the death of a Navy SEAL and the loss of an MV-22 Osprey.

According to a report by the Washington Post, the raid had been intended to nab Yemeni tribal leaders and get intelligence on their ties with al-Qaeda in the Arabian Peninsula. The snatch operation turned into a firefight when terrorists launched a counter-attack.

Among the militants firing at the SEALs were women, an several were believed to have been among the 14 terrorists killed in the raid. The SEALs were forced to call in air support from AH-1Z Cobras and AV-8B+ Harriers based on the amphibious assault ship USS Makin Island (LHD 8) as the firefight went on, the Post report says.

Additionally, officials with Central Command said Feb. 1 that investigators are looking into allegations that among the dead were civilians in the compound targeted by the SEALs. Officials said in a release that civilians were “likely” killed and “may include children.”

“The ongoing credibility assessment seeks to determine whether any still-undetected civilian casualties took place in the ferocious firefight,” CENTCOM said. “The known possible civilian casualties appear to have been potentially caught up in aerial gunfire that was called in to assist U.S. forces in contact against a determined enemy that included armed women firing from prepared fighting positions and U.S. special operations members receiving fire from all sides, including from houses and other buildings.”
To get the SEALs out, elements of what the report called “an elite Special Operations air regiment,” likely referring to the 160th Special Operations Aviation Regiment, also called the Nightstalkers. After retrieving the SEALs, the Nightstalkers intended to meet up with a Marine quick reaction force on MV-22 Ospreys to transfer the SEALs to the Makin Island, where the wounded could receive medical treatment.

That meet-up went wrong. One of the V-22s made a “hard landing” – more akin to a crash – which ended up leaving three Marines injured.

In an interview with reporters Feb. 1, Deputy Commandant for Aviation Lt. Gen. John Davis said officials are still investigating what went wrong with the Osprey, adding his suspicion was that brown-out conditions might have played a role.

“They were going into a firefight at night. … But what’s the good news? A lot of people don’t walk away from hard landings, and everybody walked away from this one,” Davis said. “There’s a Marine who kind of bumped his head, but everyone walked away.”

READ MORE HERE

Trump puts Iran "officially on notice" after missile test

THE GUARDIAN

The Trump administration has said it was “officially putting Iran on notice” in reaction to an Iranian missile test and an attack on a Saudi warship by Iranian-backed Houthi rebels in Yemen but gave no details about how Washington intended to respond.


The threat was made on Wednesday by the national security adviser, Michael Flynn, in his first public statement since taking office.

Speaking in the White House briefing room, Flynn said a missile launch on Sunday and a Houthi attack on a Saudi frigate on Monday underlined Iran’s “destabilizing behavior across the Middle East.”.


Flynn did not specify how the new administration would respond. Asked for clarification, the White House spokesman, Sean Spicer, said the president wanted to make sure the Iranians “understood we are not going to sit by and not act on their actions”.

At a White House briefing, senior administration officials repeatedly refused to rule out any options for a US response, including military intervention.

“There are a large number of options available to the administration,” one senior official said. “We’re going to take appropriate action.”


Asked if measures under consideration included a military option, the official replied: “We are considering a whole range of options.”


The official declined to say whether the White House had sent a message to Tehran putting it on notice.


“We are in the second week. We do not want to be premature or rash or take any action that would foreclose options or unnecessarily contribute to a negative response.”
Advertisement


The announcement was not accompanied by any change in the US military stance in the region, nor any immediate additional deployments.


“We saw the statement as well,” said a spokesman for US central command, which runs operations in the Middle East. “This is still at the policy level, and we are waiting for something to come down the line. We have not been asked to change anything operationally in the region.”

The Pentagon was informed before the announcement and the defense secretary, James Mattis, prevailed upon Flynn to soften his language about Iran from an earlier version. At the time of the Flynn’s statement, Mattis was en route to Asia for an official visit to Japan and South Korea.

Ali Vaez, an Iran expert at the International Crisis Group in Washington, said: “It’s either an empty threat or a clear statement of intent to go to war with Iran. Both are reckless and dangerous ... In an attempt to look strong, the administration could stumble into a war that would make the Afghan and Iraqi conflicts look like a walk in the park.”

READ MORE HERE