Nine Hundred Kilometers to Riyadh

Between Sunday, September 13, and Saturday, September 19, 2026, Yemen’s Houthis fired missiles or drones into Saudi Arabia on six of seven days. The Saudi authorities described what reached the ground. On the night of September 12 to 13 a projectile came down in Al-Tuwal, a town in the Jazan region a few kilometers from the Yemeni border, wounding two people and damaging a mosque. On September 14 ballistic missiles and drones aimed at Khamis Mushait, Abha and Taif wounded 13 civilians and damaged seven houses and two vehicles, according to the coalition spokesman, Brigadier General Turki al-Maliki. On the evening of September 15 the coalition shot down a drone south of Mecca before it could enter the airspace around the holy city, the second such attempt since 2017. On September 17 debris from an intercepted drone killed a Yemeni resident of Taif, the first death Riyadh has announced in a month that had already produced 86 wounded. And overnight on September 18 to 19 the Civil Defense sent air-raid alerts to phones in Riyadh and in Al-Kharj, 80 kilometers to the south-east, for the first time since the Houthis declared their maritime embargo on Saudi shipping in July. Two explosions were heard in Olaya, the capital’s business district. At daybreak Reuters and AFP photographed a column of black smoke rising from the fuel depot at King Khalid International Airport, and an AFP journalist saw firefighters at a burnt-out Saudi Aramco fuel tank. The coalition said one ballistic missile aimed at Riyadh had been intercepted. It said nothing about the tank. That is the whole Saudi record.

Sanaa’s record is longer. The Houthi military spokesman, Yahya Saree, claimed dozens of ballistic missiles and drones on King Khalid Air Base at Khamis Mushait on September 14, hitting “hangars, radars, runways, ammunition depots” and inflicting “significant losses"; a second barrage on the same base on September 16; “large fires and extensive destruction” at Aramco’s facilities in Yanbu, the Red Sea port that has carried most Saudi crude exports since Iran closed the Strait of Hormuz, the same day; a ballistic missile into the King Fahd Industrial Port at Yanbu overnight on September 17 to 18; a Saudi F-15 shot down over Marib in central Yemen; an attack on Sharurah air base in the eastern desert; and, on September 19, “a large number of ballistic and cruise missiles and drones” on “sensitive sites” in Riyadh and on Yanbu once more.

Between those two accounts sits a great deal of silence. Aramco has said nothing about Yanbu or the airport tank. The Saudi defense ministry has said nothing about its bases. The Houthis have shown no photographs. So, as with the East-West Pipeline strike of September 10, the Middle East Forum went to the satellites.

How a Satellite Sees a Strike

Two kinds of sensors bear on the question, and it helps to know what each can and cannot do.

The first is thermal. Two American weather satellites, Suomi NPP and NOAA-20, carry an instrument called VIIRS that passes over Arabia four times a day, twice around midday and twice in the wee hours, and record every patch of ground 375 meters on a side that is hotter than its surroundings. Each detection carries a radiative power in megawatts, a measure of how much heat the fire was throwing at the moment the satellite went over. A gas flare at a refinery reads a few megawatts. A burning oil tank reads tens. The pump station that burned on the East-West Pipeline on September 10 read 61 megawatts on the first pass after the attack and was still burning 13 hours later. These records are public within hours, and MEF pulled every one of them over Saudi Arabia and Yemen from August 20 to September 19: 32,102 distinct detections. Most are ordinary. Refineries, gas plants, and oil fields flare every day of the year, and a great deal of what looks alarming on a fire map is a plant doing what it did last month. So each claimed target was tested not against silence but against its own prior month. The question at every site was the same: did anything burn here that was not burning before?

The second sensor is optical. A pair of European satellites photograph the same ground every two to five days at 10 meters a pixel in the same colors the eye would see from orbit. At that scale a hangar is a rectangle, a runway is a stripe, and a burned building is a dark stain. It cannot see a hole in a roof, a destroyed radar dish, or a single aircraft. It can see a burn scar, a crater field, debris across an apron, and smoke, and it can see whether a base looks the same on Friday as it did on Monday. For King Khalid Air Base, which sits where two satellite tracks overlap, MEF has frames from the mornings of September 11, 14, 16, and 18, bracketing both claimed strikes. For Riyadh it has a frame from September 16, three days before the fire; the next comes on September 21. For Yanbu the one frame in the window, on September 15, was 94 percent cloud over the refineries and was taken before the claims began.

Neither sensor can prove that a missile did not land somewhere. Both can say whether it left the kind of mark the Houthis describe. “Significant losses” to hangars and ammunition depots leave one, as do “large fires and extensive destruction.” Here is what the record holds.

