The rising prevalence of drone incursions over U.S. military launch ranges poses a direct and escalating threat to national security, with a single errant or hostile unmanned aircraft capable of triggering multi-million-dollar launch scrubs and cascading delays across the entire space enterprise. In November 2024, a Chinese national flew a drone over Vandenberg Space Force Base for nearly an hour, photographing the installation after researching ways to bypass altitude limits. Two months later, a Chinese-born Canadian citizen made multiple drone flights over Cape Canaveral, capturing images of launch complexes and munitions bunkers. These rare prosecutions underscore a stark reality: most drone operators who violate restricted airspace are never caught.
The Expanding Threat Landscape
The commander of NORAD and U.S. Northern Command reported to Congress in February 2025 that 350 drone detections occurred over roughly 100 military installations in a single year. More recently, Barksdale Air Force Base, home to the nation’s B-52 bomber fleet, detected multiple unauthorized drone incursions prompting a shelter-in-place order. These incidents mirror the vulnerability of space launch ranges, where strategic assets are exposed to both careless operators and deliberate adversaries. The Eastern and Western Ranges supported 186 launches in 2025, with the Space Force projecting nearly 300 launches annually at the Eastern Range alone by 2030. More launches mean more exposure, creating expanded opportunities for disruption.
Operational and Economic Consequences
A scrubbed launch carries far more than schedule disruption. SpaceX has argued in litigation that a single scrub can cost approximately $4 million per day, while NASA’s Space Shuttle program previously estimated direct costs at $1.2 million per incident. Beyond financial impact, a drone collision during fueling or liftoff could cause catastrophic damage to infrastructure requiring years and millions of dollars to repair. Weaponized drones, as demonstrated in Ukraine and the Middle East, could carry explosives into fueled rockets or fuel storage, or be equipped for signals intelligence collection and cyber intrusion against range networks. No such attack has occurred on U.S. ranges, but current detection, tracking, and identification technology remains inadequate for the threat.
A Path Forward: Layered Defense and Shared Awareness
The U.S. launch enterprise must act on three simultaneous fronts. First, build shared situational awareness through a Common Operating Picture (COP) that fuses radar, RF detection, acoustic sensors, and other technologies into a single interface. No single sensor can catch every drone; radar misses small, low-flying targets, and RF detection fails against preprogrammed GPS routes. A layered defense merged into a COP allows range safety, security forces, FAA controllers, and law enforcement to act from a unified decision-support tool. Second, deploy properly funded counter-drone systems calibrated to the operating environment, avoiding proprietary displays that force defenders to reconcile conflicting data under time-critical conditions. Third, update the legal framework to enable rapid, lawful responses to drone interference with space launch operations.
What This Means
The damage from even a single drone-induced delay extends far beyond the rocket on the pad. Every satellite, crewed mission, and scientific payload has strategic relevance, and an adversary need not destroy a launch vehicle—merely delay it long enough to cascade schedule disruptions across the manifest. As drone costs decline and ease of use increases, the threat will only intensify. The difference between a careless operator and a hostile actor matters less than the outcome: a drone near a launch pad during countdown demands the same response—hold, scrub, or abort. The U.S. launch enterprise cannot afford to treat these incursions as nuisances. They are mission denial events that erode confidence in American launch range reliability at a time when global competition is accelerating.
— Originally reported by SpaceNews. Adapted and republished with editorial context for SpaceSecurityNews.
