Saudi strikes hit Yemen oil depots as airport attacks put civilians at risk

Saudi Arabia struck the Central Sabaha Station oil depot on Sana’a’s outskirts and Houthi oil depots at Ras Isa port in Hodeidah on Tuesday, October 13, 2026, according to the Guardian. The attacks followed deadly Houthi strikes on King Khalid International Airport in Riyadh. Exact strike times, verified depot damage and casualties at either fuel site remain unestablished.⁠1

The strongest additional corroboration concerns Sana’a. The Associated Press reported new strikes through residents as well as Houthi-run broadcaster Al Masirah. Al Jazeera described explosions shortly after the coalition’s evacuation order. That supports a warning-followed-by-strikes sequence, not a detailed assessment of what each weapon hit.⁠2⁠3

The Sana’a target appears under several names, including Central Sabaha Station and Al-Sabaha Central Station. Reporting places it at Al-Sabaha, west of the capital, and identifies a state oil-company fuel facility. The different renderings do not establish several separate targets.⁠1⁠9⁠10

The Yemeni Oil Company said the depot’s storage facilities were empty, the Guardian reported. That matters: hitting an empty storage site cannot automatically be described as destroying fuel stocks. The statement does not establish that the whole complex was empty of people, that its equipment escaped damage, or that no fuel was stored elsewhere.⁠1

The Saudi-led coalition called on civilians near the facility to evacuate and published a map identifying it. Coalition spokesman General Turki al-Maliki warned of “operations” without specifying their type; another warning account described evacuation as “for their own safety.” The complete continuous statement is unavailable.⁠6⁠19⁠20

Smoke was subsequently described over the station. Smoke alone cannot show how many tanks were damaged, how much fuel was lost or whether people were harmed. Likewise, the evacuation order proves neither that everyone could leave nor that everyone did. No verified depot casualty assessment establishes civilian deaths—or their absence.⁠10

At Ras Isa, the Guardian described ten strike waves. That remains a reported description, not an independently substantiated count. It does not tell us the number of aircraft or weapons, the number of destroyed tanks, or even how “wave” was defined.⁠1

The Guardian’s October 13 account attributes 13 deaths and 300 injuries to the Saturday, October 10 airport attack. An Associated Press source heading instead gives 12 deaths, but the accessible account does not supply the underlying casualty details or attribution. The difference remains unresolved; neither figure is an independently verified final toll here.⁠1⁠24

The Epoch Times reported on October 13 that airport attacks over the weekend killed at least 13 people and injured at least 309. That wider window is not an established correction of Saturday’s toll. Al Jazeera’s October 12 report separately described Sunday’s strike as killing one Pakistani national and injuring 11, citing a Saudi announcement. Those victims cannot responsibly be added to figures that may already include them.⁠25⁠26

Amwaj’s October 13 account described four airport strikes in five days and at least 18 deaths in the broader attack context, without allocating those deaths by strike or location. What is missing is a casualty ledger that separates incidents and explains any revisions. Different reporting windows are not interchangeable totals.⁠27

The airport is reported closed through at least Saturday, October 17. Amwaj supports that date, and the Epoch Times reports an extended closure, but the underlying Saudi aviation notice and its complete terms are unavailable. October 17 is a minimum reported closure threshold, not a guaranteed reopening date. Canceled flights, stranded passengers, repair costs and damage to particular airport systems have not been quantified in the available evidence.⁠1⁠25⁠27

Houthi military spokesman Yahya Saree warned employees and civilians near Saudi oil facilities to evacuate, calling the facilities “a legitimate target.” The New Arab names three threatened locations: Aramco facilities in Dhahran, Aramco facilities in Riyadh and King Khalid International Airport.⁠3⁠21

Nukta describes a conditional threat against Riyadh’s airport and an Aramco refinery if the coalition struck Sana’a, alongside a wider airport warning telling passengers not to travel and excluding Mecca and Medina. That exception concerns the airport threat; an equivalent exemption for oil facilities has not been established.⁠11

The warning’s exact timing is unsettled. Al Jazeera places it on Tuesday, October 13, while the New Arab’s October 13-dated account calls it a Wednesday warning. This inconsistency does not establish two separate warnings. Nor has a completed attack on the three named Saudi sites been verified as carrying out this particular threat. Fresh Houthi launch claims and coalition interception claims lack the chronology needed to settle that question.⁠3⁠21⁠28

The escalation also reaches Yemen’s land war. The Guardian reports that Houthi forces moved close enough to Taiz this week to fire rockets into residential areas, without supplying a mapped position, verified rocket count or resulting toll. The Independent describes a rapid Red Sea coast offensive and a claim of control over Bab el-Mandeb. Its precise extent is unestablished; this is not evidence that the Houthis control every shipping lane or have imposed a new blockade.⁠1⁠14

This is a later exchange than the airport fuel-depot fire we covered in September. On September 20, we reported a fire near King Khalid, flight disruption and a Houthi responsibility claim while the cause remained unconfirmed. On September 23, we reported the September 19 barrage, a burning fuel tank and no reported casualties at that depot. That earlier absence of reported depot casualties does not describe October’s deadly airport attacks.

The new reporting establishes that attacks on Riyadh and energy sites continued. It does not resolve the September fire’s cause, demonstrate successful hits at Jeddah or Yanbu, establish an outcome from Oman mediation or show a change in U.S. military action. The next fixed operational threshold is October 17: a reopening notice would establish restored airport operations; a calendar date alone will not.⁠1⁠27

The Guardian: strategic oil-depot strikes⁠1. Associated Press: Sana’a strikes reported by residents and Houthi media⁠2. Al Jazeera: Aramco and airport threats⁠3.

The Straits Times: strikes and retaliation warning⁠4. Al-Monitor: reported oil-site attack⁠5. Iran International: coalition evacuation order⁠6.

Gulf Business: evacuation ahead of an operation⁠7. Iran International: attack reported after warning⁠8. Siasat: Al-Sabaha facility⁠9.

The Monexus: reported depot strike and smoke⁠10. Nukta: conditional airport and refinery threats⁠11. The Japan Times: reported oil-site strike⁠12.

DW: Saudi–Houthi escalation⁠13. The Independent: Red Sea coast offensive context⁠14. Associated Press: Saudi air-defense context⁠15.

The Guardian: Saudi airport attacks explained⁠16. Ahram Online: coalition evacuation warning⁠17. Hamerintel: oil-site evacuation account⁠18.

Associated Press via Netscape: al-Maliki’s warning⁠19. Asharq Al-Awsat: coalition civilian warning⁠20. The New Arab: three threatened Saudi locations⁠21.

The National: Saudi response to airport attacks⁠22. The Independent: air-defense investigation⁠23. Associated Press: alternative airport death count⁠24.

The Epoch Times: weekend casualties and extended closure⁠25. Al Jazeera: Sunday airport casualties⁠26. Amwaj: repeated attacks and closure threshold⁠27.

Watan News International: launch and interception claims⁠28. TrackGulf: airport and regional-risk account⁠29. AviNews: aviation disruption context⁠30.