Two Air Bases, Four Frames, Nothing

King Khalid Air Base, on the edge of Khamis Mushait in the southwestern mountains, is the Royal Saudi Air Force’s southern hub and the origin of most Saudi sorties into Yemen. It has been the Houthis’ favourite named target for a decade, and it is the base they claimed to have hit hardest this week: dozens of missiles and drones on September 14, another barrage on September 16, with hangars, radars, runways, and ammunition depots all struck.

If any of that had happened, the thermal record would show it. An ammunition depot or a fueled aircraft burning inside a hangar produces a fire that a 375-meter pixel registers from orbit at a few megawatts, and the next satellite pass was never more than three hours away. The record shows no detection within 15 kilometers of the base on any pass from September 13 to 19. The four optical frames, taken at about 10:50 in the morning on September 11, 14, 16, and 18, show the same runways, the same rows of hardened aircraft shelters on the northern dispersal, the same aprons. and the same cantonment. There is no scar, no crater field, no debris, and no smoke. Two dark patches on the September 16 and 18 frames each sit beside a white cumulus cloud and are its shadow.

The same holds for Sharurah, about 450 kilometers east across the desert, which Sanaa claimed to have attacked on September 13 without giving a date. Nothing burned within 30 kilometers of it all week, and its frame matches its baseline.

Ten meters a pixel leaves room for small things. A drone that punched through a roof, a damaged antenna, a vehicle: none of these would show in these frames, and Saudi silence about its bases is itself a choice. But the Houthis did not claim small things. They claimed a base wrecked twice in three days, and a base wrecked twice in three days does not look the same from orbit on the fourth.

Yanbu: A Fire That Could Be Either Thing

Yanbu is where the money is. The East-West Pipeline that feeds it has been shut since the September 10 strike. The energy analytics firm Kpler counts no crude loaded there since September 11, and Reuters reported on September 15 that Aramco had told European customers some September cargoes were canceled. Brent held above $100 a barrel all week. Anything that burned at Yanbu would matter to every motorist in the world.

Something did burn. On the refinery row south of the town sits an installation that flares routinely, reading two to 27 megawatts on most days of the past month. On September 16, the day of the first Yanbu claim, it read 47 megawatts at 13:13 local time. On September 17 it read 71 megawatts at 14:15, the strongest reading at that site in the 31-day record. On September 19 it was back to 29. The two crude terminals north and south of the industrial city, the tanks and jetties where the export barrels actually sit, registered nothing above 4 megawatts all week.

There are two ways to read that. One is that a Houthi warhead set process equipment or a storage tank alight on the refinery row and the fire was brought under control within a day or two. The other is that a refinery whose crude supply was cut off on September 10 was being restarted or reconfigured, and flared hard on the two days its operators changed the feed. A refinery flares when it has more gas than it can process, and a plant swinging between shut-down and start-up produces exactly that. At 375 meters the two readings are identical. The optical frame that would separate them arrives on September 20, and MEF will publish what it shows. Until then Yanbu is unresolved, and the burden sits with Sanaa: “extensive destruction” leaves a scar at 10 meters, and the frame will show whether there is one.

Riyadh: One Tank at the Airport

The Riyadh attack is the one the week will be remembered for, and the record supports less than either side has said. The capital is 940 kilometers from Saada, the Houthi heartland; the Civil Defense alerts covered Riyadh and Al-Kharj, which is home to Prince Sultan Air Base and the American forces stationed there; the all-clear came within the hour. The plume that Reuters photographed at daybreak rose from the fuel storage at King Khalid International Airport, north of the city, where two tank farms sit about three kilometers apart: a Saudi Aramco bulk plant of 24 tanks west of the terminals, and a smaller seven-tank fuel farm belonging to the airport itself to the south-west. The AFP eyewitness saw firefighters at one burned-out Aramco tank.

Which farm burned, how many tanks, and whether the fire came from a warhead or from the debris of the interceptor the coalition says it fired, will be visible on the September 21 frame, and MEF will report it. What can be said now is this. One tank at a bulk plant is a real loss and a real humiliation. Fuel burning at the capital’s airport, filmed from the highway, does more to a country’s sense of safety than a cut runway 900 kilometers away would. It is not “sensitive sites,” and the Houthis’ own account of “a large number of ballistic and cruise missiles and drones” has to be set against a Saudi count of one missile intercepted, two explosions heard and one tank on fire.

The Pipeline Stops Flaring

