News
Elon Musk talks upgrades after SpaceX Starship launches, explodes in midair
SpaceX has completed its fourth Starship test flight in as many months, offering the latest glimpse into the often frustrating reality of a highly iterative, hardware-rich rocket development program.
Right on schedule, SpaceX Starship prototype serial number 11 (SN11) lifted off from Boca Chica, Texas at exactly 8am CDT (UTC-5) – all but completely cloaked in a thick layer of fog. While unfortunate for any unofficial observers (and possibly SpaceX’s own desire to gather video footage of a test flight), SpaceX has experience launching rockets (namely Falcon 9) in thick fog thanks to its Vandenberg Air Force Base launch site on the California coast.
As such, fog theoretically poses no fundamental threat to rockets like Starship, but SN11 still took the opportunity to explore new and exciting failure modes shortly before touchdown. CEO Elon Musk himself didn’t take long to weigh in and has even offered some details and a schedule for upgrades planned for SpaceX’s next-generation launch vehicle – upgrades hoped to alleviate whatever issues led to Starship SN11’s premature demise.
First and foremost, due to the fog, the general public saw virtually nothing throughout the launch attempt. Remote streaming cameras set up near SpaceX’s launch facilities – now, excitingly, with the company’s own permission – did manage to catch some level of detail, providing the bare minimum level of insight needed to speculate on SN11’s failed landing attempt.
Per an official webcast and NASASpaceflight’s unofficial “Danger-Close Camera,” installed a few hundred feet from the launch site with SpaceX’s permission, Starship lifted off at exactly 8am and had a seemingly nominal ascent, reaching a familiar 10 km (6.2 mi) apogee around four minutes later. SN11 then arced over onto its belly and free-fell for ~100 seconds. Aside from a few intermittent fires burning on some of the rocket’s three Raptor engines, not an uncommon sight since SN8 first flew, nothing appeared particularly out of the ordinary.
At T+5:49, however, things rapidly went wrong. Still belly-down, Starship SN11 attempted to reignite all three of its Raptor engines to propulsively flip into a vertical landing position. After at least one seemingly successful reignition, SpaceX immediately lost onboard video and telemetry feeds. Based on NASASpaceflight’s pad-adjacent camera, a substantial explosion followed one or two seconds after that attempted ignition, ending Starship SN11’s test flight around 20 seconds earlier than any of its three late siblings.
Debris began to visibly hit the ground another 5-10 seconds after that explosion was first heard, all but guaranteeing that Starship SN11 exploded in midair. At this time, it’s impossible to know what exactly went wrong, but there are two clear possibilities. Starship SN11 could have failed to reignite two or even all three Raptor engines, triggering onboard flight termination system (FTS) explosives designed to prevent the rocket from straying beyond a safe zone of operations. More likely, Starship suffered a substantial failure during that reignition and flip attempt, triggering an almost immediate explosion that tore the rocket apart around half a kilometer (~1500 ft) above the pad and landing zone.
Shortly after, Musk said that Raptor “engine #2 had issues on ascent” that were notable but not enough to explain a violent midair failure and confirmed that whatever went wrong came “shortly after landing burn start.”
Musk offers Starship upgrade schedule, details
Having suffered a failure a bit less than six minutes after launch, Starship SN11 – the fourth three-engine, high-altitude prototype – was ironically the farthest from a successful landing before something went wrong: one step forward, two steps back. While unfortunate, SpaceX still got some amount of data and uncovered one or several new failure modes – arguably the two of the most important primary goals of any developmental flight test program.
Further, Musk revealed that SpaceX intends to complete and roll Starship SN15 to the launch pad just “a few days” from now – certainly earlier than expected. While the SpaceX CEO didn’t go much into detail, he reaffirmed that SN15 would bring substantial upgrades, stating that “it has hundreds of design improvements across structures, avionics/software, & engine[s].”
Musk also touched on SpaceX’s near-term plans after SN15’s upgrade path, confirming that Starship prototypes from SN20 onwards will be “orbit-capable” with even more improvements. That seemingly delineates three clear ‘blocks’ of Starship prototypes, beginning with SN8 through SN11, proceeding with SN15 through SN19, and (nominally) gearing up for true orbital-class test flights with prototype SN20 and its successors. All told, SN11’s midair demise appears likely to be just a small blip in front of a jam-packed, well-structured series of Starship upgrades and flight tests just over the horizon.
Tesla Cybercab stands to gain from new rules that the Trump Administration is aiming to enforce on autonomous vehicles. On Thursday, NHTSA, under the Trump Administration’s U.S. Department of Transportation, commenced rulemaking on the Federal Motor Vehicle Safety Standards (FMVSS).
This effort aims to eliminate the mandate for manual brake pedals in vehicles that are designed to be driven exclusively by automated driving systems. This would impact the Tesla Cybercab, which the company has stated would operate without a steering wheel or pedals.
Tesla Cybercab launch is imminent after latest sighting at Giga Texas
The Trump Administration is looking to revise FMVSS No. 135, which requires standard braking systems on light-duty vehicles.
Currently, the regulation requires light-duty cars to use traditional manual braking systems that allow operators to slow the vehicle. With the advent of self-driving in the U.S., these regulations need updating, and these are the changes that could come to FMVSS No. 135:
- Removes requirements for hand- or foot-operated brake controls for vehicles designed never to be operated by a human. Existing rules still apply to AVs that retain manual controls.
- All subject vehicles must still meet the same stopping distance performance criteria via alternative testing procedures.
- While this update ensures AVs can physically stop when commanded, NHTSA is separately developing safety performance requirements for AVs in real-world driving scenarios.
- NHTSA will continue to use its broad defect enforcement authority to investigate unsafe ADS behavior and oversee recalls.
As autonomy becomes a greater part of passenger travel, these types of rule adjustments will be more than reasonable. It will give manufacturers the ability to self-certify their vehicles and avoid any red tape that could ultimately delay the deployment of these vehicles.
Administrators are also incredibly excited about the opportunity to play a role in the advancement of self-driving vehicles.
“We are at the cusp of the greatest technological revolution in vehicle technology since the innovation of the Model T,” NHTSA Administrator Jonathan Morrison said. “If we want America to lead the way, we have to reimagine our regulatory framework. That’s why under Secretary Sean Duffy’s AV Framework, NHTSA is tearing down pointless barriers to innovative designs while strengthening the fundamental safety requirements that matter and holding AV developers accountable for safe performance.”
The Cybercab entered mass production at Gigafactory Texas in April. Tesla ultimately plans to push the vehicle into its Robotaxi fleet, potentially when frameworks like these are established.
Tesla plans to boost production at its Gigafactory Berlin plant in Germany following a sharp rebound in sales and demand in Europe after a softer 2025.
The plans put Tesla in a better position to compete with strengthening companies in Europe and potentially other markets; demand indicators show Tesla is much better off than in 2025.
Last year was a tough year for Tesla in terms of overall demand in Europe. The company produced over 200,000 vehicles at the German plant last year, a soft figure compared to the 375,000 vehicles Tesla lists as its current capacity at the factory.
🚨 Tesla said this morning it will ramp up production at Gigafactory Berlin to a volume of 7,500 vehicles per week.
This is a 20 percent boost in production. Tesla will hire 1,000 new employees to help with the increase.$TSLA pic.twitter.com/kravKfRO5n
— TESLARATI (@Teslarati) June 25, 2026
Tesla’s overall European sales dropped significantly last year due to a variety of factors. However, sales are rebounding, and demand is strong once again, and only getting stronger. Tesla is now planning to bump production of Model Y vehicles at Giga Berlin upward by about 20 percent. It will also bring 1,000 new jobs to the plant.
Tesla confirmed the details of its planned production expansion in Germany this morning. It is a strategy to keep up with strengthening demand.
In Q1, Tesla saw a record 61,000 vehicles produced at Giga Berlin. European registrations rebounded sharply, with Model Y seeing 117 percent increases in March 2026 compared to last year. Germany alone saw stark increases, with a quadrupling in registrations to 9,252 units.
This trend continued in other key European markets, including France, Denmark and Sweden. Tesla registrations were up over 46 percent in some of these markets, and Model Y continued its trend as a top BEV in the market.
Demand has been recovering strongly in 2026, giving Tesla a reason to expand production efforts at the factory. These increases signal management’s confidence in sustained or growing European pull for Berlin-built vehicles.
Tesla is being sued by the family of the woman who was killed in a Texas crash involving a Model 3. The driver, who is also being sued, claimed the vehicle was operating on Autopilot mode, but Tesla executives have come out challenging that claim, stating that the driver of the vehicle overrode the system.
The lawsuit was filed by 76-year-old Martha Avila’s daughter and her husband, who allege a “design defect” involving a Tesla and a failure to warn. The suit alleges negligence against Tesla and the driver, Michael Butler.
Butler “stated he was operating with an automated driving assistance system engaged at the time of the crash,” the Harris County Sheriff’s Office said in a statement. He showed no signs of intoxication and was cooperative, the Sheriff’s Office said, according to NBC News.
Just after reports of the crash and numerous headlines that immediately blamed Tesla’s Autopilot suite, both Tesla CEO Elon Musk and Head of AI Ashok Elluswamy challenged that. Musk said the crash made “no sense” given that Tesla Autopilot and Full Self-Driving do not travel at the speeds the door cameras captured the car traveling at, which Tesla says was 73 MPH.
Tesla finally clarifies fatal Texas crash, confirms driver manually overrode acceleration
Elluswamy also revealed that Tesla data showed Butler overrode the system by pressing the accelerator to 100%, and that the pedal was compressed fully even after the car had crashed. Tesla has not released this data to the public, likely because it is communicating with agencies like the NHTSA on an investigation.
The suit uses a Washington Post analysis of government data that “identified at least 17 fatal incidents linked to Tesla Autopilot.”
This is far from the first time an accident has been blamed on Autopilot. A fatal crash in Texas was blamed on Autopilot several years ago, but when Tesla released data to the NTSB, which was investigating the crash, Autopilot was not available where the crash occurred, and Autosteer was never enabled, meaning the car was manually controlled at the time of the accident.
“Application of the accelerator pedal was found to be as high as 98.8 percent,” the NTSB said in their findings. The highest recorded speed in the five seconds leading up to the impact was 67 miles per hour. The area where the crash occurred is residential, and Texas State laws… pic.twitter.com/XGD97NHVZ2
— TESLARATI (@Teslarati) March 18, 2026
More information on the accident will be released as Tesla works with agencies to find the cause of the crash. From personal experience, it is hard to imagine Tesla Autopilot or FSD operating in this manner. It drives sometimes too cautiously in residential areas in parking lots, at least in my experience. Speeding happens, but at this rate in this type of area, it is hard to believe.
We look forward to more details being released with time.
Tesla Cybercab stands to gain from new Trump autonomy rules
Tesla plans production boost at Giga Berlin following rebound in Europe
