News
SpaceX Starship blew its top during rocket fueling test (updated)
Update: SpaceX has released an official statement indicating that Starship Mk1’s November 20th failure came after a decision to intentionally pressurize the rocket prototype to its limits. This likely means that the test was to max flight pressures and not an intentional burst test, so Starship’s dome failure is still a significant concern and was definitely not planned.
More importantly, SpaceX says that it had already decided to retire Starship Mk1 before any kind of flight testing, treating the vehicle as a pathfinder. Instead, SpaceX will build and use Starship Mk3 – the next Boca Chica prototype – for Starship’s first attempted skydiver-style landing and 20 km (12 mi) flight test.
SpaceX statement on the above test and incident: pic.twitter.com/r1ReRYhUhz— Michael Sheetz (@thesheetztweetz) November 21, 2019
SpaceX’s first full-scale Starship prototype has suffered a significant failure during testing, destroying or severely damaging large sections of the rocket. However, SpaceX CEO Elon Musk has already commented on the anomaly and is not all that concerned.
On November 20th, SpaceX – having canceled a planned road closure the day prior – unexpectedly requested a last-second road closure and entered into a much more serious round of testing with Starship Mk1, the rocket’s first full-scale prototype. This followed testing on November 18th that concluded with Starship Mk1’s very first ‘breath’ – some venting activity near the end of a tank proof test. SpaceX technicians spent the next 36 or so hours inspecting and working on Mk1, presumably looking for and patching minor leaks along its tank section.
The November 20th testing progressed far faster than the previous round of tests and Starship Mk1 was quickly venting again. Soon after that, frost began to appear on the exterior of its steel liquid oxygen and methane tanks, a telltale sign that some form of cryogenic testing was ongoing. Based on a distinct lack of activity at the nearby flare stack, SpaceX was using liquid oxygen (LOX) or liquid nitrogen (LN2) to verify that Starship performs as expected when filled with supercool propellant.
After initial venting and visible frost formation, SpaceX appeared to push forward, rapidly loading Starship Mk1 with LOX or LN2. This progress was easily visible thanks to the fact that the mass and pressure of all that cryogenic liquid made quick work of the slight imperfections on the exterior of Starship’s steel hull, turning the vehicle’s reflection from a speckled patchwork to an almost mirror-like finish. Roughly half an hour later, the otherwise peaceful scene was interrupted by the rapid failure of Starship Mk1’s upper LOX tank dome, instantly thrown several hundred feet into the air.
Seconds later, the crumpled upper half of Starship Mk1’s tank section appeared out of the clouds created and began hemorrhaging a huge volume of liquid oxygen, immediately boiling and vaporizing as it was exposed to the Earth’s comparatively white-hot atmosphere. Impressively, Starship appeared to remain functional after its top quite literally blew off, and the vehicle rapidly detanked and appeared to safe itself. Some ten minutes after the overpressure event, the freed liquid oxygen had boiled to nothing and Starship appeared to be quiet.
By all appearances, Starship Mk1 appeared to perform extremely well as an integrated system up to the point that its upper tank dome failed. The first frame from LabPadre’s stream with anything visibly amiss explicitly implicates the weld connecting the LOX dome to the cylindrical body of Starship’s LOX tank, point to a bad weld joint as the likeliest source of the failure. Although that hardware failure is unfortunate, Mk1’s loss will hopefully guide improvements in Starship’s design and manufacturing procedures.
Moving forward
Minutes after the anomaly was broadcast on several unofficial livestreams of SpaceX’s Boca Chica facilities, SpaceX CEO Elon Musk acknowledged Starship Mk1’s failure in a tweet, telegraphing a general lack of worry. Of note, Musk indicated that Mk1 was valuable mainly as a manufacturing pathfinder, entirely believable but also partially contradicting his September 2019 presentation, in which he pretty clearly stated that Mk1 would soon be launched to ~20 km to demonstrate Starship’s exotic new skydiver landing strategy.
Musk says that instead of repairing Starship Mk1, SpaceX’s Boca Chica team will move directly to Starship Mk3, a significantly more advanced design that has benefitted from the numerous lessons learned from building and flying Starhopper and fabricating Starship Mk1. The first Starship Mk3 ring appears to have already been prepared, but SpaceX’s South Texas focus has clearly been almost entirely on preparing Starship Mk1 for wet dress rehearsal, static fire, and flight tests. After today’s failure, it sounds like Mk1 will most likely be retired early and replaced as soon as possible by Mk3.
Above all else, the most important takeaway from today’s Starship Mk1 anomaly is that the vehicle was a very early prototype and SpaceX likely wants to have vehicle failures occur on the ground or in-flight. As long as no humans are at risk, pushing Starship to failure (or suffering unplanned failures like today’s) can only serve to benefit and improve the vehicle’s design, especially when the failed hardware can be recovered intact (ish) and carefully analyzed.
A step further, SpaceX is simultaneously building a second (and third) Starship prototype at its companion Cocoa, Florida facilities, and Starship Mk2 is nearly finished. Coincidentally, technicians installed its last tank dome – the same dome that failed on Mk1 – just days ago, and any insight that the Boca Chica team can gather from Mk1’s troubles will almost certainly be applied to Mk2, whether that means reinforcing its existing domes or fully replacing the upper dome with an improved design.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
Elon Musk
Elon Musk’s AI Grok Bot can now handle banking while your Tesla FSD handles the road
Elon Musk says Grok Bot can manage your finances through linked bank and investment accounts.
Grok Bot now wants access to your wallet, with SpaceXAI rolling out a new Finance integration for its agent platform that lets users link bank, credit card and investment accounts thereby letting their Bots help manage spending, investments and more. Elon Musk amplified the announcement on X with a short endorsement, “Grok Bot can manage your finances.”
The feature builds on two earlier steps. In early September, Grok gained the ability to answer questions about spending, savings, investments and cash flow using accounts connected through Plaid, starting with users in the U.S. Before that, on August 28, SpaceXAI let Grok Bot buy things online through Link, with users approving every spend request and the Bot receiving a single use card for each payment.
Musk has already shown how far he wants users to push it. In late August, when Tesla investor account Teslaconomics said he was weighing whether to give Grok Bot access to his bank accounts, Musk replied, “Try it out. If Grok Bot messes up, we will make you whole.” That promise goes beyond SpaceXAI’s consumer terms, which make users responsible for what their agents do and generally cap the company’s liability at the greater of fees paid or $100. SpaceXAI’s own documentation recommends requiring approval for purchases and financial transfers.
For Tesla owners, the update lands five days after Tesla brought Grok Bot into its vehicles, letting drivers hand off errands by voice while FSD (Supervised) handles the road. Bot access inside the car is currently limited to SuperGrok Heavy subscribers, though Connectors are open to anyone signed into Grok. With Finance linked, a driver could ask for a spending summary or a check on upcoming bills during the commute.
Grok’s role in the car has grown quickly since Tesla’s Summer Update let it control cabin features by voice. We have been using Grok Bot in our own Tesla for several weeks, and here’s how our latest test went.
Elon Musk
SpaceX just got the green light Starship has waited years for
The FAA has cleared Starship Flight 14, setting up SpaceX’s first orbital attempt on Monday.
SpaceX has cleared the last regulatory hurdle standing between Starship and its first trip to orbit. The Federal Aviation Administration issued the launch license for Starship Flight 14 late Saturday, keeping the mission on track for liftoff Monday, September 28, from Pad 2 at Starbase, Texas.
The 75 minute launch window opens at 7:15 a.m. Central, and Boca Chica Beach closures are also scheduled for September 29 and 30 as backup dates. This will be Starship’s first revenue generating mission.
The license was the missing piece after SpaceX completed a full wet dress rehearsal with Booster 21 and Ship 41 on September 24. At the time, the company said the flight remained on track pending regulatory approval. Because Flight 14 flies an orbital profile, the FAA had to sign off on a modified license that met its safety, payload and financial responsibility requirements.
Observers combing through the new FAA paperwork also noticed that lightning no longer appears among Starship’s listed launch hazards. If that holds, it matters more for where Starship is headed than for Monday’s attempt. Florida and Louisiana, home to LC-39A and the planned Starbase Louisiana site, see some of the most frequent lightning in the United States.
SpaceX tells the FCC that Starship Flight 14 is going to orbit
Flight 14 is the mission SpaceX has been building toward for months. Ship 41 will carry 26 Starlink V3 satellites, the first operational V3 units to be deployed, and attempt roughly six orbits at about 275 kilometers over a flight lasting just under 10 hours. SpaceX says the ship will only perform its orbital insertion burn after flight controllers confirm enough hardware redundancy remains for the deorbit burn at the end of the mission. Ship 41 is targeting a splashdown in the Pacific west of Chile, while Super Heavy will return to the Gulf of Mexico.
The date carries some symbolism as well. A Monday launch would come 10 years and one day after Elon Musk first presented the Interplanetary Transport System, the design that became Starship, at the International Astronautical Congress in Guadalajara, Mexico.
SpaceX has not announced what comes next, but air traffic planning slides reported this week, list Flight 15 no earlier than October 19 and a first Starship launch from LC-39A in Florida no earlier than October 30. Both dates depend on how Monday goes.
News
SpaceX completes another secret Pentagon launch, adding to suspected Starshield buildout
SpaceX launched the classified USSF-385 mission from Vandenberg, landing its booster on a tenth flight.
SpaceX launched another classified mission for the U.S. Space Force from California early Saturday morning, and the Falcon 9 booster that carried it landed on a drone ship in the Pacific for the tenth time. The USSF-385 mission lifted off from Space Launch Complex 4E at Vandenberg Space Force Base at 7:00 a.m. PT.
Booster B1100 touched down on Of Course I Still Love You roughly eight and a half minutes after liftoff. It was the booster’s tenth flight and tenth successful landing, following the NROL-95 national security mission and eight Starlink launches. Its previous flight, a Starlink Group 15 mission on August 22, came just 35 days earlier. SpaceX ended its livestream shortly after the landing, which is standard for classified payloads, and neither the company nor the Space Force has said what the rocket carried.
Watch Falcon 9 launch the USSF-385 mission from pad 4E in California https://t.co/CAdbx85Ydy
— SpaceX (@SpaceX) September 26, 2026
USSF-385 is the fourth Space Force launch from the same Vandenberg pad in roughly six weeks, following USSF-366 on August 15, USSF-153 on September 10, and USSF-259 on September 17. When SpaceX flew USSF-366 in August, independent trackers noted that the rocket’s stage drop zones matched SpaceX’s Starlink Group 15 missions, pointing to Starshield, the government version of the Starlink satellite bus. The Space Force later cataloged 23 satellites after both USSF-366 and USSF-153, while USSF-259 placed 17 satellites into a different orbital plane, per KeepTrack. Launch databases describe USSF-385 the same way, though the payload remains officially unidentified.
The cadence lines up with the contracts, because in July, the Space Force awarded SpaceX $1.6 billion in task orders for 18 Falcon 9 missions from Vandenberg through the end of 2027. SpaceX also holds contracts to build pieces of that same network, which pushed its Pentagon contract total for 2026 past $8 billion.
Saturday’s flight was also the sixth and final Falcon 9 launch from Vandenberg in September, according to Spaceflight Now, while only one Falcon 9 flew from the East Coast this month as SpaceX shifts its Florida infrastructure toward Starship. Launch trackers list it as SpaceX’s 112th mission of 2026 and the 108th Falcon 9 flight of the year, with SLC-4E turned around about six and a half days after its previous launch.
The West Coast pad will not stay quiet for long, considering SpaceX has another Starlink mission scheduled from SLC-4E on September 30. Meanwhile, in Texas, the company is two days away from Starship Flight 14, which is targeting Monday at 7:15 a.m. CT for the vehicle’s first attempt to reach orbit.
Elon Musk’s AI Grok Bot can now handle banking while your Tesla FSD handles the road
SpaceX just got the green light Starship has waited years for
