Cant wait for the crew camera during belly flop.
The crew wont experience crazy high G-s but your still going from horizontal to verical.
Wen humans?
arstechnica.com/space/2026/1…
2
81
XSpace retweeted
Ship is down and everyone is getting ready for a rocket parade this afternoon. Please keep the left side of the road clear so the transport can happen safely.
XSpace retweeted
Appreciate you quickly keeping the public and your partners informed. The team at @NASA is available to assist in all matters related to the investigation and remediation effort. Artemis, Moon Base, and the nation need ULA. We are in your corner and here to help.
Based on data received by our Launch Director, we confirm that the Vulcan vehicle launched from Space Launch Complex 41 suffered an anomaly 10 minutes into the flight and failed to deliver the Amazon mission to orbit.
Every flight generates data, and every flight teaches us something. Since the anomaly just occurred, we don’t have any specific data yet to understand what occurred today.
ULA exists to provide assured access to space for our nation and for the customers who depend on us. That purpose is why we take on some of the hardest missions in spaceflight, and why we hold ourselves to the standard of mission success. Today, we did not meet that standard.
We will work closely with our customer and other appropriate organizations to find the cause, determine the appropriate corrective action, and return to flight as quickly as possible.
ULA is committed to full transparency with our customers, and they will have visibility into the investigation process, which utilizes rigorous methodology and corrective action.
We will provide further updates when new information becomes available.
Vulcan suffered an anomaly at T+10 minutes, and failed to deploy the payload...
Based on data received by our Launch Director, we confirm that the Vulcan vehicle launched from Space Launch Complex 41 suffered an anomaly 10 minutes into the flight and failed to deliver the Amazon mission to orbit.
Every flight generates data, and every flight teaches us something. Since the anomaly just occurred, we don’t have any specific data yet to understand what occurred today.
ULA exists to provide assured access to space for our nation and for the customers who depend on us. That purpose is why we take on some of the hardest missions in spaceflight, and why we hold ourselves to the standard of mission success. Today, we did not meet that standard.
We will work closely with our customer and other appropriate organizations to find the cause, determine the appropriate corrective action, and return to flight as quickly as possible.
ULA is committed to full transparency with our customers, and they will have visibility into the investigation process, which utilizes rigorous methodology and corrective action.
We will provide further updates when new information becomes available.
5
404
I drew this probably in early 2026 at school and saved it, thinking this will become reality one day.
Not very accurate, but thats not the point...
"These early ships and boosters are already outdated by improved designs in production or on the test stand"
Bruh they are already outdated lol
Replying to @DJSnM
Yes, the green flame is caused by burning copper from depleting fuel in the regenerative cooling circuit and going oxygen-rich (closer to stoichiometric temperature) in the main combustion chamber.
Slight underperformance of engines on this flight is the reason. The booster is meant to land with tiny residuals, so the solution is to improve engine performance and performance consistency (underway with Raptor V3.2), as well as adjust flight software to do MECO1 about one second earlier to ensure enough propellant for boostback and landing (tiny change).
These early ships and boosters are already outdated by improved designs in production or on the test stand, so this booster loss does not change our timeline to reach high volume, fully reusable Starship flights.
1
8
963

































