News
SpaceX’s first orbital Starship launch slips to March 2022 in NASA document
A NASA document discussing a group’s plans to document SpaceX’s first orbital-velocity Starship reentry appears to suggest that the next-generation rocket’s orbital launch debut has slipped several months into 2022.
In March 2021, CEO Elon Musk confirmed a report that SpaceX was working towards a target of July 2021 for Starship’s first orbital launch attempt. At the time, it seemed undeniably ambitious but far from impossible. Less than half a year prior, SpaceX had kicked off a series of suborbital Starship test flights to altitudes of 10-12.5 km (6.2-8 mi). Beginning in December 2020, SN8 – effectively the first structurally complete Starship prototype – nearly stuck a landing on its first try, only narrowly falling short due to an engine and pressurization issue.
Less than two months later, SpaceX completed and launched Starship SN9 – again with a nearly flawless six-minute flight capped off with an unsuccessful landing attempt. Starship SN10 followed less than a month later and became the first prototype to land in one piece – albeit only for a few minutes. It was two weeks after that near-success – SpaceX’s third launch in as many months – that Musk revealed a goal of July 2021 for Starship’s first orbital launch. At that point in time, it appeared all but inevitable that SpaceX would be technically ready for an orbital launch before the end of the year.
Two weeks after Musk’s comments and less than four weeks after SN10’s near-miss, Starship SN11 gave one of the worst performances yet, invisibly exploding inside a fogbank well above the ground. However, further stoking the fires of optimism, Starship SN15 debuted a number of upgrades and became the first prototype to successfully launch, land, and survive a ~10km test flight in early May. Put simply, SpaceX built five Starship prototypes practically from scratch in roughly eight months and then completed five test flights in less than five months – all of which were largely successful.
SpaceX considered reusing Starship SN15 or launching SN16 to gain more landing experience but ultimately decided to mothball the prototypes to avoid disrupting orbital launch site construction. Just three months after SN15’s successful landing, SpaceX rolled the first orbital-class Starship and Super Heavy to the orbital launch site and briefly stacked the pair (Ship 20 and Booster 4) to their full height, forming the tallest rocket ever assembled. Although largely a photo opportunity, SpaceX still installed a full 29 Raptors on Super Heavy B4 and six Raptors on Starship S20, further raising confidence that the company’s engine production was already up to the task of supplying the nearly three-dozen needed for a single orbital test flight.
However, for reasons that are less than clear, that August 6th full-stack milestone is about where SpaceX’s H1 2021 momentum appeared to run into a brick wall. Perhaps due to a desire to focus on orbital launch site construction even at the cost of avoiding road closures or testing that would require a clear pad, Starship S20 sat on a stand for the better part of two months before completing even a minor test – by far the longest any Starship prototype has waited.
Seemingly in the midst of its third round of Raptor engine removal, Super Heavy B4 has yet to attempt a single test and it’s unclear how close to ready the orbital pad is to support booster proof and static fire tests. Neither ship nor booster has attempted to static fire its Raptor engines, though S20 could potentially be ready for its first test as early as Monday, October 18th.
Combined with recent developments in the FAA’s Boca Chica environmental review process, the odds of SpaceX attempting the first orbital Starship launch by the end of 2021 have rapidly dropped from decent to near-zero. From a technical perspective, it seems likely that SpaceX could still be ready for an orbital launch attempt just a few months from now. From a regulatory perspective, though, it would be practically unprecedented for the FAA to complete a favorable environmental review and approve even a one-off orbital Starship launch license in ~10 weeks. Even the apparent March 2022 target revealed in a NASA poster focused on the agency’s plans to film an orbital Starship reentry via high-altitude jet assumes that the FAA’s review and licensing process will take ~7 months from August 2021 – still extremely optimistic.
Ultimately, after two months with next to no prototype testing, it’s beginning to look like SpaceX has decided to focus on finishing Starbase’s first orbital launch site, refining vehicle designs, and building new prototypes (B5, S21, S22) rather than pushing hard for rapid B4/S20 testing and an imminent launch attempt. As a result, it’s becoming increasingly unlikely that Booster 4 and Ship 20 will fly as new and improved prototypes like Super Heavy B5 and Starship S21 prepare to overtake them.
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
