News
SpaceX’s orbital Starship launch debut may be pushed to 2022 by slow FAA reviews
In a rare sign of material progress, SpaceX and the FAA have finally released what is known as a draft environmental assessment (EA) of the company’s South Texas Starship launch plans.
Set to be the largest and most powerful rocket in spaceflight history when it first begins orbital launches, the process of acquiring permission to launch Starship and its Super Heavy booster out of the wetlands of the South Texas coast was never going to be easy. The Boca Chica site SpaceX ultimately settled on for its first private launch facilities – initially meant for Falcon 9 and Falcon Heavy but later dedicated to BFR (now Starship) – is simultaneously surrounded by sensitive coastal habitats populated by several threatened or endangered species and situated mere miles as the crow flies from a city whose temporary population oscillates from a few thousand to tens of thousands.
Reception and analysis of the draft and its timing have been mixed. On one hand, SpaceX’s draft EA – completed with oversight from the FAA and help from the US Fish and Wildlife Service (USFWS) – gives a number of reasons for optimism. In a sign that SpaceX is taking a pragmatic approach to the inevitable environmental review and launch license approval hurdles standing in front of orbital South Texas Starship launches, the company has actually pursued what is known as a “programmatic environmental assessment” (PEA).
Most importantly, that means that SpaceX’s Starbase PEA – if approved – will be more like a foundation or stepping stone that should make it easier to start small and methodically expand the scope and nature of the company’s plans for Boca Chica. Along those lines, as part of Starbase’s first dedicated environmental assessment, SpaceX has proposed a maximum of 23 flight operations annually while Starship is still in the development phase, including up to 20 suborbital Starship test flights and 3 orbital launches (or Super Heavy hops). Once SpaceX has worked out enough kinks for slightly more confident Starship operations, the company would enter an “operational phase” that would allow for as many as five suborbital Starship launches and five orbital Starship launches, as well as ship and booster landings back on land after all 10 possible launches.

In other words, SpaceX’s initial draft PEA is extremely conservative, requesting permission for what amounts to a bare minimum concept of operations for orbital Starship launches. At a maximum of 3-5 orbital launches per year, a PEA and subsequent launch license approved as-is would likely give SpaceX just enough slack to perform basic Earth orbit launches and no more than one or two orbital refilling tests per year. However, as an example, a five-launch maximum would almost entirely prevent SpaceX from launching Starship to Mars, the Moon, and maybe even high-energy Earth orbits without using all of its annual launch allotments on a single mission.
Perhaps most importantly, the draft PEA as proposed would unequivocally prevent SpaceX from performing the NASA Human Lander System (HLS) Moon landings it received an almost $3 billion contract to complete. Each HLS Starship Moon landing is expected to require anywhere from 10-16 launches to deliver a depot ship, HLS lander, and ~1200 tons of propellant to orbit. However, in terms of SpaceX’s prospects of developing Starship as quickly as possible, that’s actually a good thing. Above all else, SpaceX’s slimmed-down draft PEA should be far easier for the FAA to approve than a PEA pursuing permission for Starship’s ultimate ambitions – dozens to hundreds of launches annually – from the beginning. In theory, with this barebones PEA approved, SpaceX would then be able to build off the foundation with additional environmental assessments – like, for example, of expanding Starship’s maximum launch cadence.
Of course, SpaceX first needs the FAA turn this first draft PEA into a favorable environmental assessment (not a guarantee) before any of the above starts to matter. Based on the content of the draft itself and associated appendixes, SpaceX appears to have a decent shot at receiving a “finding of no significant impact (FONSI)” or “mitigated FONSI” determination. However, SpaceX began the process of creating that draft as far back as mid-2020, followed by an FAA announcement in November 2020. The implication is that the FAA managed to drag out a draft release process that some have estimated should have taken 3-4 months into an arduous 10-15 month ordeal.
Combined with the uphill battle it’s starting to look like SpaceX will have to wage for an orbital Starship launch license in South Texas, it’s looking increasingly likely that Starship, Super Heavy, and Starbase will be technically ready for orbital launch tests well before the FAA is ready to approve or license them. Barring delays, the public now has until mid-October to read and comment on SpaceX’s draft PEA, after which the FAA and SpaceX will review those comments and hopefully turn the draft into a completed review. Even if the FAA were to somehow take just two months to return a best-case FONSI, clearing Starbase of environmental launch hurdles, it’s hard to imagine that the agency could then turn around and approve an orbital Starship launch license – or even a one-off experimental permit – in the last few weeks of 2021.
Ultimately, that means that nothing short of a minor miracle is likely to prevent the FAA’s environmental review and licensing delays from directly delaying Starship’s orbital launch debut. There is at least a chance that Starship, Super Heavy, and Starbase’s orbital launch site wont be ready for orbital launches by the end of the year, but it’s increasingly difficult to imagine that all three won’t be proof tested, qualified, and ready for action just a month or two from now. For the time being, we’ll just have to wait and see where the cards fall.
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.
News
Tesla Cybercab launch catches NHTSA’s attention who wants to know more
Tesla launched the all-electric, steering wheel-less, and pedal-less Cybercab last night at a quiet and small event in downtown Austin, Texas.
The launch, which marked the beginning of unsupervised ride-hailing for Tesla’s Robotaxi platform with Cybercab, has already caught the attention of the National Highway Traffic Safety Administration (NHTSA) who has more questions.
NHTSA opened an Audit Query (AQ) into the Cybercab’s Federal Motor Vehicle Safety Standards (FMVSS) certification that Tesla gave the vehicle. Manufacturers self-certify vehicles much of the time to avoid excessive regulatory delays.

Tesla Cybercab interior, note the lack of steering wheel and pedals. (Credit: @niccruzpatane/X< /a>)
However, the agency needs more information; it said in a summary:
“On September 3, 2026, Tesla began commercial deployment with a small number of its Cybercab vehicles in Austin, Texas. Tesla notified the Agency that it certified those Cybercab vehicles as compliant with all applicable Federal Motor Vehicle Safety Standards (FMVSS). Tesla also notified the Agency that it plans to gradually expand commercial deployment of the Cybercab to include additional vehicles and locations.”
It also went on to state that the Cybercab lacks traditional automotive controls, which is a groundbreaking move. The process is entirely new to the NHTSA, which gives the agency some leverage to put Tesla’s launch under a microscope:
“The vehicles lack permanently attached, conventional manual controls, such as a brake pedal, gas pedal, steering wheel, and mirrors. NHTSA is opening this AQ to examine the process and technical data on which Tesla relied when certifying the Cybercab and related issues. Among other things, NHTSA will consider the extent to which Tesla’s certification depended on determinations that certain FMVSS are inapplicable to the Cybercab.”
Tesla has added 45 Cybercab units to its fleet of Robotaxi-enabled cars in Austin, according to public documents the company submitted to the State of Texas over the past week. Enabling this level of self-driving is something Tesla has worked toward for many years, and now that it is finally here, it seems more than reasonable that regulatory agencies will have some questions.
Many outlets might try to frame this as a negative, but it is truly an agency looking to gain more information about groundbreaking tech that Tesla has been developing for years.
In an effort to keep riders, pedestrians, and property safe, any and all data accumulated from these first days, weeks, and months of rides will likely be shared with the NHTSA to enable broader rollout strategies across the United States and more in the future.