Air Force Wants New Ground-Based Launcher for Air Base Defense

TL;DR

The Air Force has issued a Request for Information (RFI) for a new ground-based launcher system to defend air bases against cruise missiles and unmanned aircraft systems, with responses due by August 7. This RFI signals a major near-term opportunity in the air base defense market; the Air Force has requested approximately $1.4 billion for Air Base Air Defense Systems in its FY2027 budget. Defense contractors that provide counter-UAS systems, kinetic weapons, and integrated air defense solutions should prioritize responding to the RFI to shape requirements and position for the anticipated solicitation. Responding now will help firms influence capability set, qualify for follow-on procurements, and align internal capture and compliance efforts. Immediate actions should focus on preparing capability statements, mapping compliance obligations, and standing up a capture team to convert RFI engagement into a bid strategy.

Key Points

• What happened: The Air Force issued an RFI for a new ground-based launcher to defend air bases against cruise missiles and unmanned aircraft systems.
• Who is affected: Defense and aerospace contractors, particularly those in NAICS 336414, 334511, 541715, 336419, 334220, 541330; affected agencies include DOD and the Air Force; market segments include Counter-UAS, Air Defense, Weapons Systems, Integrated Air Defense Systems.
• Timeline: Responses due by August 7; FY2027 funding request of approximately $1.4 billion for Air Base Air Defense Systems noted in the Summary.
• What contractors should do NOW: Prepare and submit an RFI response by August 7, assemble a capture team, produce a capability statement and white paper focused on ground-based launcher integrations, audit DFARS (Defense Federal Acquisition Regulation Supplement)/ITAR (International Traffic in Arms Regulations)/CMMC (Cybersecurity Maturity Model Certification)/NIST 800-171 (NIST Special Publication 800-171)/EAR compliance posture, and schedule a proposal/solution readiness review.

Who Is Affected

• NAICS codes: 336414, 334511, 541715, 336419, 334220, 541330 (from segmentation).
• Agencies: DOD; Air Force.
• Contract vehicle: RFI (Request for Information).
• Compliance regimes: ITAR, DFARS, CMMC, NIST 800-171, EAR.

Specific NAICS codes, agencies, and contract vehicles pending source review for further updates.

Frequently Asked Questions

Q: What exactly is the Air Force asking for in this RFI?

A: The RFI requests information on a new ground-based launcher system to defend air bases against cruise missiles and unmanned aircraft systems. Further technical and solicitation details are pending source review; contractors should respond to the RFI by the stated deadline.

Q: Is there funding associated with this effort?

A: The Summary notes the Air Force requested approximately $1.4 billion for Air Base Air Defense Systems in its FY2027 budget. Specific contract funding and award mechanisms for this RFI are pending source review.

Q: Should we submit a response even if we do not yet meet every compliance regime listed?

A: Yes. The RFI phase is the appropriate time to describe capabilities, constraints, and planned compliance remediation. However, contractors should document current posture and mitigation plans for ITAR, DFARS, CMMC, NIST 800-171, and EAR as part of their response and capture package.

Definitions

• Ground-based launcher: A land-based launch system designed to deploy weapons or interceptors; referenced as the system the Air Force seeks.
• Cruise missiles: Guided missiles intended to deliver a payload over long distances at low altitudes; listed as a threat vector in the Summary.
• Unmanned aircraft systems (UAS): Remotely operated or autonomous aircraft platforms, cited as a threat to air bases.
• RFI (Request for Information): A procurement vehicle used to gather industry data and shape future solicitations; the vehicle issued by the Air Force in this event.

Intelligence Response

Cabrillo Signals War Room has already detected this RFI and produced this briefing. For immediate operationalization, use:

• Cabrillo Signals War Room to track any updates to the RFI and capture immediate alerting on amendments or Q&A releases.
• Cabrillo Signals Match Engine to rescore your opportunity pipeline and prioritize existing programs that align with air base defense capabilities.
• Cabrillo Signals Intelligence Hub to create saved searches for follow-on solicitations and to monitor DOD / Air Force activity for related awards.
• Proposal Studio (Proposal OS) to generate RFI response drafts, compliance matrices, and capability statements tailored to ground-based launcher requirements.
• Proposal Studio Workflow Tracker to run the capture through a 9-gate sequence, enforce compliance routing, and maintain audit-ready documentation.

Notify: capture manager, BD lead, proposal manager, security/compliance lead, lead systems engineer, and executive decision-maker. Immediate 48-hour playbook below focuses on producing an RFI response and positioning for the anticipated solicitation.

Relevant reading: Winning Federal Contracts Guide (/insights/winning-federal-contracts). For compliance preparation, see CMMC Compliance Guide (/insights/cmmc-compliance-guide) and CUI (Controlled Unclassified Information)-Safe CRM Guide (/insights/cui-safe-crm-guide).

First 48-hour response playbook

• Hour 0–4: Stand up the capture team; assign roles (capture lead, proposal owner, security lead, technical lead). Pull the RFI and confirm response mechanics and submission format. Trigger Cabrillo Signals War Room alerting for RFI amendments.
• Hour 4–12: Use Proposal Studio to draft a capability statement and white paper; map requirements and threats (cruise missiles, UAS) to existing products. Run Match Engine to rescore and prioritize related programs.
• Hour 12–24: Conduct a compliance gap assessment using Proposal Studio’s compliance matrix for ITAR, DFARS, CMMC, NIST 800-171, and EAR; produce remediation bullets for the RFI. Prepare executive summary for leadership decision.
• Hour 24–48: Finalize and submit the RFI response; configure saved searches in Intelligence Hub for follow-on solicitations and set notification rules. Begin capture plan for full solicitation: competitive landscape, teaming outreach, and funding alignment.