News
SpaceX Starship go for nosecone installation after historic static fire
SpaceX CEO Elon Musk has confirmed that Starship and Raptor’s first triple-engine static fire was a success, opening the door for nosecone installation.
Around 3:13 am CDT, October 20th, Starship serial number 8 (SN8) successfully fired up three Raptor engines less than two hours after completing the first successful three-engine preburner test. With zero direct human intervention, SpaceX remotely detanked the rocket’s cryogenic liquid methane and oxygen propellant – the remnants now too warm to be used again in a controlled manner. In an hour or less, SpaceX engineers combed through the data produced and concluded that all three Raptor engines were healthy after their partial ignition test.
Effectively reset to a stable state, SpaceX once again proceeded to load Starship SN8’s propellant tanks with a small amount of supercooled LOx and LCH4, almost exactly mirroring the preburner test. Around 50 minutes after the recycle commenced and 25 minutes after propellant loading kicked off, Starship SN8 ignited three Raptors simultaneously – a major milestone for any rocket engine. Static fire now completed, Starship SN8 has been cleared to become the first operational prototype to reach its full 50m (~165 ft) height.
Shortly before Musk confirmed SN8’s static fire success, SpaceX canceled a preexisting October 20th static fire window and scheduled several new road closures on Wednesday, October 21st. Unlike the company’s recent static fire closures, all but one of which ran from 9pm to 6am, SpaceX’s new Wednesday closures are scheduled from 7am to noon and 3pm to 5pm local (CDT).
While a minor data point, in context with Starship SN8’s static fire success, the closures alone made it clear that SpaceX planned to begin installing Starship SN8’s nosecone on October 21st. Musk confirmed that assumption a few hours after those road closures were published.
It’s not entirely clear but most observers are assuming that Wednesday’s 7am-12pm window is needed to transport a large, new crane the ~2 miles between SpaceX’s Boca Chica factory and launch facilities. Starship SN8’s stacked nose section would then likely be installed on the same self-propelled mobile transporters (SPMT) and rolled to the launch pad from 3pm to 5pm, after which the nose would be lifted and stacked atop Starship SN8.
SpaceX has only fully stacked a Starship prototype once before when Mk1’s nose section was temporarily mated to its tank section to be the centerpiece of CEO Elon Musk’s October 2019 Starship event. It’s unclear why SpaceX wouldn’t simply use one of the mobile cranes its rented for Starship tank section operations (and stacking Mk1) in the past, so it remains to be seen what Wednesday’s road closures will actually be used for.
SpaceX’s road closure plans end with a wildcard, however. Once installed, the plan is to perform a second triple-Raptor static fire while only drawing propellant from SN8’s header tanks – small internal tanks designed to hold landing propellant, one of which is situated at the tip of Starship’s nosecone. On October 21st and 22nd, SpaceX still has two 9pm-6am closures scheduled for “SN8 static fire” testing. Filed early on October 20th, before SN8’s successful static fire, the most likely explanation is a simple clerical error or miscommunication, with Cameron County or SpaceX failing to properly communicate that those subsequent static fire test windows are no longer needed.
If retaining the static fire closures was intentional, it would mean that SpaceX – likely at Musk’s urging – intends to install Starship SN8’s nosecone in a matter of hours. It’s almost inconceivable that Starship SN8’s nosecone – outfitted with multiple gas thrusters, forward flaps powered by Tesla motors, a liquid oxygen header tank, vents, and plenty of plumbing – can be installed and made ready for testing in less than 12 hours. Barring a surprise method of mating SN8’s nose and tank sections, the nosecone will have to be welded to the rest of SN8 and the weld inspected – typically a multi-day process.
Regardless, given how quickly SpaceX moves and how dead-set CEO Elon Musk is at pushing limits and breaking barriers, it seems reasonable to assume that Starship SN8 may be fully integrated and ready for a second static fire test just a handful of days from now. Once completed, SN8 will be ready to attempt Starship’s first high-altitude flight test, launching to ~15 km (~9.3 mi) to attempt an untested skydiver-style descent and landing.
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
