Request for Information (RFI) for C-sUAS and sUAS Solutions FA4659-RFI-CSUAS+SUAS

Request for Information (RFI) for C-sUAS and sUAS Solutions

FA4659-RFI-CSUAS+SUAS v3

Response Requested Not Later Than 30 April 2026 @ 1600 CST

Request for Information (RFI) for C-sUAS and sUAS Solutions for Group 1-3 Unmanned Aerial Systems (UAS)

Introduction:

The Point Defense Battle Lab (PDBL) is seeking information from industry to improve USAF

understanding of market capabilities and identify qualified vendors to collaborate with who are capable of providing Counter Small Unmanned Aircraft Systems (C-sUAS) and Small Unmanned Aircraft Systems (sUAS) integration, development, training, and sustainment services.

Responses to this RFI will help identify businesses with sUAS and C-sUAS technologies and expertise capable of collaborating with the PDBL to carry out its mission to “develop and validate Tactics, Techniques, and Procedures necessary to advance C-sUAS detection, tracking, interception, and neutralization, improving the ability of units to secure Air Force assets, personnel, and continuity of operations.”

All interested and qualified businesses (i.e., Small Business, Other than Small) are encouraged to submit your information on the PDBL Vendor Landing Page at the following link. https://www.grandforks.af.mil/Point-Defense-Battle-Lab/PDBL-Vendor-Landing-Page/

Background:

The USAF established the PDBL to serve as a hub for collaboration, pushing boundaries in

C-sUAS capabilities, ensuring the Air Force maintains tactical superiority against evolving threats, and as a key part of the service’s effort to develop and evaluate advanced technologies to defend installations from sUAS threats.

The PDBL priorities include:

Shift installation defense against airborne threats to a more proactive posture.

Integrate cutting-edge technology, unit expertise in tactical execution, and academic and industry to rapidly develop TTPs for defeating sUAS threats and ensuring robust force protection.

Develop and evaluate advanced technologies to ensure the DAF maintains tactical superiority against evolving aerial threat

Requirements:

PDBL is seeking to collaborate with industry businesses that meet the following requirements:

Ease of Use: The technology or services should be easy to use and require minimal training for operators.

Rapidly Deployable: The technology or services should be capable of being transported via palletized cargo. Able to be set up with a small team (4 personnel or less) within 2 hours.

Extreme Weather: The technology or services must be capable of withstanding and operating in ambient air temperatures of -40, and 20-30 mph winds.

Proprietary Technology: The PDBL Prioritizes Non-proprietary technology, and will accept information on interoperable technology. The PDBL will also accept Proprietary Technology, note proprietary information should be clearly marked.

Technical Parameters for C-sUAS:

The PDBL is interested in technologies or services that meet the following technical parameters:

A. Ability to consistently detect and track all Group 1 UAS types at ranges of 2 km or greater; increased range and track accuracy is preferred.

B. Autonomous classification of detected tracks, distinguishing small UAS from non‑UAS objects; unresolved tracks may be designated as “unknown air tracks.”

C. Effective discrimination of biological clutter, ground clutter, and false tracks to maintain a clean air picture.

D. Simultaneous detection and tracking of multiple UAS threats.

E. Must function in GNSS denied or degraded environments and maintain low physical and spectral signatures to support survivability in contested battlespaces.

System Characteristics

E. Compatibility with existing shore power or standard U.S. military generators (5 kW–30 kW).

F. Provision of radar cross section (RCS) data for detected targets.

G. Rapid integration capability with Government‑designated C‑UAS fire control systems.

H. All‑weather engineering sufficient to maintain performance in adverse environmental conditions.

I. Ease of operator usability with a preference toward the ability to reduce sensor calibration times, mean time between failures, and maximize field maintenance efficiency by operators

Secondary Attributes

J. Capability to detect, track, and classify Group 2 and Group 3 UAS with actionable data on threat disposition

K. Provision of a 360‑degree azimuth and 30‑degree elevation search air picture, with up to 90‑degree elevation in track coverage; distributed architectures are acceptable.

L. Ability to steer search and track elevation below 0 degrees relative to sensor emplacement.

M. Desired minimum detection range between 50m and 500m, with preference toward shorter ranges.

N. Ability or path to detect and track hovering UAS exhibiting 0 Hz Doppler characteristics.

O. Capability or planned development path to provide physical target length estimates.

P. Tracking accuracy sufficient to support downstream effector, sensor cueing, and multi-modal sensor fusion, expressed in azimuth and elevation error.

Q. Track update…