Saudi Arabia's public missile alerts went quiet for 13 days while strikes on Riyadh's main airport killed at least 18 people in a week. This issue walks through rebuilding an attack timeline from flight-tracking playback and NOTAMs when a state stops publishing one. Riyadh is the proof: the alerts stopped, filming carried legal risk, and the aircraft kept a public clock.
Intercept Strikes on King Khalid International killed at least 18 people in a week, and the deadliest, on 10 October, came with no public alert. The last civil defence warning had gone out on 29 September. When did the open record hold enough to see it coming? |
Signal Flight-tracking playback and NOTAMs hold an airport's own timeline, stamped in UTC and independent of any ministry statement. The departures board usually gets read as background. Here is how to read it as evidence. |
Shadow Official statements this week described interceptions and an "unidentified projectile", while the aviation record shows an airport that kept closing. Proving who fired is out of reach from the outside. Documenting the gap between the two accounts is not, and here is how. |
| 01 | Section 01 of 03 · Intercept Riyadh's deadliest airport strike came after 11 days without a public alert |
|
On Saturday 10 October a strike on King Khalid International Airport in Riyadh killed 12 people and injured 309, according to Saudi Arabia's General Authority of Civil Aviation (GACA). India's embassy later said an injured Indian national had died, taking the toll to 13. The Houthis claimed the attack. The next day a projectile hit Terminal 4, and GACA reported one dead and 11 injured. Reuters counts at least 18 people killed in attacks on the airport in one week, and reports that Saturday's strike came with no alert from the kingdom's warning system.
| 7 Oct | Saudi officials: attacks on Riyadh and Abha airports kill three |
| 8 Oct | Large blast at King Khalid International; departures halted, passengers evacuated |
| 10 Oct | Deadliest strike: 12 killed, 309 injured (GACA); toll later 13 |
| 11 Oct | Projectile hits Terminal 4; one killed, 11 injured (GACA) |
| Alerts | Last civil defence alert 29 Sept (Najran); next alerts 12 Oct |
| At least 18 dead at one airport in a week. No public alert before the deadliest strike. |
The open record was not quiet. On 30 September the European Union Aviation Safety Agency issued Conflict Zone Information Bulletin CZIB-2026-09, telling operators to avoid part of the Jeddah flight information region and citing Houthi missile and drone activity against aviation-related targets. On 6 October the Interior Ministry warned that filming, publishing or sharing information about interceptions and impact sites exposed people to legal liability. On 8 October the Houthis warned airlines operating in Saudi airspace "for the last time", and Flightradar24 said the Riyadh airport had closed again.
So when did the open record hold enough to flag Saturday's strike? By 8 October, two days before it. By then it held a named threat to airlines, an EASA advisory on the airspace, deadly strikes on the Riyadh and Abha airports on 7 October, a further blast and closure at Riyadh on 8 October visible in public flight data, and a civil defence X account with no alert since 29 September. None of it required access to Saudi air defence systems.
Do this now Open Flightradar24 today and play back King Khalid International (RUH, ICAO OERK) for 8 and 10 October. The free tier keeps seven days of history, so Saturday's window starts closing on 17 October. Screenshot each frame with the UTC clock visible and log every query. Captured now, those frames give everyone on the story a timeline independent of official statements. |
Saudi rules since March 2026 restrict imagery of interceptions and impact sites, the US Mission warned on 12 October that Americans had been detained over photographing attack sites, and alerts can stop without explanation. When the eyewitness layer shrinks, transponders, NOTAMs and airline schedules become the record we can all still stand on.