News
SpaceX fan spots sooty Falcon 9 Block 5 booster at Kennedy Space Center
On July 2nd, Twitter user Sideralmente (@astroperinaldo) spotted a sooty Falcon 9 Block 5 booster arriving at SpaceX’s Pad 39A hangar facilities, currently operating as a sort of defacto refurbishment hub.
Likely a prelude to a near-term launch, SpaceX has several missions scheduled over the next few months. More likely than not, all of them will fly on flight-proven Falcon 9 boosters, now so common that launching new boosters has started to feel exceedingly rare and unusual. July 2nd’s booster spotting is also a rare (albeit slightly less rare) treat, given the general lack of access (aside from a bus tour) members of the public have to Kennedy Space Center’s operational facilities and the total lack of access they have to Cape Canaveral Air Force Station, home of SpaceX’s most active launch pad (LC-40).
CRS-18
Up next for SpaceX is Cargo Dragon CRS-18, the spacecraft’s second International Space Station (ISS) resupply mission this year. At least over the last 2-3 years, SpaceX and NASA have been fairly consistent with Cargo Dragon launches in the winter, late-spring/early-summer, and late-fall (Q1, Q2/Q3, Q4) for an average of three launches annually. 2018/2019 is no different: CRS-16 launched in early-December 2018 and CRS-17 in early-May 2019, while CRS-18 is scheduled to launch NET 7:35 pm ET, July 21st and CRS-19 is targeted for early-December 2019.

Meanwhile, CRS-18 is also expected to be the first time a NASA mission launches on a flight-proven Falcon 9 Block 5 booster, potentially paving the way for NASA’s first launch on a twice-flown Block 5 booster with CRS-19 – hopefully later this year. Of course, that subsequent milestone will depend on a successful launch and landing during CRS-18. Falcon 9 booster B1056 – previously tasked with launching CRS-17 on May 4th, 2019 – is assigned to the mission and has been speedily refurbished for its next mission. Assuming the static fire goes well and there are no anomalies over the next 11 days, B1056 will launch twice in 78 days, a close second to B1048, B1052, and B1053 – all tied for first place at 74 days.

AMOS-17
Following CRS-18, SpaceX’s next launch is expected to occur soon after, launching Spacecom’s AMOS-17 communications satellite on a Falcon 9 (likely flight-proven) no earlier than early-August, although the tail-end of July is also a possibility. This mission will be extremely symbolic, owing to the fact that AMOS-17 is effectively an insurance-funded replacement for AMOS-6, destroyed on September 1st, 2016 when Falcon 9 suffered a catastrophic failure.
Thankfully, since that failure nearly three years ago, Falcon 9 has performed admirably, suffering no publicly-known failures or partial failures during its primary mission, although SpaceX has suffered two failed booster landing attempts over the same period.

It’s possible that the mystery booster spotted above is meant for AMOS-17, although that’s far from certain. Based on an image showing the core number, it is almost certainly B104X, while the second digit could easily be a 7 or a 9. If the booster in question is B1047, the odds are much better that it’s wrapping up refurbishment and waiting at 39A for CRS-18 to launch before heading to LC-40.
Starlink?
On the other hand, if the booster in question is B1049, it can be all but guaranteed that AMOS-17 will not launch on it, the reason being that – quite literally burned by its last experience with Falcon 9 – Spacecom probably doesn’t want to be the first SpaceX customer to launch on a thrice-flown booster. At the same time, SpaceX is probably exceptionally conscious of the need to ensure mission success and has no interest in adding risk to the AMOS-17 mission profile, no matter how minor.

B1049 launched for the third time in support of SpaceX’s first dedicated Starlink launch on May 23rd, known internally as Starlink v0.9. At this point in time, B1046.3 is believed to be assigned to Crew Dragon’s in-flight abort (IFA) test, expected no earlier than Q4 2019. B1048.3’s status is unknown since the rocket successfully completed its third launch in February 2019. With B1049’s newfound history as the first SpaceX booster to launch on a completely internal mission, it would make a lot of sense for SpaceX to reuse B1049 for the next Starlink mission.
Simultaneously, SpaceX could demonstrate the first launch of a thrice-flown Falcon 9 booster without pushing that risk onto customers, opening up B1048 and future thrice-flown boosters for near-term commercial missions. A step further, this would set SpaceX up perfectly to use internal Starlink missions as full-fidelity demonstrations of booster reuse milestones, going from the four launches to five, six, seven, and beyond.

Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
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.