One more signal came from 900 kilometers east of the capital, and it points the other way. Since the September 10 strike, the flare complex at the head of the East-West Pipeline near Abqaiq had been burning at 400 to 980 megawatts a day, against a baseline of one to 22 in the month before. That is the thermal signature of a pipeline shut with nowhere to send its crude and its associated gas: the plant burns off what it cannot move. On September 18 that ended. The complex read 144 megawatts on the 02:44 night pass, three megawatts at 12:34 that afternoon and two megawatts at noon on September 19—in other words, a plant back at its ordinary level. The same day Reuters reported that three pumping stations had been damaged in the September 10 attack and that Riyadh aims to have about half the line’s capacity back within days.

The end of relief flaring is consistent with crude moving west again at a partial rate. It is also consistent with Aramco shutting in production upstream so that nothing needs flaring at all. Saudi output was already 6.24 million barrels a day in August, the lowest since 1990. The tanker schedule at Yanbu, not the satellite, will say which; if crude is flowing, ships will load within days. Either way, the head of the line is no longer burning off the kingdom’s exports.

Why the Target List Is the Story

Set the two records side by side and three things stand out.

The first is reach. In the first half of September, every confirmed Houthi impact on Saudi soil was within 200 kilometers of the Yemeni border, in Jazan, Asir, and Najran. This week they were confirmed in Taif, on the approaches to Mecca, at Yanbu and, 940 kilometers from Saada, in Riyadh. In May 2019, when Houthi drones hit two pump stations on the East-West Pipeline about 950 kilometers from Sanaa, the attack was treated as a watershed. This week matched that range with ballistic missiles and repeated it on consecutive nights.

The second is the target set. Every confirmed Saudi loss this week is civilian or economic: a mosque, houses, vehicles, a fuel tank. Every claimed military effect, the two air bases and the F-15, is either unsupported by the record or beyond its reach. That is not an accident of accuracy. The Houthis are not fighting for air superiority over the Yemeni border. They are fighting for leverage over Riyadh’s blockade of Hodeidah port and Sanaa airport, and they have learned since 2019 that a single tank fire at a capital’s airport moves oil markets and ministers more than a cratered runway at Khamis Mushait. The claims of military destruction are for the home audience. The civilian and economic strikes are the message to Riyadh.

The third is the defensive ledger. Two regional officials told the Associated Press on September 16 that Saudi interceptor stocks are running low and that Riyadh has asked France, Britain, Pakistan, and Egypt to deploy air defense systems to the kingdom. One added that the American stock has itself dwindled over six months of war with Iran. MEF’s own survey of regional missile defense reached the same conclusion from the inventory side: the radars see the missiles, and the interceptors run out. A Patriot PAC-3 round costs several million dollars and cannot be replaced for months. A Houthi drone costs tens of thousands and can be replaced next week. Saudi Arabia is spending the expensive one to stop the cheap one, at the far end of a supply chain Washington is drawing down for its own war.

That war is the context for all of it. Reuters reported on September 9, citing two Iranian sources, that Tehran had encouraged the Houthi attacks on the kingdom, while a Pakistani envoy carried a Saudi warning to Iran to rein its allies in; Tehran denied any hand on September 14. That same weekend, Houthi representatives meeting American officials in Muscat assured them that they would not attack United States ships in the Bab el-Mandeb. That is the tell. Sanaa wants Washington neutral while it works on Riyadh, and Tehran wants Saudi Arabia, the one Gulf producer with an export route that bypasses Hormuz, under fire from a client it can disown.

What Washington Has Done, and What It Should Do

Crown Prince Mohammed bin Salman called President Trump twice on September 10 asking for American strikes on the Houthis. The president declined and offered intelligence and targeting data instead; a senior official described the policy as “empowering our regional partners to take the lead.” CNN reported on September 19 that officials in both capitals are frustrated and that neither has a plan to reverse the Houthi advance. In the same week, and at Riyadh’s request to Washington, Israel began passing intelligence on Houthi forces to Saudi Arabia through American channels, and Central Command proposed a regional command to coordinate the response.

The administration’s restraint rests on two judgments: that the Houthis will leave American ships alone, and that Saudi Arabia can carry the fight with American intelligence behind it. The first is a Houthi promise relayed through Oman by a movement the United States has designated a foreign terrorist organization. The second is contradicted by the record above. With American targeting, Saudi aircraft are hitting the Hajjah coast and the edges of Hodeidah, and the Houthis are still reaching Riyadh. A strait that a militia has closed to one country’s ships by decree is not an open strait, whatever it says about American hulls.

