A platform listed on the DCMA Blue UAS Cleared List has passed a certification process. That process does not ask where the battery cells come from. It was not designed to. The statute it operationalizes does not enumerate batteries as a covered component. When someone cites Blue UAS clearance as evidence of battery supply chain compliance, they are applying a certification to a domain it does not cover, and the public record makes this verifiable in about ten minutes.
This piece maps what EO 14307 requires, what the DCMA portal exposes, and where battery-level provenance falls through the resulting gap. The practical output is a set of questions grounded in specific, documented absences.
What the EO Directed
EO 14307 directed DoD to expand the Blue UAS list within 90 days to include all drones and "critical drone components" compliant with FY2020 NDAA §848, update it monthly, and restrict waivers to cases where they are "absolutely necessary." The Hegseth memo directing the transition from DIU to DCMA described a future digital platform with "retained component and supply-chain findings" and "testing evaluations." Breaking Defense reported a "trust-but-verify" system using sampling to ensure vendors meet statutory requirements.
Both descriptions imply a compliance verification layer deeper than what the public portal shows. But the statutory requirements being verified are §848 requirements, and §848 does not cover batteries. Even if a non-public verification layer exists behind the portal, it would still be bounded by §848's component enumeration unless DCMA has adopted a broader interpretation. No public document confirms such an interpretation. The depth of the verification process is a separate question from its scope, and scope is the binding constraint here.
The phrase "critical drone components" in EO 14307 is the strongest textual hook for anyone arguing the mandate extends beyond §848's enumeration. It is worth engaging directly. The EO ties this phrase to §848 compliance: the expansion covers components "compliant with" §848. The DCMA Framework's component taxonomy, as documented below, maps almost exactly to §848's categories. The current operational interpretation, as evidenced by what the portal actually lists, appears bounded by the statute. No public DoD document, policy directive, or implementation guidance reviewed here defines "critical drone components" more broadly. The phrase creates theoretical room for expansion. The public record shows no one has walked through that door.
What §848 Covers
§848 of the FY2020 NDAA defines the component categories that trigger a China-origin prohibition for covered UAS. The enumerated list: flight controllers, radios, data transmission devices, cameras, gimbals, ground control systems or operating software, and network connectivity or data storage.
Batteries, motors, and electric speed controllers are absent from the enumeration.
The logic is legible. §848 was scoped around data-handling and data-transmission components: the parts of a UAS that could exfiltrate information or be remotely compromised. Cameras store imagery, radios transmit telemetry, flight controllers process navigation data. A battery stores electrochemical energy. The exclusion follows cybersecurity logic — batteries don't transmit or store data — but it leaves the single component most concentrated in Chinese manufacturing outside the compliance perimeter.
"Experts familiar with Blue UAS described §848's covered components as focused on items that store or transmit data, while 'dumb' electrical or mechanical components such as motors were not treated as fail points."
What the Portal Shows
The DCMA portal hosts categories for UAS, Additive Manufacturing, Counter-UAS, and UxS, with a separate Framework page describing "interoperable NDAA-compliant UAS components, sub-components, modules, and software."
The UAS Cleared List exposes 67 platform records. Visible fields: Date Added, Platform, Type, Manufacturer, Website, Provisional, and Select. No field identifies a battery supplier, cell supplier, cell chemistry, cell format, pack assembler, BMS supplier, battery country of origin, or component-cost provenance.
The Framework page exposes 197 records across ten component types:
| Component Type | Records |
|---|---|
| Radio | 58 |
| Camera | 31 |
| Flight Controller | 29 |
| GCS | 21 |
| Data Transmission Device | 21 |
| Gimbal | 14 |
| GNSS Module | 9 |
| Companion Computer | 9 |
| Software | 4 |
| Payload | 1 |
| Battery / Cell / Energy Storage / Power Source | 0 |
Zero Framework records exist under Battery, Cell, Energy Storage, or Power Source. The single "power" match is a ModalAI VOXL Power Module V3, classified as a Data Transmission Device.
The Framework's component categories map almost exactly to §848's enumerated list. The portal operationalizes the statute, and the statute does not cover batteries.
Two additional observations from the portal's architecture. The Cleared List and the Framework are structurally separate: DCMA distinguishes between certifying a platform and certifying its components. But the two are not linked in the public interface. No cleared platform record connects to a bill of materials. No Framework component record maps back to a specific platform configuration. Second, the portal's page source contains commented-out columns for manufacturer origin and domicile on the UAS list page, and a commented-out country column on the Framework page. These fields were considered. They are not active. Whether they are populated behind the public layer is unknown from the public record.
The DIU Process Did Not Ask Either
The transition from DIU to DCMA is sometimes discussed as if it represents a step-change in rigor. The Hegseth memo's language about "retained component and supply-chain findings" suggests a more structured process. But the prior DIU process also did not assess battery provenance as a certification condition. The DefenseScoop reporting from November 2025, which predates the full DCMA transition, already documented Chinese-sourced batteries in Blue UAS-approved platforms. The gap existed under DIU. The transition changed the institutional owner and the ambition of the digital infrastructure. The statutory scope of what the list certifies carried over unchanged.
The Gap in the Public Record
The November 2025 DefenseScoop reporting remains the strongest public signal. Multiple sources said most drones cleared through Blue UAS had motors sourced in China. A former senior defense official identified the top three Chinese-sourced components in Blue UAS-approved platforms as motors, batteries, and electric speed controllers. AUVSI's Michael Robbins noted that motor and battery risk includes both embedded risk and supply chain resiliency risk. No subsequent public reporting in the seven months since has updated, corrected, or contradicted these findings. That silence, from an institutional standpoint, is itself informative about how much energy is being directed at this particular gap.
The inference for batteries is direct: if motors, which share the same statutory exclusion, are not a fail point for Blue UAS certification, batteries are not a fail point either. A platform can carry Chinese-origin cells and remain Blue UAS-cleared, because the certification does not ask the question.
Closing this gap would require one of three things: legislative action amending §848 to enumerate batteries and motors, a new DoD policy directive that imposes battery provenance requirements beyond §848, or an interpretation of "critical drone components" in EO 14307 that extends past the §848 enumeration. The public record as of this writing shows no introduced legislation, no public DoD statement, and no implementation guidance pursuing any of the three.
Separate Authorities, Separate Questions
Battery procurement restrictions do exist elsewhere in defense law. Title 10 §4864-4865 addresses critical components and foreign sourcing for certain defense systems. NDAA Section 842 (FY2024) addresses FEOC restrictions on battery components for defense applications. These are separate authorities with separate implementation timelines, separate definitions, and separate enforcement mechanisms.
A prime contractor citing Blue UAS clearance is answering a §848 question. If you are asking a §842 question or a §4864 question, you are in a different compliance domain, and the Blue UAS list is not evidence in that domain.
The risk is conflation. Platform certification under one authority gets cited as if it satisfies obligations under a different authority. The compliance landscape is fragmented enough that the boundaries between authorities are genuinely non-obvious to anyone who has not mapped them. The consequence is the same regardless of intent: a procurement decision made on the basis of evidence that does not apply.
Questions to Bring Into the Room
The following target specific gaps documented above. They are designed for a conversation with a prime contractor's supply chain team or a program manager who has cited Blue UAS platform certification as evidence of battery compliance.
1. Is the battery pack and cell supplier identified in the certified platform configuration? The DCMA portal does not expose battery supplier data for any cleared platform. If the prime claims the battery supply chain is compliant, ask where that determination is documented. It is not in the public certification record.
2. What is the cell chemistry, format, and country of manufacture for the cells in the delivered configuration? Neither the Cleared List nor the Framework exposes chemistry or cell-format fields. If they are not documented in the certification, they are not controlled by the certification.
3. Is the compliance claim based on §848, or on a separate battery-specific authority? §848 does not enumerate batteries. If the prime is claiming §848 compliance only, that claim is silent on battery provenance by statute. If they are claiming compliance under §842 or another authority, ask for the specific statutory reference and the evidence basis.
4. Does any Framework component record cover the battery, BMS, charger, or power-management system? The Framework's 197 records contain zero battery-category entries. If a battery-related component has been assessed, it would need to appear under a different category label or in a non-public record. Ask which.
5. Can the prime provide country-of-origin and FEOC/non-FEOC attestation for battery functional cell components: cathode, anode, separator, electrolyte? Blue UAS platform listing does not require or disclose this evidence. If the prime has it, they obtained it through a process outside Blue UAS certification. Ask what that process was and who validated it.
6. Does any waiver, provisional status, or follow-up requirement apply to the platform's battery configuration? The portal exposes provisional and select flags at the platform level but not battery-specific waiver detail. If a platform is provisionally cleared, ask whether the provisional condition relates to battery sourcing.
7. If the cell supplier changes, does the platform's Blue UAS clearance require re-evaluation? The portal does not link platform clearance to a specific cell supplier. If the supplier is not part of the certification basis, a supplier change would not trigger re-evaluation under Blue UAS. The compliance posture you assessed at procurement may not match the compliance posture of the platform you receive.
Blue UAS certification is scoped by §848 to cybersecurity and data-integrity. Battery provenance is outside that scope. The portal confirms this: 67 platforms, 197 component records, zero battery entries. Anyone evaluating battery-level compliance behind a Blue UAS-certified platform needs to know where the certification's authority ends and their own due diligence begins.
- DFARS implementation clock running: The statute required DoD to amend DFARS to incorporate §4865 battery restrictions within 180 days of December 18, 2025, but Federal Register searches return no visible rulemaking artifact as of late June 2026.
- Compliance repository due January 2027: §4864 requires a publicly available online repository for covered-product compliance registrations by January 1, 2027, with an initial congressional briefing that was due by May 1, 2026 and has produced no public output.
- China's bilateral enforcement tightening: China announced export restrictions on June 22, 2026, targeting ten U.S. military-related companies including drone makers Red Cat Holdings, Teal Drones, and Jaia Robotics alongside critical-minerals firms MP Materials and USA Rare Earth.
- Global battery concentration unchanged: IEA's 2026 outlook reports China produced over 80% of global battery output in 2025 and held over 80% of nameplate capacity, with U.S. and EU production costs running up to 50% higher before public support.