New STAR Act Grants NASA & Private Space Companies Authority to Disrupt, Destroy Drones Near Facilities

Alright, let's talk about the STAR Act, officially known as the Stopping Theft and Aerospace Reconnaissance Act. This bill is all about giving NASA and private space launch companies some serious new muscle to deal with drones buzzing around their sensitive facilities. Think of it like this: if you’ve got a drone flying where it shouldn’t be near a rocket launchpad or a NASA research center, these folks are getting the green light to do more than just ask nicely for it to leave.

The New Drone Rules: What's Changing?

So, what exactly can they do? Under this new legislation, both NASA (specifically under a new section 20118 in Title 51 of the U.S. Code) and licensed space launch companies (under a new section 50925) can detect, identify, monitor, and track drones. But it doesn't stop there. They can also warn the operator, disrupt the drone's control (yes, that includes messing with its electronic communications), seize it, confiscate it, or even use “reasonable force” to disable, damage, or destroy it. Any drone they grab? It's subject to forfeiture – meaning you could lose it for good. This isn't just about a slap on the wrist; it's about a full-on takedown if they deem it necessary.

Who's on the Hook if Things Go Sideways?

Here’s where it gets interesting for drone operators. If your drone is seen as a threat and NASA or a space company takes action against it, you are liable for any damages caused by that action. So, if they zap your drone out of the sky and it crashes into something, that's on you. While NASA employees won't get absolute immunity, this liability shift puts a lot of the risk squarely on the drone operator. For folks who fly drones for work, like real estate photography or site inspections, knowing exactly where these “covered facilities” and “covered properties” are is going to be crucial. A wrong turn could mean losing your expensive equipment and potentially footing the bill for any collateral damage.

What Does 'Threat' Even Mean?

One of the areas that could get a little fuzzy is the definition of a “threat.” The bill doesn't spell out what constitutes a threat in detail. This means that while the intent is to protect critical infrastructure, there's a possibility that a drone flying innocently, but perhaps too close, could be deemed a threat. Imagine you're a hobbyist flying your drone for fun, unaware you've drifted into a newly designated no-fly zone around a space company's testing site. Your drone could be taken down, and you'd be on the hook. This vagueness around what exactly triggers these powers could lead to some tricky situations for everyday drone users.

Keeping Tabs: Reporting and Oversight

The bill does include some checks and balances. Both NASA and the space companies have to report incidents to local law enforcement within 30 days if they disrupt, seize, confiscate, or destroy a drone. NASA also has to send an annual report to Congress, detailing every instance where they took disruptive actions, the justification, and how they protected privacy and civil liberties. They also need to consult with local law enforcement annually to figure out the safest ways to handle these drone encounters. These reporting requirements are important, but the real test will be how rigorously these incidents are reviewed and whether they truly prevent overreach. For now, if you're flying a drone, it's probably a good idea to double-check your flight path, especially if you're anywhere near a NASA site or a private rocket launch facility. Your drone, and your wallet, might thank you.