Blue UAS certification produces no battery-origin evidence artifact, and the framework's statutory basis makes clear why. The framework certifies platforms against FY2020 NDAA Section 848, which enumerates covered components along the data-path threat vector: flight controllers, radios, cameras, gimbals, ground control systems, operating software, network connectivity, data storage. Batteries are not in that enumeration. 10 U.S.C. § 4865, the statute that governs battery-origin compliance for DoD procurement, names a completely different set of components, applies a different cost-origin threshold, and operates through a compliance mechanism that, as of this writing, lacks a DFARS clause to flow into contracts. Treating Blue UAS clearance as relevant to battery-origin compliance is a category error whose operational consequences grow with every platform added to the cleared list.
What Section 848 Screens For
EO 14307, published June 11, 2025, directs the Secretary of Defense to update the Blue UAS list monthly and expand it within 90 days to include all drones and critical drone components compliant with Section 848 "to the fullest extent practicable." The executive order ties Blue UAS expansion and waiver minimization to Section 848. It does not reference 10 U.S.C. § 4865.
Section 848 prohibits DoD operation or procurement of covered UAS manufactured in China or by China-domiciled entities, or incorporating specified covered-country components. The specified components are flight controllers, radios, data transmission devices, cameras, gimbals, ground control systems, operating software, network connectivity, and data storage.
Batteries, battery cells, battery packs, BMS hardware, cathode materials, anode materials, separators, electrolyte. None appear. The omission is internally coherent. Section 848 was drafted to address cybersecurity and data-exfiltration risk from Chinese-manufactured UAS. It screens for components through which data flows or through which platform behavior can be compromised remotely. A lithium-ion cell does not present that threat profile. The statute's drafters excluded batteries because, within Section 848's own logic, batteries are not the attack surface.
The exclusion becomes a problem only when Blue UAS certification is read as covering more than it was written to cover.
What the Cleared List Contains
The DCMA Blue UAS portal went live December 3, 2025, after the July 2025 Secretary of War memo transferred list management from DIU to DCMA. The public UAS Cleared List displays seven columns: Date Added, Platform, Type, Manufacturer, Website, Provisional, and Select. The underlying data endpoint confirms the same field structure: platform identifiers, manufacturer name and website, creation and modification timestamps, and status flags for public, select, provisional, and legacy designations.
As of July 10, 2026, the endpoint returns 68 public UAV rows. Some are variants of the same platform family (multiple Harris Aerial Carrier H6 configurations, multiple Parrot ANAFI entries), so 68 overstates distinct systems, but the order of magnitude is right. Of the 68, 21 carry select status and 10 carry provisional flags. Dated entries span from pre-EO legacy platforms through June 5, 2026, with additions visible in most months since the DCMA transition. The monthly-update directive from EO 14307 appears at least partially operationalized.
The list contains no field for battery supplier, cell supplier, cell chemistry, pack assembler, BMS supplier, functional-cell-component origin, cost-origin percentages, FEOC technology-license status, or Section 4865 compliance or waiver status. The table markup includes commented-out columns for manufacturer origin and manufacturer domicile, but these are not rendered in the public table and do not appear populated in the endpoint data.
The absence tracks directly to the list's statutory mandate. Blue UAS certifies against Section 848. Section 848 does not ask about batteries. The list tracks exactly what it is required to track.
What Section 4865 Requires
10 U.S.C. § 4865 asks about batteries at a level of specificity that has no analog in the Blue UAS framework. The threshold is 95% non-FEOC functional-cell-component cost. The named components: cathode, anode, separator, electrolyte and salts, current collector foils, binders, casing, and internal safety devices. The compliance deadlines are tiered: January 2028 for new programs, January 2029 for standard batteries and NSN items, January 2031 for existing programs.
The waiver architecture is narrow. Secretary of Defense authority, delegable only to USD(A&S). One-year duration. System-or-battery-specific. No per-waiver public disclosure required, but a congressional briefing is due by December 1, 2028. The architecture is a relief valve designed for exceptional cases, and it will behave like one under load.
| Section 848 (Blue UAS) | Section 4865 (Battery Origin) | |
|---|---|---|
| Threat model | Cybersecurity / data exfiltration | Supply chain dependence on FEOC sources |
| Covered components | Flight controllers, radios, cameras, gimbals, GCS, software, network, data storage | Cathode, anode, separator, electrolyte/salts, foils, binders, casing, safety devices |
| Threshold | Country-of-manufacture / entity domicile | 95% non-FEOC functional-cell-component cost |
| Compliance artifact | Blue UAS Cleared List placement | None operational (no DFARS clause as of July 2026) |
| Waiver authority | DoD component heads | SecDef only, delegable to USD(A&S) |
| Battery data captured | None | N/A — no contracting mechanism to collect it |
The implementation picture is worse than the statutory gap alone would suggest. The 180-day DFARS revision deadline for Section 4865 passed in mid-June 2026 with no Federal Register or eCFR artifacts visible. No DFARS clause exists to flow Section 4865 requirements into contracts. The contracting officer working from the Blue UAS Cleared List today has neither the data to assess battery-origin compliance nor the contractual vehicle to require it from the vendor. The information gap and the authority gap are concurrent.
Where the Risk Concentrates
EO 14307 is working as designed. It is accelerating the transition to non-Chinese drone platforms. The Blue UAS list is growing. Procurement demand is channeling toward cleared systems.
Every one of those systems contains a battery. For small UAS in the Group 1–3 class, those batteries draw from a lithium-ion cell supply base in which China holds roughly 85% of global production capacity, per IEA's 2024 assessment. The non-Chinese drone platforms that Blue UAS certification promotes are, in the majority of cases, powered by cells manufactured in or sourced through the supply chain that Section 4865 is designed to restrict.
Blue UAS certification does not surface this. It does not require vendors to disclose cell origin. It produces no evidence artifact a contracting officer could use to assess Section 4865 posture. The operational pathway is concrete: a program manager selects a platform from the cleared list, the platform enters the procurement record with a Section 848 compliance artifact, and no downstream trigger in the current process initiates a Section 4865 review. No mechanism in the procurement chain asks the battery-origin question.
When Section 4865 deadlines begin to bind in January 2028, platforms procured through Blue UAS clearance become compliance events simultaneously, and the only relief mechanism is a SecDef-level waiver with a one-year clock.
The contracting officer discovers that the battery inside the cleared platform may not meet the 95% non-FEOC threshold, that no data exists in the procurement record to determine whether it does, and that the only relief mechanism is a SecDef-level waiver with a one-year clock.
Waiver demand concentrates because a small number of cell suppliers feed a large number of drone platforms. If those suppliers cannot demonstrate non-FEOC origin at the functional-cell-component level, the waiver demand hits simultaneously across multiple programs and platforms, all of which were cleared through a process that never asked the relevant question.
No Bridge in the Public Record
No government source, GAO report, or defense trade press article identified in the reviewed public record explicitly acknowledges this specific gap between Blue UAS certification and Section 4865 battery-origin compliance. Business Insider's February 2026 reporting on Blue UAS discusses supply chain risk assessment for parts sourced from certain foreign countries, but the component discussion centers on Chinese-made motors, not batteries. The absence of public acknowledgment does not prove the gap is unrecognized inside DoD. It may be understood and simply unaddressed.
But the public-facing procurement infrastructure contains no mechanism to bridge Blue UAS clearance to battery-origin compliance. The data fields do not capture it. The statutory cross-references do not connect the two frameworks. The DFARS clauses that would create the connection have not been written. What exists is a list doing its job under Section 848, growing under EO 14307's directives, and channeling procurement toward platforms whose battery-origin compliance status is invisible to the framework that approved them. Every month the list grows without a parallel battery-origin mechanism, the waiver queue on the far side of January 2028 gets longer.
- DFARS implementation artifacts for 4865: The 180-day DFARS revision deadline passed in mid-June 2026, and Federal Register and eCFR searches still return zero Section 4865 implementation documents, leaving no public contracting clause to flow battery-origin requirements to vendors.
- Section 836 repository scope: The compliance repository due January 1, 2027 under Section 836 defines "covered sourcing requirements" as §§ 4862–4864 and Title 41 Ch. 83, potentially excluding § 4865 batteries from the repository by a legislative drafting gap.
- QPL-32565 qualified manufacturers: DLA's QPL-32565 listing remains active with a January 2017 document date and July 2026 data update, but public metadata still exposes no qualified manufacturer names, CAGE codes, or product rows.
- First public Section 4865 waiver: The statutory waiver architecture allows SecDef to grant one-year, system-specific relief, but no public waiver request, template, SAM.gov modification, or congressional notification has surfaced in the reviewed record, making the first disclosed waiver a key signal for how DoD operationalizes the mandate gap.