Sanaa airport hit, Abha targeted: a Monday afternoon exchange between Yemen's armed forces and Saudi warplanes
Yemeni armed forces say Saudi airstrikes struck Sanaa International Airport at 13:54 local time; hours later the Houthis claimed missiles and drones at Abha.

At 13:54 local time on Monday 13 July 2026, Saudi warplanes carried out airstrikes on Sanaa International Airport, according to a written statement released by the spokesman of the Yemeni Armed Forces, Yahya Saree. The strike, the statement said, struck an airport still handling humanitarian flights and was timed to deepen what the Houthis describe as a siege on the Yemeni population. By 19:16 UTC on the same day, the same armed forces announced that they had engaged Saudi warplanes over the airport in retaliation, and by 19:44 UTC, Houthi channels were claiming ballistic-missile and drone launches against Abha International Airport inside Saudi Arabia, framed as a response to the Sanaa strike.
The exchanges matter for two reasons that travel further than the war itself. First, the airport is not a battlefield in the conventional sense: the Yemeni armed forces and their spokespeople have consistently framed Sanaa International Airport as the entry point for civilian humanitarian traffic into a country where the United Nations and humanitarian agencies have run the world's worst aid operation for most of a decade. Striking that infrastructure puts an immediate question to the Saudi-led coalition: was the military objective worth the civilian cost. Second, the simultaneous claim of an attack on Abha, a civilian airport in the Saudi southwest serving the city of roughly comparable population to Sanaa, narrows the gap between the two sides' exposure. Each side's commercial gateway to the world now sits inside the other's reach.
What Sanaa's armed forces say happened
The principal document on the record is the statement issued by Yahya Saree, the Houthi-run armed forces spokesman, carried verbatim by Telegram channels including Middle East Spectator at 18:45 UTC on 13 July 2026. It places the airstrike at precisely 13:54 on Monday afternoon and characterises the Saudi action as an act of aggression aimed at prolonging what the statement calls the unjust siege of the Yemeni people. A second statement, posted by the same armed forces and relayed by Fars News and Al Alam Arabic at roughly 18:47 UTC and 18:58 UTC, adds a diplomatic note: Sanaa formally thanks the Islamic Republic of Iran for assistance the armed forces say was decisive in opening the airport to humanitarian traffic after a prior closure. The third statement, posted by The Cradle and The Cradle Media at 19:16 UTC, claims engagement with Saudi warplanes over Sanaa in response to the airstrikes. The phrasing of all three statements is consistent and appears coordinated; the substantive content, the timing, and the choice of language to describe the Saudi action as aggression against a humanitarian facility recur across them.
The counter-strike claim
At 19:44 UTC, the Houthi-aligned Telegram channel wfwitness published what is being read as the retaliatory strike: ballistic missiles and drones launched at Abha International Airport. The framing in the channel is explicit that this is presented as a response to the Saudi strike on Sanaa. Abha is a significant civil airport in the Asir region of southwestern Saudi Arabia, serving the regional capital and connecting to domestic and limited international routes. There has, as of the close of the source window, been no Saudi-led statement corroborating the Abha strike, and no independent on-the-ground reporting inside the kingdom of damage assessment. The ballistic-missile-and-drone combination is consistent with prior Houthi operations against Saudi and UAE targets over the past five years, several of which have been subsequently confirmed by Saudi air-defence statements and by debris analysis. The asymmetry is that confirmation tends to lag for strikes into Saudi territory; the Saudi state controls the official record, and Western wire reporting on Yemen reaches outside sources faster than inside-the-Saudi-kingdom reporting.
Why the airport itself is the dispute
The humanitarian framing is not a sideshow. Sanaa International Airport has, since 2016, been at the centre of recurring legal disputes over who controls Yemeni airspace and over the civilian traffic that does and does not move. The Saudi-led coalition has historically restricted flights into Sanaa through its control of the airspace over north-western Yemen; the International Committee of the Red Cross and UN agencies have repeatedly negotiated limited windows of operation through Sanaa for medical evacuation, aid delivery, and UN staff rotation. When the Yemeni armed forces describe the Saudi strike as an attack on humanitarian flights, the claim is that the airport is functionally operating as a humanitarian corridor even when it is also serving civilian aviation, and a strike on the runway or on airport infrastructure sets back a process that takes months to negotiate.
The Iranian dimension of the Sanaa statements, easy to skim past, is the substantive one. The Yemeni armed forces' thanks to Tehran for assistance in reopening the airport inserts a specific dispute about who, regionally, has the standing to assist Yemen's civilian population. Saudi Arabia and the United Arab Emirates have historically held that any external facilitation of Yemeni civilian life should run through the coalition or through UN-coordinated logistics; an Iranian role, however indirect, inside an airport that the coalition considers its own zone of air control is the kind of detail that ends up in diplomatic notes filed in Riyadh, Abu Dhabi and the Gulf capitals that follow such statements.
What the records do not yet show
The sources do not contain casualty figures from the Sanaa strike: the Yemeni armed forces statements record that an airstrike took place and characterise the target as the airport, but the available thread does not include a health-ministry toll, runway-damage imagery, or independent satellite-product confirmation. The Saudi side has, at the time of writing, not issued a statement carried in the thread contradicting or contextualising the Sanaa strike, and likewise has not confirmed or denied the Abha strike. Independent wire-service reporting from Reuters, Associated Press and the established Western outlets is not present in the available thread, which means the framing on both sides still rests on aligned Telegram channels: wfwitness and The Cradle on the Houthi side, Fars News and Al Alam Arabic carrying Sanaa's statement and its Iran acknowledgement, and Middle East Spectator and DD Geopolitics relaying the armed forces text.
The sources do not specify whether the Abha strike landed, where exactly it was aimed inside the airport perimeter, or whether Saudi air defence engaged it. They do not specify whether civilian aviation was disrupted in either country, and they do not include statements from UN agencies, the International Committee of the Red Cross, or the Saudi-led coalition's joint command. A definitive account of what happened at 13:54 Sanaa time, and what hit Abha later in the evening, will require the wire filings, the Saudi state media acknowledgement or denial, and any airport-authority statements that the next 12 to 24 hours make available. Until those arrive, the Yemeni armed forces statements stand as the primary, on-the-record account of their own strikes and of the airport hit they say precipitated them, and they should be read alongside the conspicuous absence of a contradicting Saudi position rather than in place of one.
What it adds up to
The structural pattern is straightforward: an airport-to-airport exchange, in which the humanitarian framing of one side and the security framing of the other are both partly true and partly instrumental, and in which the role of external state assistance inside civilian infrastructure inside north-western Yemen is being formally recorded by the Yemeni armed forces themselves in language that appeals to a regional audience. Sanaa's thanks to Tehran is a sentence that travels. Saudi silence on a strike on the airport it has, at various points since 2015, defined as a target of military operations is a different kind of sentence, and will be read differently again if Saudi air-defence statements land in the next day. The shape of the next 24 to 48 hours is the wire confirmations, the Saudi-led coalition statement or its absence, and any UN-coordinated humanitarian statement on the airport's operating status. Until then, the record on this page is the record of what the actors involved say happened, in the order that they said it, with the gaps where the silence is itself a signal.
*Desk note: Monexus framed the exchange as Yemeni-armed-forces-claim first because that is the side on the record in the available thread, and carried the Saudi and coalition positions as the conspicuous gaps. Where independent Western-wire corroboration is absent, this article has said so rather than imported a frame.
Wire provenance
This editorial synthesis draws on the following public wire/social posts:
- https://t.me/wfwitness
- https://t.me/thecradlemedia
- https://t.me/farsna
- https://t.me/alalamarabic
- https://t.me/DDGeopolitics
- https://t.me/Middle_East_Spectator