As fighter pilots prepare to command drone wingmen, BAE bets on new helmet tech

TL;DR

The Air Force has requested nearly $1 billion from Congress to begin procurement of Collaborative Combat Aircraft (CCA), a new fleet of semi-autonomous drone wingmen intended to operate alongside crewed fighters such as the F-35 and F-22. This signals a major new acquisition line that opens contracting opportunities across autonomous systems, AI integration, human-machine interface technologies, and avionics. BAE Systems is positioning helmet-mounted display technology to support pilots commanding multiple drones, highlighting emerging technical requirements for pilot-centered control and situational awareness. Affected markets include defense and aerospace firms, autonomous/unmanned systems suppliers, avionics and HMI developers, advanced manufacturing, and R&D organizations. Contractors should begin capture and technical alignment now, prioritize applicable cybersecurity and export compliance, and establish monitoring for follow-on solicitations and funding actions. Immediate implications include early-stage requirements definition, potential IDIQ (Indefinite Delivery/Indefinite Quantity)/OTA/Defense Production Act Title III pathways, and elevated emphasis on pilot interface and AI-human teaming capabilities.

Key Points

• What happened: The Air Force has requested nearly $1 billion to begin procurement of Collaborative Combat Aircraft (CCA), a fleet of semi-autonomous drone wingmen to fly alongside crewed fighters; BAE Systems is promoting helmet-mounted display technology to support pilot control of multiple drones.
• Who is affected: Defense and aerospace contractors across the listed market segments and NAICS codes in segmentation (336411, 334511, 541512, 541715, 336413, 334220, 541330); agencies named in segmentation (DOD, Department of the Air Force, Air Force Materiel Command).
• Timeline: Timeline TBD pending source review.
• What contractors should do NOW: Begin capture planning and gap analysis focused on autonomous systems, AI integration, HMI/helmet-mounted displays, and avionics; confirm export and cybersecurity posture against ITAR (International Traffic in Arms Regulations), EAR, CMMC (Cybersecurity Maturity Model Certification), NIST 800-171 (NIST Special Publication 800-171), and DFARS (Defense Federal Acquisition Regulation Supplement) 252.204-7012; position teams to respond to IDIQ, OTA, or Defense Production Act Title III opportunities; set saved searches and alerts for solicitations and funding notices.

Who Is Affected

Affected segments include defense and aerospace suppliers, autonomous systems and unmanned aerial systems integrators, AI/ML developers for mission systems, avionics and human-machine interface (HMI) technology providers, advanced manufacturing vendors, and research and development organizations. Specific NAICS codes, agencies, contract vehicles, and compliance regimes are listed in the segmentation and include:

• NAICS: 336411, 334511, 541512, 541715, 336413, 334220, 541330
• Agencies: DOD, Department of the Air Force, Air Force Materiel Command
• Contract vehicles: IDIQ contracts, Other Transaction Authority (OTA), Defense Production Act Title III
• Compliance regimes: ITAR, CMMC, NIST 800-171, DFARS 252.204-7012, Export Administration Regulations (EAR)

If you need program- or solicitation-level specifics, those are pending source review.

Frequently Asked Questions

Q: What exactly are Collaborative Combat Aircraft (CCA)?

A: Collaborative Combat Aircraft (CCA) are described in the summary as a fleet of semi-autonomous drone wingmen designed to fly alongside crewed fighters such as the F-35 and F-22.

Q: How large is the funding request and what does that mean for contract opportunities?

A: The Air Force has requested nearly $1 billion from Congress to begin procurement of CCA. What this means operationally is an early-stage acquisition that can produce opportunities across autonomous systems, AI integration, HMI/helmet-mounted displays, avionics, manufacturing, and R&D. Specific opportunity schedules and procurement instruments are pending source review.

Q: Are there specific contract vehicles or compliance requirements I must prepare for?

A: The segmentation identifies IDIQ contracts, OTA, and Defense Production Act Title III as potential vehicles; compliance regimes flagged include ITAR, CMMC, NIST 800-171, DFARS 252.204-7012, and EAR. Exact vehicle and compliance applicability to solicitations will be confirmed when solicitations and procurement guidance are released.

Definitions

• Collaborative Combat Aircraft (CCA): Semi-autonomous drone wingmen designed to operate alongside crewed fighters to extend mission capability.
• Helmet-mounted display technology: Pilot-worn display systems that present flight, sensor, and control information; cited as a candidate interface for pilots commanding multiple drones.
• Drone wingmen / semi-autonomous: Unmanned aerial systems operating with degrees of autonomy to support crewed aircraft and execute coordinated missions.

Intelligence Response

Cabrillo Signals War Room has already detected this event and delivered this briefing. Use the following Cabrillo products to operationalize an immediate response and maintain continuous coverage:

• Cabrillo Signals War Room — Primary alerting source; already detected this event and provided this flash brief. Use it for continuous monitoring of policy, funding notices, and public statements that refine CCA requirements.
• Cabrillo Signals Match Engine — Rescore your opportunity pipelines and reprioritize opportunities when CCA-related solicitations or requirements are published.
• Cabrillo Signals Intelligence Hub — Track affected agencies (DOD, Department of the Air Force, Air Force Materiel Command), NAICS codes, and contract vehicles (IDIQ, OTA, Defense Production Act Title III). Set saved searches to alert on SAM.gov (System for Award Management) postings and notices.
• Proposal Studio (Proposal OS) and Proposal Studio Workflow Tracker — Begin capture and proposal workflows immediately with AI-assisted compliance matrices, win themes, and the 9-gate capture tracker.

Notify these roles immediately: Capture Lead, Business Development Director, CTO/Systems Engineering Lead, Cybersecurity and Compliance Lead, and Proposal Manager. First 48-hour playbook:

• Hour 0–4: Convene capture standup; assign roles; enable saved searches in Cabrillo Signals Intelligence Hub; circulate this brief to named roles.
• Hour 4–12: Run Match Engine rescore of active pipelines for CCA relevance; prioritize top pursuits; open Proposal Studio workspaces for prioritized efforts.
• Hour 12–24: Complete cybersecurity and export compliance gap analysis (ITAR, CMMC, NIST 800-171, DFARS 252.204-7012, EAR); begin technical approach outlines focused on AI integration and helmet-mounted HMI concepts.
• Hour 24–48: Populate Proposal Studio with compliance matrices and win themes; initiate capture tasks in Proposal Studio Workflow Tracker (9-gate), schedule stakeholder engagements, and prepare capability briefs for IDIQ/OTA/Defense Production Act Title III pathways.

For guidance on proposal and compliance posture, consult our primary hub and related guides:

• Winning Federal Contracts Guide (/insights/winning-federal-contracts)
• CMMC Compliance Guide (/insights/cmmc-compliance-guide)
• CUI (Controlled Unclassified Information)-Safe CRM Guide (/insights/cui-safe-crm-guide)