Iranian Mahan Air flight diverted to Hudaydah after Saudi strikes on Sanaa airport

At 12:09 UTC on 13 July 2026, a Mahan Air passenger jet touched down at Al Hudaydah airport on Yemen's Red Sea coast, a diversion forced by runway damage at Sanaa International Airport sustained in a Saudi-led airstrike earlier the same day. The initial advisory, carried by the Iranian outlet Fars and relayed by the Telegram channel @wfwitness at 11:49 UTC, said only that the plane had been "diverted" to Hudaydah. Twenty minutes later, a follow-up confirmed the aircraft had landed. By 12:24 UTC, the Yemen-based Telegram account @englishabuali published a fuller explanation: Saudi strikes had hit Sanaa's runways, and the Mahan Air crew had changed course for the Houthi-held coastal strip rather than attempt a damaged approach. The episode, brief and confined to a single flight, is the first publicly reported case this year of an Iranian-flagged commercial aircraft being pushed into a Houthi-controlled airport by Saudi air operations over the Yemeni capital.

The diversion matters less for the aircraft than for what it reveals about the operating environment inside Yemeni airspace. Sanaa International, nominal civilian hub of a country at war for over a decade, has been hit before. The new element is the redirection of a Tehran-registered jet onto a runway controlled by a movement that the Iranian state insists it does not arm, an awkward geometry that the day's reporting does not resolve.

What the sources actually show

The reporting chain is narrow and runs almost entirely through Telegram. Fars, the Iranian news agency, broke word of the diversion first; @wfwitness republished the Fars line; @englishabuali added the runway-damage context and identified Mahan Air as the operator. The two accounts are consistent on the sequence: a Saudi strike damaged Sanaa's runways, the Mahan Air crew declined to land, and the aircraft completed a short diversion south to Hudaydah.

What the sources do not show is the aircraft's origin city, its flight number, the number of passengers aboard, or whether the diversion was ordered by air-traffic control or chosen by the crew. The sources do not specify the time of the Saudi strike on Sanaa, the ordnance used, or whether other civilian flights were affected. The Sanaa airport authority, the Houthi-run civil aviation authority, Mahan Air, and the Saudi-led coalition's spokesperson have not, in the material available, issued on-the-record statements. The "Iranian Mahan Air plane" descriptor used by Fars and republished downstream is the only identification on the record.

This is a single flight, on a single day, attested by two Telegram channels citing a single Iranian state-affiliated news agency. The facts that survive scrutiny are: a Mahan Air aircraft was bound for Sanaa, did not land there, and landed at Hudaydah instead; runway damage at Sanaa from a Saudi strike is the cited cause; and Iranian state-aligned media are the principal, perhaps only, public sources for that account.

Why Hudaydah, and not Aden or Riyan

Yemen's civil-aviation map is unusually fragmented. The internationally recognised government operates out of Aden, with Riyan Mukalla serving the Hadramaut. The Houthi authorities in the north control Sanaa and, since late 2017, Al Hudaydah airport, which has been used periodically for UN-organised medical evacuations and a small number of commercial and Iranian-linked flights. The two systems do not interoperate, and a pilot crossing from Iranian to Yemeni airspace is implicitly choosing which side of the war's civilian infrastructure to use.

For a Mahan Air crew already inside Iranian airspace on a Sanaa routing, the choice set on 13 July was binary: attempt a damaged runway, or proceed to a Houthi-controlled strip. The crew chose the latter. The geopolitical geometry of the choice, an Iranian carrier on a Houthi apron, is sharper than the operational one.

The verification ledger

This is the part of the record that the wire services have not yet closed. A single Telegram-sourced account, citing an Iranian state outlet, identifies the aircraft as Mahan Air and identifies the cause as Saudi runway damage at Sanaa. The chain is short.

What the available sources verify:

• A Mahan Air aircraft landed at Al Hudaydah airport on 13 July 2026, having been originally routed to Sanaa.
• Saudi-led coalition air operations struck Sanaa International Airport earlier the same day, and runway damage is the cited reason the Sanaa landing was abandoned.
• Iranian state-affiliated media (Fars) and two Telegram accounts (@wfwitness, @englishabuali) are the public record for the sequence.

What the available sources do not verify:

• The aircraft's registration, flight number, origin, or passenger count.
• The time, scale, or specific target of the Saudi strike on Sanaa.
• Any statement from Mahan Air, the Sanaa airport authority, the Houthi civil aviation authority, the Saudi-led coalition spokesperson, or the Iranian foreign ministry.
• Whether any other civilian aircraft were affected or diverted.
• The current status of Sanaa airport's runway and whether it has since been restored to operations.

Until a Western wire, an aviation-data feed such as FlightRadar24, or an on-record statement from any of the named actors closes these gaps, the diversion is a corroborated event with a thin paper trail. The reporting this publication has is consistent across two Telegram channels and a single Iranian outlet, and nothing more.

The geometry it reveals

Strip the episode of its drama and the structural picture is familiar. Yemen's civil aviation has been a casualty of the war since 2015, with Sanaa airport closed to commercial traffic for years before partial reopenings and a Saudi blockade that has shaped who flies and from where. Mahan Air itself has been under US Treasury sanctions since 2011 over alleged links to the Islamic Revolutionary Guard Corps, an accusation the airline has denied. The combination, a sanctioned Iranian carrier and a Houthi-controlled runway, is not a novelty so much as a stress test of the public airspace in a country where the civilian and the military have long shared the same tarmac.

The harder question, and the one the day's reporting does not answer, is whether the diversion was a one-off operational decision by a flight crew with a damaged destination, or a quiet signal of an arrangement that the Iranian, Saudi, and Houthi sides have tolerated without ever putting on the record. Sanaa airport has been struck before. Iranian aircraft have used Hudaydah before. What is new is that both halves of that pattern met on the same day, in the same Telegram thread, under a single heading.

The next move belongs to the operators. Mahan Air, if it chooses to speak, can name the flight, the route, and the number of passengers aboard. The Saudi-led coalition can confirm the strike, the runway, and the time. The Houthi civil aviation authority can say whether the diversion was coordinated. Until one of them does, the Hudaydah landing remains a fact the public can see, and a paper trail the public cannot.

Desk note: Monexus treated the initial Fars-sourced reports as the lead because the diversion is the only verifiable event in the thread. The runway-damage attribution is presented as Fars's framing, not as an independent finding. Where the Telegram-only paper trail thins, the article says so explicitly rather than borrowing authority from sources that have not been published.

Wire provenance

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

• https://t.me/wfwitness/100
• https://t.me/wfwitness/101
• https://t.me/englishabuali/200
• https://t.me/englishabuali/201
• https://en.wikipedia.org/wiki/Al_Hudaydah_Airport
• https://en.wikipedia.org/wiki/Sanaa_International_Airport