The U.S. Department of Defense is watching Ukraine fight for its survival with a kind of agile, distributed, and improvisational use of drones that makes even the most advanced Western drone development programs feel sluggish. The recently launched "Project GI" by the Defense Innovation Unit aims to push U.S. drone makers to innovate more like Ukraine. But as promising as that is, deeper institutional obstacles persist. Chief among them are the rigid boundaries set by the Blue UAS list, and a fundamentally outdated logistics and acquisition structure that is misaligned with the speed, scale, and nature of modern drone warfare.
The Blue List Bottleneck
The Blue UAS list was designed with good intentions to vet and secure small UAS platforms for use by U.S. military forces and ensure compliance with cybersecurity, supply chain, and interoperability standards. But in practice, the list has become a barrier to entry for startups and smaller manufacturers that cannot afford the lengthy, expensive vetting process. If a platform is not Blue-listed, it often cannot even get into the room for a serious contract conversation.
This stifles innovation precisely when the U.S. needs to scale rapidly. The Ukrainians are fielding dozens of drone variants within weeks, tweaking designs daily based on feedback from the front. Meanwhile, U.S. vendors are still waiting for certification approval or navigating redundant security assessments. If the Blue List remains a prerequisite for procurement rather than a parallel track for risk mitigation, we will continue to fall behind adversaries who are not bound by such limitations.
The Key FPV Question: Munition, Robot, or Tool?
One of the most profound logistical dilemmas facing the Department is conceptual: what exactly is an FPV drone? Is it a munition? A piece of robotics gear? A training tool? That classification matters. A lot.
If the military designates FPV drones as munitions, they fall under the same handling, storage, and inventory rules as bullets and explosives. That means they require armory storage, serialized tracking, and controlled access. But FPV drones are not traditional weapons. They are modular, powered by off-the-shelf batteries, and require regular charging, firmware updates, camera swaps, and reconfiguration. The logistics burden is massive, particularly if these drones are being cycled through at scale.
Imagine a junior supply officer at a squadron-level logistics unit being told to manage 1,000 FPV drones. That officer is likely trained to handle rifles, radios, or rations, not digital flight controllers, antenna variants, or LiPo battery management protocols. They would be forced to apply a Cold War-era supply framework to a 21st-century technology that is closer in function to software-defined weapons than to traditional gear.
Training and Tolerance for Loss
Another challenge to tackle is the cultural mindset around losses in training. In a world of attritable drones, where the expectation is that many will crash, get jammed, or be destroyed in use, senior leadership must recalibrate what it considers acceptable loss.
If a young Marine crashes six FPV drones during training, is that seen as a waste or as a necessary cost of proficiency? Current supply and accountability structures might treat each crashed drone as a reportable loss, possibly triggering investigations or career repercussions. That mindset is incompatible with the reality of drone-centric warfare, where operators need hundreds of reps to become effective. We would never penalize a fighter pilot for burning jet fuel during flight hours. We should not penalize a drone operator for crashing cheap aircraft during training.
Batteries, Charging Cycles, and the Forgotten Backbone
Few people outside the drone community understand just how demanding battery logistics can be. Lithium polymer (LiPo) batteries, commonly used in FPV drones, are sensitive, prone to swelling, and degrade quickly if not properly cycled. They must be stored at specific voltages, kept within temperature ranges, and regularly rotated. Charging infrastructure alone can become a bottleneck if not planned for at scale. Also, energized batteries are a significant fire hazard, requiring additional storage considerations. A drone crashing with a fully charged LiPo battery is a fire risk, requiring additional range considerations in a similar manner as firing tracer rounds on a bone-dry range.
Drones might be cheap, but battery support systems are not. If we field 1,000 drones to a forward unit, do we also field enough chargers, storage cases, power converters, and replacement packs? Who maintains and inventories those batteries? Who teaches units about safe charging protocols and fire prevention? Logistics is where autonomy dies if not thought through from the beginning.
Battery sourcing is an understated strategic vulnerability that cannot be stressed enough. Most military-grade batteries are either sourced from, or use components manufactured in, Asia. The U.S. must invest in domestic battery manufacturing capacity not just to secure the supply chain, but to innovate beyond what is available on the commercial market. This includes funding custom battery development with higher energy density, better thermal stability, and integrated smart management systems. Battery production must be treated as a strategic industrial priority, on par with chip manufacturing or rare earth processing.
A New Framework for Drone Employment and Training
The DoD and services must create a new class of equipment, where drones are neither munition, nor vehicle, nor IT system, but something in between. Call it operational robotics or attritable autonomy, or something equally catchy. This category should come with its own simplified acquisition rules, reduced reporting requirements, and embedded sustainment pathways that reflect the operational realities of drone use.
Drone warfare is not just about pilots. It requires maintainers, logistics planners, electronic warfare technicians, battery handlers, firmware specialists, and network engineers. The current training infrastructure within the greater DoD is focused primarily on operator qualification. That is insufficient for a battlefield where software, spectrum, and power are as critical as payload.
Service Chiefs must mandate the creation of additional military occupational specialties, whether they are drone tech officers or tactical autonomy specialists, but they must be integrated just as communications or intelligence officers are now standard. These specialists would manage fleets, coordinate charging stations, handle firmware updates, and train operators, not unlike a motor pool manager, but for drones. To support scale, the services must expand their training pipelines to produce drone techs and support specialists in the same way they do with aviation mechanics or vehicle maintainers.
Decentralize, Decentralize, Decentralize
One of Ukraine's greatest advantages has been decentralization. Their ability to push decision-making down to the unit level allows frontline forces to adapt quickly. U.S. drone operations are often centrally controlled, bound by airspace deconfliction layers, rules of engagement, and program office approvals. To compete with near-peer adversaries in a fast-moving drone fight, we need to push more authority down the chain of command and empower units to test, field, and adapt their own drone solutions.
This will require cultural change at the senior leadership level, increased risk acceptance, and new pathways for bottom-up innovation from those Marines, Sailors, Airmen, and Soldiers that are working with this tech every day. Without it, we will continue to lag behind agile opponents who are not waiting for permission to innovate, and aren't burdened by such red tape.
Export Controls and International Collaboration
Another overlooked barrier to innovation is the patchwork of export control regulations governing drone components. Many startups or small-scale manufacturers that build cutting-edge FPV systems or supporting hardware run into legal walls when trying to work with allies. If a component is deemed controlled under export regulations, it cannot be shared without extensive licensing and oversight. This slows down collaborative development with nations like Ukraine or Taiwan and discourages U.S.-based manufacturers from entering the defense market in the first place.
Meanwhile, our adversaries are unconstrained. Components from Chinese suppliers are exported globally without meaningful restriction, and low-cost hobby drones can be modified into deadly strike platforms with tools available at any hardware store. If U.S. companies are restricted from building and scaling at speed while adversaries can iterate freely, that is a strategic imbalance with real-world consequences.
From Tools to Doctrine: Drone-First Mission Design
We also need to begin writing doctrine not just for how drones support existing missions, but how missions can be redesigned around drone-centric force design. In some cases, this may mean replacing certain traditional manned reconnaissance patrols with persistent loitering drones that cost less and offer less risk. In others, it could mean redesigning infantry formations to carry and launch their own suite of mixed-use drones, including ISR, loitering munitions, counter-UAS, and communication relay systems.
Drones should not be treated as bolt-ons to existing force structures. They should shape how missions are conceived, planned, and executed. This will require wargaming, simulation, and field experimentation that are not bound by traditional bureaucratic stovepipes. We should be rapidly funding this innovation and experimentation, but it must be paired with coordinated frameworks and shared standards to ensure units can adapt quickly without drifting into a thousand incompatible systems.
Additive Manufacturing and Local Sustainment
Fielding thousands of drones becomes much more feasible if forward units can repair, reprint, or reassemble components in theater. Additive manufacturing should be fully integrated into sustainment planning for drone programs. This does not mean printing every part from scratch in a field tent, but it does mean empowering unit-level innovation by providing CAD libraries, spare motor stocks, and swap-in controllers. Training for these users on CAD development and 3D printing tools should be standard.
This approach decentralizes sustainment and allows for adaptation at the tactical edge. It also reduces dependency on long logistics chains vulnerable to disruption. Ukraine's use of 3D printed airframes and quick-change modules has proven the viability of this model.
We Cannot Afford to Wait For Funding
Even when the ideas are sound, the funding is often the bottleneck. Small drone startups or DIY shops working with operators often lack the financial runway to navigate months-long or years-long federal contracting processes. A procurement process designed for multi-billion dollar jets simply does not work for ninety-day drone iteration cycles.
DIU's Project GI is a good start, but it needs to come with real money, awarded fast, in increments that can sustain prototyping at scale. If Congress or senior defense leadership wants to unlock true drone innovation, they will need to fund a field-ready, risk-tolerant procurement model. One that trusts operators and incentivizes velocity over perfection.
The Pentagon needs more than a drone strategy. It needs a doctrinal overhaul on how robotics and autonomy are integrated into the force.
This means breaking the Blue List bottleneck, redefining how drones are categorized and managed, changing how we train and tolerate losses, building new logistics frameworks, decentralizing innovation, and rewriting doctrine to reflect drone-first planning. Most of all, it means treating drones not as niche tools, but as foundational to the future fight.