Saudi airstrikes on Sanaa airport aim to block Iranian Mahan Air landing in Hodeidah
Saudi jets struck Sanaa International Airport on 13 July 2026 as an Iranian Mahan Air flight approached Yemeni airspace, escalating a multi-year air campaign into direct aviation interference with Tehran.

Saudi fighter jets struck Sanaa International Airport at roughly 11:35 UTC on 13 July 2026, hours before an Iranian Mahan Air aircraft entered Yemeni airspace bound for Houthi-held Hodeidah on the Red Sea coast. Houthi-aligned media described the strikes as an attempt to prevent the Iranian airliner from landing; Yemen's defence ministry, quoted by an open-source monitor, said its own forces had struck the Sanaa runway to block the Iranian plane. Both accounts agree on the outcome: an Iranian aircraft did touch down at Hodeidah, and Saudi Arabia did bomb the Sanaa airfield.
The episode marks the first time in the current phase of the Yemen war that an Iranian civilian flight has been visibly caught up in the aerial contest between the Saudi-led coalition and the Iran-aligned Houthi movement. It also lands inside a longer pattern: coalition air operations against Sanaa have intensified since late 2024, and Iran has steadily expanded air-bridge flights into Houthi-controlled territory. What changed on Monday is that two of those trends collided in real time over a passenger aircraft.
What actually happened at Sanaa
According to Middle East Spectator's breaking alert, Saudi jets bombed Sanaa International Airport specifically to prevent an Iranian Mahan Air flight from landing. Iran had, the same channel reported, broken what it called a "siege on Yemen" by carrying out multiple flights into Sanaa in recent days. Open Source Intel, citing Houthi-affiliated media, framed the Saudi strikes as a response to that air bridge; a separate Houthi statement, relayed by PressTV, said Yemen's armed forces had struck the Sanaa runway to block the Iranian plane. Both versions land on the same core fact: at least one Iranian aircraft was operating in Yemeni airspace while coalition aircraft were active over the capital.
Within forty minutes, Fars News Agency reported that the Iranian plane had landed at Hodeidah Airport in western Yemen, with a Houthi spokesperson framing the touchdown as a deliberate demonstration that the air blockade had been broken. PressTV carried the same Iranian-aircraft-in-Hodeidah line independently, an unusual convergence of Tehran-aligned outlets on a specific operational detail.
The competing narratives
Two stories sit inside the same set of events. The first, pushed by Houthi and Iranian channels, is that the Saudi strikes were an act of aggression against a civilian flight path, and that the Mahan Air landing at Hodeidah proves Iran can still reach Yemen by air. The second, advanced by the coalition and Western observers of the war, is that Iran has been using civilian aviation as a vector to move personnel, equipment, and dual-use materiel to the Houthis, and that any interference with those flights is a legitimate countermeasure rather than an attack on a civilian airliner. The sources in this thread do not adjudicate between those two readings. They do show that both sides treated Monday's flight as a political event, not a routine arrival.
Why a civilian airliner
Yemen's air war has, until now, been fought largely over launch sites, missile storage, and radar infrastructure. Targeting the airport from which an Iranian flight was about to arrive marks a shift. It says, in effect, that the Iranian air bridge to Sanaa is now treated as a sanctioned target rather than a tolerated nuisance. The Houthi defence ministry's claim that its own forces struck the runway is harder to square with the geography: a Yemeni ground strike against the Sanaa runway would have had to come from inside Houthi territory, which the Houthis themselves control. That detail is one of several that the open-source record cannot yet reconcile.
The Mahan Air angle matters beyond symbolism. Mahan Air has been under US Treasury sanctions since 2011 over allegations of links to the Islamic Revolutionary Guard Corps-Quds Force, and remains on the European Union's air safety blacklist. Saudi Arabia has long accused Iran of using the carrier as a logistics arm in Syria, Lebanon, and Yemen. A Saudi strike on an airport at the precise moment a Mahan flight is inbound is therefore not a generic act of war; it is an act of war aimed at a specific Iranian instrument that Riyadh has been naming for over a decade.
What the next hours and days will tell
Three signals will indicate whether this is a one-day escalation or a new operating posture. First, whether coalition public affairs confirms the Sanaa strikes in on-the-record language or lets them sit as unclaimed tactical action. Second, whether Iran escalates with a counter-strike, an additional Mahan or Iran Air flight, or a diplomatic démarche through the UN. Third, whether commercial carriers serving Sanaa route diversions are publicly announced, which would tell us how the wider aviation industry reads the airspace after Monday. None of those signals had appeared in the open-source record by 12:14 UTC on 13 July 2026, the timestamp of the most recent item in this thread.
What is clear is that the Saudi-Iranian contest over Yemeni airspace has crossed a threshold. Until Monday, the Saudi-led coalition had treated Sanaa's runway as something to deny to missiles and drones, not to passenger aircraft. Treating the airport itself as a target of opportunity rather than a piece of protected civilian infrastructure is a meaningful doctrinal step, regardless of which side one credits for the immediate action.
Desk note
This article is built from nine Telegram-channel items dated between 11:35 and 12:14 UTC on 13 July 2026. We have leaned on Houthi-, Saudi-, and Iranian-aligned channels in roughly equal weight and flagged where their accounts diverge, rather than treating any one feed as authoritative. Where wire confirmation from Reuters, AP, or AFP lands in the next 24 hours, this piece will be rewritten with that scaffolding.
Sources are listed in the Sources section below.
Wire provenance
This editorial synthesis draws on the following public wire/social posts:
- https://t.me/Middle_East_Spectator
- https://t.me/osintlive
- https://t.me/presstv
- https://t.me/thecradlemedia
- https://t.me/ClashReport