Short version up front: as of December 15, 2025 there is no FCC public notice numbered DA-25-1086 available in the public record. What does exist and matters for public safety operators and the broader UAS ecosystem is a statutory trigger in the FY2025 National Defense Authorization Act and a series of FCC actions this year that make clear how the agency could respond once an interagency national security determination is delivered. I summarize the legal trigger, the FCC s existing tools, what a forthcoming FCC action might do, and practical steps for public safety agencies, vendors, and hobbyist communities to consider.

What the statute requires

Congress wrote a specific one year clock into the FY2025 NDAA. Section 1709 of Public Law 118-159 directed an appropriate national security agency to determine, within one year of the law s enactment, whether certain communications or video surveillance equipment pose an unacceptable risk to national security. If that determination is not made by the statutory deadline, the law requires the FCC to add the specified equipment to its Covered List. The NDAA language and structure are explicit about the one year timing and the statutory mechanism.

Why the FCC s Covered List matters for UAS

The FCC maintains a Covered List under the Secure and Trusted Communications Networks Act and related FCC rules. Equipment or services on that list are treated as posing an unacceptable national security risk for purposes of FCC equipment authorization and related imports and sales controls. The FCC has been active in 2025 using those authorities to tighten authorizations and to warn the market about covered communications and video-surveillance gear. In October 2025 the FCC issued a National Security Advisory reminding companies and purchasers that covered equipment presents unacceptable risks and that the Commission s Covered List is the operative mechanism for blocking equipment authorizations.

Putting the two pieces together: what to expect after the Section 1709 deadline

Because the NDAA sets a firm one year window, many stakeholders expected a formal interagency National Security Determination on the listed equipment or entities by late December 2025. The statutory design creates three practical possibilities:

  • An explicit interagency determination that some named equipment or entities do pose unacceptable risks, triggering the FCC to add them to the Covered List pursuant to the statutory instruction.
  • An interagency determination that particular equipment or entities do not pose unacceptable risks, which could leave the Covered List unchanged with respect to those items.
  • No determination by the deadline, which the statute contemplates as an outcome and which would require the FCC to act under the NDAA language. The statutory deadline and the lack of a single named auditor within the text of Section 1709 have been the sources of legal and operational uncertainty since the law s enactment.

Policy and operational consequences for public safety and allied sectors

If the FCC were to place a category of UAS or UAS critical components on the Covered List, the immediate regulatory lever is equipment authorization. Devices that fall within the Covered List framework are ineligible for new FCC equipment authorizations. That has downstream effects on importation, marketing, and sale in the United States for devices that rely on regulated radio functions. Because modern UAS are radio and software intensive, a location or origin based prohibition over critical components could substantially constrain new models entering the U.S. market and slow supply chains. The FCC s covered-equipment regime has already been used to restrict other categories of foreign-produced telecommunications and surveillance equipment, and the agency has signaled a willingness to use those tools aggressively.

For public safety operators the key short term points are these:

  • Existing inventory. Most regulatory regimes that use the Covered List have not instantaneously criminalized possession or operation of already-authorized devices. Instead the immediate effect is on new authorizations and future imports. Agencies should document the make, model, and FCC authorization status of the UAS and peripherals in active service so they can evaluate exposure if authorization pathways change.

  • Procurement plans. Procuring agencies should assess the supply chain origin of critical components, ask vendors about domestic manufacturing options, and plan for vendor risk in multi year contracts.

  • Interagency coordination. Public safety agencies reliant on commercial platforms for emergency response should engage with state and federal partners to understand potential waiver or exemption pathways that a national security determination might allow or that implementing guidance might create.

What a sensible risk management posture looks like now

1) Inventory and documentation. Catalog UAS hardware and firmware with an emphasis on radio modules, flight controller origins, and any cloud or telemetry connections. Knowing which models have current FCC equipment authorizations is the fastest way to triage near-term impact.

2) Vendor conversations. Ask suppliers for written statements about where critical components are produced and whether they can provide substitution roadmaps. If a vendor cannot or will not disclose origins, that is a governance risk for procurement.

3) Insurance and continuity planning. Evaluate whether vendor nonavailability would disrupt critical operations and develop fallback plans that prioritize safety critical missions.

4) Advocacy. Municipal, state, and sectoral groups should coordinate with industry and the FAA on pragmatic carve-outs or transition support for public safety users if broad restrictions are adopted. Market disruption without transition assistance could degrade emergency response capabilities.

Closing note on DA-25-1086 and transparency

You asked about DA-25-1086. As noted at the top, there was no DA-25-1086 public notice in the record as of December 15, 2025. The statutory and regulatory hooks that would make an FCC notice consequential are already public: the NDAA s Section 1709 establishes the deadline and the FCC s Covered List process is the enforcement mechanism. Stakeholders should track two items very closely after December 15: any interagency National Security Determination required by Section 1709, and any FCC public notice or staff guidance implementing that determination. Those two documents are what will convert a statutory trigger into operational rules and market effects.