Strikes on Abha, strikes on Sanaa: the cycle Yemen's 2022 truce was supposed to break

At 16:50 UTC on 13 July 2026, the war monitor channel Intel Slava reported that Abha International Airport, in Saudi Arabia's southern Asir province, had been struck. Forty-three minutes later, at 17:33 UTC, the same channel said all civilian flight operations at the airport had been suspended. By that point, Yemen's Houthi movement had effectively closed the principal southern gateway into the kingdom, and the Saudi-led coalition had spent the previous twenty-four hours hitting Sanaa International Airport in retaliation for what it said was an attempt to land an Iranian civilian aircraft carrying an official Yemeni delegation.

The two events, separated by a single day, capture where the Yemen file now sits: a 2022 truce architecture that was supposed to convert a grinding war into a negotiating track has been hollowed out from both sides. Neither Riyadh nor Sanaa has formally renounced the arrangement. Neither has observed it in the form it was signed.

What happened on 13 July

The first public reporting of the Abha strike came through Telegram at 16:49 UTC, when Intel Slava flagged "reports coming in of strikes hitting Saudi Arabia." The Tasnim News English feed, the English-language service of Iran's Tasnim News Agency, repeated the account one minute later, citing "some news sources" reporting an attack on the international airport in southern Saudi Arabia. By 16:56 UTC, Intel Slava was reporting that all civilian flight operations at Abha had been suspended in the wake of a Yemeni attack. The framing left the operational chain implicit: Houthi drones and ballistic missiles, which in earlier rounds of the war repeatedly targeted Abha and the nearby King Khalid Air Base, are the only combat formation on the Yemeni side with the reach, the flight profile, and the propaganda incentive to hit a Saudi airport in 2026.

On the other side of the same 24-hour window, Saudi Arabia had struck Sanaa International Airport. The Palestine Chronicle reported at 15:37 UTC that Saudi airstrikes had targeted Sanaa International Airport "in an effort to prevent an Iranian civilian aircraft carrying an official Yemeni delegation from landing." A follow-up at 15:41 UTC expanded the account, framing the strikes as a response to a separate Saudi action against the same airport, and noting rising tension over the Iranian aircraft. The frame the publication advanced, that the Saudi strikes were an attempt to ground an Iranian diplomatic flight, is not independently verified in the source material and should be read as one account rather than a settled chronology.

At 16:12 UTC, Muhammad Al-Bukhaiti, a senior Houthi figure, went on record via the Al-Alam Arabic channel saying Saudi Arabia had "did not adhere to or implement the agreement concluded with Sanaa in 2022." Twenty-one minutes later, at 16:33 UTC, the same channel quoted Al-Bukhaiti saying Saudi Arabia had "put dozens of women, children and men at risk with its aggression against Sanaa Airport under the pretext of violating Yemeni sovereignty." Read together, the two statements are a deliberate attempt to recast the Saudi strike as a violation of Yemeni airspace, and the Houthi retaliation at Abha as a defensive response.

The 2022 truce, and what is left of it

The agreement Al-Bukhaiti referenced was the UN-brokered truce signed in April 2022, a two-month arrangement that rolled over several times before lapsing in October of the same year. It halted large-scale cross-border strikes, allowed commercial flights into Sanaa for the first time in seven years, and brought a measure of fuel ships into Hodeidah. It did not, however, settle the underlying war. It converted a hot conflict into a slow one in which both sides kept their weapons pointed.

The events of 13 July are consistent with the post-truce template. Neither Saudi Arabia nor the Houthis has issued a statement in the source material formally abandoning the framework. The Saudi side, according to the Palestine Chronicle account, justifies its Sanaa strike as enforcement of a transit restriction on an Iranian aircraft. The Houthi side, through Al-Bukhaiti, justifies its Abha strike as retaliation for what it calls a Saudi violation of the 2022 agreement. The legal architecture remains, in the diplomatic sense, intact. The behavioural architecture has dissolved.

