News
SpaceX gets first taste of coronavirus epidemic's consequences
SpaceX’s next scheduled rocket launch has been indefinitely delayed after Argentina – responsible for the SAOCOM 1B satellite payload – put strict travel restrictions in place, the first sign of the coronavirus epidemic’s consequences for the company.
Previously expected to launch as early as March 30th, the ~3000-kg (6600 lb) SAOCOM 1B radar satellite departed its Bariloche production facilities and arrived at Cape Canaveral around February 23rd, around the same time pandemic impacts began to be felt outside of China. Now likely sitting in a SpaceX payload processing facility at Cape Canaveral Air Force Station (CCAFS), it appears that SAOCOM 1B will have to wait for the foreseeable future before teams from Argentina and other countries are able to access the spacecraft and prepare it for launch.
While the delay is unfortunate, it hardly comes as a surprise at the same time dozens of countries around the world are considering – or already enacting – extreme countermeasures to mitigate the damage that will be caused by the COVID-19 pandemic. Thankfully, once Argentinian space agency (CONAE) employees are able to prepare SAOCOM 1B for flight, the mission is still set to make history, marking the first time a rocket launches on a polar trajectory from the United States’ East Coast in more than a half-century. In the meantime, SpaceX – while not deriving any income – also has ways of potentially taking advantage of a bad situation and exploiting unexpected downtime as a result of customer delays.
In October 2018, SpaceX successfully launched SAOCOM 1B’s predecessor – SAOCOM 1A – from its Vandenberg Air Force Base (VAFB) facilities, using a West Coast landing pad (LZ-4) for the first time ever. The spacecraft has successfully operated in space ever since, serving scientists, farmers, and more with high-quality satellite radar and Earth observation data.
Planned as a two-satellite constellation, CONAE spent another 15 or so months manufacturing and assembling the sister spacecraft, reaching the integration completion milestone in December 2019. After completing a few additional mechanical and electrical tests to verify the satellite’s health in January and February 2020, SAOCOM 1B was loaded aboard a Russian Antonov cargo plane and flown directly to Florida’s Kennedy Space Center (KSC), landing at the same runway NASA’s Space Shuttle once used.
Shortly after the growing global pandemic began to bare its teeth, the Argentinian government made the decision to almost completely ban international travel for the time being, while citizens now face heightened restrictions in a bid to legally enforce social distancing precautions. A scientific satellite launch has unsurprisingly not won exemption rights, meaning that it’s now all but impossible for the Argentinian space agency to send people and supplies back and forth from Florida – a necessity for something as complex as a satellite launch campaign.
As such, SpaceX’s SAOCOM 1B launch will be delayed until Argentina is able to loosen domestic and international travel restrictions – the timeline for which is anyone’s guess.
Bittersweet lemonade
Prior to the commercial mission’s indefinite delay, SpaceX’s seventh dedicated Starlink and sixth v1.0 satellite launch – Starlink L7 or Starlink V1 L6 – was expected no earlier than (NET) April 2020, sometime shortly after SAOCOM 1B’s NET March 30th launch. However, CEO Elon Musk and a second executive recently revealed that SpaceX is building Starlink satellites faster than it can launch them – churning out as many as six spacecraft in a single day.
Previously proposed on Teslarati, SpaceX may thus have a substantial backlog – ranging from one to several launches worth – of satellites that are ready for flight and either waiting for transport or already in Florida. In 2020, SpaceX has completed four 60-satellite Starlink launches in ~11 weeks, averaging a bit less than three weeks per mission. Even if SpaceX’s Starlink factory only averages 4-5 satellites per day each month, that would mean that the company is still building at least 20-40 extra satellites for each batch of 60 it launches.
In other words, if a separate Falcon 9 booster, upper stage, and payload fairing are already prepared for launch or SAOCOM 1B customer CONAE is willing to let SpaceX use its rocket (much less likely), the company could feasibly replace the mission on its manifest with an internal Starlink launch. This would reduce the amount of time the company’s workforce is listless as a result of the pandemic – a move that wouldn’t save money, per se, but would more efficiently distribute resources that will otherwise be wasted. For now, though, we – and the rest of the world – will have to wait and see.
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
