News
SpaceX Starship prototype in limbo after engine test lights rocket on fire
The fate of SpaceX’s fourth full-scale Starship prototype appears to be in limbo after a third (seemingly successful) engine ignition test unintentionally caught the rocket on fire.
Now more than 12 hours after Starship SN4 fired up its new Raptor engine, the ~30m (~100 ft) tall, 9m (~30 ft) wide prototype is apparently trapped with one or both of its propellant tanks still partially filled with liquid (or gaseous) methane and/or oxygen. An initial road closure scheduled from noon to 6pm local quickly came and went and SpaceX and Cameron County Texas have since modified the paperwork, extending the closure a full 24 hours. In other words, SpaceX has reason to believe that Starship SN4 may continue to be unsafe (i.e. pressurized) as many as ~30 hours after it technically completed its third static fire test – extremely unusual, to say the least.
There’s only one obvious conclusion to draw. Whether it was something invisible to the public eye or damage related to the off-nominal fire that burned for some 15 minutes after Raptor shut down, SpaceX appears – to some extent – to have lost control of Starship SN4.
At the moment, it’s unclear what is wrong and what SpaceX is attempting to do to resolve the problem. Based on photos of Starship SN4 taken before the fire, there is good news and bad news from what can be publicly ascertained. Controlled from the ground by unprotected wires strung up and down the rocket and connected at its base, the uncontrolled fire that burned in at least two locations around Starship’s aft may have severed some or all of those critical connections.
That would render Starship – potentially perfectly healthy and operational – almost entirely uncontrollable, while also potentially removing SpaceX’s access to telemetry. In other words, the company may currently have no idea how pressurized all or part of Starship SN4 is and may also have little to no control of some or all of the rocket. For that to be true, Starship SN4 would, however, have to have less than fully redundant control hardware. To perform hops, for example, the ship would need both wired and radio links capable of sending telemetry and receiving commands to remain both on the ground and after liftoff.
It’s possible that Starship SN4 has the necessary hardware installed but that it wasn’t activated for the static fire test (think “Starship will never leave the ground, why would we need to enable wireless controls?”). It’s also possible that the blown pipe and methane leak that appeared to cause the secondary fire damaged crucial propellant management hardware (valves, pumps, etc.) or was just a symptom of an even worse overpressure event that damaged or destroyed multiple such systems.
Given that safety is almost certainly the priority, chances are that some combination of fairly mild hardware failure and telemetry/control loss has left SpaceX with just enough uncertainty that it can’t risk sending technicians to the launch site to inspect the damage and reestablish control. As a result, the only option left is to quite literally sit and wait until it’s once again safe to approach the rocket. Thankfully, at this point, the risk of the mystery problem actually destroying Starship SN4 is very low. If, as it appears, only its methane tank is affected, leaving some unknown quantity of latent liquid methane trapped inside, it’s possible that waiting will actually solve the problem and safe the rocket.
The fact that Starship hasn’t exploded yet strongly implies either that the amount of propellant trapped is minuscule or that the vast majority of SN4’s propellant management systems (including vents) remain functional. Assuming that’s the case, any remaining cryogenic propellant will eventually boil into gas, increasing the pressure inside Starship’s tanks, while those tanks will continue to vent to prevent an explosion or rupture. Eventually, Starship SN4 will be empty once again and SpaceX will be able to approach the rocket to regain control and begin inspections and repairs.
Regardless, after such an unintentionally eventful static fire test, it’s extremely unlikely that SN4 will be ready for its inaugural flight test within the next few days. Stay tuned for updates as SpaceX works to regain control over the fourth full-scale Starship prototype.
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
