News
SpaceX President updates schedule for Starship’s orbital launch debut
SpaceX COO and President Gwynne Shotwell says that the company now expects Starbase to be ready for Starship’s first orbital launch attempt as early as June or July, pushing the schedule back another month or two.
To accomplish that feat, SpaceX will need to more or less ace a wide range of challenging and unproven tests and pass a series of exhaustive bureaucratic reviews, significantly increasing the odds that Starship’s orbital launch debut is actually closer to 3-6 months away. While SpaceX could technically pull off a miracle or even attempt to launch hardware that has only been partially tested, even the most optimistic of hypothetical scenarios are still contingent upon things largely outside of the company’s control.
Will FAA or won’t FAA?
Both revolve around the Federal Aviation Administration (FAA), which – in SpaceX’s case – is responsible for completing a ‘programmatic environmental assessment’ (PEA) of orbital Starship launches out of Boca Chica, Texas and issuing a launch license for the largest and most powerful rocket ever built. In some ways, both tasks are unprecedented, but the bureaucratic processes involved are still largely the same as those SpaceX has successfully navigated over the last two decades.
First up, the FAA’s environmental review. Until very recently, the fate of Starbase’s PEA was almost completely indeterminable and could have gone any number of ways – most of which would not be favorable for SpaceX. However, just a few days ago and about a week after the FAA’s latest one-to-two-month PEA delay announcement, the agency updated an online dashboard to show that the fourth of five main PEA processes had been completed successfully. The most important part of the update is the implication that SpaceX and the FAA have now completed almost every aspect of the PEA that requires cooperation with other federal agencies and local stakeholders.
Only one more cooperative process – ensuring “Section 4(f)” compliance – still needs to be completed. Without delving into the details, there is no convincing evidence to suggest that that particular step will be a showstopper, though SpaceX might have to compromise on certain aspects of Starbase operations to complete it. Once Section 4(f) is behind them, the only thing standing between the FAA and SpaceX and a Final PEA is the completion and approval of all relevant paperwork. In other words, for the first time ever, the FAA’s targeted completion date – currently May 31st, 2022 – may actually be achievable.
Still, as the FAA itself loves to repeatedly point out, “the completion of the PEA will not guarantee that the FAA will issue a launch license – SpaceX’s application must also meet FAA safety, risk, and financial responsibility requirements.” Even if the PEA is perfect, SpaceX still has to secure an FAA launch license for the largest and most powerful rocket in history. It’s unclear if SpaceX and the FAA have already begun that painful back-and-forth or if some tedious fine print prevents it from starting before an environmental review is in place. Without knowing more, launch licensing could take anywhere from a few days to several months.
A series of tubes
Without the FAA’s launch license and environmental approval, any Starship SpaceX builds cannot legally launch from Starbase. On the other side of the coin, though, it’s just as true that the FAA’s nods of approval are worth about as much as the paper they’re written on without a rocket that’s ready to launch. In a perfect world, SpaceX would have a Starship and Super Heavy booster fully qualified, stacked, and sitting at Starbase’s orbital launch site when the FAA finally gives a green light. However, that’s not quite what SpaceX’s reality is today.
First Starship orbital flight will be with Raptor 2 engines, as they are much more capable & reliable. 230 ton or ~500k lb thrust at sea level.
We’ll have 39 flightworthy engines built by next month, then another month to integrate, so hopefully May for orbital flight test.— Elon Musk (@elonmusk) March 21, 2022
SpaceX has made a significant amount of progress in the last month and a half, but contrary to CEO Elon Musk’s hopes as of March 21st, the company will absolutely not be ready to attempt an orbital launch by the end of May. Nonetheless, Shotwell’s estimate of “June or July” may not be completely out of reach. Since Musk’s tweet, SpaceX finished assembling Super Heavy Booster 7, rolled the rocket to the launch site on March 31st, and completed several major tests in early April. However, during the last test, an apparent operator error significantly damaged a large part installed inside the booster, forcing SpaceX to return Super Heavy B7 to Starbase’s build site. After two and a half weeks of repairs, Booster 7 returned to the launch site on May 6th and completed another ‘cryoproof’ test, seemingly verifying that those quick repairs did the job.
Had Booster 7 not required repairs, it’s not impossible (but still hard) to imagine that SpaceX could have had a Super Heavy booster ready to launch by the end of May. Still, the static fire testing Booster 7 needs to complete is almost entirely unprecedented and could take months to complete. To date, SpaceX has never ignited more than six Raptors at once on a Starship prototype, while Super Heavy will likely need to complete multiple 33-engine tests before it can be safely considered ready for flight. Worse, there is no guarantee that SpaceX actually wants to fly Booster 7 after the damage it suffered. If Booster 8 carries the torch forward instead, Starship’s orbital launch debut could easily slip to late Q3 or Q4 2022.
Meanwhile, Super Heavy is only half of the rocket. When Musk tweeted his “hopefully May” estimate, SpaceX was nowhere close to finishing the Starship – Ship 24 – that is believed to have been assigned to the orbital launch debut. However, SpaceX finally accelerated Ship 24 assembly within the last few weeks and ultimately finished stacking the upgraded Starship on May 8th. A great deal of work remains to truly complete Ship 24, but SpaceX should be ready to send it to a test stand within a week or two. Even though the testing Ship 24 will need to complete has been done before by Ship 20, making its path forward less risky than Booster 7’s, Ship 24 will debut a number of major design changes and likely needs at least two months of testing to reach a basic level of flight readiness.
Last but not least, there’s the question of the orbital launch site (OLS) itself. Is the launch mount ready to survive a full Super Heavy static fire? Is the pad’s tank farm ready to fill Starship and Super Heavy with several thousand tons of flammable, explosive cryogenic propellant? If it’s a goal of the test flight, is the launch tower ready for a Super Heavy booster to attempt to land in its arms? While there are reasons to believe that the answer to some of those questions is “yes,” plenty of uncertainty remains and plenty of work is still incomplete.
Ultimately, Shotwell’s June goal is almost certainly unachievable. Late July, however, might be within the realm of possibility, but only in the unlikely event that all Booster 7 and Ship 24 testing is completed almost perfectly and without further delay. For the pragmatic reader, August or September is a safer bet. Thankfully, at least one thing is certain: activity at Starbase is about to get significantly more exciting.
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
