Air Force Seeks Flight-Ready AI for Autonomous Cislunar Spacecraft

The Department of the Air Force is surveying industry for commercially available, flight-ready artificial intelligence and machine learning software that can support autonomous spacecraft operating in cislunar space. Its request for information (RFI) reflects a broader government objective to develop a sustained architecture beyond Earth orbit. The service is seeking mature capabilities that can be integrated with limited adaptation, rather than proposals to launch a new government-funded research and development program. Responses are due December 4, 2026, and information collected may inform future requirements and procurement decisions. The RFI itself does not constitute a contract award or a funded development opportunity.

The operational case for autonomy centers on the scale of cislunar space and the resulting communications delays. According to the RFI, the larger domain can make traditional ground-based command, control, and mission planning systems difficult to use on operationally relevant timelines. Software that enables spacecraft to plan and execute actions without continuous ground contact could help address that constraint. The requested capabilities include autonomous mission planning and spacecraft operations, predictive analytics for maintenance and anomaly detection, trajectory optimization, computer vision, and hazard avoidance. The source material also cites station-keeping and identifying celestial bodies or man-made objects as relevant autonomous functions.

For contractors, this is principally a market-research signal and an opportunity to shape the government’s understanding of available commercial technology. The Air Force is looking for software that is already developed or readily demonstrable, not a lengthy development roadmap. The RFI establishes demanding transition milestones: initial software and simulation verification within 90 days of an Authority to Proceed, followed by full flight qualification within 18 months. Prior experience in cislunar space is not necessarily required; respondents can explain how software proven in other orbits applies to cislunar dynamics. Companies should distinguish demonstrated performance from planned capability and show how their existing products can meet the schedule with little training and minimal adaptation.

A strong response will connect algorithm performance to the spacecraft environment and the practical path to deployment. The Air Force asks respondents to describe hardware and computing needs, including processor architecture, memory, and power consumption, as well as data-rights considerations. It also wants approaches for in-orbit verification and software updates, plus safeguards against erroneous decisions caused by sensor failures or adversarial inputs. These details matter because an autonomy product must operate within spacecraft resource limits and remain testable and controllable when communication with Earth is delayed. Vendors should make their assumptions explicit and explain how simulation evidence, testing, and flight qualification can be achieved against the stated milestones.

• Opportunity type: An RFI seeking industry white papers; it is not a solicitation, contract award, or funded R&D program.
• Response deadline: December 4, 2026. Interested organizations should allow time to document technical evidence and integration assumptions.
• Primary capability areas: Autonomous mission planning and spacecraft operations, predictive analytics, trajectory planning and optimization, and computer vision; hazard avoidance and other relevant technical areas are also identified.
• Operational rationale: Cislunar distances and domain volume can introduce communications latency that limits reliance on ground-based command, control, and mission planning.
• Transition targets: Initial software and simulation verification within 90 days of an Authority to Proceed, and fully qualified flight-ready software within 18 months.
• Flight heritage: Prior cislunar flight experience is not a prerequisite if respondents can demonstrate that software used in other orbits applies to cislunar conditions.
• Technical response detail: Address processor architecture, memory, power consumption, data needs and rights, in-orbit verification, and software update mechanisms.
• Safety and assurance: Explain safeguards for sensor failures, anomalous conditions, and adversarial inputs, including how the system limits or detects erroneous autonomous decisions.
• Procurement implication: White papers may help shape future requirements and contracts, so vendors should clearly separate current, demonstrable capability from future development needs.

For prospective respondents, the most useful positioning is evidence-based: identify the functions the software performs today, the environments in which it has been tested or flown, and the adaptation required for cislunar operations. The RFI’s emphasis on rapid readiness favors companies able to support a near-term demonstration and a credible verification plan, rather than organizations whose core offering depends on substantial new development. Vendors should also explain how autonomy can be validated without uninterrupted ground contact and how operators can review, update, or constrain software behavior in orbit.

The announcement follows earlier public comments by Tom Ainsworth, then performing the duties of the Air Force assistant secretary for space acquisition and integration, that the Space Force would begin establishing leadership positions to acquire technologies for the cislunar mission area. That context points to growing institutional attention, but it does not establish a funded program or guarantee a follow-on procurement. Industry should treat the RFI as a chance to communicate the state of the market, identify integration requirements, and influence potential future acquisition planning while avoiding assumptions about a specific award or timeline beyond the milestones stated in the request.