Wire
21:30ZINTELSLAVAIran Conducts Drone Strikes Against Kurdish Separatist Parties in Erbil21:28ZPRESSTVYemeni forces attack Jizan, Yanbu; Ansarullah says Saudi response shows confusion21:27ZSHAAMNETWONational Authority for Missing Persons weighs international day for missing women with families21:25ZTASNIMNEWSExplosions reported in Erbil, northern Iraq21:24ZFARSNAMultiple explosions reported near US consulate in Erbil, Iraq21:22ZPRESSTVGermany approves major arms exports to Israel during Gaza conflict21:22ZTASNIMPLUSArab media reports attack hits positions in Erbil, northern Iraq21:22ZFARSNEWSINAttacks Target Anti-Iranian Separatists in Erbil
  • S&P 500 ETF 0.06%
  • Nasdaq 0.18%
  • Nasdaq 100 0.32%
  • Dow ETF 0.08%
Terminal ↗
← The MonexusMena

Houthi-held Sana'a airfield struck after Iranian Mahan Air plane lands at Hodeidah

Saudi Arabia hit the runways of the Sana'a airfield hours after an Iranian Mahan Air passenger jet was reported to have landed at Hodeidah, sharpening a long-running air blockade and pulling Iran's civil aviation into the line of fire.

Houthi-held Sana'a airfield struck after Iranian Mahan Air plane lands at Hodeidah

Saudi aircraft struck the runways of Sana'a International Airport on the morning of 13 July 2026, hours after an Iranian Mahan Air passenger plane was reported to have landed at the airport of Al-Hudaydah (Hodeidah) on Yemen's Red Sea coast. The strike marks the most visible Saudi response yet to Tehran's continued civil-aviation outreach to Houthi-controlled territory, and the first time in this escalation cycle that a commercial jet operated by an Iranian carrier appears to have broken the air blockade without being turned back.

What the day's reporting adds up to is a slow-bleed blockade giving way, episode by episode, to direct runway denial. Saudi Arabia's logic is familiar: if the runway is unusable, neither Iranian cargo aircraft carrying weapons components nor symbolic civilian flights can touch down. The cost is paid by Yemeni civilians, who have now lost their second-biggest international runway for an indeterminate period, and by the diplomatic fiction that Iranian civil aviation operates independently of Iranian statecraft.

The day's timeline, as reported

Two Telegram channels, Abu Ali Express and Clash Report, carried the story in overlapping bursts between 11:28 and 12:14 UTC. The first report, at 11:28, said Saudi Arabia had attacked the Sana'a airfield runways after another Iranian passenger plane broke the air blockade on the Houthis. A second item, at 11:45, flagged the sequencing problem: it was not clear whether the Iranian aircraft had already landed before the runway was hit, or was still airborne at the time of the strike. By 12:04, Abu Ali Express was treating the landing as a fait accompli, identifying the aircraft as a Mahan Air plane and pinning the landing site at the airport of Al-Hudaydah. The fourth item, carried by Clash Report at 12:14, corroborated the Mahan Air identification and the Hodeidah destination, and framed the incident as "a further escalation in tensions between Saudi Arabia and the Iran-backed Houthis."

The chain of four briefs leaves open the most important operational question. Did the Saudis strike the runway to prevent a landing, in the middle of one, or after one had already taken place? Each scenario carries a different implication. A pre-emptive strike is a warning; a strike during landing is intimidation against the crew; a post-landing strike is punishment. The reporting does not yet distinguish between them.

Why Mahan Air matters

Mahan Air is the Iranian carrier most closely associated with the Islamic Revolutionary Guard Corps' external operations wing, and has been under US Treasury sanctions since 2011. It is also the airline that, for years, has served routes into Syria's Damascus and Latakia during the worst of that country's fighting, and into Beirut even during periods of Israeli air operations. A landing at Hodeidah is not the first time the airline has put a civilian airframe into a frontline theatre; it is the first time, on the public record available here, that one has done so inside a zone the Saudi-led coalition has explicitly forbidden.

That matters because civil aviation is one of the few remaining categories of Iran-to-Arab-Peninsula traffic not yet fully militarised. Humanitarian flights by UN agencies, Yemenia Airways when it still flew, and Iranian Red Crescent medevac movements have all, at various points, moved through or over Saudi-controlled airspace with quiet accommodation. A commercial Mahan landing at Hodeidah pushes that grey zone further toward confrontation.

What the Saudi calculus looks like

Saudi Arabia has said, through coalition spokespeople in past cycles, that any aircraft landing at Houthi-held airfields without coalition clearance is treated as participating in the Iranian logistics chain to the Houthis. The practical instrument of that policy has, until now, been interception and diversion rather than destruction of the runway itself. Striking the runway elevates the response from air policing to infrastructure denial, with two consequences.

First, it is reversible but slow. Runway repair at Sana'a is not a one-day job, and the Saudis can repeat the strike on any subsequent attempt to reopen. That puts the burden of restoration squarely on the Houthis and their Iranian backers, and adds a new cost line to the Iranian supply chain to western Yemen.

Second, it drags Iranian civil infrastructure, rather than Iranian military equipment, into the targeting picture. Iran can still deny that its passenger aircraft are carrying weapons. It cannot easily deny that a Mahan Air jet on the ground at Hodeidah makes that denial harder to sustain in UN and Western capitals. The Houthi-aligned channel reporting on the event treated the landing as a propaganda win; the structural reality is more uncomfortable for Tehran than that.

What remains contested

The 13 July briefings do not specify which Saudi entity conducted the strike (Royal Saudi Air Force, coalition joint air component, or a contracted operator), nor whether the runway at Hodeidah itself was hit in addition to Sana'a. They do not give a casualty count, a flight number, or the nationality of passengers on the Mahan aircraft, and they do not name the Iranian or Houthi official who, on either side, claimed credit. The Clash Report item is the most expansive but is still short on operational detail.

Read against the wider wire of the past year, the pattern is consistent: Iranian aircraft land, coalition aircraft punish the runway, Iranian state media frames it as defiance, Saudi-aligned outlets frame it as enforcement. The only material change on 13 July is that two independent Telegram channels, working from different feeds, both identified the aircraft as Mahan and the destination as Hodeidah, which is a notch higher confidence than the single-source confirmations that have carried previous episodes.


Desk note: Monexus reads the 13 July reporting as the latest move in a recurring runway-blockade exchange between Saudi Arabia and the Iran-aligned Houthi-Tehran axis. The exact sequencing of the strike relative to the Mahan Air landing is the operative unknown; until that is clarified, claims about Saudi intent are tentative.

Wire provenance

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

  • https://t.me/abualiexpress
  • https://t.me/abualiexpress
  • https://t.me/abualiexpress
  • https://t.me/ClashReport
© 2026 Monexus Media · AI-native reporting from public-source material