An ESC is NDAA-compliant when it is not manufactured by a covered foreign entity, is accompanied by a CoC and BOM with per-component country-of-origin, and its firmware is free of covered-entity IP. This guide explains the four compliance regimes, what documentation procurement offices require, and what red flags to watch for in supplier evaluation.
An NDAA-compliant ESC is an electronic speed controller that (1) is not manufactured or substantially transformed by any company on DoD's covered-entity list — primarily Chinese firms linked to the People's Liberation Army or Chinese state apparatus; (2) uses firmware that is either open-source and auditable or verifiably produced outside covered entities; and (3) ships with a CoC, CoO letter, and a BOM that traces every component to a non-covered manufacturer. Compliance is not self-declared — it requires documentation that survives procurement-office audit.
NDAA §848 (FY2020) includes a statutory list of covered UAS components. Electronic speed controllers appear on that list alongside flight controllers, cameras, radios, ground control stations, and data transmission devices. The legislative intent was to close every power and control pathway in a drone platform against supply-chain compromise.
The threat model is straightforward: an ESC sits between the battery and every motor. A compromised ESC could desync a motor at a critical moment, drain the battery pack in a controlled pattern to reduce operational range, or report falsified telemetry upstream. Because the ESC is the final stage of the propulsion authority chain, it has both the access and the position to cause mission failure.
The list has not been narrowed in subsequent NDAA cycles. Section 817 (FY2023) tightened the definitions and added operational restrictions on existing inventory. The American Security Drone Act (ASDA, FY2024) extended these prohibitions from DoD to the entire federal government. An ESC that was prohibited for DoD programs in 2020 is now prohibited for every federal agency.
A fully compliant ESC for federal drone programs must satisfy all four of these requirements simultaneously. They are layered: each subsequent regime builds on or extends the previous one.
Section 848 of the FY2020 NDAA prohibits the Department of Defense from procuring or operating UAS or covered components manufactured by entities owned, controlled by, or connected to the governments of China, Russia, Iran, or North Korea. It established the initial covered-entity list and the definition of covered UAS components. Applies to all DoD procurement and operations.
Section 817 of the FY2023 NDAA tightened the §848 definitions, expanded the list of prohibited entities, and added operational restrictions on covered UAS already in DoD inventory. It also clarified that ESCs, flight controllers, and communication modules are covered regardless of final assembly location or rebranding. Any product substantially transformed by a covered entity remains a covered component.
The ASDA, enacted in the FY2024 NDAA, extended NDAA-equivalent covered-UAS restrictions from DoD to every federal agency. Civilian agencies — DHS, CBP, DOI, DOE, USDA, and others — cannot procure, operate, or use drones or covered components from covered entities. An operational ban on already-owned covered UAS took effect in . The practical effect: a drone OEM selling to any federal customer must now maintain the same compliance posture previously required only for DoD programs.
Executive Order 13981 directs federal agencies to prioritize domestically sourced hardware for national security technology applications, reinforcing the NDAA prohibitions with a broader supply-chain security mandate. For ESC procurement, EO 13981 provides an independent compliance basis that some agency solicitations reference alongside FAR 52.225 clauses.
Non-compliance can occur at the hardware, firmware, or documentation level. Any one of the three is sufficient to fail a procurement review.
If the bare PCB is fabricated in China, if the SMT assembly is performed in China, or if any major subassembly is produced by a company on DoD's Section 1237 list, the ESC is a covered component. This applies even if final test, packaging, or distribution occurs outside China. "Substantial transformation" is the legal threshold — not country of final assembly or country of shipping.
The NDAA's covered-component definition includes "operating software" embedded in components. Firmware developed by or licensed from a covered entity would be implicated. Even where firmware is not from a covered entity, closed-source firmware introduces a supply-chain security risk — a security reviewer cannot confirm there are no backdoors. Open-source firmware (AM32) is auditable; proprietary firmware is not. DoD programs increasingly require auditable firmware.
An ESC that may be compliant in hardware cannot be verified without documentation. Procurement offices require a Certificate of Conformance (CoC), a Country of Origin (CoO) letter, and a BOM that identifies the manufacturer and country of origin for each component line item. Without these documents, the ESC fails the procurement gate regardless of its actual hardware provenance.
When a federal drone program submits for contracting or a DoD prime flows down compliance requirements to its ESC supplier, these are the documents that will be requested. Having them ready before the question is asked distinguishes a program-ready supplier from an aspirational one.
Lirith provides all of the above as standard deliverables for every production program. See the full documentation package →
What is an NDAA-compliant ESC?
An ESC that is not manufactured by a covered foreign entity, uses auditable firmware, and ships with a CoC, CoO, and component-level BOM documenting non-covered-entity sourcing throughout the supply chain.
Can a Chinese-branded ESC be NDAA-compliant?
No. If manufactured or substantially transformed by a Chinese company on DoD's Section 1237 list, it is a covered component regardless of branding, repackaging, or distribution channel.
Does firmware need to be NDAA-compliant?
NDAA statutes focus primarily on hardware manufacturers. However, defense programs increasingly require auditable firmware. AM32 (open-source, non-covered-entity) is preferred because its full codebase can be independently reviewed.
What's the difference between §848 and ASDA?
§848 applies to DoD only. ASDA (FY2024) extends the same restrictions to the entire federal government. An ESC for any federal program — not just military — must now comply with ASDA.
Is Blue UAS listing required?
No — Blue UAS listing is a pre-vetting framework that speeds procurement, not a statutory requirement. An ESC can be fully NDAA-compliant and procured on a federal contract without Blue UAS listing.
Where can I buy an NDAA-compliant ESC?
Lirith manufactures the QuadDrive 80A — a US-designed, US-manufactured quad ESC compliant with NDAA §848, §817, ASDA FY24, and EO 13981, with full documentation package standard. Contact sales@lirith.com.