FCC November 2026 Drone Spectrum Agenda: 450 MHz C2 and 24 GHz Radar Procurement Guide

Research status: October 31, 2026. The November 19 FCC vote is scheduled, not completed. This independent procurement guide separates proposed spectrum changes from effective requirements.

The buyer’s question: will a newly authorized radio band solve an operational problem, or simply move that problem into licensing, coverage, integration and vendor contracts? The Federal Communications Commission has tentatively scheduled a November 19, 2026 open-meeting vote on aviation-spectrum changes affecting both drone command-and-control links and ground-based drone-detection radar. These are different technologies, with different purchasers and different authorities. Neither should be sold as a substitute for FAA operating authorization.

The agenda concerns safety-related data links in the 450 MHz band, secondary ground-based radiolocation in 24.45–24.65 GHz, and changes to the separate 849–851/894–896 MHz air-ground band used for in-flight connectivity. Another item concerns satellite connectivity for moving platforms. The FCC’s October 29 action opening a different 800 MHz Cellular band to drone communications is already adopted, but should not be confused with these November proposals. The FCC 800 MHz drone-spectrum decision is covered separately; its on-site article awaits a dated post-vote correction.

What is actually under consideration?

The FCC’s October 29 tentative November agenda describes a Report and Order for advanced air mobility and unmanned aircraft, and public draft coverage identifies two practical infrastructure tracks:

• 450 MHz aviation safety data links: Proposed modernization of an older aviation air-ground licensing framework so eligible networks could support command, control and other flight-safety communications for crewed or uncrewed aircraft. The proposal contemplates a nationwide licensing route rather than isolated site-by-site licenses. AURA Network Systems is identified in the FCC’s underlying proceeding as the incumbent licensee; this is not evidence that every U.S. route is presently covered at low altitude.
• 24.45–24.65 GHz ground radar: Proposed secondary radiolocation rules would create a more general licensing basis for fixed ground-based systems that detect or track drones. Current deployment examples and waivers involve companies such as Echodyne and MatrixSpace. Radar authorization is not permission to jam, spoof, intercept or disable an aircraft.
• 849–851/894–896 MHz air-ground: A distinct legacy air-ground communications service, not the same as the FCC’s October 29 decision concerning the wider 800 MHz Cellular band. A procurement specification should label each band by its precise frequencies, service and purpose.

Because the November item has not been adopted, purchasing or bid documentation should use “subject to final FCC rules, license conditions, equipment authorization and effective dates” rather than asserting universal availability. The proposed text, the final voted order and the Federal Register effective date are separate milestones.

Three procurement categories that should not be conflated

1. Flight-critical communications: the command-and-control layer

A command-and-control (C2) service carries information needed to supervise and safely manage an aircraft. It has different priorities from video streaming, package tracking, telemetry analytics or customer notifications. More nominal spectrum is not, by itself, a safety case. An enterprise buyer needs credible coverage at expected aircraft altitudes, latency and availability measurements, resilience to site failure, documented degradation behavior, cybersecurity controls and a clear boundary between onboard autonomy and network-dependent functions.

When evaluating a 450 MHz provider, distinguish a spectrum license, an operational network, a tested geographic service, and a contractual service-level commitment. Ask for maps by altitude, terrain and local interference environment. Ground-station counts, nationwide rights or press announcements are not equivalent to validated reliability on a specific proposed flight corridor. A licensed band may provide interference-management advantages, but it does not eliminate other radio or aviation risks.

For a package-delivery fleet, C2 needs to connect with aircraft radios, supervisory control, flight planning, incident management and emergency procedures. Those interfaces belong in the complete UAV systems procurement framework, not in a standalone modem purchase.

2. Ground radar: detection, identification and situational awareness

A 24 GHz ground radar may help operators monitor airspace around a site, classify tracks and cue cameras or incident-response tools. Its value depends on real coverage geometry, clutter, weather performance, radar cross section, false alarms, track continuity and integration with the customer’s operating procedures. Counter-UAS use cases—airports, prisons, industrial facilities and event venues—have different thresholds and governance needs from ordinary delivery hub monitoring.

