CCA - Khan BMS Battlefield Management System
What CCA (Collaborative Combat Aircraft) actually does on a contested cca protocols link, and why Khan BMS treats it as a formation-level primitive instead of a vendor integration.
Ask any signaller who has worked through Russian EW and they will tell you what CCA actually does for a living. The textbook calls it Collaborative Combat Aircraft. The fight calls it the difference between a tasking that lands and one that times out.
Strip the marketing and CCA is exactly what the standard says: Collaborative Combat Aircraft. U.S. Air Force program for affordable, autonomous wingmen teamed with crewed fighters. CCA is the U.S. Air Force's program of record for autonomous, attritable or exquisite uncrewed aircraft that team with NGAD, F-35, and F-22 to multiply sensors, shooters, and EW effects. Increment 1 vendors include General Atomics (YFQ-42A) and Anduril (YFQ-44A). Open standards (OMS, UCI, FACE), modular payloads, and government-owned autonomy reference architectures are central to the program's affordability and competition strategy.
Khan BMS treats CCA as a property of the formation, not a feature of the radio. Every node in a cca protocols stack publishes its CCA state to its parent tier as a signed envelope; every parent reasons about CCA the same way it reasons about fuel, ammunition or sensor coverage.
That is the unglamorous version of why Khan BMS exists: to make CCA a routine operating assumption instead of a research demo.