In the Space Force's Victus Haze orbital war game, Rocket Lab's Puma satellite was on orbit and maneuvering within 37 hours; True Anomaly's Jackal 0004 satellite spent 61 hours treating it as a 'non cooperative target spacecraft' — an unidentified
When the U.S. Space Force gave Rocket Lab a 24-hour launch notice in mid-June, the company lifted off 16 hours and 42 minutes later. Its Puma satellite reached orbit and within 37 hours and 36 minutes had completed its first orbital maneuver, beating the 72-hour commissioning window the service had set. That speed is the point of Victus Haze, the Space Force's most recent test of how quickly it can put a commercial-built spacecraft into a useful orbit and use it to characterize an unknown object overhead.
The exercise, formally part of the Tactically Responsive Space (TacRS) program, is built on a simple premise: the U.S. has no live combat record in orbit, and the question is not whether satellites can chase each other but whether one can be put on orbit, maneuver, and identify an unknown vehicle fast enough to matter if something goes wrong. Victus Haze staged that drill with two commercial partners, Rocket Lab for the launch and True Anomaly for the chase spacecraft.
Rocket Lab's Puma launched on an Electron rocket on June 19. True Anomaly's Jackal-0004 had been on orbit since May 3, when it lifted off on a SpaceX Falcon 9. The Space Force's plan was for Puma to come up, maneuver into Jackal's orbital regime, and let Jackal characterize it as a "non-cooperative target spacecraft," the kind of object an adversary might put overhead without identifying itself. The two vehicles then ran a series of evasive and approach maneuvers to simulate interception. In Space Systems Command's account, the rendezvous and characterization completed inside the program's timing target.
Bryon McClain, the Space Force's acting portfolio acquisition executive for Space Combat Power, framed the mission as the ability to "respond to irresponsible behavior on orbit under operationally realistic conditions," a phrase that points at the practical use case without claiming one has occurred. His title is itself a marker. "Acting" status on a Space Force acquisition role is perishable, and the program he runs is the Space Force's responsive-space effort.
The speed target is not new. Victus Haze is the latest in a line of TacRS demonstrations that began in 2023 with Victus Nox, when a Millennium Space Systems satellite reached orbit roughly 27 hours after order. Each iteration has compressed the timeline further. Puma's 37 hours and 36 minutes to first maneuver and Jackal's 61-hour characterization inside the 72-hour window are the new marks. The drill demonstrates that the commercial-vendor pipeline can deliver a usable on-orbit asset on a phone-call timeline. It does not yet show that this asset will be decisive in a real crisis, when the orbital geometry, the threat profile, and the rules of engagement would all be different.
That gap is the harder question Victus Haze does not answer. The chase-and-characterize capability has civilian inspection uses too: verifying a friendly satellite, imaging debris, supporting space-traffic management. In a contested orbit, the same hardware becomes part of a posture the U.S. has not previously exercised. Running practice intercepts in shared orbits raises debris and escalation questions, though the program has not publicly detailed how it handles them. And the commercial partners doing the building have revenue that depends on Space Force contracts. Victus Haze demonstrates speed. It does not, on its own, demonstrate judgment.
The next test for the program is the next TacRS iteration, which the service has not yet dated publicly. Until then, the program has a number it can publish: 37 hours and 36 minutes from notice to first maneuver, against a 72-hour deadline it set itself.