News
NASA may prematurely kill long-lived Mars rover with arbitrary wake-up deadline
In a decision with no obvious empirical explanation, JPL’s Opportunity Mars rover project manager John Callas was quoted in an August 30th press release saying that the NASA field center would be “forced to conclude” that the dust storm-stricken rover was effectively beyond saving if it fails to come back to life 45 days after 2018’s massive dust storm can be said to have officially ended.
Below the upbeat-sounding title of this press release is the scarier fact that after tau clears below 1.5, the rover has 45 days to wake up before NASA stops actively trying to revive it. Come on, #WakeUpOppy https://t.co/piCQLeaCEO
— Emily Lakdawalla (@elakdawalla) August 30, 2018
Over the course of that press release, Callas made a number of points that may technically hold at least a few grains of truth, but entirely fail to add up to any satisfactory explanation for the choices described therein. This is underscored in one critical and extended quote:
“If we do not hear back [from Opportunity] after 45 days, the team will be forced to conclude that the Sun-blocking dust and the Martian cold have conspired to cause some type of fault from which the rover will more than likely not recover. At that point, our active phase of reaching out to Opportunity will be at an end. However, in the unlikely chance that there is a large amount of dust sitting on the solar arrays that is blocking the Sun’s energy, we will continue passive listening efforts for several months.” – John Calwell, JPL
Scott Maxwell, a former JPL engineer who led drive planning for rovers Spirit and Opportunity, solidly explained the differences between active and passive recovery attempts:
Because it's a FAQ … "active listening" has two parts: (1) forcing Opportunity's radio, if she's listening, to a particular frequency (because it can drift), and (2) a command to talk to us. Pretty much guaranteed to work if she's awake with her radio on. https://t.co/iaHbHXFKqm
— 🇺🇦ScottMaxwell @marsroverdriver@deepspace.social (@marsroverdriver) August 31, 2018
The JPL press release offers exactly zero explanation for the “45-day” deadline, starting the moment that dust clears from Martian skies near Opportunity to a certain degree, likely to happen within the next few weeks. Nor does it explain why “active” recovery attempts would stop at that point, despite the fact that the PR happens to directly acknowledge the fact that the best time to attempt to actively restore contact Opportunity might be after Mars’ windy season is given a chance to blow accumulated dust off of the rover’s solar arrays.
In fact, while all points Callas/the press release makes may theoretically be valid, the experiences of the actual engineers that have been operating Opportunity and MER sister rover Spirit for nearly two decades suggest that his explanations are utterly shallow and fail even the most cursory comparison with real data.
Thanks largely to a number of comments collected by The Atlantic from past, present, and anonymous employees involved with Opportunity, it would seem that there is no truly empirical way to properly estimate the amount of dust that may or may not be on the rover’s solar arrays, no rational engineering-side explanation for the 45-day ultimatum, no clear excuse for how incredibly short that time-frame is, and essentially zero communication between whoever this decision originates from and the engineers tasked with operating and restoring communications with the forlorn, 15-year old rover.

Most tellingly, this exact impromptu dust-storm-triggered hibernation already occurred several times in the past, and even resulted in the demise of Opportunity’s sister rover Spirit in 2010. The Atlantic notes that when a dust storm forced that rover into hibernation in 2010, JPL mission engineers spent a full ten months actively attempting to resuscitate Spirit, followed by another five months of passive listening before the rescue effort was called off.
Given that Opportunity’s engineers appear to believe that there is every reason to expect that the rover can, has, and should survive 2018’s exceptional Martian dust storm, the only plausible explanation for the arbitrary countdown and potentially premature silencing of one of just two active rovers on Mars is purely political and financial. While it requires VERY little money to operate scientific spacecraft when compared with manufacturing and launch costs, the several millions of dollars needed to fund operations engineers and technicians (roughly $15 million per year for Opportunity) could technically be funneled elsewhere or the employees in question could be redirected to newer programs.
For example, the ~$200 million spent operating the rover from 2004 to 2018 could instead fund considerably less than 20% of the original cost of building and launching both Opportunity and Spirit. This is to say that that cutting operation of functioning spacecraft to save money can be quite fairly compared with throwing an iPhone in the trash because the charging cable ripped because $10 could instead be put towards buying a new phone months or years down the line.
Ultimately, all we can do is hope that Opportunity manages to successfully wake up over the course of the next two or three months. If the rover is unable to do so, chances are sadly high that it will be lost forever once active communications restoration efforts come to an end. With an extraordinarily productive 15 years of exploration nearly under its belt, Opportunity – originally designed with an expected lifespan of ~90 days – would leave behind a legacy that would fail to disappoint even the most ardent cynic. Still, if life may yet remain in the rover, every effort ought to be made to keep the intrepid craft alive.
For prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket recovery fleet check out our brand new LaunchPad and LandingZone newsletters!
News
Tesla crosses major Unsupervised Self-Driving milestone
Tesla has reached a notable benchmark in its autonomous driving program after its Robotaxi fleet surpassed one million miles of unsupervised operation. The company made the announcement during its Cybercab event in Austin on September 3.
Tesla Vice President of AI Ashok Elluswamy told attendees he was happy to report the fleet had achieved one million miles of unsupervised Robotaxi operation as a testament to safety.
The new total marked a sharp increase from the 380,000 unsupervised miles Tesla disclosed during its second-quarter 2026 earnings update in late July.
In roughly six weeks, the company added about 620,000 miles. That acceleration followed Tesla’s decision to remove in-vehicle safety monitors from most of its operations outside the San Francisco Bay Area.

Credit: Tesla
Tesla first launched Robotaxi service in Austin in June 2025 with safety drivers present. It later began fully unsupervised rides and expanded into Dallas, Houston, Miami, Orlando, and Tampa. The San Francisco Bay Area remains the exception, where a safety monitor still rides in the vehicle under California permitting rules.
The company has not released a city-by-city breakdown of the one million unsupervised miles.
The milestone arrived as Tesla began offering public Cybercab rides in Austin. The purpose-built vehicle has no steering wheel or pedals and is designed only for autonomous ride-hailing. Production versions joined the existing fleet of modified Tesla vehicles already operating in the service.
Tesla’s unsupervised mileage is growing at a double-digit weekly rate according to earlier company comments, yet its fleet size remains modest compared with established competitors. Waymo has accumulated more than 200 million fully autonomous rider-only miles. Tesla has described its own unsupervised operations as having recorded zero notable incidents in the period leading up to the July update.
The one-million-mile figure reflects Tesla’s shift from supervised testing to broader driverless service in multiple states. It also highlights the company’s strategy of using both existing Model Y vehicles and the new Cybercab to scale its network.

Credit: Tesla
Whether the rapid recent growth continues will depend on further city expansions, regulatory approvals, and the performance of the purpose-built Cybercab in everyday paid rides. Tesla has not specified how many of the latest miles involved the new vehicle versus the rest of the fleet.
The announcement underscores Tesla’s progress toward a larger robotaxi network while illustrating the remaining gap in total autonomous experience relative to longer-operating rivals.
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.