Connect with us

News

SpaceX’s upgraded Starship completes second Raptor engine test in ~24 hours

SpaceX has fired up Starship SN15 for the second time in ~24 hours. (NASASpaceflight.com)

Published

on

SpaceX Starship prototype SN15 has completed a second ‘static fire’ test of its Raptor engines in the last 24 hours, hopefully setting up the rocket for a launch and landing attempt on Thursday or Friday.

While Monday’s test was a total success, it’s unclear if April 27th’s static fire went according to plan. Notably, it was much shorter than the Monday engine test and involved either one or two – but not all three – of Starship SN15’s Raptor engines. Historically, unusually brief static fires (~2-3 seconds) aren’t unprecedented, but they’ve generally been part of a process of troubleshooting after a prototype runs into technical issues during earlier testing.

According to Musk, SpaceX also moved to reigniting all three sea level Raptors for landing burns from Starship SN10 onwards, meaning that an intentional two-engine SN15 static fire is either a reversion to earlier two-engine landing burns or a sign of a static fire abort or engine ignition failure. If SpaceX needs to perform another test, particularly if one or more Raptors need to be replaced, Starship SN15’s launch will likely slip into early May. Stay tuned for updates.

SpaceX CEO Elon Musk says that the next Starship launch could happen “later this week” after the company’s first ‘upgraded’ prototype aced a three-engine static fire test on the first try.

Advertisement

While substantially delayed from optimistic initial targets just a week or two after the rocket rolled from factory to launch pad, upgraded Starship prototype serial number 15 (SN15) – outfitted with “hundreds of improvements” – fired up its three Raptor engines for a few seconds around 5pm CDT on Monday, April 26th. Also upgraded, the rocket’s engines seemed to perform nominally and SpaceX ultimately closed out the evening’s testing a few hours early.

Around the same time as SN15’s first static fire attempt was wrapping up, SpaceX distributed safety notices to Boca Chica Village residents, indicating that a second static fire test may be planned on Tuesday. Musk didn’t mention plans for a second static fire, but he did imply that the first test was completed successfully enough to enable Starship SN15 to launch just a few days from now.

Like four other “high-altitude” flight tests before it, Starship SN15 is expected to target a similar ~10-12 kilometer (6-8 mi) apogee and once again attempt to perform a complete ascent, controlled bellyflop, landing flip maneuver, and soft touchdown. Between December 2020 and April 2021, Starships SN8 through SN11 tried and failed to survive that challenge intact, though prototype SN10 did manage to survive for around ten minutes on the ground before its still-hard landing led to an explosion.

All four failures ultimately had different causes. Starship SN8 lost fuel tank pressure, starving its Raptors and causing a near-total loss of thrust seconds before touchdown. One of SN9’s Raptors failed to ignite for a landing burn, triggering an even more aggressive impact with the ground. Starship SN10 landed in one piece but its lone landing engine underperformed when it began to ingest helium ullage gas – a quick-fix implemented after SN8’s pressurization issue. SN11 exploded almost immediately after attempting to ignite its three engines for landing, failing even earlier than its predecessors.

Advertisement

All four flight tests saw each respective Starship prototypes narrowly miss a fully successful and survivable landing, providing SpaceX a great deal of data and direct experience to improve the rocket’s design and operations with. Two of the four failures – SN9 and SN11 – appear to have been the fault of one or more of Starship’s three Raptor engines. Beginning with Starship SN15, SpaceX has moved to an upgraded iteration of the next-generation engine, raising hopes that whatever changes the company has implemented will substantially improve reliability and thus the odds of a successful high-altitude launch and landing test.

As of April 26th and in spite of one or two weeks of delays, the fact that Starship SN15 managed to complete a three-Raptor static fire test on its first true attempt is a great sign that the rocket’s many “improvements” may already be paying dividends. A launch “later this week” would make the effects of those improvements even harder to deny. A successful launch and landing in the next few days would all but guarantee that SpaceX’s process of iterative development is working like a charm. Regardless of whether SN15 survives its first flight, Starship SN16 will likely be ready to take over a matter of days later.

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

News

Tesla Cybercab stands to gain from new Trump autonomy rules

Published

on

Credit: Teslarati

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.

Continue Reading

News

Tesla plans production boost at Giga Berlin following rebound in Europe

Published

on

Credit: Andre Thierig | X

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’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.

Continue Reading

News

Tesla and driver sued by family of woman killed in Texas crash: what we know

Published

on

Credit: CNBC

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.

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.

Continue Reading