News
SpaceX’s first orbital Starship launch runs into more FAA delays
The US Federal Aviation Administration (FAA) says it’s at least two months behind schedule on an environmental review that must be completed before SpaceX will be allowed to attempt the first orbital Starship launch attempts.
In mid-November, the FAA revealed plans to complete SpaceX’s “SpaceX Starship/Super Heavy Launch Vehicle Program” programmatic environmental assessment (PEA) – a review that can be built upon down the road – by December 31st, 2021, officially delaying Starship’s first orbital launch attempt into 2022. Based on the lack of updates from the FAA and progress with the Starship and booster assigned to the mission, that delay was already largely expected, but the rare update nonetheless confirmed it with certainty. Now, less than a month and a half after the FAA announced its Dec 31st target, the agency has waited until three days before that estimated deadline to announce that it will take at least two more months to complete the review.
Somewhat insultingly, in its official statement on the delay, the FAA appears to attempt to implicate the review of “over 18,000 public comments” received during a comment period as a source of those delays. That six-week comment period ended on November 1st, weeks before the FAA published its first December 31st target date. In other words, for comment reviews to be responsible for any of the new delays, the FAA’s environmental compliance group would have had to underestimate the amount of work required to complete that process by at least 100% – not all that encouraging for an agency in which precision and accuracy are of the utmost importance.
“The FAA plans to issue the Final Programmatic Environmental Assessment (PEA) for the SpaceX Starship / Super Heavy project on Feb. 28, 2022. The previous target date was Dec. 31, 2021.
Under the oversight of the FAA, SpaceX is currently drafting responses for the over 18,000 public comments received on the Draft PEA and continues to prepare the Final PEA for the FAA’s review and acceptance. In addition, the FAA is continuing consultation and coordination with other agencies at the local, State and Federal level.
The environmental review is just one part of the FAA commercial space licensing process. SpaceX’s license application must also meet FAA safety, risk and financial responsibility requirements.”
The real delays, which the FAA acknowledges in much less detail, are likely the result of “continuing consultation and coordination with other agencies at the local, State, and Federal level [sic].” In the FAA’s defense, some of those delays may technically be out of its control if slow responses from other agencies are partly to blame. Nonetheless, it was the FAA’s decision to wait from November 2020 to June 2021 to actually proceed with SpaceX’s Starship environmental assessment, which the company officially began drafting in March 2021.
Had the FAA started work on the PEA in earnest several months prior, which appears to have been well within its power, SpaceX’s extremely limited orbital Starship PEA might already be complete, allowing the agency to begin ensuring that SpaceX “meet[s] FAA safety, risk and financial responsibility requirements.” If the process of securing a limited license for far less risky suborbital Starship launches is anything to go off of, securing a similar license for orbital Starship launches with 10-20 times the explosive potential could be an agonizing months-long ordeal. It’s ambiguous if the FAA is already deep into that process or if it’s waiting for a complete, approved PEA to begin work on Starship’s first orbital launch license.
Regardless, the fact remains that it’s no longer clear if the FAA’s delays or poor schedule estimates will actually delay Starship’s first orbital launch attempt. Originally said to be no earlier than July 2021 and almost every subsequent month since by Elon Musk, the CEO’s most recent estimate was January or February 2022. According to a relevant NASA research project published a month prior to Musk’s estimate, the space agency anticipated Starship’s orbital launch debut no earlier than March 2022. Now that the FAA doesn’t expect to complete Starship’s orbital-class PEA before February 28th, 2022, March or April 2022 appears to be a more accurate NET.
That will give SpaceX another three months at minimum to – just maybe – finally complete Super Heavy B4’s aft assembly, qualify and fill the methane side of Starbase’s orbital-class tank farm, perform several unprecedentedly ambitious wet dress rehearsals and static fires, really make sure Ship 20 is ready for flight, and activate the orbital launch tower’s massive ‘chopstick’ arms – meant to eventually catch rockets out of the air but also necessary for SpaceX to install Starship on top of Super Heavy.
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 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.
Tesla Robotaxi will be a 24/7 service: here’s when
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
