Skip to content

The Rocket That Lost 13 Satellites in Under a Minute

In Simple Terms

Super Strypi was a U.S. rocket designed to send small satellites into space quickly and at lower cost. It lost control shortly after launching in Hawaii in 2015, destroying all 13 satellites it carried, and the program never flew again. The need for rapid launches remained, however, and the U.S. Space Force later turned to commercial companies for that capability.

A Fast Launch, an Early End

On the evening of November 3, 2015, an experimental rocket lifted off from the Pacific Missile Range Facility near Barking Sands on the island of Kauai, Hawaii. The launch was unusual: Super Strypi was designed to leave the ground with help from a launch rail. The test was part of a U.S. Air Force effort to make getting payloads into orbit faster and less expensive. But the rocket never made it to space. Less than a minute after liftoff, it began tumbling out of control, and the flight ended in a crash that destroyed the small satellites aboard.

A Fast Takeoff and a Sudden Failure

The test belonged to a program intended to provide a way to send small payloads into orbit when needed, especially in situations calling for a rapid response. The rocket lifted off from the Hawaii launch site at about 9:45 p.m. local time. It climbed at first, but its path soon went awry. Rather than continue on a steady ascent, the rocket began to wobble and spin.

The critical part of the flight lasted less than a minute. Before long, the rocket had crashed, taking every payload with it. Available explanations pointed to a possible problem with the first-stage engine, but published information about the accident did not establish that as the definite cause. It is therefore more accurate to describe a first-stage propulsion problem as a suspected fault, not a confirmed explanation.

Thirteen small satellites were lost. They did not all belong to a single project or organization: the rocket carried one primary satellite along with a group of smaller spacecraft that had joined the flight. The impact of the failure therefore went beyond the loss of the launch vehicle itself. Several different plans depended on those payloads reaching space, and all were affected.

A New-Era Design with Old Roots

Super Strypi took its name and broad inspiration from the Strypi rocket, which first appeared in the 1960s. The earlier vehicle was a suborbital research rocket used in tests involving atmospheric reentry vehicles and targets for anti-missile systems. The newer version aimed to take the concept much further: it was a three-stage vehicle designed to reach orbit, rather than follow a short flight path that ended before getting there.

All three stages used solid-fuel rocket motors made by Aerojet Rocketdyne. Dividing a rocket’s flight into stages allows different sections to operate in sequence during ascent, rather than having the entire vehicle act as one unit from beginning to end. A launch rail was another distinctive feature. It helped guide the rocket as it left the launch site, offering an alternative to a conventional vertical launch from a standard pad.

The project was more than a historical redesign. The Air Force wanted to test a system that could be prepared for national security missions and offer a lower-cost way to put small satellites into orbit. The stated goal was to carry up to 300 kilograms of payload into space for about $15 million per mission. On paper, those figures made the idea appealing: the rocket could carry a useful load of small satellites at a price intended to make orbital launches more accessible for certain missions.

Thirteen Satellites on One Flight

The primary payload was the ORS-4 satellite, short for Operationally Responsive Space-4. Engineers at the University of Hawaii developed it for the Air Force, and it was also known as HiakaSat. The plan was for the satellite to take pictures of Earth and monitor environmental conditions over the course of one year. The mission was expected to provide data from orbit while also testing whether the new rocket could do the job it had been built to perform.

The other 12 satellites were rideshare payloads. The group included eight CubeSats prepared for NASA’s EDISON demonstration of small satellites, as well as four satellites from universities. CubeSats are built in relatively small sizes, making them suitable for experiments and programs that do not require a large spacecraft. Several can also be operated as a group, spreading a mission across multiple units instead of relying on a single satellite.

But small size and relatively low cost do not mean that losing satellites has no consequences. Each spacecraft represents a mission or experiment, along with the work of the teams behind it, the launch plans, and the data they hope to collect. This flight brought together payloads from the Air Force, NASA, and several universities on a single rocket. When the launch failed, the whole group was lost at once, and none of the 13 satellites reached its intended orbit.

The Failure That Halted the Program

Super Strypi was meant to add a new option for rapid launches, but its test flight did not lead to a series of follow-up attempts. The Air Force did not resume using the rocket after the accident, and no further launches took place. Over time, the program lost momentum and never became a regularly used operational launch system.

The outcome highlights an important lesson in rocket development: a promising design and a low target price are not enough to create a dependable service. A vehicle has to pass its tests, prove it can deliver payloads safely, and demonstrate that it can do so repeatedly. When an early mission carrying multiple satellites fails, the cost of deciding what to do next goes beyond the loss of the rocket. It also includes confidence in the system and the time organizations need to determine whether another attempt is worthwhile.

A single incident does not prove that launching from a rail cannot work, nor does it reveal every reason the program stalled. What the flight does show is that the rocket lost control before achieving its goal, and that a possible first-stage problem did not provide a sufficient basis for the program to return to flight. Super Strypi thus became an example of the gap between the promise of rapid response and the practical challenge of building a rocket that works reliably when needed.

From a Government Project to Commercial Response

After Super Strypi was grounded, neither the Air Force nor the U.S. Space Force launched another mission using the same rocket. Instead, the Space Force turned to commercial companies for faster launch options. The shift reflects a different way of meeting the need: rather than depending on a single experimental government vehicle, the military could work with providers that already had rockets and launch services in operation.

One example of this approach is the U.S. Space Force’s partnership with Rocket Lab to launch the Victus Haze mission. Preparations for launch were made with just 17 hours’ notice, a turnaround described as a new record for such a short-notice response. That does not mean every space mission can be carried out so quickly. It does, however, illustrate the capability military organizations sought to develop: reducing the time between requesting a launch and carrying it out by making use of rapid commercial arrangements.

This is where Super Strypi’s original purpose connects to later launch strategies. The problem the program was designed to address did not disappear when the rocket failed. There is still a need to get small satellites into orbit quickly when a mission calls for it. What changed was the means: the answer no longer depended on bringing the experimental rocket back into service, and commercial companies became part of the approach chosen to meet urgent launch requirements.

What Remains of the Hawaii Test?

The November 2015 flight offers a compact picture of the risks involved in developing new launch systems. One project brought together a plan to lower costs, carry a payload of up to 300 kilograms, use a three-stage design, and provide rapid response for national security. But a flight that ended in failure less than a minute after liftoff showed that these goals do not become practical capabilities simply because they appear in a promising design.

The loss also underscored that CubeSats are part of a broader system, not just small devices that are easy to replace. The 13 payloads represented different missions: a primary satellite intended to monitor Earth and the environment for one year, eight satellites associated with a NASA demonstration, and four university satellites. Sharing a single rocket made the launch efficient in terms of carrying multiple payloads together, but it also meant that the accident affected all those plans at the same time.

The clearest legacy of the project is that rapid launch remained a priority even after Super Strypi’s final flight. The rocket stopped flying, but the goal it was designed to serve continued to appear in other arrangements, including preparations to launch a mission with 17 hours’ notice. The two approaches differed greatly in their hardware and execution, but both addressed the same question: how can a payload be sent into orbit quickly when speed is central to the mission?

The Bottom Line

Super Strypi was an ambitious attempt to turn a rocket with roots in the 1960s into a three-stage orbital vehicle capable of carrying small satellites for a target cost of $15 million per flight. Its November 3, 2015, test in Hawaii ended in a crash less than a minute after launch, destroying 13 satellites. A first-stage engine problem was suspected but never confirmed, and the program did not return to flight. The U.S. Space Force later pursued rapid launches through commercial providers, with the Victus Haze mission demonstrating a 17-hour notice period. The rocket failed, but the need it was built to address did not go away.