Air Force Official: CCAs Will Be ‘Optionally Attritable’

TL;DR

The Air Force has clarified that Collaborative Combat Aircraft (CCA) will be designated as "optionally attritable" rather than fully attritable or expendable. This means commanders may choose to risk CCAs on high-threat missions but platforms could also be expected to have extended service lives, changing design, sustainment, and lifecycle cost expectations. Contractors pursuing CCA work must plan for flexible design specifications that balance affordability with durability and prepare for sustainment models that support both recoverable and risked employment. Expect capture strategies, proposal requirements, and long-term support contracts to reflect this dual-use lifecycle approach. Immediate implications include re-evaluating materials and modularity choices, updating cost models, and ensuring sustainment plans can accommodate variable attrition rates.

Key Points

• What happened: The Air Force clarified its CCA acquisition posture — CCAs will be "optionally attritable" rather than fully attritable or expendable.
• Who is affected: Defense and aerospace contractors in the following segments and NAICS codes: 336411, 336413, 541712, 541330, 336414, 541715; affected agencies include DOD, Air Force, and AFMC; contract vehicles called out include IDIQ (Indefinite Delivery/Indefinite Quantity), OTA, and AFWERX; compliance surfaces include CMMC (Cybersecurity Maturity Model Certification), NIST 800-171 (NIST Special Publication 800-171), ITAR (International Traffic in Arms Regulations), DFARS (Defense Federal Acquisition Regulation Supplement) 252.204-7012, and EAR.
• Timeline: Timeline TBD pending source review.
• What contractors should do NOW: Initiate capture reviews to adjust requirements for optional attritability, rescore opportunities, update lifecycle cost and sustainment assumptions, and route engineering and security teams to reconcile durability vs. affordability trade-offs.

Who Is Affected

Affected market segments and roles include Defense, Aerospace, Unmanned Systems, Aircraft Manufacturing, Defense R&D, and Autonomous Systems contractors working in development, manufacturing, and sustainment of CCA platforms. Specific NAICS codes, agencies, contract vehicles, and compliance regimes named in the segmentation are:

• NAICS: 336411; 336413; 541712; 541330; 336414; 541715
• Agencies: DOD; Air Force; AFMC
• Contract vehicles: IDIQ; OTA; AFWERX
• Compliance regimes: CMMC; NIST 800-171; ITAR; DFARS 252.204-7012; EAR

Frequently Asked Questions

Q: What does "optionally attritable" mean for platform design requirements?

A: Per the Air Force clarification, "optionally attritable" signals that CCAs may be risked in high-threat missions at commanders' discretion while also being expected to have potential extended service lives. Contractors should therefore design for modularity, recoverability options, and lifecycle serviceability. Specific technical requirements and thresholds are pending source review.

Q: Will this change affect sustainment contracting and lifecycle cost modeling?

A: Yes. The policy shift directly impacts sustainment approaches and lifecycle cost structures because platforms must support both expendable-risk operations and longer-term sustainment. Detailed contract and solicitation language that defines sustainment expectations is pending source review.

Q: Which solicitations or contract vehicles will reflect this change immediately?

A: Pending source review. The segmentation indicates IDIQ, OTA, and AFWERX as relevant vehicles to monitor, but exact solicitations and timelines will be identified when follow-on notices or solicitations appear.

Definitions

• Collaborative Combat Aircraft (CCA): Unmanned or optionally-manned aircraft that operate collaboratively with manned assets and other unmanned systems as described in the event title and summary.
• Optionally attritable: A classification indicating a platform may be risked or expended in certain missions by commander decision while also being expected to support longer service life and sustainment in other contexts.
• Attritable: Describes systems designed to be low-cost and potentially expendable in contested environments.
• Expendable: Describes systems intended to be used with the expectation they will not be recovered after certain missions.

Intelligence Response

• Which Cabrillo products to leverage:
• Cabrillo Signals War Room — Already detected this event and delivered this briefing. Use it for continuous monitoring of policy discussion and official clarifications.
• Cabrillo Signals Match Engine — Rescore and reprioritize live opportunity pipelines to reflect increased emphasis on dual-capability platforms (affordability + durability).
• Cabrillo Signals Intelligence Hub — Run saved searches against agencies and contract vehicles (IDIQ, OTA, AFWERX) and set alerts for follow-on solicitations or RFPs.
• Proposal Studio (Proposal OS) & Proposal Studio Workflow Tracker — Begin bid/no-bid decisions, update compliance matrices for CMMC/NIST/DFARS/ITAR/EAR, and initiate the 9-gate capture workflow for prioritized opportunities.
• Who to notify:
• Capture Managers — immediate bid/no-bid and strategy adjustments.
• Business Development / BD Leadership — go/no-go and pipeline reprioritization.
• Systems Engineering / Design Leads — technical trade-off analysis for durability vs. cost.
• Sustainment / Logistics Leads — update long-term support models and spares strategies.
• Security & Compliance Officers — verify CMMC, NIST 800-171, DFARS, ITAR, and EAR implications.
• Proposal Teams — prepare solicitation response templates and compliance matrices.
• First 48-hour response playbook:
• Hour 0–4: Alert capture and BD teams via Signals War Room; push notification to capture owners and systems engineering leads. Run an immediate rescore in Match Engine for all active CCA-related opportunities.
• Hour 4–12: Intelligence Hub: execute saved searches for IDIQ, OTA, and AFWERX solicitations; assemble draft bid/no-bid assessments in Proposal Studio.
• Hour 12–24: Convene cross-functional working group (BD, engineering, sustainment, compliance) to identify key design and sustainment trade-offs; start updating lifecycle cost models.
• Hour 24–48: Lock initial capture plan and schedule Proposal Studio Workflow Tracker 9-gate capture timeline; create targeted compliance checklist referencing CMMC Compliance Guide (/insights/cmmc-compliance-guide) and secure data handling steps per CUI (Controlled Unclassified Information)-Safe CRM Guide (/insights/cui-safe-crm-guide). Refer teams to Secure Operations Guide (/insights/secure-operations-guide) for operational security baseline.

Links and resources:

• Primary hub: Secure Operations Guide (/insights/secure-operations-guide)
• Related guides:
• CMMC Compliance Guide (/insights/cmmc-compliance-guide)
• CUI-Safe CRM Guide (/insights/cui-safe-crm-guide)