News
(Update: Sunday) SpaceX’s high-altitude Starship launch debut slips to Monday
Update #2: Per new Temporary Flight Restrictions, there’s now a chance that SpaceX has rescheduled Starship’s (now slightly less) high-altitude launch debut on Sunday afternoon, December 6th.
As always with experimental testing, uncertainty remains. Stay tuned for updates as we close in on Starship SN8’s 12.5-kilometer (~7.8 mi) launch debut.
Update: SpaceX’s high-altitude Starship launch debut appears to have slipped to no earlier than (NET) Monday morning, December 7th, and been reduced from 15 km to 12.5 km.
FAA-approved flight restrictions filed on December 2nd were retracted on December 3rd for unknown reasons, ultimately giving SpaceX several more days to prepare Starship SN8 for an ambitious high-altitude launch, coast, freefall, and landing attempt.
Meanwhile, SpaceX has also lowered Starship SN8’s apogee target to 12.5 km (7.8 mi) from 15 km, itself a reduction from 20 km made earlier this year. Why is entirely unclear but it’s likely that the company is in active discussion (and probably arguments) with the FAA, perhaps requiring a compromise to ensure regulatory approval.
It remains to be seen if SpaceX will perform any additional testing over the weekend or if the company will attempt to schedule Starship SN8’s launch debut on Saturday or Sunday. Stay tuned for updates and Elon Musk’s promised SpaceX webcast.
SpaceX has received FAA approval to attempt Starship’s high-altitude launch debut as early as Friday according to a Temporary Flight Restriction (TFR) filed on December 2nd.
SpaceX’s first high-altitude Starship TFR revealed that the crucial flight test is now scheduled sometime between 8 am and 5 pm CST (14:00-23:00 UTC) on Friday, December 4th, with identical backup windows available (and cleared with the FAA) on Saturday and Sunday. Originally scheduled as early as November 30th, the delays are less than surprising given the complexity and unprecedented nature of the flight test facing SpaceX.
Starship serial/ship number 8 (SN8) – the first functional full-height prototype – is tasked with launching from Boca Chica, Texas to an apogee of 15 kilometers (~9.5 miles) and dropping back to Earth to test an unproven approach to rocket recovery.
Often referred to as a bellyflop or skydiver-style attitude, Starship SN8 will attempt to freefall belly-down back to earth, using four large flaps to maintain a stable approach much like skydivers use their arms and legs to control heading and speed. When landing on planets or moons with relatively thick atmospheres, a controlled freefall could save Starship a huge amount of structural mass (no need for wings or actual airfoils) and propellant – a major benefit for what aims to be the largest reusable orbital spacecraft ever built.
Powered by three Raptor engines capable of producing up to 600 metric tons (1.3 million lbf) of thrust at full throttle, SN8’s launch debut will mark Starship’s first multiengine flight – a major milestone for any rocket prototype. SpaceX CEO Elon Musk also recently noted that Starship SN8’s propellant tanks will only be “slightly filled” for its 15 km launch debut, potentially resulting in an extremely healthy thrust to weight ratio at liftoff.
Based on several unofficial estimates, Starship SN8 is also likely to break the sound barrier on ascent, potentially putting the prototype through conditions similar to what an actual orbital launch might see at Max Q (the point of maximum aerodynamic pressure). Further adding to the daunting list of ‘firsts’, SN8’s 15 km debut will be the first Starship hop or flight with a nosecone, making it the first full-scale structural test of a nose section and the methods used to attach it to Starship’s tank section. It’s hard to exaggerate the number of things that could go wrong and the number of ways Starship SN8 could fail during its first flight.
In the interim, SpaceX has taken Starship’s launch delay as an opportunity to perform some kind of additional testing on the evening of December 2nd, involving some kind of cryogenic proof test (using liquid nitrogen) or wet dress rehearsal (WDR; using real liquid methane and oxygen). While there were initial signs that SpaceX would put SN8 through one or several more Raptor static fires before clearing the rocket for flight, it appears that those plans were cancelled earlier this week.
Less testing amplifies the risk that Starship SN8 will fail after liftoff, the probability of which Musk has pegged at ~67%. Regardless, SN8’s launch debut is bound to be spectacular and Starships SN9 and SN10 are nearly ready to take over wherever SN8 leaves off.
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
