+

Cookies on the Business Insider India website

Business Insider India has updated its Privacy and Cookie policy. We use cookies to ensure that we give you the better experience on our website. If you continue without changing your settings, we\'ll assume that you are happy to receive all cookies on the Business Insider India website. However, you can change your cookie setting at any time by clicking on our Cookie Policy at any time. You can also see our Privacy Policy.

Close
HomeQuizzoneWhatsappShare Flash Reads
 

SpaceX tried to launch a Mars spaceship prototype on its first big flight, but the test was cut short after ignition

Jul 25, 2019, 08:05 IST

Advertisement
An aerial view of SpaceX's Starhopper rocket ship prototype after it aborted launch attempt from Boca Chica Beach, Texas, on July 24, 2019.SpaceX/YouTube

SpaceX tried to launch and fly its gleaming Starhopper rocket ship prototype into the skies of south Texas on Wednesday, but an as-yet unexplained issue cut short the test flight.

Starhopper stands more than 60 feet tall and 30 feet wide, has three landing legs, and is made out of stainless steel. The vehicle isn't designed to fly into space, though; it's a test-bed for technologies that could eventually power a much larger and more powerful launch system known as Starship.

SpaceX's Starhopper rocket ship prototype sits on a launch pad in south Texas in July 2019.SpaceX via dearMoon

Elon Musk, the founder of SpaceX, envisions Starship as a nearly 400-foot-tall, fully reusable system that can ferry about 100 people and more than 100 tons of cargo at a time to Mars. Where Starhopper has one Raptor rocket engine, a full-scale Starship headed for deep space may use more than 40, according to Musk.

Musk tweeted last week that Starhopper was supposed to lift off, hover, traverse sideways, and then land during this test. If successful, it would represent the most ambitious test yet for the vehicle, which workers chained to its launch pad during the very first launches in early April.

Advertisement

However, the test did not play out as SpaceX hoped it might on Wednesday evening, as a YouTube broadcast by the company revealed.

'As you can see, the vehicle did not lift off'

The video above show's about 20 seconds of the Starhopper's launch attempt.

The rocket ship ignited its single engine just after 8:32 p.m. ET (7:32 p.m. CT) blowing out a cloud of rocket exhaust, steam, and dirt. But two or three seconds later, either SpaceX engineers or automated systems shut down the engine and terminated the flight.

"It appears as though we have had an abort on today's test," Kate Tice, certification engineer at SpaceX, said during the broadcast. "As you can see there, the vehicle did not lift off."

Seconds after the engine shut down, a vent located on top of the vehicle flared up and began shooting flames, though it did not appear to cause any visible damage and quickly died out.

Advertisement

The aborted launch follows a successful test-firing last week, though that test apparently disconnected a fuel line, spilled liquid methane onto the launch pad, and triggered an enormous flare-up.

Read more: A huge fireball briefly swallowed SpaceX's Mars rocket prototype, but Elon Musk says there is 'no major damage'

Tice reminded viewers during Wednesday's launch attempt that Starhopper is part of an ongoing development program and not an operational rocket system.

"Today was a test flight designed to test the boundaries of the vehicle," Tice said.

A SpaceX spokesperson previously told Business Insider in an email that the hop-and-hover test is "one in a series of tests designed to push the limits of the vehicle as quickly as possible to learn all we can, as fast as we safely can."

Advertisement

A company representative could not immediately provide additional information about the launch abort, its cause, or when SpaceX would make its next attempt.

NOW WATCH: Elon Musk's multibillion-dollar Starship rocket could one day take people to the moon and Mars

You are subscribed to notifications!
Looks like you've blocked notifications!
Next Article