Elon Musk's SpaceX suffers capsule anomaly during Florida tests

Orange smoke was seen rising above SpaceX’s facilities, and that the anomaly was contained with no injuries


Reuters April 23, 2019
A SpaceX Falcon Heavy rocket lifts off from historic launch pad 39-A at the Kennedy Space Center in Cape Canaveral, Florida, US, February 6, 2018. PHOTO: REUTERS

Elon Musk’s SpaceX suffered an anomaly in one of its Crew Dragon capsules while conducting engine tests at the Cape Canaveral Air Force Station in Florida on Saturday, the company said.

“The initial tests completed successfully but the final test resulted in an anomaly on the test stand,” the company said in a statement.

The issue was earlier reported by Florida Today, which said orange smoke was seen rising above SpaceX’s facilities, and that the anomaly was contained with no injuries.

NASA heading back to Moon soon, and this time to stay

SpaceX said its teams are investigating and are working closely with US National Aeronautics and Space Administration (NASA) partners.

"NASA has been notified about the results of the SpaceX Static Fire Test and the anomaly that occurred during the final test," its administrator Jim Bridenstine said in a tweet.

“This is why we test. We will learn, make the necessary adjustments and safely move forward with our Commercial Crew Program,” he added.

Black hole image gives Twitter a field day

NASA has awarded SpaceX and Boeing Co a total of $6.8 billion to build competing for rocket and capsule systems to launch astronauts into orbit from American soil.

In March, the privately owned SpaceX successfully completed its mission of sending an unmanned capsule to the International Space Station and returned safely to Earth, a mission seen as crucial to NASA’s plans to resume human space flight from US soil.

SpaceX’s first crewed test flight is slated to launch in July with US astronauts Doug Hurley and Bob Behnken.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