Riyadh Airport Was Closed for Safety Checks. Then It Was Hit Again.

Saudi authorities said the October 11 projectile struck Terminal 4, also described as Passenger Hall No. 4, and caused injuries. They gave no injury count. The previous day’s attack killed at least 12 people and wounded more than 300, some critically. Those hundreds of injuries belong to Saturday—not to the new terminal fire.⁠15⁠2

In our October 8 report, we described earlier Saudi airport attacks and disruption to Riyadh flights. What has changed is the much deadlier Saturday terminal attack, Sunday’s further impact and an expired closure deadline without a verified reopening. Secretary of State Marco Rubio has also confirmed that an American citizen was among Saturday’s dead, providing US-government confirmation beyond the Saudi-reported nationality list.⁠2⁠352

The Saudi-led coalition’s account contains two distinct assertions: an unidentified projectile hit Terminal 4 and caused a fire; air defences intercepted a missile near the airport. Coalition spokesperson Major General Turki al-Maliki specified a cruise missile in the account relayed by Saudi Gazette.⁠324⁠329

That statement does not identify what struck the terminal. Neither an intact missile nor interception debris has been established as the cause of Sunday’s fire. Emergency authorities responded, and damage and facility-safety assessments continued. No completed structural survey, quantified fire damage, injury-severity breakdown or confirmed Sunday death toll is available.⁠15⁠369⁠371

Saturday’s attack struck the domestic-terminal complex serving Terminals 3 and 4. Accounts placed an impact at Terminal 3 or near gate 401, but they do not amount to a complete damage map. Saturday was described as a missile attack; its precise weapon type and impact mechanism remain unresolved. Sunday’s description of an unknown projectile cannot simply be transferred to Saturday as proof that both incidents happened the same way.⁠83⁠62⁠64

Saturday’s exact toll is also unsettled. Reuters via Al-Monitor reported 12 killed and 309 wounded on October 11. BBC News that day gave 13 killed and 308 injured; The Guardian gave 13 killed and more than 300 injured. The later Reuters account still carried 12 and 309, so the difference cannot safely be dismissed as an older count superseded by a final one.⁠2⁠15⁠14

The Saudi aviation authority’s reported nationality breakdown accounts for 12 deaths: four Saudis, two Bangladeshis and one person each from the United States, Egypt, Jordan, Palestine, Syria and Sudan. It does not identify a possible thirteenth victim. Nor does the numerical change from 12 deaths and 309 injuries to 13 and 308 prove that a hospitalized patient died. No such individual medical outcome has been established, and the complete original casualty statement remains unavailable.⁠77⁠3⁠301

Earlier casualties need equally careful separation. Channel 4 News reported on October 11 that Thursday’s attack at the airport killed three; ABC News Australia’s October 11 account said two earlier attacks killed four. These cover different, incompletely reconciled periods—not two totals to add. Saudia captain Hamoud Ali al-Kalthami was reported killed in Thursday’s incident, not identified as a Saturday victim. Saudia said a parked aircraft was damaged and had no passengers aboard; that does not establish whether the captain was inside it.⁠16⁠27⁠57⁠60

The reported airport closure was extended until 9 p.m. Sunday, October 11, Riyadh time—18:00 UTC. By the reporting cutoff at 22:08 UTC, no timestamped official reopening notice or post-deadline extension had been established. Another relayed aviation-authority statement described an additional 24-hour suspension and used “until further notice,” but its publication time does not establish when that operational decision was made.⁠2⁠367

The disruption is extensive, but cancellation figures cannot be read as a recovery trend. Reuters via Al-Monitor cited at least 225 cancellations in 24 hours; an earlier FlightAware snapshot carried at least 291. The observation times and window endpoints needed to compare them are missing. The National’s later October 11 report listed more than 650 cancellations on Sunday—a calendar-day count, not necessarily the same rolling period. Its earlier report differed internally between “nearly 600” and “more than 600.”⁠2⁠83⁠339⁠309

Lufthansa Group’s announced Riyadh suspension ran through October 16, based on an October 8 spokesperson statement. Newer secondary reporting replaces Air India’s earlier October 10 endpoint with cancellations through October 15 and gives Air India Express a suspension through October 14. Direct notices were not available, and Docstox assigns those two dates in reverse order from Rajkaran and TravelTourister. These are reported carrier-specific extensions, not confirmed universal schedules or guarantees of next-day resumption.⁠315⁠335⁠316⁠332

Riyadh schools reportedly moved to remote learning, with The Guardian describing the arrangement as lasting until Thursday, October 15. The original education notice and precise coverage have not been established. Economist John Sfakianakis warned that insecurity could hurt tourism and perceptions of Saudi Arabia’s Vision 2030 diversification plans. That is a risk assessment; measured tourism losses or cancellations of Riyadh’s major business events have not been established.⁠14⁠24⁠18

Saudi Arabia and its coalition blamed the Houthis for Saturday. Earlier accounts said no fresh formal claim had appeared; Sunday reporting described the attack as Houthi-claimed. That strengthens the account of claimed responsibility, but a date-specific original statement identifying precisely which airport incident each claim covers remains unavailable. Neither a claim nor Iran’s support for the movement independently establishes the launch, weapon or command chain.⁠22⁠14⁠15

Houthi military spokesperson Yahya Saree warned airlines, workers and travellers away from Saudi airports and airspace, except Mecca and Medina. A reposted Friday message offered permission for humanitarian flights approved through a coordination centre in Sanaa. That conditional permission is neither a safety guarantee nor evidence that a flight operated.⁠21⁠22

The coalition called Saturday’s attack a war crime and promised a “decisive” response. Deliberate attacks on civilian objects are prohibited, but the coalition’s label is not a court judgment. Saudi Arabia has intensified strikes in Yemen; the Houthis describe their airport attacks as retaliation, which does not justify attacking civilian travellers. The Houthi-run health ministry’s claimed Yemen toll of 91 killed and 168 injured over five weeks remains independently unverified and separate from the airport casualties.⁠2⁠16⁠21

International support also requires a chronology correction. The official Saudi–Pakistani–Turkish emergency-meeting statement is dated October 5, not the October 12 date described in The Guardian’s October 11 account. It predates Saturday’s attack and calls for accelerated defence commitments and rapid deployment; it does not establish a completed new deployment after the attack. Britain described ground-based air-defence and air-to-air refuelling support—not new bombing missions in Yemen.⁠357⁠361⁠14⁠16

Donald Trump said the United States “may” join Saudi strikes after reviewing the attack. No new authorization, operational timetable or subsequent US strike has been established. The White House confirmed existing intelligence support and military experts; The Guardian reported about 200 advisers. That is not a count of newly arrived combat forces.⁠2⁠20⁠14

Washington has fought the Houthis before. Its 2025 campaign struck more than 1,000 targets—not necessarily 1,000 individual strikes—and reportedly cost more than $1 billion before ending following a US–Houthi agreement. Renewed direct combat could prompt further Houthi attacks on Bab al-Mandab shipping. That wider danger remains a risk, while Riyadh’s immediate requirement is concrete: a verified safety assessment and an operational notice passengers can rely on.⁠342⁠340⁠341⁠14