News
High winds scrub SpaceX Starship SN9’s Monday launch attempt
Update (2:30 pm CST): SpaceX appears to have called off Monday’s Starship SN9 launch attempt due (primarily) to high winds along the flight corridor. Additional opportunities are available from 8 am to 6 pm CST (UTC-6) on Tuesday (Jan 26) and Wednesday (Jan 27).
Technically, lacking any official confirmation, there’s still a chance of a launch attempt or additional ground testing happening today but either possibility is extremely unlikely at this point.
Update: SpaceX has completed what is known as a Flight Readiness Review (FRR) and determined that Starship prototype SN9 is ready to attempt its first high-altitude launch as early as today.
All necessary aviation and maritime notices and restrictions are in place and the company has begun the process of closing a public highway and clearing the launch site of employees. Today’s (Jan 25) launch window lasts from noon to 6 pm CST (UTC-6) and Starship SN9 could likely be made ready to launch anytime after 2pm be ready to fly as early as 4 pm CST according to a loudspeaker announcement at the launch pad. Stay tuned for updates and, hopefully, an official SpaceX webcast.
All signs point to SpaceX’s second high-altitude Starship prototype preparing for a 12.5-kilometer (~40,000 ft) as early as Monday, January 25th in a bid to rectify a last-second bug that caused its predecessor to explode last month.
Known as Starship serial number 8 (SN8), the SpaceX-built prototype was the first to have its basic airframe (tank and nose sections) fully integrated, as well as the first Starship to attempt to break the 150m (~500 ft) ceiling set by Starhopper, SN5, and SN6. Break the ceiling SN8 most certainly did, performing a spectacularly successful 12.5 km launch that aced almost every single goal SpaceX had hoped to complete. Keyword almost.
After an impressive 280 seconds of uninterrupted operation of its Raptors, Starship SN8 shut down the last of those three engines, flipped onto its belly, and successful freefell ~12 kilometers back to Earth. The rocket then carried that success even further, reigniting two Raptors, performing a dramatic 120-degree flip, orienting itself vertically, and beginning to slow down for a soft landing.
Only then did Starship SN8’s performance deviate from virtual perfection. At T+6:38, a few seconds after beginning its crucial landing burn, one of Starship’s active Raptors shut down and the other effectively stopped generating thrust. The reason, CEO Elon Musk would later explain, was low head pressure in a smaller tank (‘header tank’) dedicated to supplying fuel during Starship’s wild flip and landing maneuver. It was never confirmed if the Raptor engine shutdown observed milliseconds prior to the other engine losing thrust was intentional.
Cause aside, the end result was unsurprising: without enough thrust to slow down, Starship SN8 accurately impacted the concrete landing zone but did so at high speed – likely around 50-60 m/s (100-150 mph). Given that Starhopper and Starships SN5 and SN6 had already successfully proven Starship’s ability to gently land from 150 meters on a single Raptor engine and that, prior to SN8, Starship’s bizarre belly-flop descent and 90-degree flip had been almost entirely theoretical, SpaceX deemed the launch a spectacular success.
Nothing better exemplifies that than the fact that a little over a month later, SpaceX quite literally began scrapping the most complex, completed section of a future Starship prototype (SN12) before it ever reached the assembly phase. Instead, SpaceX appears to be more focused than ever on a mysterious series of “major” upgrades Musk has said will debut on Starship SN15. Nearly all SN15 subsections have been completed and are simply waiting to be joined together, while parts of SN16 and SN17 are also starting to pile up in staging areas.
Starship SN10 is practically ready to move to the launch pad to prepare for flight as soon as SpaceX chooses to do so and Starship SN11 is likely no more than a week or two of work away from reaching same level of readiness.
Ultimately, despite a long and delay-ridden test campaign, Starship SN9 finally completed what looked like a full-duration static fire of all three of its Raptor engines – the rocket’s sixth static fire overall. On Saturday, January 23rd, SpaceXers installed SN9’s flight termination system (FTS) – a system of explosives designed to destroy Starship if it flies too far off course. For Starship, FTS installation all but guarantees that a launch attempt is a matter of days away. Fresh county roadblocks, Temporary Flight Restrictions (TFRs) granted by the FAA, and Coast Guard a safety notice further imply that SN9 will attempt to launch as early as Monday morning, January 25th, with backup opportunities on Tuesday and Wednesday.
With any luck, like SN8’s high-altitude debut, SpaceX hopefully livestream Starship SN9’s own attempt at the same feat. Stay tuned for more details as they come.
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
