FCC COVERED LIST / FLEET PLANNING
Fleet Transition Readiness for Agencies and Enterprise Operators
The FCC’s Covered List action doesn’t ground the drones you already own — but it does mean the product line most organizations standardized on won’t refresh. That turns fleet planning from a purchasing decision into a multi-year transition with budget, training, and data-continuity consequences. We manage that transition so your data and deliverables survive the platform change.
Last reviewed: August 26, 2026
What the FCC Action Actually Did (And Didn't Do)
The FCC has added foreign-manufactured drones and certain drone components — including models from DJI and Autel — to its national security Covered List. Here’s precisely what that means, because the imprecise version circulating online is causing real confusion.
What It Did
Blocks new equipment authorizations for covered foreign-made drone models going forward. Manufacturers cannot get FCC authorization for newly manufactured models — why the newest DJI and Autel releases have not entered the U.S. market through normal channels since the designation.
What It Didn't Do
It did not ban, recall, or make illegal any previously authorized drone your organization already owns. Models authorized before the Covered List designation remain lawful to import, sell, and fly.
The nuance that changes your planning horizon: The FCC’s Office of Engineering and Technology has extended a waiver allowing already-authorized DJI, Autel, and certain other covered devices to continue receiving firmware and software updates — but currently only through January 1, 2029. That’s not a permanent guarantee. It’s a clock, and it’s a shorter clock than most fleet replacement cycles assume.
Separately, federal procurement rules tied to the Department of Defense and the Blue UAS program are unchanged by this action — Blue UAS requirements were already stricter than general FCC authorization, and remain so.
Sources: FCC drone Covered List update coverage — Wiley Law; firmware waiver extension through January 1, 2029.
Why "We'll Replace Them When They Break" Costs More Than It Looks Like
The instinct to run current aircraft until failure and replace one-for-one when something breaks feels like the cheapest option. For an organization with any meaningful data continuity requirement — recurring inspection deliverables, litigation-grade mapping, multi-year infrastructure monitoring — it usually isn’t, for reasons that don’t show up until you’re mid-transition:
- Sensor differences. A replacement platform’s camera, LiDAR, or thermal sensor rarely matches your legacy sensor’s specifications exactly, which can shift resolution, accuracy, or spectral characteristics in ways that matter for comparison-over-time deliverables.
- Data format changes. New platforms often mean new file formats and metadata structures, which can break existing processing pipelines built around your current aircraft’s output.
- Reprocessing. Historical datasets may need reprocessing to stay comparable with new-platform data — an unplanned cost if you’re switching platforms reactively rather than on a planned schedule.
- Retraining. Pilots and data processing staff need to relearn a new platform’s flight characteristics and software under time pressure if a failure forces an unplanned switch.
- Deliverables that must stay comparable year over year. If a client, regulator, or stakeholder expects consistent reporting format and accuracy across years, an unplanned platform switch mid-series is a harder conversation than a planned one.
None of this is a reason to panic-replace a working fleet today. It’s a reason to plan the transition on your timeline instead of on a failure’s timeline.
ACSL SOTEN — one of the NDAA-compliant “Blue List” platforms we help organizations migrate to when a Covered List aircraft needs replacing.
The Fleet Audit
Before you can build a realistic transition plan, you need an honest inventory of what you’re actually running and how much runway it has left. A fleet audit covers:
- Aircraft-by-aircraft inventory — make, model, authorization status, and current condition
- Procurement and security exposure — which aircraft are subject to the Covered List restrictions, which are Blue UAS or NDAA-compliant already, and where your procurement documentation has gaps
- Realistic support horizon — factoring in the firmware/software update waiver’s January 1, 2029 boundary, expected part availability, and manufacturer support trajectory
- Replacement priority — which aircraft to transition first based on mission criticality, support horizon, and budget cycle
Migration Roadmap: Built for a Capital Request
A fleet transition is a multi-year budget item, not a single purchase order, and it should be presented to whoever approves your capital budget that way. We build a phased roadmap that maps replacement priority against your budget cycles — which aircraft transition in year one, which in year two, and what each phase costs — so it can go directly into a capital request instead of being reverse-engineered from a vendor quote after the fact.
Making the Workflow Platform-Agnostic
The organizations that handle a fleet transition most smoothly aren’t the ones who picked the “safest” replacement platform — they’re the ones whose workflow doesn’t actually depend on a specific platform. That means standardizing, independent of aircraft brand:
01 — Data capture standards
Consistent overlap, resolution, and flight parameters regardless of which aircraft is flying the mission.
02 — File naming conventions
So historical and new-platform data live in the same structure.
03 — Accuracy reporting formats
Consistent methodology for reporting positional accuracy across platforms.
04 — Processing chains
Software and pipelines chosen or configured to accept multiple platforms’ output formats.
Get this right once, and your next platform transition — because there will be a next one — becomes a routine procurement decision instead of a multi-month workflow rebuild.
Training the Transition, Not Just Buying It
A new aircraft on the ramp isn’t a completed transition. Pilots need real flight-characteristic training on the new platform, not just a demo flight. Data processing staff need training on any new software or format the new platform introduces. We build training into the migration roadmap as a scheduled phase, not an afterthought squeezed in after the hardware arrives.
Ongoing Managed Program Option
01 — Authorization tracking
Monitoring your fleet’s FCC authorizations and any Covered List developments affecting your specific models.
02 — Pilot currency
Keeping your flight crew’s certifications and platform-specific proficiency current.
03 — Policy updates
Revising your internal drone-use and procurement policy as the regulatory landscape shifts.
04 — Periodic compliance review
A scheduled checkpoint (annually, more often during active transition years) reassessing your fleet against current requirements.
Questions for Your Own IT Security Team
If your organization has an IT security or risk team that will ask about your drone fleet, these are the questions they’re likely to ask — and the ones you should be able to answer before they ask:
- Which of our current aircraft are on the FCC Covered List, and what does that actually restrict versus what it doesn’t?
- What is our realistic support horizon for firmware and software updates on our current fleet, and what’s our plan for after that window closes?
- Do any of our current or planned aircraft need to meet Blue UAS or NDAA-compliance requirements for specific contracts or grant funding, and do they?
- What’s our documented procurement and data-security policy for drone hardware, and does it reflect the current regulatory environment or an outdated version?
- If we needed to demonstrate to an auditor or grant administrator that our fleet decisions were deliberate and documented, could we produce that paper trail today?
We help operators build defensible answers to all five before they’re asked under pressure.
Frequently Asked Questions
Our Clients
Contact Us
Interested in starting a UAS program?
Need additional information?