The proposed FCC authority is about using radio spectrum for radar detection. It does not create new legal authority for a private party to interfere with a drone or physically stop it. An RFP should separately define detection, tracking, alerting, identification, escalation and any response measures, and obtain counsel’s review of applicable law before claiming a complete counter-drone capability.

Do not treat a radar vendor’s demonstration detection range as guaranteed at every installation. Request a field-verified detection envelope, false-alert performance and a site-specific interference and coordination plan. A base-mounted sensor is also a physical asset requiring power, networking, maintenance and suitable mounting permissions.

3. Connectivity beyond these two bands

The November agenda also addresses an air-ground broadband service and satellite-terminal flexibility for moving platforms. The latter is relevant to remote aviation and autonomous logistics, but its feasibility depends on terminal mass, electrical load, antenna orientation, radio licensing and coverage. It is not an off-the-shelf solution for every lightweight delivery UAV. Likewise, the FCC’s adopted October 29 Cellular change and proposed November air-ground change should be evaluated against the mission and carrier ecosystem—not combined into a single undefined “800 MHz drone network” purchase.

For the aviation boundary, the FAA says compensated BVLOS transportation of another party’s property ordinarily follows its Part 135 certification process with applicable exemptions or waivers. The proposed Part 108 BVLOS rule is not yet in effect. See the regulation guide and the FAA’s package-delivery certification guidance.

Before issuing a procurement RFP: required vendor evidence

A technical proposal should answer all 12 questions below in writing, with customer references or reproducible test results where appropriate. Never accept “FAA compliant” or “nationwide” without an identified certificate, license, scope, test method and date.

1. Licensing: Which FCC radio service and frequencies apply to the offered equipment, and which entity holds the relevant license or is responsible for obtaining authority?
2. Regulatory dependency: Which functions rely on a proposal scheduled for November 19, and which can already operate under existing authorizations or waivers?
3. Coverage evidence: For C2, what are the measured coverage, outage and interference profiles at the intended flight altitude, route and operating hours?
4. Availability: How is service availability measured? What exclusions apply during maintenance, backhaul failures, severe weather or unexpected terrain shadowing?
5. Latency and capacity: What end-to-end performance has been measured with representative aircraft, traffic loads and failover conditions? What data is considered flight-critical?
6. Integration: Which documented APIs, radio interfaces, data formats and log exports connect to the aircraft, supervisory control, flight-dispatch platform and incident system?
7. Security: How are credentials, over-the-air updates, cryptographic keys, access privileges, audit logs and suspected compromise handled?
8. Failure behavior: What does the system do when a link or sensor fails? Identify decision authority, lost-link procedures, safe-state logic and verification records.
9. Radar performance: For detection systems, provide the track-detection envelope, false alarms per operating hour, clutter tests, target differentiation and sensor-fusion limitations.
10. Deployment: What mounting, power, environmental protection, network connectivity, frequency coordination, zoning or site permissions are required?
11. Commercial terms: What are the setup fee, recurring license or subscription, usage charge, support cost, spare-unit policy and early termination obligations?
12. Change management: Who bears the retrofit or cancellation costs if final FCC rules, FAA authorization, the vendor roadmap or service availability differ from the bid assumptions?

Acceptance tests for a representative deployment

The following tests make an RFP auditable rather than rhetorical. Set threshold values in a joint statement of work before testing; no universal acceptance metric is asserted here.

Test A — Route coverage: Survey every proposed flight corridor at the anticipated altitude using the actual radio and mission profile. Report signal quality, interruptions, repeatability and conditions, not just a colored marketing map.

Test B — Degraded link: Intentionally impair the primary link in a controlled, authorized test. Record detection time, command/failover behavior, aircraft response, operator alerts and recovery. Never create unauthorized interference.

Test C — Multi-aircraft load: Reproduce expected simultaneous operations, background telemetry, dispatch events and ground-control workload. Evaluate time synchronization and evidence retention.

