News
SpaceX static fires Falcon 9 with satellites on board for the first time in years
SpaceX has successfully completed a Falcon 9 static fire ahead of Starlink’s first dedicated launch, breaking a practice that dates back to Falcon 9’s last catastrophic failure to date.
That failure occurred in September 2016 around nine minutes before a planned Falcon 9 static fire test, completely destroying the rocket and the Amos-6 communications satellite payload and severely damaging Launch Complex 40 (LC-40). Since that fateful failure, all 42 subsequent Falcon 9 and Falcon Heavy satellite launches have been preceded by static fire tests without a payload fairing attached. This process typically adds 24-48 hours of work to launch operations, an admittedly tiny price to pay to reduce the chances of a rocket failure completely destroying valuable payloads. With Starlink v0.9, SpaceX is making different choices.
When supercool liquid oxygen ruptured a composite overwrapped pressure vessel (COPV) in Falcon 9’s upper stage, the resultant explosion and fire destroyed Falcon 9. Perhaps more importantly, the ~$200M Amos-6 satellite installed atop the rocket effectively ceased to exist, a loss that posed a serious threat to the livelihood of its owner, Spacecom. Posed with a question of whether saving a day or two of schedule was worth the potential destruction of customer payloads, both customers, SpaceX, and their insurers obviously concluded that static fires should be done without payloads aboard the rocket.
The only exceptions since Amos-6 are the launch debuts of Falcon Heavy – with a payload that was effectively disposable and SpaceX-built – and Crew Dragon DM-1, in which Falcon 9’s integration with Dragon’s launch abort system had to be tested as part of the static fire. Every other SpaceX rocket launch since September 2016 has excluded payloads during each routine pre-flight static fire.
SpaceX’s Spacecraft Emporium
Why the change of pace on this launch, then? The answer is simple: for the first time ever, SpaceX is both the sole payload/satellite stakeholder and launch provider, meaning that nearly all of the mission’s risk – and the consequences of failure – rest solely on SpaceX’s shoulders. In other words, SpaceX built and owns the Falcon 9 assigned to the mission, the 60 Starlink test satellites that make up its payload, and the launch complex supporting the mission.
Even then, if Falcon 9 were to fail during an internal SpaceX mission, customer launches could be seriously delayed by both the subsequent failure investigation failure and any potential damage to the launch complex. In short, although an internal mission does offer SpaceX some unique freedoms, it is still in the company’s best interest to treat the launch like any other, even if some customer-oriented corners are likely begging to be cut. Additionally, the loss of SpaceX’s first dedicated payload of 60 Starlink satellites could be a significant setback for the constellation, although it may be less significant than most would assume.
This is not to say that SpaceX won’t take advantage of some of the newfound freedom permitted by Starlink launches. In fact, CEO Elon Musk has stated that one of SpaceX’s 2019 Starlink missions will become the first to reuse a Falcon fairing. Additionally, SpaceX is free to do things that customers might be opposed to but that the company’s own engineers believe to be low-risk. Notably, Starlink missions will be an almost perfect opportunity for SpaceX to flight-prove reusability milestones without having to ask customers to tread outside of their comfort zones.
The sheer scale of SpaceX proposed Starlink constellation – two phases of ~4400 and ~12,000 satellites – means that the company will need all the latent launch capacity it can get over the next 5-10 years, at least until Starship/Super Heavy is able to support internal missions. Extraordinary packing density will help to minimize the number of launches needed, but the fact remains that even an absurd 120 satellites per launch (double Starlink v0.9’s 60) would still require an average of 12 launches per year to finish Starlink before 2030.
In the meantime, thoughts of a dozen or more annual Starlink launches are somewhat premature. SpaceX’s first dedicated Starlink launch (deemed Starlink v0.9) is scheduled to lift off no earlier than 10:30 pm EDT (02:30 UTC), May 15th, and is being treated as an advanced but still intermediary step between the Tintin prototypes and a finalized spacecraft design. Still, in an unprecedented step, SpaceX has built sixty Starlink satellites for the development-focused mission, in stark contrast to the six satellites (still a respectable achievement) competitor OneWeb launched in February 2019 as part of its own flight-test program.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
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.
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 crosses major Unsupervised Self-Driving milestone
Tesla Robotaxi will be a 24/7 service: here’s when
