General Atomics delivers FQ-42 Vengeance to Nevada air base

TL;DR

General Atomics delivered its FQ-42 Vengeance Collaborative Combat Aircraft to Creech Air Force Base for operational testing, a milestone in the Air Force's Collaborative Combat Aircraft (CCA) program that signals accelerating program momentum. The Air Force's FY2027 budget request includes $2.37 billion for CCA procurement and development, with plans to field at least 500 autonomous aircraft by 2032. General Atomics is self-funding production to maintain delivery at six aircraft per month while government funding plans mature. This combination of funded program intent and industry self-funding creates near-term demand signals for systems integration, autonomous systems support, logistics, and operational test sustainment. Contractors in defense, autonomous systems, UAS, AI/ML integration, and aerospace manufacturing should treat this as a high-priority opportunity to align capture and compliance activities. Immediate implications: monitor for follow-on solicitations and IDIQs, validate cybersecurity and export controls posture, and ready capture artifacts for accelerated response.

Key Points

• What happened: General Atomics delivered the FQ-42 Vengeance Collaborative Combat Aircraft to Creech Air Force Base for operational testing in support of the Air Force CCA program.
• Who is affected: Defense contractors and suppliers in the listed market segments and NAICS footprints — NAICS: 336411, 336413, 541330, 541712, 541715, 336414, 541513; Agencies: DOD, Air Force, Air Combat Command.
• Timeline: FY2027 budget request includes $2.37 billion for CCA procurement and development; plans to field at least 500 autonomous aircraft by 2032; General Atomics is producing at a pace of six aircraft per month while government funding plans mature.
• What contractors should do NOW: Stand up or refresh a dedicated capture team, validate CMMC (Cybersecurity Maturity Model Certification)/NIST/ITAR (International Traffic in Arms Regulations)/DFARS (Defense Federal Acquisition Regulation Supplement) compliance posture, configure monitoring for CCA-related solicitations and IDIQs, and prepare proposal skeletons and compliance matrices targeting systems integration, autonomous systems support, and operational testing/logistics work.

Who Is Affected

Affected segments include defense and aerospace companies focused on autonomous systems, unmanned aerial systems, systems integration, AI/ML integration, operational testing and evaluation, and logistics support services. Specific NAICS codes, agencies, contract vehicles, and compliance regimes named in the segmentation are:

• NAICS: 336411; 336413; 541330; 541712; 541715; 336414; 541513
• Agencies: DOD; Air Force; Air Combat Command
• Contract vehicles: Air Force CCA Program; IDIQ (Indefinite Delivery/Indefinite Quantity) contracts for autonomous systems; Air Force Life Cycle Management Center contracts
• Compliance surfaces: CMMC; NIST 800-171 (NIST Special Publication 800-171); ITAR; DFARS 252.204-7012; NIST 800-53

If you need capture targeting templates, see the primary hub: Winning Federal Contracts Guide (/insights/winning-federal-contracts) and related compliance resources: CMMC Compliance Guide (/insights/cmmc-compliance-guide) and CUI (Controlled Unclassified Information)-Safe CRM Guide (/insights/cui-safe-crm-guide).

Frequently Asked Questions

Q: Is procurement funded for the CCA program now?

A: The Air Force's FY2027 budget request includes $2.37 billion for CCA procurement and development. General Atomics is also self-funding production to keep deliveries at six aircraft per month while government funding plans mature.

Q: Will this create new contracting opportunities for systems integrators and support contractors?

A: The Summary identifies potential contracting opportunities in autonomous systems integration and support, operational testing, and logistics. Specific solicitations, award timelines, and procurement vehicles are pending source review.

Q: Where is operational testing occurring?

A: The delivered FQ-42 Vengeance was delivered to Creech Air Force Base for operational testing.

Definitions

• FQ-42 Vengeance: The Collaborative Combat Aircraft platform delivered by General Atomics referenced in this event.
• Collaborative Combat Aircraft (CCA): The Air Force program for autonomous collaborative aircraft described in the Summary.

Intelligence Response

• Cabrillo Signals War Room — Already detected this event and delivered this briefing. Continuously monitors regulatory changes, contract vehicles, and policy shifts related to large defense programs and autonomous systems.
• Cabrillo Signals Match Engine — Will automatically rescore and reprioritize opportunity pipelines when this event shifts competitive dynamics, flagging downstream IDIQs and task orders for capture teams.
• Cabrillo Signals Intelligence Hub — Tracks the affected agencies, NAICS codes, and contract vehicles identified in the segmentation. Saved searches will alert when follow-on solicitations appear on SAM.gov (System for Award Management) or related sources.
• Proposal Studio (Proposal OS) & Proposal Studio Workflow Tracker — Use Proposal OS to generate compliance matrices, win themes, and a bid/no-bid decision record; then run the capture through Proposal Studio Workflow Tracker’s 9-gate process to produce audit-ready documentation.

Who to notify now:

• BD/Capture Lead — to assign capture owner and begin opportunity mapping.
• CTO/Systems Engineering Lead — to assess technical fit for systems integration and autonomy workloads.
• Cybersecurity/Compliance Lead — to validate CMMC, NIST 800-171, DFARS 252.204-7012, and ITAR readiness.
• Proposal Manager — to initiate proposal skeleton and compliance matrices.

First 48-hour response playbook

• Hour 0–4: Trigger Cabrillo Signals War Room alert stream; create saved search in Cabrillo Signals Intelligence Hub for CCA-related solicitations and the listed NAICS codes/agencies.
• Hour 4–12: Run opportunity rescoring in Cabrillo Signals Match Engine; convene BD/Capture lead and CTO for quick Go/No-Go assessment.
• Hour 12–24: Start compliance gap analysis against CMMC, NIST 800-171, DFARS 252.204-7012, and ITAR; open a Proposal Studio (Proposal OS) capture workspace and import baseline artifacts.
• Hour 24–48: Populate Proposal Studio Workflow Tracker gates 1–3 (capture plan, compliance matrix, win themes); assign draft responsibilities and schedule an internal red team timeline.

Leverage the hub and guides referenced above for compliance and CRM practices: Winning Federal Contracts Guide (/insights/winning-federal-contracts), CMMC Compliance Guide (/insights/cmmc-compliance-guide), CUI-Safe CRM Guide (/insights/cui-safe-crm-guide).