SciTec, a Firefly Aerospace company, announced on 8 October a $1.5 million extension to its Cloud-Based Command and Control (CBC2) contract with the US Department of the Air Force. The company says the extension brings the total contract value to $31 million and will add a new class of approved counter-unmanned-aircraft-system sensor feeds to its existing data-fusion work for the Advanced Battle Management System. This is a contract expansion and planned integration, not evidence that the new feeds have already been deployed or validated in operations.
Why the integration matters
Counter-drone defence depends on combining observations from sensors that may detect or track the same small aircraft differently. A data-fusion layer can help present a coherent track to operators, but its usefulness depends on the quality of each input, timeliness, association of observations and connection to decision-making systems. SciTec says its extension is intended to improve situational awareness by adding approved CUAS sensor data sources. It does not name those sensors, their suppliers, installations, number of feeds or integration schedule.
The company's announcement does not publish detection ranges, false-alarm rates, track accuracy, latency measurements, independent test results or a new counter-drone defeat capability. Nor does it say the $31 million total is solely for counter-UAS; that figure is the cumulative CBC2 contract value after the $1.5 million addition. This distinction matters when comparing spending on sensors, data fusion and effectors.
The next milestone would be evidence that the named feeds were integrated, tested with operational users and used in a defined counter-UAS workflow. Until then, this is a funded software and sensor-data integration step within an existing Air Force battle-management programme.
Publication history
- — Added CBC2 counter-UAS sensor integration award with funding and fielding limits.
Suggest a correction to this entry
Follow the evidence
Source types identify who makes the claim. Programme milestones and supplier statements should be read in context.
