News
SpaceX CEO Elon Musk’s hat is safe after ULA Vulcan rocket launch slips to 2023
In the latest unfortunate development for SpaceX competitor United Launch Alliance’s next-generation Vulcan Centaur rocket, it looks like CEO Elon Musk may have been right all along when he forecast major delays more than three years ago.
In February 2018, even before SpaceX had flown Falcon Heavy for the first time, detractors with axes to grind were already busy attempting to downplay the rocket’s capabilities. On February 6th, Falcon Heavy lifted off for the first time, launching a several-ton Tesla Roadster car into interplanetary space and marking the first debut of a super heavy-lift rocket since the 1980s. That successful launch also meant that ULA’s last bastion of competitive advantage – the Delta IV Heavy rocket, fittingly by way of monopoly – was no longer alone.
Indeed, mere months after its near-flawless debut, Falcon Heavy had already secured its first operational US military launch contract. Delta IV Heavy, on the other hand, had already been preparing for retirement as part of ULA’s plan to replace two complex rockets (Delta and Atlas) with Vulcan.
Musk mercilessly took to task ULA’s heavy-lift rocket when commenters brought it up, noting that Falcon Heavy is largely comparable in a partially-reusable configuration but completely outclasses Delta IV Heavy – while still being dramatically cheaper – if all boosters are expended. The SpaceX CEO estimated that Delta IV Heavy launches would cost ULA significantly more than $400M after the company had effectively announced the end of Delta IV Medium production, though ULA CEO Tory Bruno still claimed a launch price of ~$350M.
In response to a reply noting that ULA’s plan was to replace Atlas V and Delta IV with Vulcan Centaur for launches “after 2020,” Musk pulled no punches, stating that he would “seriously eat [his] hat with a side of mustard if [Vulcan] flies a national security spacecraft before 2023.” At the time, ULA’s CEO did not exactly seem to share Musk’s shocking appraisal of the situation, which was out of left field even for major SpaceX proponents.
At the time, ULA’s party line touted Vulcan Centaur lifting off for the first time in late 2019 – the very next year. Ironically, weeks after Musk threw down his hat-eating gauntlet, ULA announced that Vulcan’s first launch had slipped to “mid-2020” – with a second flight later the same year – to give the company time to move straight to a larger upper stage originally meant to debut later on. Six months later, ULA announced yet another delay for Vulcan, this time pushing the rocket’s launch debut from mid-2020 to no earlier than (NET) April 2021.
Three years later, April 2021 has come and gone and ULA’s latest public Vulcan launch target is now “late 2021,” though that is all but guaranteed to slip into early 2022. In the latest (not-so-) shocking development for ULA’s next-generation rocket, the company has now requested and received permission from the US military to swap out Vulcan for an Atlas V rocket on what would have been the vehicle’s first military launch.
Exercising a contract loophole that had to have been explicitly designed to give ULA – and ULA alone – the option to fall back on its Atlas V or Delta IV rockets if Vulcan were to experience major delays, Atlas V will now take over the ULA’s USSF-51 mission. As a result, Vulcan Centaur’s first dedicated ‘national security’ launch is now officially scheduled no earlier than 2023, saving Elon Musk from having to eat his hat.
As of May 2021, ULA has now replaced one Vulcan launch with an Atlas V and inexplicably closed nine Atlas V launch contracts with Starlink competitor Amazon, bringing into question whether the company is ever actually going to simplify its rocket production lines. Given that ULA no longer appears to be planning on reusing parts of Vulcan, the only possible way Vulcan will end up more affordable than the rockets its replacing is if it quickly becomes the only rocket ULA produces, which was originally the plan. With ULA now apparently going out of its way to sell Atlas V commercially instead of Vulcan Centaur, it’s difficult to argue that the company has any interest at all in lowering the cost of access to space or offering SpaceX serious competition outside of lobbying and greasing the hinges of revolving doors.
News
Tesla crosses major Unsupervised Self-Driving milestone
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.
News
Tesla Robotaxi will be a 24/7 service: here’s when
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.
News
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
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.