News
SpaceX Starlink launch ambitions just saved a space station resupply mission from bigger delays
SpaceX’s ambitious 2020 Starlink launch goals have unintentionally saved a Cargo Dragon spacecraft mission from much longer delays after a major part of its Falcon 9 rocket had to be replaced at the last second.
Known as SpaceX’s 20th NASA Commercial Resupply Services (CRS-20) mission, SpaceX’s Cargo Dragon spacecraft was initially scheduled to launch supplies to the International Space Station (ISS) as early as March 2nd, 2020, a date that recently slipped four days to 11:50 pm EDT (04:50 UTC), March 6th. Simultaneously, a separate Falcon 9 Starlink mission – assigned to a different launch pad – found itself delayed from March 4th to March 11th.
A day or so after news of the CRS-20 launch delay first broke, NASA published a blog post noting that SpaceX had taken the extraordinary step of fully replacing the mission’s Falcon 9 second stage, the part of the rocket (pictured underneath Dragon in the photo above) tasked with taking payloads from the edge of space into Earth orbit (or beyond). Triggered by a faulty component in its space-optimized Merlin Vacuum engine, the fact that SpaceX chose to replace the upper stage and still only delayed CRS-20’s launch by four days suggests that its ambitious Starlink launch plans are already creating positive side effects for commercial customers.
"SpaceX identified a valve motor on the second stage engine behaving not as expected and determined the safest and most expedient path to launch is to utilize the next second stage in line that was already at the Cape and ready for flight."https://t.co/E9dokEAf0n— Michael Baylor (@MichaelBaylor_) February 25, 2020
As of late, multi-day hardware-related launch delays have been rather rare for SpaceX, who has instead suffered numerous weather-related scrubs over the course of completing its Fall 2019 and Winter 2020 launch manifest. SpaceX’s February 17th Starlink-4 mission did suffer a minor second stage valve-related delay that was fixed in about 24 hours, but things have otherwise been quite smooth for Falcon 9.
Given all that goes into building and testing Falcon 9 second stages, there are very few good explanations (aside from pure luck) that would allow for a given SpaceX launch to entirely replace its assigned second stage a week before liftoff and only slip a handful of days. Nevertheless, with CRS-20, SpaceX is attempting to do exactly that.
“SpaceX identified a valve motor on the second stage engine behaving not as expected and determined the safest and most expedient path to launch is to utilize the next second stage in line that was already at the Cape and ready for flight. The new second stage has already completed the same preflight inspections with all hardware behaving as expected. The updated target launch date provides the time required to complete preflight integration and final checkouts.”
NASA.gov — February 25th, 2020
The specific lead times SpaceX’s Falcon rocket family parts require is almost totally unknown but it’s safe to say that the process of building a Falcon upper stage from scratch, performing acceptance testing in Texas, and shipping said stage to the launch pad takes months from start to finish. For SpaceX to be able to attempt to minimize CRS-20’s delays to just four days while still fully swapping out its upper stage, the company would have quite literally had to have had another Falcon stage just sitting around in Florida.
As it turns out, per NASA’s official statement, that is precisely what transpired. A separate second stage was already in Florida and “ready for flight”, giving SpaceX the luxury of selecting the safest option theoretically available. Beyond the hardware already being ready to go in Florida, the stage reassignment almost certainly also hinged upon the mission it was assigned to being somewhat nonessential – a label that SpaceX would be hard-pressed to affix to any of its customers’ launches. An internal Starlink mission, however, would be a perfect opportunity, allowing SpaceX to avoid both picking favorites and seriously impacting (aside from the ~4-day CRS-20 delay) its paying customers.
To be clear, SpaceX was thus able to swap out CRS-20’s upper stage at the last second with only a minor schedule impact almost exclusively because of it’s ambitious plans for 20-24 Starlink launches this year. If the company wasn’t pursuing a more than biweekly 2020 launch cadence, it’s much more likely that CRS-20 would have had to make do with its second stage or wait for a new one to be built, potentially delaying the launch by one or two weeks, if not longer.
In simple terms, the launch cadence SpaceX is targeting (and needs) for its Starlink constellation is already exhibiting signs of a future where its high-performance orbital-class rockets have been almost entirely commodified.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
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