This is the structural story. The truce was a confidence-building instrument, not a peace settlement. Once the political will to renew the confidence drains out, the instrument reverts to its dormant state. The strikes at Abha and Sanaa are not an announcement that the war has resumed. They are evidence that, for both parties, the war never really paused.

The Iran thread, in plain language

The Palestine Chronicle's framing, that the Saudi strike on Sanaa was meant to prevent the landing of an Iranian civilian aircraft, is the kind of detail that, if independently corroborated, would harden into a major diplomatic event. As reported, the claim places Tehran at the centre of the Houthi diplomatic footprint in a way that is consistent with the kingdom's public position since 2015, and with the 2023–2024 rounds in which Iranian-aligned actors have been broadly read as directing Houthi strikes on Red Sea shipping and southern Saudi infrastructure.

It is also the kind of detail that should be handled with care. Iranian civilian flights into Sanaa have, at times, transported Houthi negotiating delegations; they have also, at times, transported wounded from the Saudi-led coalition's earlier bombing campaigns. The flight itself is not the incriminating fact. The question is what was on it, who was meant to receive it, and whether the Saudi strike was calibrated to deny a specific outcome (the landing of a named official, the transfer of materiel, the staging of a public diplomatic event) or was instead a generalised demonstration against any Iranian presence in Yemeni airspace. The source material does not resolve that question. The reporter reading the situation from these wires alone cannot, in good faith, answer it either.

The Al-Alam Arabic channel, which is owned by the Iranian state broadcaster IRIB, carries statements from the Houthi political leadership and is, by Western wire standards, a partisan source. It is also, in this case, the principal on-the-record outlet for Al-Bukhaiti's account, which is itself a primary source in the same sense that a State Department briefing is a primary source. The framing is not neutral. But the statements are real, attributed, and on the record.

What this looks like from the southern Saudi side

Abha is not a symbolic target. It is the principal civilian airport serving the Asir region and the broader southern border belt, and it has been attacked before. In the 2019 round, the Houthis hit the airport with cruise missiles, wounding civilians and prompting temporary closures. The 2022 truce was meant, in part, to take Abha off the target list. Its return to the list, on 13 July, is the clearest single signal that the Houthi command does not regard itself as bound by the original terms.

The suspension of all civilian flight operations is the operationally significant fact, not the strike itself. Abha connects the southern provinces to Riyadh, Jeddah, Cairo, and a thin set of regional destinations. A sustained closure cuts the population of the south off from domestic medical evacuation routes, business travel, and the Hajj transit pipeline. It also imposes a real cost on the Saudi tourism push in the Asir highlands, which has been a domestic priority of Crown Prince Mohammed bin Salman's Vision 2030 diversification agenda.

From the Saudi perspective, the calculus is straightforward: an attack on a domestic civilian airport cannot go unanswered; the visible cost of non-response is the encouragement of further attacks. The kingdom's choices are escalation, calibrated retaliation, or quiet diplomacy. The source material gives no indication that quiet diplomacy is the path being chosen on 13 July.

What the regional media machine does to the story

The two principals are not the only actors. Intel Slava, which broke the Abha reporting in the Telegram feed, is an open-source-intelligence aggregator with a Syria-and-Iraq war pedigree and a global audience that has expanded into Yemen coverage since 2023. The Palestine Chronicle is a pro-Palestinian outlet with a sympathetic editorial line on the Houthi war effort. Tasnim is an Iranian state outlet. Al-Alam Arabic is the Arabic service of Iranian state media. The Reuters of the Saudi side, the Saudi Press Agency, is not in the thread context, and the Houthi side's official media, Al-Masirah, is not in the thread context either.

That asymmetry matters. A reader of the 13 July story fed only the Telegram material gets a partial picture: an attack on Saudi Arabia, an attack on Yemen, an Houthi spokesperson's framing of the Saudi strike as a violation. The Saudi framing, in its own words, is largely absent from the thread. This is a structural fact about how the story is travelling, not a judgment about which side is right. It does, however, shape the editorial line any single outlet can responsibly run.