Test D — Radar clutter and target set: For ground sensors, test representative aircraft sizes and flight paths against local background returns, vehicles, birds and structures. Log both misses and nuisance alerts.

Test E — Cybersecurity and evidence: Exercise role-based access, credential rotation, network interruption, audit-log export, firmware provenance and incident notification with test accounts.

Test F — Field service: Demonstrate replacement of a failed radio, radar or edge computer, including calibration, restoration, software configuration and documentation.

Test G — Compliance gate: Have the vendor provide the actual applicable FCC license/authorization, equipment identification, proposed site-specific permits and an updated matrix after the November vote. A draft order is not an authorization.

Weighted vendor scorecard: 100 points

A purchasing team can apply the following weights separately to C2 providers and radar providers; it should not use the same technical thresholds for both.

• Regulatory evidence and limitations — 20 points. Correct identification of adopted versus proposed rules, radio authority, equipment status and responsible parties.
• Mission performance — 25 points. Route-level measurements for C2, or site-level detection/false-alert evidence for radar.
• Safety and failure response — 20 points. Demonstrated safe degradation, escalation and incident procedures.
• Security and interoperability — 15 points. Integration documents, access controls, supported exports and change control.
• Lifecycle economics — 10 points. Comparable total cost, support, replacement and exit terms.
• Deployment and supplier maturity — 10 points. Realistic timeline, service footprint, references, staffing and warranty.

Scoring rule: require a regulatory pass/fail gate first. For each category, score 0–5 based on evidence and multiply by its weighted share. Missing evidence scores zero; marketing claims without verifiable tests are not equivalent to commissioned service. Document the reasons for each score and reserve the right to re-score after the FCC’s final action.

How drone-delivery operators should plan around the November vote

Use three phases. Now (before November 19): issue a nonbinding information request; compare carrier, aviation C2 and independent radar options; map existing authorizations; and identify where proof-of-coverage or sensor trials are needed. After the FCC vote: read the final adopted text and effective dates, determine if license and equipment-certification steps change the purchase, and request a revised vendor compliance matrix. Before field deployment: align the radio project with FAA operating approvals, local ground-facility authorizations, security design, maintenance coverage and documented flight or site acceptance tests.

Commercial usefulness comes from keeping these approvals separate. A location can have a permitted site and an authorized aircraft but no workable communications link; a network can offer radio coverage without an operator holding the relevant aviation approvals; and a radar can lawfully detect a drone without giving its operator powers to neutralize it.

The drone-delivery docking-station checklist and dispatch-software RFP provide complementary field-infrastructure and integration requirements.

Independent market watch: suppliers, not endorsements

AURA Network Systems is relevant to the 450 MHz licensed aviation communications track. Echodyne and MatrixSpace are relevant to the 24 GHz radar ecosystem. A procurement team can also assess carrier, avionics, flight software and systems-integration providers where their supported offerings match the mission. These names identify organizations to research, not approved suppliers, advertisers, partners or prospective acquirers of UAVPackage.com.

For strategic companies evaluating the sector, UAVPackage.com maintains independent coverage of the communications, aircraft, software and facilities needed to operate autonomous delivery systems. The property’s acquisition and partnership inquiry page is separate from editorial coverage.

Source and status references

• FCC November 2026 open-meeting page — official publication point for meeting agenda and draft items; check the final release after November 19.
• FCC November 19 agenda summary, October 29 — reproduces the FCC’s announced agenda.
• Detailed November draft reporting, October 29 — technical scope and licensing distinctions pending final vote.
• Commercial UAV News analysis, October 29 — operator-focused summary of the announced changes.
• AURA Network Systems technical overview — vendor’s own description of its licensed network; not independent verification of coverage.
• Echodyne FCC authorization announcement — vendor statement about a specific product, not approval of all future installations.
• FAA package-delivery guidance — separates radio permissions from Part 135 air-carrier and BVLOS requirements.

Editorial note: This article is an independently prepared industry procurement framework, not legal advice, a guarantee of deployment eligibility, or an endorsement of any named company. It will require a post-meeting status review on or after November 19, 2026.