News
SpaceX rolls next Starship to the launch pad nine days after midair explosion
Update: Right on schedule, SpaceX has transported Starship serial number 15 (SN15) from its Boca Chica rocket factory to a launch and test site just down the road.
SN15’s pad arrival comes just nine days after Starship SN11 – the last in a batch of four first-generation prototypes – exploded in midair some 30 seconds before a planned landing. While minor, SN11’s midair failure was undoubtedly a step backward relative to Starship SN10, which (briefly) became the first full-size prototype to land in one piece less than a month prior. Both SN8, SN9, and SN10 made it further into their identical flight tests, leaving SN11 somewhat high and dry and putting extra pressure on Starship SN15.
After Starship SN8’s unexpectedly successful December 2020 test flight, in which the rocket made it just a dozen or so seconds away from soft landing after more than six minutes in flight, SpaceX made the decision to scrap Starship SN12 and kill SN13 and SN14 before assembly could begin. Effectively a gamble that SN8-SN11 would produce enough of a foundation for future testing to start off on, it’s hard to say if that gamble paid off.
All four Starship flights managed the extraordinary feat of more than four minutes of powered flight and spent two minutes free-falling like no rocket ever before them, but they also made it clear that both Raptor and autogenous pressurization (using gasified propellant to pressurize Starship’s tanks) are not quite mature enough for reliable launches and landings. Featuring “hundreds of improvements,” many of which were hopefully designed to tackle some of those shortcomings, it’ll be up to Starship SN15 to attempt to carry that torch forward – and, with any luck, further than any prototype before it.
After SpaceX unexpectedly used a Monday road closure to deliver its first custom-built rocket fuel tank, plans for the next Starship test campaign and launch have begun to solidify.
Most importantly, the initial schedule for Starship serial number 15’s (SN15) test campaign appears to be clear. As of Wednesday, April 7th, road closures filed by SpaceX suggest that the first of a new group of upgraded Starships will be transported from build site to launch pad as early as 11am-1:30pm CDT (UTC-5) on Thursday, April 8th. Once SN15 is installed on ‘Suborbital Pad A,’ SpaceX means to waste no time and has scheduled a 7am-12pm road closure on Friday.
As usual, the weekend will once again be free of any testing or activity requiring road closures, but SpaceX has already cordoned off noon to 8pm on Monday and Tuesday (April 12/13) to continue putting its newest Starship prototype to the test.
While road closure notices no longer offer any real detail, a few basic details can still be inferred. The April 7th closure, for example, warns that SpaceX only plans to intermittently close the highway but not Boca Chica Beach – implying that the window poses no threat to residents or beachgoers. Historically, that means that something will be transported – likely Starship SN15, in this case.
On Friday, SpaceX has scheduled a full five-hour closure of both the highway and beach, implying that some kind of testing is likely on the books. The same goes for Monday and Tuesday, but with longer eight-hour closures.
More likely than not, assuming Starship SN15’s pad transport and launch mount installation goes smoothly, SpaceX will use the shorter Friday window to complete a basic ambient pressure test – filling the rocket with ambient-temperature nitrogen gas to test its complex plumbing and propellant tanks for leaks. Continuing the IFF (if and only if) string, SpaceX will then spend the weekend preparing Starship SN15 for a cryogenic proof test and thrust structure stress test – simulating the thrust of three Raptors after loading the rocket with extremely cold liquid nitrogen (LN2).
SpaceX will then most likely spend another one or two days inspecting Starship SN15 and removing the hydraulic ram used to simulated thrust from the launch mount the ship is installed on. Once SN15 and its mount are cleared, SpaceX can move into static fire testing. Given that – according to CEO Elon Musk – SN15 will debut Raptor engines with an unknown degree of upgrades, it’s reasonable to assume that SpaceX will take things relatively slowly and possibly perform more than one static fire test even if the first attempt is a total success.
If not and SpaceX continues to push hard like it did with SN10 and SN11, it’s not out of the question that Starship SN15 will be ready for its first launch attempt around Friday, April 16th or Monday, April 19th. Stay tuned for updates as SpaceX hopefully rolls the rocket to its Boca Chica, Texas launch site later today.
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 launched the all-electric, steering wheel-less, and pedal-less Cybercab last night at a quiet and small event in downtown Austin, Texas.
The launch, which marked the beginning of unsupervised ride-hailing for Tesla’s Robotaxi platform with Cybercab, has already caught the attention of the National Highway Traffic Safety Administration (NHTSA) who has more questions.
NHTSA opened an Audit Query (AQ) into the Cybercab’s Federal Motor Vehicle Safety Standards (FMVSS) certification that Tesla gave the vehicle. Manufacturers self-certify vehicles much of the time to avoid excessive regulatory delays.
Tesla Cybercab interior, note the lack of steering wheel and pedals. (Credit: @niccruzpatane/X< /a>)
However, the agency needs more information; it said in a summary:
“On September 3, 2026, Tesla began commercial deployment with a small number of its Cybercab vehicles in Austin, Texas. Tesla notified the Agency that it certified those Cybercab vehicles as compliant with all applicable Federal Motor Vehicle Safety Standards (FMVSS). Tesla also notified the Agency that it plans to gradually expand commercial deployment of the Cybercab to include additional vehicles and locations.”
It also went on to state that the Cybercab lacks traditional automotive controls, which is a groundbreaking move. The process is entirely new to the NHTSA, which gives the agency some leverage to put Tesla’s launch under a microscope:
“The vehicles lack permanently attached, conventional manual controls, such as a brake pedal, gas pedal, steering wheel, and mirrors. NHTSA is opening this AQ to examine the process and technical data on which Tesla relied when certifying the Cybercab and related issues. Among other things, NHTSA will consider the extent to which Tesla’s certification depended on determinations that certain FMVSS are inapplicable to the Cybercab.”
Tesla has added 45 Cybercab units to its fleet of Robotaxi-enabled cars in Austin, according to public documents the company submitted to the State of Texas over the past week. Enabling this level of self-driving is something Tesla has worked toward for many years, and now that it is finally here, it seems more than reasonable that regulatory agencies will have some questions.
Many outlets might try to frame this as a negative, but it is truly an agency looking to gain more information about groundbreaking tech that Tesla has been developing for years.
In an effort to keep riders, pedestrians, and property safe, any and all data accumulated from these first days, weeks, and months of rides will likely be shared with the NHTSA to enable broader rollout strategies across the United States and more in the future.
Tesla Robotaxi will be a 24/7 service: here’s when
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
