News
SpaceX’s upgraded Starship completes second Raptor engine test in ~24 hours
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.
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.
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.
Tesla has reached a notable benchmark in its autonomous driving program after its Robotaxi fleet surpassed one million miles of unsupervised operation. The company made the announcement during its Cybercab event in Austin on September 3.
Tesla Vice President of AI Ashok Elluswamy told attendees he was happy to report the fleet had achieved one million miles of unsupervised Robotaxi operation as a testament to safety.
The new total marked a sharp increase from the 380,000 unsupervised miles Tesla disclosed during its second-quarter 2026 earnings update in late July.
In roughly six weeks, the company added about 620,000 miles. That acceleration followed Tesla’s decision to remove in-vehicle safety monitors from most of its operations outside the San Francisco Bay Area.
Credit: Tesla
Tesla first launched Robotaxi service in Austin in June 2025 with safety drivers present. It later began fully unsupervised rides and expanded into Dallas, Houston, Miami, Orlando, and Tampa. The San Francisco Bay Area remains the exception, where a safety monitor still rides in the vehicle under California permitting rules.
The company has not released a city-by-city breakdown of the one million unsupervised miles.
The milestone arrived as Tesla began offering public Cybercab rides in Austin. The purpose-built vehicle has no steering wheel or pedals and is designed only for autonomous ride-hailing. Production versions joined the existing fleet of modified Tesla vehicles already operating in the service.
Tesla’s unsupervised mileage is growing at a double-digit weekly rate according to earlier company comments, yet its fleet size remains modest compared with established competitors. Waymo has accumulated more than 200 million fully autonomous rider-only miles. Tesla has described its own unsupervised operations as having recorded zero notable incidents in the period leading up to the July update.
The one-million-mile figure reflects Tesla’s shift from supervised testing to broader driverless service in multiple states. It also highlights the company’s strategy of using both existing Model Y vehicles and the new Cybercab to scale its network.
Credit: Tesla
Whether the rapid recent growth continues will depend on further city expansions, regulatory approvals, and the performance of the purpose-built Cybercab in everyday paid rides. Tesla has not specified how many of the latest miles involved the new vehicle versus the rest of the fleet.
The announcement underscores Tesla’s progress toward a larger robotaxi network while illustrating the remaining gap in total autonomous experience relative to longer-operating rivals.
Tesla AI lead Ashok Elluswamy said this week that 24-hour Robotaxi service is close. Replying on X to a rider who wanted Cybercab trips all night, he wrote that the capability would arrive “next month or so” once “the next tech to merge on the v15 plan” is ready.
The comment landed on September 4, one day after Tesla opened public Cybercab rides in Austin. It is the clearest near-term timeline yet for overnight unsupervised operation. Tesla’s paid Robotaxi network currently runs from 6 a.m. to 10 p.m. seven days a week across Austin, Dallas, Houston, Miami, Orlando, and Tampa.
next month or so. the next tech to merge on the v15 plan will enable it.
— Ashok Elluswamy (@aelluswamy) September 4, 2026
That 16-hour window is shorter than the 6 a.m. to 2 a.m. schedule the company used for much of the prior year.
Elluswamy did not name the specific feature or say whether the change would apply first to purpose-built Cybercabs, the existing Model Y fleet, or both. He also offered no city-by-city rollout list. The link to Full Self-Driving v15 is nevertheless significant.
Tesla has described v15 as a step-change architecture with seven parallel improvement tracks and roughly ten times more parameters than earlier builds. Early versions of that software already operate on the Robotaxi fleet and contain about 40 percent of the planned gains.
By July 2026, the unsupervised fleet had logged more than 380,000 miles across six cities in two states with what the company called an impeccable safety record and no notable incidents caused by the vehicles themselves. Tesla has repeatedly argued that camera-based end-to-end neural networks, rather than extra sensors, are the core of the solution.
Overnight service would test that claim in lower-light conditions and would also raise vehicle utilization, a key variable for Robotaxi unit economics. The company has already begun using public Superchargers at night and is building dedicated Robotaxi charging sites.
Riders have asked why software must change if the cars already drive in the dark. The practical answer appears to be reliability and scale: Tesla has held back mass expansion until more of the v15 stack is merged, citing the need for higher confidence before putting thousands of unoccupied vehicles on streets around the clock.
If the next module arrives on the timetable Elluswamy sketched, 24-hour service could begin in October 2026 in at least some markets.
That would mark a shift from a daytime-bounded pilot to a service that can run whenever demand exists, including the late-night hours that have so far remained out of reach.
Tesla is beginning to roll out Full Self-Driving Supervised v14.3.9 with a new active safety layer that can take control even when the driver is operating the car manually.
Tesla AI said the software can activate FSD on the driver’s behalf when an imminent collision is detected and Automatic Emergency Braking may not be enough. It may also engage if the system detects heavy distraction or an accidental FSD disengagement.
FSD Supervised v14.3.9 starting to roll out shortly
This release includes a new active safety feature set: FSD Supervised can now activate on your behalf when an imminent collision is detected and Automatic Emergency Braking (AEB) may not be enough.
It may also engage if we…
— Tesla AI (@Tesla_AI) September 4, 2026
The capability is essentially Automatic Collision Evasion. However, unlike conventional AEB, which mainly applies the brakes in a straight line, this feature can use steering, braking, and acceleration together if the car calculates that stopping alone will not prevent impact and a safer path exists. The system may change lanes or move toward a shoulder when conditions allow, then continue driving after the immediate threat is handled rather than simply coming to a stop.
The intervention is meant as a last-resort safety net, not a replacement for attentive driving.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
Tesla’s own description still frames FSD as supervised assistance. Secondary reports on internal release notes say the feature can fire while the car is being driven manually if cabin-camera monitoring suggests the driver is not sufficiently attentive, such as reaching toward the back seat, or if FSD appears to have been turned off unintentionally.
After the emergency maneuver, the car is expected to alert the driver and request a return to manual control.
The safety case is straightforward. Many collisions happen in the last second because a driver is looking away, fumbles a control, or faces an obstacle that braking cannot fully solve. A system that can both recognize that AEB is insufficient and execute a coordinated evasive path can reduce those remaining high-severity events.
Re-engaging after accidental disengagement also addresses a practical failure mode: a small steering nudge that drops FSD at the worst moment. The advantage is a background safety net that uses the same vision stack already running in v14, instead of leaving the car solely to emergency braking once the driver is no longer in command.
The feature still depends on FSD being enabled and, according to reports, an active FSD purchase or subscription. It does not make the vehicle unsupervised. Drivers remain responsible, and Tesla has not published how often the system is expected to intervene or how it will handle false positives.
If the rollout is conservative and the false-alarm rate stays low, the update is a meaningful step: FSD is no longer only a feature the driver turns on. In the rare moments when disaster is already forming, it can step in.
Tesla crosses major Unsupervised Self-Driving milestone
Tesla Robotaxi will be a 24/7 service: here’s when