This publication's read: the available evidence supports the following load-bearing claims, and no more. (1) Abha International Airport was struck on 13 July 2026, and civilian flight operations were suspended. (2) Sanaa International Airport was struck by Saudi-led coalition aircraft in the 24 hours preceding the Abha attack. (3) The Houthi movement, through Al-Bukhaiti, frames the Saudi strike on Sanaa as a violation of the 2022 agreement, and frames its strike on Abha as retaliation. (4) The Palestine Chronicle's account of an Iranian civilian aircraft carrying an official Yemeni delegation is one version of the trigger for the Saudi Sanaa strike; the source material does not independently corroborate it. (5) The 2022 truce architecture is, in operational terms, defunct, though neither side has formally renounced it.

Stakes over the next 30 to 90 days

Three trajectories are possible, and the next two weeks of reporting will narrow the field. The first is a return to the 2022 framework through quiet Omani and Saudi diplomatic channels, in which case the strikes at Abha and Sanaa are read as coercive signals, not as a strategic decision to resume the war. The second is a measured escalation, in which both sides continue to hit each other's airports and the diplomatic track freezes, and the humanitarian cost climbs. The third is a wider regional pull-in, in which the Iran-Saudi contest over the airspace around Sanaa draws in the US Fifth Fleet posture in the Red Sea and forces a diplomatic re-engagement from Washington that has been absent for the better part of 2026.

The political cost of the third trajectory is, for the moment, the most underappreciated. Abha is a civilian airport inside Saudi territory. A successful, repeated, and unanswered strike campaign against Saudi civilian aviation is a domestic-political event in the kingdom. The Saudi response space runs from quiet retaliation in Yemeni territory to a public confrontation with Iran, and the choice between those two poles is made in Riyadh, not in Sanaa. The Houthis have, in earlier rounds, absorbed Saudi retaliation and waited the kingdom out. The open question for 2026 is whether the kingdom is willing to escalate the Houthi war on the ground, with all that implies for the humanitarian file, in order to defend the southern airspace.

What is not yet in the record, and what a careful reading should mark as uncertain: the specific weapon used against Abha, the casualty count, the identity of the Iranian aircraft said to have been targeted at Sanaa, the diplomatic content of the Yemeni delegation reportedly on board, and the operational chain between the Houthi political command in Sanaa and the launch crews that fired whatever hit Abha. These are not minor gaps. They are the facts the next 72 hours of reporting will fill in, or fail to. Until then, the structural frame holds: the 2022 truce is a shell, and the war is being fought in the airspace above the same two cities it has been fought in for a decade.

This publication framed the 13 July strikes as the predictable failure of a confidence-building instrument, rather than as a fresh start to the war, because the source material consistently points to a slow erosion of the 2022 framework rather than a discrete decision by either party to resume large-scale hostilities.

Notes on sourcing. The principal inputs are the Telegram threads of Intel Slava, Tasnim News English, Al-Alam Arabic, and Palestine Chronicle, all dated 13 July 2026. None of these is a tier-one Western wire, and the picture they draw is asymmetric toward the Houthi and Iranian framing of the day's events. The Reuters / AP / AFP of the Saudi position is not present in the thread context. A reader seeking a fuller picture should treat the Al-Bukhaiti statements as on-the-record primary source material from one side of the conflict, and the Palestine Chronicle's account of the Iranian aircraft as one version of the trigger for the Saudi Sanaa strike rather than as an established chronology.

Wire provenance

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

• https://t.me/intelslava
• https://t.me/tasnimnews_en
• https://t.me/intelslava
• https://t.me/intelslava
• https://t.me/alalamarabic
• https://t.me/alalamarabic
• https://t.me/PalestineChronicle
• https://t.me/PalestineChronicle