News
SpaceX uses robot dog to inspect Starship after first engine test in months
SpaceX’s first orbital-class Starship prototype has survived the first of several expected Raptor tests, kicking off an engine test campaign that could mark a number of new milestones.
With just 20 minutes left in a seven-hour test window, Starship prototype S20 (Ship 20) appeared to either unsuccessfully attempt its first Raptor static fire test or complete its first intentional Raptor preburner test around 11:40 pm CDT (UTC-5) on Monday, October 18th. Rather than a violent jolt and roar kicking up a cloud of dust, Ship 20 came to life with a (relatively) gentle fireball that lasted for several seconds.
In pursuit of maximum efficiency, Starship’s Raptors require two separate closed-cycle gas generators known as preburners to – as the name suggests – turn its cryogenic (very cold) liquid oxygen and methane propellant into a hot gas mixture that the engine re-ignites to produce thrust. A preburner test, if that’s what Starship S20 completed on Monday night, thus involves activating only the first half of that equation, rapidly producing a giant cloud of flammable gas without actually igniting to produce meaningful thrust.
Preburner tests have become increasingly rare as SpaceX’s sea-level Raptor design matured over the course of tens of thousands of seconds of ground testing and, later, thousands of seconds of ground and flight testing on Starship prototypes. Starship S20 had two engines during its first test. One Raptor was the sea-level optimized variant SpaceX has built dozens of and fired for 30,000+ seconds on the ground. The other, however, was a vacuum-optimized Raptor with a much larger nozzle – the first of its kind to participate in any kind of test while installed on a Starship prototype.
It’s possible that Raptor Vacuum (RVac) engines have even more design tweaks outside of their larger expansion nozzles. Regardless, SpaceX has only built and tested around 10 RVac prototypes over the last year, making it a less mature engine than its sea-level cousins. That could explain why SpaceX appears to have chosen to perform a preburner test first instead of jumping straight into a wet dress rehearsal and static fire. That also means that October 18th’s test was likely the first time a Raptor Vacuum engine has (partially) ignited while installed on a Starship.
The above view from a uniquely situated LabPadre camera all but guarantees that Starship S20’s first engine test was a Raptor Vacuum preburner test and doesn’t offer any strong evidence that it was a two-engine test. Ship 20 still has a number of crucial tests ahead of it before SpaceX can even begin to consider it (or its general design) qualified for flight. That includes multiple static fires, including the first side-by-side static fire of two Raptor variants (RVac and Raptor Center), the first simultaneous static fire of more than three engines, and the first Starship static fire with a full six engines installed.
Ship 20’s preburner test is SpaceX’s first Starbase Raptor test since the first Super Heavy booster static fire in mid-July, almost exactly three months ago.
With any luck, S20’s first preburner test has opened the door for an inaugural static fire of one or both installed engines later this week. However, during that preburner test, the giant fireball Raptor Vacuum emitted appeared to ignite several pieces of pad hardware. SpaceX took advantage of one of at least two Boston Dynamics Spot robots on-site to physically walk a camera up to the active pad and inspect several secondary fires. Ultimately, SpaceX appears to have successfully safed Starship with no damage to the vehicle itself, but odds are good that the sources of those secondary fires will need to be fixed and any pad damage repaired before Ship 20 proceeds into static fire testing. SpaceX has two more 5pm-12am test windows scheduled on October 19th and 20th.
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
