John Berrigan retweeted
Three years ago today, Starship Flight 2 (IFT-2) lifted off from Starbase Pad 1 with Booster 9 and Ship 25.
All 33 Raptors ran through ascent, and Starship debuted hot staging, with Ship 25 lighting its six engines while still attached to the booster.
Booster 9 was lost during its boostback burn, but Ship 25 pushed on to around 93 miles altitude and nearly 15,000 mph, the first Starship to reach space, before its flight termination system fired about eight minutes in.
A huge step on from Flight 1.
nasaspaceflight.com/2023/11/…
John Berrigan retweeted
It is super cool to work with @vast to supply the propulsion system for Haven-1! Saiph thrusters have now flown in space on 5 different spacecraft, soon to be many more.
Flight Saiph Thrusters by @GoToImpulse being prepared for Haven-1 integration. The station is designed to carry 48: 24 for fault-tolerant attitude control and 24 dedicated to deorbit. Three Saiph thrusters flew on Haven Demo, which completed its controlled deorbit in February.
John Berrigan retweeted
You might have noticed the orange trail on Starship 42 during Flight 15, originating from the upper LOX tank section and extending all the way down.
This happened because a single heatshield tile fell off during the ascent phase.
STARSHIP has multiple protective layers beneath the tiles: Pyron ablative material, Kaowool insulation, and a Crunch Wrap layer. These will provide additional thermal protection to ensure the underlying steel tanks remain protected. ( pic credit : @AshleyKillip )
Even in the event of a tank burn through, Starship could potentially retain the ability to land safely because it uses separate header tanks in the nosecone for the landing burn, rather than relying on propellant from the main tanks.
The header tanks also help mitigate propellant boiloff during extended orbital missions and simplify propellant and pressurization management.
Yeah, I was going over the whole Starship heat shield earlier today. Overall, it looks great. The engines look great too. Ship 42 could probably be reflown with a few weeks of refurbishment.
However, many small fixes are needed to achieve immediate reusability (like an airplane), which requires zero expected refurbishment, apart from scheduled maintenance.
John Berrigan retweeted
If you would’ve told me 60% of Vulcan’s first 5 flights would have an anomaly back in like 2019 I wouldn’t have believed you.
John Berrigan retweeted
Still in disbelief that this happened. Huge thanks to everyone that contributed. 7+ years in the making, and it would never have happened without thousands of absolute winners that I have the privilege of working with!
John Berrigan retweeted
Multiple sources say the anomaly that impacted today's Vulcan launch occurred in the booster stage, not the Centaur V upper stage or SRBs. I don't yet know if the booster stage issue was caused by the BE-4 engines, the propellant management system, or another problem.
John Berrigan retweeted
This is utterly terrible for DoD and NSSL. From the NSSL wiki page, SpaceX has 3 phase 2 launches and 17 phase 3 launches planned for 2027.
Vulcan has 19 phase 2 launches and 2 phase 3 launches, also all planned for 2027.
This is not a path for success. DoD has hard choices...
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.
John Berrigan retweeted
Replying to @KenKirtland17
Exactly. I thought a simple rocket from a company with a good track record had a chance to steal a majority of the Amazon LEO work.
This is a disaster for NSSL. Vulcan has a huge backlog for NSSL alone...














































