[Leaked] S34's engine bay & skirt footage showing a Raptor exploding
Source: @exyspear

Test Tank 18.1 getting ready for a Super Crusher test.

TT 18.1 is a pathfinder for the new generation of Superheavy Booster. V3 here we come!

📷 Jordanguidry6
Source: @FelixSchlang

Did you catch our latest starbase flyover update video? Just released recently, watch it here:
https://youtu.be/ZGMta2525W4
Source: RT @RGVaerialphotos

‍Watch Falcon 9 launch 28 Starlink satellites to orbit from Florida https://t.co/vwNy2OTzfp
Source: @SpaceX

Deployment of 28 Starlink satellites confirmed
Source: @SpaceX

Cryo loading has begun on Ship 36 ahead of tonight's static fire.
Source: @LabPadre

ANOMALY! Just before Ship 36 was set to Static Fire, it blew up at SpaceX Masseys!
Source: @NASASpaceflight

Massive explosion as Ship 36 explodes on the Static fire test stand.

This will be a major setback as there is likely significant damage to the entire back half of Massey's
Source: @CSI_Starbase

Ship 36 experiences a RUD at Massey's during testing prior to Starship Flight 10. Seen in slow motion.
Source: RT @dwisecinema

SpaceX's full statement on this anomaly

On Wednesday, June 18 at approximately 11 p.m. CT, the Starship preparing for the tenth flight test experienced a major anomaly while on a test stand at Starbase. A safety clear area around the site was maintained throughout the operation and all personnel are safe and accounted for.

Our Starbase team is actively working to safe the test site and the immediate surrounding area in conjunction with local officials. There are no hazards to residents in surrounding communities, and we ask that individuals do not attempt to approach the area while safing operations continue
Source: @SpaceX

Preliminary data suggests that a nitrogen COPV in the payload bay failed below its proof pressure.

If further investigation confirms that this is what happened, it is the first time ever for this design.
Source: RT @elonmusk

🚨BREAKING: Here’s some initial footage of the SpaceX Massey’s test site after the Ship 36 anomaly.

As expected, the test stand seems to be heavily damaged. Repairs will likely take some time.

Huge thanks to RaptorRoostTX for going out there so quick for us! ❤️
Source: @FelixSchlang

‍An update on last night's Starship static fire

On Wednesday, June 18 at approximately 11 p.m. CT, the Starship preparing for the tenth flight test experienced an anomaly while on a test stand at Starbase.

After completing a single-engine static fire earlier this week, the vehicle was in the process of loading cryogenic propellant for a six-engine static fire when a sudden energetic event resulted in the complete loss of Starship and damage to the immediate area surrounding the stand. The explosion ignited several fires at the test site which remains clear of personnel and will be assessed once it has been determined to be safe to approach. Individuals should not attempt to approach the area while safing operations continue.

As is the case before any test, a safety zone was established around the test site and was maintained throughout the operation. There are no reported injuries, and all personnel are safe and accounted for.

There are no hazards to the surrounding communities in the Rio Grande Valley. Previous independent tests conducted on materials inside Starship, including toxicity analyses, confirm they pose no chemical, biological, or toxicological risks. SpaceX is coordinating with local, state, and federal agencies, as appropriate, on matters concerning environmental and safety impacts.

Engineering teams are actively investigating the incident and will follow established procedures to determine root cause. Initial analysis indicates the potential failure of a pressurized tank known as a COPV, or composite overwrapped pressure vessel, containing gaseous nitrogen in Starship’s nosecone area, but the full data review is ongoing. There is no commonality between the COPVs used on Starship and SpaceX’s Falcon rockets.

The SpaceX team would like to thank officials and residents in the surrounding Rio Grande Valley communities for their support, particularly first responders who have assisted since shortly after the anomaly took place.

Source: @SpaceX

Before / after S36 anomaly.

Photos RGVaerialphotos & FelixSchlang
Source: @mcrs987