Who was behind the drone near Mecca?

Highlights:

• Saudi Arabia says a Houthi drone was intercepted near Mecca.
• Houthis deny targeting the holy city.
• Analysts say it may have been headed for another Saudi target.
• No evidence links a third party to the incident.
• The drone's origin and intended target remain unconfirmed.

The Saudi-led coalition says it intercepted and destroyed a Houthi drone south of Mecca before it entered the holy city's restricted airspace. But the Houthis have categorically denied targeting Mecca, leaving a key question unanswered: where was the drone actually headed and who was responsible for sending it?

Saudi coalition spokesman Turki al-Malki said the drone was intercepted on Tuesday before entering prohibited airspace around Mecca and described the security of Islam's two holiest sites as a "red line". Saudi Arabia called the incident a Houthi attempt to target the holy city. The coalition also said it was the second alleged Houthi attempt to target Mecca, following a ballistic-missile incident in 2017. Reuters reported the Saudi account, while the BBC said the Organisation of Islamic Cooperation condemned what it described as an attack on Mecca.

The Houthis, however, rejected the allegation. Houthi political bureau member Mohammed al-Farah described the claim as "an outright lie with no basis in truth", according to the Houthi-run Saba news agency, and accused Riyadh of exploiting the incident to divert attention from the war in Yemen. Middle East Monitor separately reported a Houthi military source categorically denying any threat from Yemen against Mecca or other Islamic holy sites.

That leaves open the possibility that the drone was headed towards another target and happened to approach Mecca. Analysts at the Institute for the Study of War (ISW) assessed that the drone may have been targeting Saudi military or oil infrastructure near or north of Mecca rather than the holy city itself. ISW said it was unlikely that the Houthis deliberately targeted Mecca, noting that the city has few military or economic targets and that such an attack would risk widespread condemnation. It said a drone launched from western Yemen could have approached Mecca while travelling towards a target farther north, such as Yanbu.

Saudi air defences intercept Houthi drone near Mecca; rebels deny attack

But the Houthi denial also warrants scrutiny. The group has a documented record of launching drones and missiles against Saudi military and energy targets. Reuters reported that, around the same time as the Mecca incident, Houthi military spokesman Yahya Saree claimed attacks on Saudi targets including the Red Sea oil port of Yanbu and Khamis Mushait airbase. The Houthis said they had also shot down a Saudi F-15 fighter jet, although Reuters said no immediate evidence was presented for that claim.

On September 16, the Houthis claimed that they had carried out missile and drone attacks against a Saudi Aramco facility in Yanbu and the Khamis Mushait airbase. Those claims, too, were not independently verified at the time. This does not prove that the Mecca-bound drone was Houthi-launched, but it establishes that the group was conducting attacks against Saudi targets during the same period.

There is also a broader reason to treat the Saudi claim cautiously. A viral video circulated online purporting to show the interception over Mecca was found by a Pakistani fact-checking organisation to be old footage from 2025 showing an object over Medina, not the latest incident. That does not disprove the Saudi military's account, but it demonstrates how quickly unverified material surrounding the incident has spread.

Could a third party have been responsible?

There is no publicly available evidence at present linking any third party to the drone. Nor have the BBC, Reuters or Middle East Monitor attributed the incident to any country. The suggestion that Israel might have staged or facilitated an attack to deepen tensions between Saudi Arabia and the Houthis therefore remains speculation rather than an established explanation.

Israel does have at least one officially documented historical case of a false-flag operation: the 1954 Lavon Affair, in which Israeli military intelligence recruited Egyptian Jews to carry out bomb attacks against Egyptian, American and British civilian targets, intending to make the attacks appear to have been carried out by other groups, according to Israel's own Ministry of Defense archives.

That historical record establishes a documented Israeli false-flag operation in 1954, but it does not provide evidence that Israel was involved in the Mecca incident.

Bangladesh condemns reported drone attack targeting Mecca, reaffirms support for Saudi Arabia

There is another relevant development. Middle East Monitor reported this week, citing Israeli and other sources, that Saudi Arabia may have sought Israeli intelligence assistance through US Central Command as the Houthi threat has intensified. The report said the alleged assistance involved intelligence and threat mapping, not Israeli military intervention, and stressed that neither Riyadh nor Jerusalem had confirmed the reports.

This makes the incident particularly sensitive. Saudi Arabia is already fighting an escalating Houthi campaign against its territory, while the wider Middle East conflict has brought multiple regional actors into direct or indirect confrontation.

For now, however, the publicly available evidence establishes that Saudi Arabia says it intercepted a Houthi drone south of Mecca and attributes it to the Houthis, while the Houthis deny targeting the holy city. The Houthis have a documented record of attacking Saudi military and energy targets, but some of their contemporaneous claims have not been independently verified. That makes their denial a claim requiring scrutiny, just as the Saudi attribution requires evidence.

Whether the drone was actually headed for Mecca, another Saudi target, or was launched by a third party remains unproven.

Further evidence -- such as debris analysis, the drone's model and origin, its flight path, launch-site intelligence or independent satellite data -- would be needed to determine who was behind the incident.