News
[Update: Scrubbed] SpaceX Starship to attempt same-day static fire and launch
Update: Starship SN11 did manage a timely static fire around 8am CDT but after hours of work, SpaceX appears to have scrubbed a Friday, March 26th launch attempt.
SpaceX’s website has yet to be updated and Friday’s FAA TFR is still active but a road closure meant to last until 7:30 pm CDT to cover the static fire and launch was retracted after the highway was reopened around 2:45 pm. It’s unclear what caused the scrub but weather or technical issues from the static fire are two likely candidates. SpaceX still has TFRs active on Saturday and Sunday, but the company hasn’t tested or flown on a weekend in months.
Lacking only an official confirmation, SpaceX appears to be readying the fourth full-size Starship prototype to attempt a Raptor static fire test and launch on the same day.
That hopeful day in question happens to be today – Friday, March 26th. If all goes according to plan, Starship serial number SN11 will fire up its three Raptors, verifying their health after an engine was apparently swapped out on Wednesday. Possibly just an hour or two later, after detanking and retanking liquid oxygen and methane propellant, the Starship prototype could lift off on SpaceX’s fourth high-altitude test flight.
Late on March 24th, SpaceX rolled Raptor engine SN46 from its Boca Chica factory to the launch pad, where Starship SN11 is installed on one of two suborbital launch mounts. The engine move and subsequent installation came as a surprise, as nobody managed to catch an implied Starship SN11 engine removal in the two or three days prior (extremely thick fog being the likeliest cause).
The implied issue with the Raptor that was removed is likely to blame for a several-day launch delay that followed Starship’s seemingly successful Monday static fire. After that test, SN11’s launch was initially scheduled as early as Tuesday or Wednesday, only to slip day by day as the week proceeded. SN11 first rolled to the launch pad on March 8th, just 18 days ago, so launch delays don’t come as a huge surprise given that the current factory-to-launch record for a three-engine Starship is 33 days, three static fires, and one engine swap.
If SN11 manages a same-day static fire and launch on March 26th, it will still crush that record by almost 50%. To an extent, the feat also isn’t unprecedented. On March 3rd, Starship SN10 aborted its first true launch attempt milliseconds after Raptor ignition when the rocket’s flight computer detected indications that they were producing too much thrust. Amazingly, instead of scrubbing the launch attempt, SpaceX loosened Starship SN10’s thrust limit parameters and tried again, successfully lifting off just three hours after the abort.
Despite the abort and immediate hands-free recycle, Starship SN10 subsequently became the first prototype of its kind to launch to 10 km (6.2 mi), free-fall back to earth, and land in one piece. Minutes later, a fire and harder landing than expected conspired to make SN10 explode, but the test flight was arguably still a massive success. Simultaneously, the flight indicated that Starships are technically capable of successfully flying hours after a post-ignition launch abort, demonstrating an extraordinary level of robustness for clustered high-performance rocket engines.
As such, while it’s probably reasonable to assume that Starship SN11 wont launch today, SN10 proved that there is nonzero chance of a static fire and launch hours apart. Additionally, given just how close SN10 go to unequivocal success (i.e. a soft and survivable landing), Starship SN11 has the best chance yet at at launching, landing, and making it through the ordeal without exploding.
Starship SN11’s third static fire and first launch attempt are both currently scheduled sometime between 7am and 7:30pm CDT (UTC-5). Stay tuned for updates as we wait for SpaceX’s official confirmation and an evacuation notice of Boca Chica Village residents.
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
