News
SpaceX test-fires Falcon 9 for expendable Block 5 launch as bad weather threatens delays
SpaceX has fired up twice-flown Falcon 9 booster B1047 ahead of Block 5’s second expendable launch ever, but the company avoided its usual confirmation that a ‘quick look’ data analysis shows the vehicle as ready for launch.
Aside from the unusual phrasing of SpaceX’s static fire confirmation, stating instead that the company “is assessing data”, the weather forecast for the launch of AMOS-17 is looking about as dreary as it was during SpaceX’s most recent July 25th launch, CRS-18. CRS-18 was scrubbed once before the instantaneous launch window luckily coincided with an only partially metaphorical gap in the clouds. However, scheduled to lift off no earlier than 6:52 pm EDT (22:52 UTC), August 3rd, the AMOS-17 commsat launch features a comparatively luxurious ~90-minute window, giving SpaceX a much better shot at ‘threading the needle’.
Still, as indicated in the tweet above, the combination of a horrible weather forecast (70% chance of weather violation on Aug. 3, 60% on Aug. 4), uncertainty surrounding Falcon 9’s static fire test results, and the gravity of this particular launch all suggest that delays are likely.
With most things in rocketry, the adage, “Better late than never!” almost invariably holds true when dealing with late-stage launch vehicle processing, and SpaceX will be taking that to the extreme with this launch for reasons that will become clear. If SpaceX can avoid the growing probability of minor delays, generally an annoying non-issue more than anything else, customer Spacecom will certainly be appreciative, but the most important thing is ensuring the safe orbital delivery of AMOS-17.
Weighing roughly 6500 kg (14,300 lb) fully-fueled, AMOS-17 is a relatively large geostationary communications satellite built by Boeing and, practically speaking, is meant to replace Amos-6, an Israeli-built satellite that was destroyed in September 2016 during a catastrophic Falcon 9 failure. Spacecom effectively took the insurance funds it received from the loss of Amos-6, purchased AMOS-17 via Boeing, and then chose a contract option that gave the company a free Falcon 9 launch instead of taking a cash payout of $50M.
Be it financial necessity or a genuine decision to trust SpaceX that led Spacecom to manifest its replacement satellite on Falcon 9, a second failure and loss of payload (AMOS-17) during this launch would be a spectacular embarrassment and a major wound to SpaceX’s growing reputation as a reliable launch provider. If there is any launch in particular that SpaceX explicitly wants to avoid a failure on, it’s probably AMOS-17.
Perhaps to this end, SpaceX has actually chosen – presumably at the request or suggestion of Spacecom – to expend a Falcon 9 Block 5 booster in support of the AMOS-17 launch. Confirmed by SpaceX to be B1047.2, the company will preclude a landing attempt and instead sacrifice a booster that might otherwise fly a dozen more launches to give Spacecom a larger safety margin and help AMOS-17 start serving customers as quickly as possible. The sooner AMOS-17 can reach its final geostationary orbit (GEO), the sooner Spacecom can begin generating revenue from the satellite.
Finally, SpaceX fairing recovery vessel GO Ms. Tree (formerly Mr. Steven) has just departed Port Canaveral (c. August 1st) and is headed nearly 1000 km (600 mi) east into the Atlantic Ocean for what could be the ship’s second successful fairing catch ever. Stay tuned as SpaceX provides updates and we near AMOS-17’s tentative launch date.
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
