Saudi jets hit Sanaa airport runway as Iran-linked Mahan Air flight triggers escalation
Riyadh struck the runway of Sanaa International Airport on 13 July 2026 as an Iranian Mahan Air passenger jet entered Yemeni airspace, ending what the Houthi foreign ministry called the de-escalation period.

Saudi warplanes struck the runway of Sanaa International Airport on the morning of 13 July 2026, in what the Houthi foreign ministry described within hours as an effective declaration of war. The bombing, reported by Houthi-affiliated media and relayed by open-source intelligence monitors, came as an Iranian Mahan Air passenger aircraft was approaching Yemeni airspace, prompting a sequence of events that Yemen's defence ministry framed as a direct attempt to block an Iranian plane from landing.
The strike, if confirmed at the scale initially described, would mark the most serious Saudi escalation inside Houthi-held territory since the informal de-escalation that followed the 2022 truce, and the first time the kingdom has publicly risked a direct aerial confrontation with a commercial flight operated by an Iranian carrier. Riyadh has not, as of publication, issued a public statement; the Houthi side has, and the asymmetry of the information environment is itself part of the story.
What the wires say happened
Open-source intelligence accounts began circulating the news at 11:27 UTC on 13 July 2026, after a Telegram channel run by the Houthi-affiliated outlet Al-Masirah reported that Saudi aircraft had hit the takeoff and landing runways of Sanaa International Airport. The trigger, per the same channel, was a Mahan Air passenger plane that had broken what Saudi Arabia has treated as a blockade on Iranian flights into Houthi-controlled airspace and was attempting to land.
Within eight minutes, the open-source monitor Osint613 posted that Saudi fighter jets had conducted multiple airstrikes on the airport, noting that the Iranian Mahan Air aircraft had entered Yemeni airspace while Saudi aircraft were reported in the area. At the same timestamp, Yemen's defence ministry put out a competing read: that its own armed forces had struck the airport runway in order to prevent the Iranian plane from landing. The two accounts are not reconcilable on their face, and that contradiction is the single most important fact for any reader to hold onto.
By 11:39 UTC, the Houthi-run foreign ministry had escalated the framing further, accusing Saudi Arabia of "effectively declaring war" by striking the airport and announcing the end of what it called the de-escalation and ceasefire period. By 12:05 UTC, Osint613 was using the phrase "major escalation" to describe the trajectory, and warning that the strike pattern, if it continued, would be incompatible with any return to the post-truce status quo.
The Iranian flight and the air blockade question
Mahan Air, a privately operated Iranian carrier placed on US sanctions lists in 2011 over its alleged links to the Islamic Revolutionary Guard Corps, has been one of the principal commercial conduits between Tehran and destinations across the Middle East and South Asia. Its appearance in Yemeni airspace is, on its own, a politically loaded act: there is no scheduled Mahan Air service to Sanaa, and Iranian commercial aviation into Houthi-held territory has long been treated by Riyadh as a line.
Saudi Arabia does not formally acknowledge a blockade of Ansarullah-controlled airports; the kingdom's position has been that any Iranian aircraft entering Yemeni airspace without Riyadh's coordination is, by definition, in violation of the air restrictions the coalition has maintained since 2015. Houthi media frames the same restrictions as a siege. The flight on 13 July 2026 sits squarely inside that unresolved dispute, and the choice of runway as the target suggests Riyadh judged the political cost of letting the plane land as higher than the cost of disabling the strip.
The Houthi foreign ministry's language, "ending the de-escalation and ceasefire period," is not throwaway. It signals that the Ansarullah side has decided, at least in its public posture, that the 2022 understanding with Riyadh, which had already frayed through 2024 and 2025, is now formally over. That is a strategic declaration, not a press release.
The competing read from Sanaa
Yemen's defence ministry's claim that its own armed forces struck the runway, rather than Saudi aircraft, is harder to evaluate without independent imagery. Sanaa International Airport has been struck repeatedly since 2015, and the Ansarullah side has often sought to control the narrative of damage, including by issuing its own communiqués before international observers can verify them. The Houthi foreign ministry's own statement credits Saudi aircraft with the attack, which sits in obvious tension with the defence ministry line.
The most plausible read, given the sequence of reporting and the geographic and technical realities of the airport, is that the strikes were Saudi and that the Yemeni defence ministry statement was either a miscommunication, a translation artefact, or a deliberate attempt to obscure the role of Mahan Air in triggering the strike. The sources available to Monexus do not settle this, and any reader who treats either side's communique as final is reading past the evidence.
What the escalation actually changes
If the Houthi declaration holds, the operational consequences are immediate. The runway strike, if it disabled the main landing strip, would ground civilian traffic into and out of Sanaa, cutting off the principal humanitarian and commercial air corridor into Houthi-held territory. Aid organisations have long warned that any sustained closure of the airport would deepen a humanitarian crisis that already includes widespread food insecurity.
The strategic consequences are larger. A declared end to the de-escalation period would, in Ansarullah's framing, license renewed attacks on Saudi territory and on shipping in the Red Sea and Bab el-Mandeb, the same corridor that has been a Houthi target since November 2023. Houthi capability in that theatre has been degraded but not eliminated, and the political decision to resume strikes is distinct from the technical capacity to mount them.
For Iran, the incident is a test of whether the cost of operating commercial flights into contested airspace is one Tehran is willing to bear publicly. Mahan Air's role here is not incidental: the carrier sits under US Treasury designation, and any flight it operates into Sanaa is, from Washington's vantage, an act of Iranian state policy. The read from Tehran on 13 July 2026 will be a meaningful signal about whether the Islamic Republic is prepared to absorb the diplomatic heat of being named, again, as the power behind the Houthi runway.
What remains uncertain
The sources available to Monexus do not include any official Saudi statement, any verification from a non-aligned monitoring group such as the UN panel of experts on Yemen, or any imagery that has been independently geolocated. The competing claims of who struck the runway, Houthi accounts of casualties, and the precise state of the landing strip are all unresolved as of publication. The framing of the incident as a "major escalation" is, for now, a read of the trajectory rather than a verdict on the event.
What can be said with confidence is narrower. Saudi aircraft were reported in the area of Sanaa International Airport at 11:27 UTC on 13 July 2026. An Iranian Mahan Air aircraft was reported to have entered Yemeni airspace in the same window. The runway was struck, and the Houthi foreign ministry announced, by 11:39 UTC, that the de-escalation period was over. The rest is contested, and the reader is right to treat it as such.
Desk note: Monexus has relied here on Houthi-affiliated and open-source intelligence channels because no Western wire has, as of 12:30 UTC on 13 July 2026, published independently verified reporting on the strike. The article names the asymmetry rather than papering over it.
Wire provenance
This editorial synthesis draws on the following public wire/social posts:
- https://t.me/englishabuali/
- https://t.me/osintlive/
- https://t.me/osintlive/
- https://t.me/wfwitness/
- https://t.me/osintlive/