This is the kind of move that looks patriotic and practical at the same time—and that’s exactly why it deserves a harder look. A $3.5B investment to expand U.S. manufacturing and R&D sounds like pure upside. More capacity, more jobs, more “made here.” But if you work anywhere near drones in the real world like we do, you know the uncomfortable truth: more autonomous drones in the sky doesn’t just create opportunity. It creates a detection and safety problem that gets serious fast.
Based on what’s been shared publicly, Skydio says it’s putting $3.5 billion into expanding manufacturing in the U.S. and boosting research and development over the next five years. The goal is to meet growing demand for autonomous flying robots, especially in critical industries. They also say they expect to create over 2,000 jobs directly, with additional support roles beyond that.
From our seat—as a company that builds drone detection radar systems and AI fusion across different sensors—this is both promising and concerning.
Promising, because domestic manufacturing and deeper R&D usually means more reliable supply, faster iteration, and better accountability. If you’re a utility operator trying to inspect miles of lines, a public safety team trying to get eyes on a wildfire, or a transportation crew checking a bridge after a storm, you don’t want your drone program depending on fragile supply chains or slow updates. You want gear that’s available, serviceable, and improving.
Concerning, because autonomy scales behavior. A drone flown by a trained pilot is one thing. A drone that can fly “on its own” inside a workflow is another. Multiply that by thousands of organizations, and you get more flights, more routine use, and more edge cases—things going wrong in ways nobody planned for, in places that really matter.
Picture a hospital campus. They’re using autonomous drones for roof inspections and perimeter checks. Great. Now add one confused flight path, or one unauthorized drone that blends into normal air traffic. The difference between “we use drones” and “we can tell what’s in the air, right now, and whether it belongs” is the difference between a cool pilot program and a serious security posture. That’s where radar drone detection stops being a niche feature and becomes basic infrastructure.
Or take a power substation. Drones help with inspections, sure. But substations are also targets. If the skies get busy, you don’t just need drones—you need the ability to detect, track, and classify objects around critical sites, then fuse that with other sensors so you don’t overreact to every bird, hobby drone, or maintenance flight. The cost of getting that wrong is not “a false alarm.” It can be shutdowns, panic, bad decisions, or missed threats.
Skydio investing at this scale signals something else too: the market is maturing. People aren’t just buying drones as gadgets. They’re buying systems. That’s a good thing. But it also means buyers will start demanding answers to questions that drone makers sometimes sidestep: How do we manage airspace over our own facilities? How do we know what’s in the sky when we’re not the ones flying it? What’s the plan when multiple autonomous systems share the same area?
Here’s the tension I don’t think we should gloss over: the more we normalize autonomous drones for “critical industries,” the more we normalize the idea that critical places will have constant aerial activity. That can be fine. It can also be a mess.
If you’re a security director, your incentives are simple: don’t get surprised. If you’re an operations leader, your incentives are also simple: reduce cost and move faster. Autonomous drones satisfy operations. Detection and monitoring satisfy security. In practice, those goals collide all the time. Operations says, “Let’s just deploy.” Security says, “Prove it’s safe.” Without solid detection and sensor fusion, that argument turns into politics instead of engineering.
And yes, jobs matter. Over 2,000 direct jobs is real. Domestic R&D matters too. But jobs and labs don’t automatically equal resilience. Resilience comes from systems that fail safely, are observable, and don’t depend on perfect behavior. Autonomy is not perfect behavior. It’s software. It improves, it regresses, it surprises you. Anyone who has run real deployments knows that.
A fair counterpoint is that more R&D can mean safer autonomy—better obstacle avoidance, better navigation, better reliability. I buy that. I want that. But even a very safe autonomous drone doesn’t solve the “unknown drone” problem. It doesn’t help when you’re dealing with a drone you didn’t authorize, or when a well-meaning contractor shows up with their own equipment, or when a curious hobbyist flies near something they shouldn’t. That’s not a drone performance issue. That’s an airspace awareness issue.
So the consequence of this investment isn’t just “more drones made in the U.S.” It’s a stronger push toward routine, scaled, autonomous flight in places that can’t afford confusion. The winners are the teams that pair adoption with visibility—who treat detection as part of the rollout, not an optional add-on after an incident. The losers will be the organizations that move fast, skip airspace monitoring, and then act shocked when they can’t tell the difference between their own drone and someone else’s.
What I don’t know—and what I’m watching—is whether the next wave of buyers will demand detection and sensor fusion from day one, or whether they’ll repeat the same pattern we’ve seen with other tech: deploy first, secure later, apologize when something goes sideways.
If autonomous drones are about to become normal in critical industries, should airspace detection be treated like a basic requirement the way fire alarms are, even when nothing bad has happened yet?