When the Airport Becomes the Target: What Riyadh and Abha Just Taught Every ARFF and Police Leader

3 days ago

4 min read

Over the past two weeks, airports in Saudi Arabia have been attacked again and again. Before talking about lessons, it's worth saying plainly: people died. Travelers, workers, and residents went to an airport and did not come home. Our thoughts are with their families, the injured, and the responders who have worked this event for days.

This post is not about the conflict behind the attacks. It is about what the pattern means for those of us who plan airport emergency response.

What happened

Here is what has been reported, based on Saudi official statements carried by news outlets:

Oct. 5: An attack on King Abdullah bin Abdulaziz International Airport in Jazan injured three people (Arab News, citing the coalition).
Oct. 6: An attack on Abha International Airport, near the Yemen border, killed two women and injured 28 (BBC and Arab News, citing Saudi civil aviation authorities).
Oct. 7: An attack on Riyadh's King Khalid International Airport killed one person and injured eight.
Oct. 8: Another attack on King Khalid killed three people and injured five, according to coalition figures reported by Arab News. The National reported that a Saudia aircraft was damaged.
Oct. 10: A missile struck King Khalid, killing 13 people and injuring 309. Airport operations were suspended, and flights were cancelled or diverted (The National; Anadolu Agency).
Oct. 11: A projectile struck the terminal area at King Khalid, killing one person and injuring 11.

Najran and Dammam airports were also reported hit or damaged. Anadolu Agency counted 10 attacks on five Saudi airports from Oct. 5 to 11. On Oct. 15, the coalition spokesperson said King Khalid alone had faced 20 attacks since Oct. 1. He put the total from attacks on airports at 19 dead and 364 injured. The Houthis claimed responsibility for many of the attacks, and Riyadh's airport operations remained suspended into this week. The event is still unfolding.

Exact counts differ a little from outlet to outlet, which is normal in a fast-moving event. I've used the official figures as reported, with dates.

The planning gap

I've run tabletop exercises for a lot of worst-case scenarios, and the uncomfortable truth is most airport emergency plans assume one bad event, not a sustained, multi-day, multi-site attack.

That is not a criticism of anyone's planners. It reflects how we build and exercise plans. A typical full-scale exercise has one start time, one scene, one surge of patients, and one hotwash. We practice the first two hours very well. We rarely practice day three.

Riyadh shows what day three looks like. The same airport was struck repeatedly in a few days. Operations were suspended, and the suspension was extended.

What a continuity branch should cover

A continuity branch is not a separate plan. It is a section of your existing ARFF, police, and Emergency Operations Plan (EOP) that answers one question: what if this happens again tomorrow, or somewhere else at the same time?

Here are the areas I'd look at first:

Crew endurance and relief. Who relieves your first-due ARFF crews and patrol officers on day two? On day four? Map it by name and shift, not by hope. Fatigue becomes a safety problem fast.
Apparatus, agent, and equipment readiness. After a major fire, how quickly can you restore foam, medical supplies, and out-of-service apparatus? Who is your backup if your own units are committed?
Mutual aid that lasts. Most mutual aid agreements are built for a surge. Ask partners what they can sustain for a week, and what they need back from you.
Hospital and mass-casualty partners. One strike in Riyadh injured more than 300 people. Talk with your hospital partners about repeat surges, not one.
Reopening decisions. Your EOP should spell out who decides to resume operations, on what criteria, and who decides to suspend them again. Write the trigger points down before you need them.
Multi-site coordination. If an airport in your region and one in a neighboring city are hit on the same day, who coordinates resources? The answer should not be made up during the event.
Responder wellness. Repeated incidents wear people down. Build peer support and family support into the plan, not as an afterthought.

How to test it

You don't need a new exercise program. Take the tabletop you already have and add a second inject: the incident is over, the hotwash is scheduled, and then it happens again, at your airport or a nearby one. Then add a third, two days later. Watch where the plan runs out of people, equipment, or authority. That is your gap list.

Bottom line

Your ARFF and police response plans need a branch that assumes the threat doesn't end after the first incident, because in Riyadh, it didn't. If your plan hasn't been stress-tested against something that repeats, this is the week to schedule that review.