If you are a DoD contracting officer or program manager evaluating unmanned aircraft systems, NDAA Section 848 compliance is not a feature — it is a threshold requirement. This post covers what the restriction means in practice, what documentation you need from vendors, why the domestic supply chain distinction is harder to verify than most vendors suggest, and what a compliant procurement process looks like end to end.

What NDAA Section 848 Actually Restricts

Section 848 of the National Defense Authorization Act prohibits the Department of Defense from procuring, or entering into or renewing a contract for the procurement of, a covered unmanned aircraft system from certain entities. The covered entities include manufacturers incorporated in China, Russia, Iran, North Korea, and their subsidiaries and affiliates.

The restriction is not limited to the airframe. It covers components — meaning a platform assembled in the United States using flight controllers, cameras, communication modules, or battery management systems sourced from covered entities fails the test regardless of where final assembly occurred.

This has significant implications. A vendor can legitimately claim their drone is “assembled in America” while using a DJI-manufactured flight controller, a Chinese-sourced camera gimbal, or a battery management system with Chinese-manufactured cells. Each of those component choices creates a compliance failure under Section 848 — even if none of them appear on the vendor’s marketing materials.

The Four Covered Entity Categories

Section 848 identifies four primary categories of covered entities:

Chinese state-owned enterprises and their subsidiaries. DJI is the most widely known example, but the prohibition extends to their subsidiaries and any entity under their effective control. SZ DJI Technology Co., Ltd. and its affiliates are explicitly named in associated legislation.

Entities on the Department of Defense’s 1260H list. This list identifies Chinese military companies operating in the United States and is updated annually. Procurement from any listed entity or its subsidiaries is prohibited.

Entities subject to the Entity List (Department of Commerce). Some UAS-adjacent component manufacturers appear on the BIS Entity List, creating overlap with NDAA restrictions even when the NDAA prohibition may not apply directly.

Affiliates and subsidiaries of the above. This is the category that creates the most compliance complexity. A component manufacturer that is a minority-owned subsidiary of a covered entity may still trigger the restriction depending on ownership structure and control.

The Documentation Standard

A vendor claiming NDAA compliance should be able to provide all of the following on request before contract award:

1. Bill of Materials (BOM) identifying all electronic components by manufacturer, part number, and country of origin. The BOM should be component-level — not a system-level summary. A document that says “electronics: domestic” without identifying specific components is not sufficient for acquisition file purposes.

2. Component traceability records linking each BOM line item to a domestic or approved-country supplier. This means purchase orders, invoices, or supplier certifications that document the supply chain for each covered component.

3. Declaration of conformance signed by an authorized company representative, explicitly stating NDAA Section 848 compliance and identifying the specific statutory provision being satisfied.

4. CAGE code and active SAM.gov registration confirming the vendor is eligible for federal procurement. An active registration with a valid CAGE code is a baseline verification that the entity is who they claim to be.

If a vendor cannot produce all four on request before contract award, the procurement is at compliance risk. Program managers who proceed without this documentation may face audit findings, contract disputes, or termination for cause.

Why “Assembled in America” Is Not Enough

Several UAS vendors market platforms as American-made while using flight controllers, gimbal systems, or communication modules manufactured by covered entities. Assembly location does not determine compliance — component origin does.

The distinction matters for three specific reasons:

Flight controllers. The Pixhawk ecosystem includes numerous hardware variants manufactured by Chinese companies. While some variants use domestic or European-manufactured components, others do not. The flight controller is the most common compliance gap in platforms claiming domestic manufacture.

Camera systems. Optical and thermal imaging systems are frequently sourced from Chinese manufacturers even on platforms marketed as NDAA-compliant. Sony sensors, Flir thermal modules, and similar components are generally permissible — Chinese-manufactured alternatives may not be.

Communication hardware. Radio links, telemetry systems, and video transmission modules are a common supply chain gap. Several popular FPV and telemetry systems use Chinese-manufactured RF chips or are produced by Chinese-majority-owned companies.

Program managers who accept assembly location as a proxy for NDAA compliance are exposed to audit risk and potential contract termination for convenience if compliance gaps are discovered post-award.

The Blue UAS Framework Connection

The Defense Innovation Unit’s Blue UAS Framework provides a pre-vetted list of NDAA-compliant UAS platforms that have undergone security review. Platforms on the Blue UAS list have cleared both the component-level NDAA review and a cybersecurity assessment.

For program managers who need to move quickly, a Blue UAS Framework designation significantly reduces the compliance verification burden — the supply chain review has been done by DIU, and the documentation is available. For platforms not yet on the Blue UAS list, the full BOM-level vendor documentation process described above applies.

Forge and Flight Labs is pursuing Blue UAS Framework certification. Our four platforms — Longbow-8, Aether-10, Vanguard-14, and Titan-20 — are designed from the ground up for this certification pathway. All electronics are manufactured by our in-house Electronics Manufacturing Division using 100% domestically sourced components.

What a Compliant Procurement Process Looks Like

A defensible NDAA Section 848 compliant procurement follows this sequence:

Vendor pre-qualification. Require all vendors to submit BOM documentation and a signed declaration of conformance before the proposal deadline. Vendors who cannot provide this should be disqualified.
Verification against covered entity lists. Cross-reference each BOM component manufacturer against the DoD 1260H list and BIS Entity List. This can be done manually for small BOMs or through procurement compliance tools for larger programs.
Document retention. Retain all vendor-provided compliance documentation in the acquisition file. If the contract is audited, this documentation is your primary defense.
Post-award monitoring. Require vendors to notify the contracting officer of any supply chain changes that could affect NDAA compliance. A vendor that substitutes a domestic component with a foreign equivalent mid-contract without notification has created a compliance event.

Forge and Flight Labs’ Compliance Position

Every platform we manufacture — Longbow-8, Aether-10, Vanguard-14, and Titan-20 — is built with 100% domestically sourced electronics through our in-house Electronics Manufacturing Division. We provide full BOM documentation, component traceability records, and NDAA Section 848 compliance certificates with every purchase order.

Our CAGE code (18VF2) and active SAM.gov registration (UEI: SUVKLZLPBJC1) are verifiable in real time. We respond to compliance documentation requests within 48 hours of contract award.

For procurement officers who need to document vendor compliance for acquisition files, we provide everything required at no additional cost or scheduling delay. Contact us to request a sample compliance package before submitting your RFQ.

NDAA Section 848: What DoD Procurement Officers Must Know