If you’re procuring UAV systems for a federal program, defense application, or dual-use platform, NDAA compliance isn’t optional. It’s also more complicated than avoiding DJI. The National Defense Authorization Act’s drone-related provisions restrict specific manufacturers, extend to components beyond complete aircraft, and carry procurement consequences that surface late in programs when they’re most expensive to […]
If you’re procuring UAV systems for a federal program, defense application, or dual-use platform, NDAA compliance isn’t optional. It’s also more complicated than avoiding DJI. The National Defense Authorization Act’s drone-related provisions restrict specific manufacturers, extend to components beyond complete aircraft, and carry procurement consequences that surface late in programs when they’re most expensive to fix.
This post explains what NDAA compliance means for UAV procurement, which manufacturers and systems are restricted, what the Blue UAS Approved List is, and what compliance actually requires in practice.
NDAA compliance determines whether a UAV program can legally use federal funding and which hardware is off the table.
The NDAA is the annual legislation that authorizes U.S. defense spending. The primary current law governing drone procurement is the American Security Drone Act (ASDA), passed as part of the FY2024 NDAA (Sections 1821-1833). It expanded restrictions government-wide. Earlier provisions, particularly Section 848 of the FY2020 NDAA, established the original DoD-specific restrictions. ASDA extended those to all federal agencies and federally funded programs, including contractors and grant recipients, with full operational restrictions that took effect December 22, 2025.
The practical effect: programs funded by federal appropriations cannot use drone hardware from restricted manufacturers. That restriction applies to the complete aircraft and extends to components. Cameras, flight controllers, batteries, and electronics from restricted supply chains can disqualify an otherwise compliant platform.
For defense contractors and federal procurement teams, NDAA compliance affects vendor selection, BOM decisions, and supply chain documentation requirements throughout the program lifecycle. Getting it wrong is a program disqualification risk.
The NDAA restrictions target drones manufactured by companies with ties to certain foreign governments, primarily Chinese-owned or Chinese-affiliated manufacturers. The most prominent restricted manufacturers include:
The list has expanded with each NDAA reauthorization cycle, and the interpretation of what constitutes a “covered” manufacturer has broadened to include component suppliers beyond airframe OEMs. Programs that built compliant platforms using restricted electronic components have faced retroactive compliance challenges.
The restriction is a supply chain question. Brand selection is only the start of it.
The Blue UAS Approved List is a DoD-curated list of commercial unmanned aircraft systems certified as NDAA-compliant for use in federal programs. It was developed by the Defense Innovation Unit (DIU) as a practical answer to the procurement gap created by NDAA restrictions: a vetted set of alternatives to restricted Chinese-manufactured platforms. As of July 2025, management of the list transitioned from DIU to the Defense Contract Management Agency (DCMA).
Systems on the Blue UAS list have been reviewed for security vulnerabilities, supply chain integrity, and NDAA compliance. For procurement teams, sourcing from the Blue UAS list is the clearest path to compliance documentation.
The list covers complete aircraft systems and component-level sourcing. Flight controllers, avionics, and electronics from Blue UAS-affiliated vendors carry the supply chain documentation defense programs require. It’s a living document; a platform approved today may be reviewed again as supply chain ownership changes. Always verify current status directly from DCMA rather than relying on secondary sources or manufacturer marketing materials.
NDAA compliance in a UAV program is an engineering and supply chain discipline.
The most common compliance gap in UAV programs isn’t the airframe. It’s the components inside it. Flight controllers, cameras, electronic speed controllers, and battery management systems frequently include hardware from restricted manufacturers, even on platforms marketed as NDAA-compliant.
Genuine NDAA compliance requires tracing the supply chain at the component level: country of origin for major electronics, ownership structure of component manufacturers, and documentation that restricted hardware isn’t embedded in the subsystems. For custom-developed UAV systems, this means making compliance part of the BOM review process from the first design decision.
Defense programs require supply chain documentation as part of procurement. Not just a compliance attestation; traceable sourcing records for major components. Development partners and hardware suppliers who work in the defense UAV space must be able to produce component-level sourcing documentation. If a vendor can’t, that’s a program risk worth surfacing before you’re deep in the build.
Where a UAV is assembled matters for NDAA compliance. U.S. assembly by a U.S. entity is a positive compliance signal. Assembly performed overseas, even with compliant components, can create documentation complications in programs with strict domestic content requirements. Assembly location is part of the compliance profile.
For programs developing custom UAV systems rather than procuring commercial off-the-shelf platforms, NDAA compliance needs to be built into the development process from day one.
The failure mode is treating compliance as a post-design review: building the system with the best available components, then checking compliance at the end. By that point, replacing a non-compliant flight controller or battery management system is a redesign, not a swap.
The development partner who builds compliant systems knows which suppliers are on the Blue UAS list before the BOM is written, sources from compliant vendors as a default, and produces documentation as a standard output of the build process. That’s the difference between a program that closes cleanly and one that hits compliance problems at contract close.
NDAA restrictions apply directly to federal programs: contracts funded by federal appropriations and systems operated on U.S. government networks or infrastructure. Commercial programs not funded by federal money are not legally required to comply. Dual-use programs, commercial platforms intended for future government sale, and programs with federal contractors in the supply chain increasingly treat NDAA compliance as a practical requirement regardless of the direct legal obligation. The compliance documentation gets expected later in the program lifecycle regardless of where the legal obligation starts.
Not in a way that satisfies most program requirements. The NDAA restrictions on DJI apply to the complete aircraft system, and DJI’s flight controller and software infrastructure are deeply integrated into their platforms. Replacing surface-level components doesn’t address the underlying supply chain and software dependencies. Programs requiring NDAA compliance typically need to start with a compliant platform or build a custom system from compliant components.
The Blue UAS list is a living document maintained by DCMA, which took over from DIU in July 2025. It is updated periodically as new systems complete the review process and as existing approvals are renewed or revised. Program managers should verify current approval status directly from DCMA. Ownership changes, supply chain modifications, or security findings can affect a platform’s listed status; historical documentation may not reflect it.
Documentation requirements vary by program and contracting officer, but typical expectations include:
For custom-developed systems, this documentation should be a byproduct of the development process, produced as the build progresses rather than assembled retroactively at contract close.
Yes. Battery cells, BMS electronics, and associated charging hardware from restricted manufacturers can create compliance exposure in a UAV program, even if the airframe and avionics are fully compliant. Many commercially available lithium battery packs include cells or management electronics from Chinese manufacturers covered under NDAA restrictions. For defense and dual-use programs where NDAA compliance is required, battery sourcing warrants the same rigor as flight control and avionics hardware. Treetown Tech sources cells and components from NDAA-compliant manufacturers. BMS and chargers are designed to the same standard for programs where clients require it.
Treetown Tech engineers UAV systems with NDAA compliance built into the development process: Blue UAS-approved component sourcing, in-house battery engineering, and domestic assembly in Ann Arbor, Michigan. If you’re building or sourcing UAV hardware for a defense or dual-use program, see how we approach NDAA-compliant UAV development.
You have the vision. We have the team and expertise to get it built. Let's collaborate to innovate, problem-solve, and de-risk every step of the way.