One argument against doing more comes from Senator Edward Markey (D-MA), whose resolution, introduced on September 17 with Senator Jeff Merkley (D-OR), would block the $5 billion sale of 10,000 JDAM precision-guidance kits to Riyadh on the grounds that arming Saudi Arabia deepens a proxy war and Yemen’s humanitarian catastrophe. Yet, the week’s record refutes it. The party escalating against civilians is the one firing at Taif, a mosque in Jazan, and a civilian airport. Precision kits are what keep the Saudi response from becoming the mass-casualty events the senator fears; withholding them produces less accurate Saudi bombing, not less bombing.

Seven steps follow from the evidence.

Refill Saudi air defense now. The president can draw down PAC-3 and THAAD interceptors from American stocks under existing authority, with an expedited sale to replace them, and can ask allies with Patriot stocks to backfill as they did for Ukraine. An interceptor shortage in the kingdom is a shortage in the one country whose exports still reach the market without passing Hormuz.

Vote down the Markey resolution. Congress should send the opposite signal to the one Sanaa is reading.

Turn the intelligence relay into a standing regional cell. Central Command’s proposal should become a permanent cell with Saudi Arabia, the United Arab Emirates, Egypt, Jordan, and Israel, which has sat in Central Command’s area of responsibility since 2021. Israel’s part should be sequenced: intelligence first, which is already happening; then radar and track sharing, so that a missile leaving Saada is seen by every sensor between Eilat and Riyadh and the Saudi operators know which interceptor to spend; and any kinetic role only at Saudi request and with the discretion Riyadh has asked for. Israel has struck Houthi targets at Hodeidah and Sanaa on its own account since 2024 and holds the region’s deepest file on the movement. The Saudis need that file more than they need to be seen taking it.

Escort Saudi-linked shipping. The Fifth Fleet should extend escort to Saudi-flagged and Saudi-chartered tankers between Yanbu and the Gulf of Aden and say so publicly. Whether Houthi shore batteries then fire on an American escort is Sanaa’s decision, and it ends the Muscat pretense either way.

If they fire, strike the launch sites. The Hodeidah, Mocha, and Perim littoral is within reach of the carrier aviation already in theater. The targets are shore batteries and launch positions, not the city.

Put Iran’s hand on the table. When the president meets Gulf leaders in New York on September 22, the Houthi campaign should be treated as part of the Iran negotiation, not a sideshow to it. No arrangement on Hormuz should leave the Bab el-Mandeb in Houthi hands or the ban on Saudi shipping in force.

Ask Riyadh to publish. Aramco’s silence on Yanbu and the airport tank leaves the field to Saree. In September 2019 Saudi Arabia laid out the Abqaiq debris for the world’s cameras within four days. It should do so again. A government that shows the world one burned tank has a better story than a militia that claims a wrecked air base and shows nothing.

What to Watch

Four things in the coming week will test the reading above. First, the Yanbu frame due on September 20: a burn scar on the refinery row means a hit; a clean plant means a restart. Second, the Riyadh frame due on September 21: which tank farm, how many tanks, and whether the debris pattern points to a warhead or an interceptor. Third, the tankers: if crude loads at Yanbu in the next few days, the end of flaring at Abqaiq meant the line was running again; if not, it meant the kingdom shut its wells in. Fourth, Al-Kharj: the alerts on September 19 covered the town that hosts Prince Sultan Air Base and its American contingent. The Houthis have promised Washington they will not attack American ships. They have made no such promise about American airmen 80 kilometers from the Saudi capital, and the night they test that promise is the night the administration’s policy is decided for it.

The satellites say the Houthis hit houses, a mosque, and one fuel tank this week and missed or never reached the bases they claim. That is not a reason for Washington to relax. It is a reason to act while the damage is still small.

Method note: Thermal detections are VIIRS 375-meter active-fire records from Suomi NPP and NOAA-20, obtained from NASA’s GIBS service for August 20 to September 19, 2026 and processed by the Middle East Forum; 32,102 unique detections after removal of tile duplicates. Each site is tested against its own detections in the prior 24 days. Radiative power is measured at the moment of overpass and is not a measure of damage. Optical frames are 10-meter true-colour scenes; the King Khalid Air Base frames were acquired at 10:44 to 10:55 local on September 11, 14, 16, and 18; the Riyadh frame at 10:42 local on September 16. Site functions are read from undated commercial basemap imagery and OpenStreetMap and have not been confirmed by Saudi Aramco. Records for September 19 were incomplete at the time of writing (22:00 UTC); the night passes over Riyadh had not yet been published. Casualty figures are those of the Saudi authorities. All MEF measurements are unaudited and offered alongside, not instead of, official statements.