US Space Force stages first unclassified satellite dogfight in orbit

Two commercial-built satellites, on a US Space Force call-up, were launched and maneuvered into a pursuit-and-evasion pattern in low-Earth orbit within about 17 hours of the order. It is the first unclassified public demonstration of orbital pursuit and evasion, and it turns "responsive" space operations from a poster phrase into a measured operational tempo.

The mission is Victus Haze, the latest in a line of Space Force drills meant to test how quickly the US military and its commercial partners can put a satellite on orbit once a threat or opportunity appears. The tempo target set by Space Force is 72 hours from call-up to first on-orbit maneuver. Rocket Lab's Puma satellite, already built and in storage, was held against a 24-hour call-up. Once the order came, Rocket Lab rolled its Electron rocket and Puma to a New Zealand pad and launched them on June 19, less than 17 hours later. Within 38 hours of launch, Puma was fully activated and ready for its first orbital maneuver, beating the 72-hour requirement by more than a day.

The chase partner was True Anomaly's Jackal satellite, also known as Panther, which had launched earlier in May 2026 as part of the same Victus Haze campaign. Both satellites are roughly the size of a dishwasher to a small refrigerator, and Puma is built on Rocket Lab's Pioneer satellite platform. That scale is the point. Satellites this size can be warehoused and put on orbit without the multi-month build cycle of traditional military satellites.

Ars Technica reported the pursuit-and-evade scenario from True Anomaly's Wednesday announcement. True Anomaly co-founder and CEO Even Rogers framed the milestone as the culmination of four years of company work. The company has positioned Jackal as a chase vehicle and inspector, and the drill was the first time two commercial-built satellites publicly played pursuer and evader in a real conflict scenario, rather than a simulated one.

A 17-hour call-up-to-launch window and a 38-hour launch-to-maneuver window, against a 72-hour Space Force requirement, is not a marginal beat. It is a categorical change in the launch-to-operations timeline, from months of lead time to hours of lead time, and it puts the public proof behind a claim the Space Force has been making for several years. The public first is the proof. The chase happened, and the clock ran out faster than the requirement allowed.

This is one drill, with one call-up, on a publicized timeline. The open question is not whether the drill happened, since Ars Technica reports it and both companies have confirmed their parts, but whether the 17-and-38-hour tempo reproduces across call-ups, weather, range availability, and adversary behavior. Separately, no third-party technical confirmation of the pursuit-and-evade geometry has been published. The operational claim rests on the True Anomaly announcement as carried by Ars Technica, and the press has not yet laid out a public orbit-by-orbit reconstruction.

The next test is the second Victus Haze call-up, if and when Space Force runs one. If the second drill hits a comparable tempo, the hours-not-months framing becomes the new baseline. If it does not, the first drill is the exception, not the new rule, and the categorical claim retreats back to a hopeful one.