Sanaa airport runways struck: what the Saudi-Houthi flare-up tells us about an unraveling detente

Saudi-led coalition warplanes struck both the landing and takeoff runways at Sanaa International Airport on the morning of 13 July 2026, in a four-airstrike sequence that Yemen's Houthi-run Ministry of Defence said targeted the runway infrastructure directly. The attacks, first reported by Sanaa-based Saba News Agency and carried by The Cradle Media at 11:06 UTC, hit a civilian aviation hub that has functioned as the movement's main external air link and as a recurring pressure point in an on-again, off-again blockade on Yemeni airspace.

The strike ended a phase of de-escalation that the Houthis themselves had been advertising. Houthi military spokesperson Yahya Saree called the attack an "unjust and brazen aggression" and warned that it "will not go unanswered," according to Telegram channels Liveuamap and World Footage Witness. Saree's framing, that the raid broke a truce that had not been formally codified, is the political claim the next 72 hours will test.

The runways, the airliner, and the alibi problem

A claim that began circulating within thirty minutes of the strikes has shaped the day's narrative. Middle East Spectator reported at 11:34 UTC that Saudi jets had bombed the airport to prevent an Iranian airliner from landing, asserting that Iran had "broken the siege on Yemen by carrying out multiple flights to Sanaa in recent" days. Iran's Fars news agency added a corroborating detail at 11:35 UTC, saying the Iranian plane diverted to Hodeidah airport on the Red Sea coast after the strike on Sanaa.

If accurate, the framing inverts the standard reading of the war. The airport becomes a place Riyadh is defending against Iranian penetration rather than a target being punished for Houthi behaviour. The Houthi transport ministry, in a separate Telegram statement at 11:30 UTC carried by World Footage Witness, framed the strikes as a "continuation of the blockade on Yemen's airports," a phrasing that treats the runways themselves as the prize. The two narratives, a punitive raid versus a defensive denial of Iranian access, are not mutually exclusive, and the public record so far does not let a careful reader choose between them.

A cabinet in permanent convocation

Inside the internationally recognised government, the response was institutional rather than rhetorical. The Yemeni Cabinet, seated in Aden, convened an extraordinary session and declared a "state of permanent convocation" to confront what it called Houthi escalation, according to a Telegram post by World Footage Witness at 11:43 UTC. The session approved a committee structure to manage the crisis, language that signals the Aden government is preparing for a long political campaign inside the anti-Houthi coalition rather than a quick military response of its own.

For a government whose writ rarely extends beyond its meeting room, the phrase "permanent convocation" is a way of staying visible during a moment when its patron's restraint is being questioned. It also implicitly concedes that the airport, and the airspace around it, is the terrain on which the next phase will be fought in front of cameras and foreign capitals.

What "de-escalation" was, and what it wasn't

For most of the past year, Sanaa airport has been the barometer of how seriously the Saudis and the Houthis are talking. Reopening the runway to commercial traffic has functioned as a confidence-building gesture, its closure as a punishment, and the threat of closure as leverage. The Houthi transport ministry's reference to a continuing blockade suggests that even before today's strikes, the airport was already operating under constraints that civil aviation authorities would not recognise as normal.

Saree's claim that the de-escalation phase has ended, therefore, is not the same as saying a new war is starting. It is closer to saying the previous arrangement, whatever its exact terms, is no longer operative. The Houthis are warning of retaliation; the coalition has not publicly disowned the strikes; and the airport's runways are, at minimum, cratered. The two sides now have to decide whether to escalate further or to negotiate a new de-escalation that will, by definition, be worse than the one being mourned.

The pattern underneath the day's headlines

A strike on a runway, followed by an Iranian diversion, followed by a Houthi retaliation threat, followed by a coalition framing that emphasises punishment for previous Houthi attacks on shipping and Saudi territory, is the standard sequence in this war's latter phase. Each party claims the other forced its hand. Each frames its action as defensive in spirit. The public evidence base is dominated by Telegram channels and outlets that sit on one side or the other of the conflict, which means the cleanest analytical move is to treat the day's statements as a record of positions taken, not a record of facts established.

What is established is the airport's runways are damaged, the Iranian flight ended up in Hodeidah, the Houthi political leadership has declared a truce over, and the Aden government has put itself on a war footing in word if not yet in deed. What is not established is whether the strike was timed against an Iranian aircraft specifically, as Middle East Spectator and Fars claim, or against runway infrastructure in a continuing campaign, as the Houthi transport ministry implies. The reader should hold the two readings side by side and wait for satellite imagery, flight-tracking data, or an official Saudi statement to adjudicate.

The practical question for the rest of the region is whether this is the start of another cycle, or a single noisy act inside a longer, quieter contest for control of Yemen's airspace. The Houthis now own the response. The Saudis now own the consequences. The Iranian airliner is in Hodeidah, and the clock is back to where it was before the so-called de-escalation began.

How Monexus framed this: the public record on the 13 July Sanaa airport strike is dominated by Houthi-run outlets and Telegram channels sympathetic to one side or the other. We have reported the competing framings as competing framings, and held back on a definitive attribution of motive until independent flight-tracking or official statements corroborate the Iranian-airliner claim.

Wire provenance

This editorial synthesis draws on the following public wire/social posts:

• https://t.me/thecradlemedia/1
• https://t.me/intelslava/1
• https://t.me/intelslava/2
• https://t.me/wfwitness/1
• https://t.me/wfwitness/2
• https://t.me/wfwitness/3
• https://t.me/Middle_East_Spectator/1
• https://t.me/farsna/1
• https://t.me/wfwitness/4