Two Riyadh airport terminals reportedly reopen. Flights are another question.

Two terminals are reported back in use at Riyadh’s King Khalid International Airport after more than two weeks of disruption. That is a significant opening for passengers and airport workers after deadly attacks—but it is not yet evidence of a functioning, sustained commercial restart. Saudi Arabia said the terminals reopened on Sunday, October 25; how many aircraft actually took off or landed remains unestablished. ²

The reported arrangements assign Terminal 1 to domestic flights and Terminal 2 to international flights operated by Saudi national carriers. That qualification matters: this was not an announcement that every international airline would return. Time Out Riyadh lists Saudia, Flynas, Flyadeal and Riyadh Air, while advising passengers to confirm their booking status with their airline before travelling to the airport. Inclusion in those arrangements does not establish that a carrier operated a flight that day. ^{5 7}

On October 13, HeyDay News reported repeated deadly attacks at the airport, suspended operations and no confirmed reopening. The new reports change the terminal status. They do not settle the scale of resumed service, explain how the airport’s defenses were breached or resolve the cause of a subsequent terminal fire.

There are three separate steps here: authorities clear a terminal for use, an airline decides to operate, and an aircraft completes its departure or arrival. Reports of the October 25 reopening support the first step. They do not provide a complete record of the other two. The original dated airport or aviation-authority reopening notice has not been independently authenticated; the terminal arrangements rest on published accounts of that announcement. ^{5 11}

The Independent described little traffic on Flightradar24 on Sunday. Other secondary reporting described a handful of Saudi-airline departures. Neither supplies a flight-by-flight list with identifiers and actual movement times sufficient to establish the day’s total. The available October 26 tracking snapshots likewise do not demonstrate how much service operated on October 25 or whether the restart continued through Monday. ^{2 62 65 66}

That absence should not be turned into a claim that the airport remained completely closed. Sparse tracking displays are not comprehensive movement records, and an airport board without dated flight rows cannot prove that no aircraft moved. Aggregate counts also require care: RUH Watch assigns flights to their scheduled Riyadh date, even when a departure occurs after midnight. Such figures cannot simply be treated as calendar-day takeoffs and landings. ^{64 67 68}

The reported restart coincided with another warning from Houthi military spokesman Yahya Saree. Middle East Eye reported that he called King Khalid International Airport “unsafe” and a “military target.” Accounts of the warning addressed international, regional and local airlines, airport employees and travellers, urging them not to use it. ^{43 45}

The statement was reported as having been issued on Saturday evening, around the reopening announcement, although its original timestamp has not been authenticated. The supported quoted wording is “unsafe” and “military target,” not the longer formulation that the airport would “never be safe.” The warning makes the group’s declared threat explicit; it does not independently establish the airport’s security condition or prove that another attack occurred. ^{43 48 50}

The Houthis claimed responsibility for the October 10 assault preceding the suspension. That claim is not a forensic explanation of the attack or independent proof of who launched the weapon. The reported casualty account began with 12 deaths. BBC coverage subsequently cited the Indian Embassy in Riyadh as saying an Indian national died of injuries on October 11, bringing that account to 13. ^{15 17}

The initial dead included four Saudi citizens, two Bangladeshis and one person each from the United States, Jordan, Palestine, Syria, Sudan and Egypt, according to the aviation-authority figures reported by the BBC. More than 300 people were reported injured; detailed accounts gave 309, but an exact, reconciled final injury total remains unavailable. ¹⁸

Those figures must not be confused with our October 13 report of at least 20 deaths across the preceding week’s airport attacks, including an American. That was a reported cumulative toll without a complete incident-by-incident accounting. The later figure of 13 concerns the October 10 assault alone, not a reduction in deaths across the series. A Khaleej Times account updated October 14 gave 14 deaths across the weekend attacks, but did not explain each incident’s contribution. These differently scoped numbers do not resolve the overall toll. ²¹

A separate October 11 incident involved an unidentified projectile striking Terminal 4, followed by a fire. The projectile’s identity and the fire’s cause remain unresolved. Reopening Terminals 1 and 2 is an operational development, not an explanation of what happened at Terminal 4. ¹⁶

Saudi Arabia also announced interceptions across several regions. CNN Arabic’s October 25 account attributed to coalition spokesman Major General Turki al-Maliki a breakdown of 10 ballistic missiles directed toward the southern region, one ballistic missile toward Riyadh, one cruise missile toward Khamis Mushait and one drone in the Riyadh region. That is a claim involving 11 ballistic missiles, a cruise missile and a drone—not 12 ballistic missiles. The weapon outcomes have not been independently verified. ⁵⁹

Separate October 24 reports described two ballistic missiles intercepted over Riyadh and Khamis Mushait. The reporting windows may overlap, so adding the announcements risks counting weapons twice. Nor is it established which interceptions, if any, correspond to Houthi claims of attacks on Saudi airports and oil facilities. ^{56 58}

Saudi Civil Defense said debris from two intercepted ballistic missiles injured two people in Khamis Mushait and Ahad Rafidah on October 25, damaging three residential buildings and seven vehicles. Those were reported casualties in southern Saudi Arabia, not at the capital’s airport. The statement does not identify which of the separately announced interceptions produced that debris. ^{52 60}

In Yemen, Houthi authorities alleged Saudi strikes hit residential areas and a cement factory in Sana’a. Yemen Press Agency reported a preliminary toll of 10 killed and 11 wounded, attributed to the health ministry in Sana’a. These are allegations of civilian casualties, not independently confirmed findings. ³²

Other accounts overlap without producing a reliable combined toll. The Times of Israel reported 11 deaths attributed to Houthi media; ABNA reported eight deaths at cement-factory workers’ accommodation; Dawn reported 16 across Sana’a and Hodeida. Some descriptions included six women and a child among the dead. DW separately reported an allegation of at least four deaths in “Huda province,” but it remains unclear whether that name refers to the Hodeida or Hodeidah used elsewhere. The figures cannot safely be added together. ^{34 38 37 1}

No specific Saudi admission, denial or explanation addressing those civilian casualty allegations is established in the available reporting. An interception announcement is not a response to an allegation about people killed in Yemen. ^{1 34}

For travellers, the immediate instruction is narrower than the reopening headlines: contact the airline and confirm the booking before setting out. Two terminals reportedly becoming available is a change worth reporting. Whether it becomes a dependable return to commercial service still requires identifiable flights, sustained operations and clear airline restrictions—not merely permission to resume. ⁵