News
SpaceX Falcon Heavy rocket to launch record-breaking communications satellite
A report on the latest in a long line of SpaceX launches significantly delayed by customer payload readiness has been updated to confirm that the satellite in question will launch on Falcon Heavy, not Falcon 9.
Hughes revealed that it had selected SpaceX to launch its Maxar-built Jupiter-3 geostationary communications satellite during an industry conference on March 21st, 2022. At the time, Hughes stated that the satellite was on track to launch in the fourth quarter of 2022, a refinement but also a delay from earlier plans to launch sometime in H2 2022. Just six weeks later, manufacturer Maxar reported that the completion of Jupiter 3 – like many other Maxar spacecraft – had been delayed, pushing its launch to no earlier than (NET) “early 2023.”
At the same time, Maxar revealed that Jupiter 3 – also known as Echostar 24 – was expected to weigh around 9.2 metric tons (~20,300 lb) at liftoff when that launch finally happens. That figure immediately raised some questions about which SpaceX rocket Hughes or Maxar had chosen to launch the immense satellite.
Earlier on, regulatory documents revealed that Jupiter 3 would have a dry weight of 5817 kilograms (~12,825 lb). In July 2018, SpaceX broke the record for heaviest commercial geostationary satellite launch when a Falcon 9 rocket successfully delivered Telesat’s 7076-kilogram (15,600 lb) Telstar 19V to geostationary transfer orbit (GTO). To account for the satellite’s weight and still allow for Falcon 9 booster recovery, SpaceX launched Telstar 19V to a transfer orbit with its apogee (high point) well below geostationary orbit, meaning that the satellite had to do more of the work of orbit-raising. In other words, it wasn’t inconceivable that Jupiter 3 would also be launched to a low (subsynchronous) GTO on a recoverable Falcon 9.
However, in hindsight, Jupiter 3’s 5.8-ton dry mass should have already made it clear that that was unlikely. Telstar 19V, for example, had a reported dry mass of just over 3 tons (~6700 lb), meaning that more than half its wet mass was fuel for orbit-raising and maneuvers. In more normal cases, large geostationary satellites tend to launch with an extra 50-80% of their dry mass in fuel, not ~130%. Even at the low end of large geostationary satellites, Jupiter 3 was likely to have a launch mass of well over 8 tons.
Small bit of breaking news at this session: The @HughesConnects Jupiter 3 satellite will be launched on a @SpaceX rocket. #SATShow— Seth Miller (@WandrMe) March 21, 2022
At 9.2 tons, Jupiter 3 will leapfrog the world record for the largest commercial geostationary satellite ever launched by 30%. Barring the possibility of secret military spacecraft, it will likely be the heaviest spacecraft of any kind to reach geostationary orbit 35,785 km (22,236 miles) above Earth’s surface. More importantly, Jupiter 3 may also have the heaviest dry mass of any spacecraft to reach GEO, meaning that the actual hardware it will use to fill its role as a communications hub will also be exceptionally large and powerful. Jupiter 3 will deliver a maximum bandwidth of 500 gigabits per second.
With its exceptional heft, a recoverable Falcon 9 launch may have only been able to loft Jupiter 3 around half the way to GTO from low Earth orbit (LEO). It was little surprise, then, to learn that Hughes and Maxar had actually selected SpaceX’s far more capable Falcon Heavy rocket to launch the satellite. Even with full recovery of all three Falcon Heavy first-stage boosters, there’s a good chance that the rocket would be able to launch Jupiter 3 most of or all the way to a nominal geostationary transfer orbit. If the center core is expended and the side boosters land at sea, Falcon Heavy would likely be able to launch Jupiter 3 to a highly supersynchronous GTO, meaning that the spacecraft’s apogee would end up well above GEO. For example, on Falcon Heavy’s Block 5 launch debut, the rocket sent the ~6.5-ton (~14,250 lb) Arabsat 6A communications satellite to a GTO with an apogee of almost 90,000 kilometers (~56,000 mi), shaving about 20% off of the satellite’s orbit-raising workload.
Falcon Heavy’s Jupiter 3 mission won’t beat the record for total payload to GTO in a single launch, held by Arianespace’s Ariane 5 rocket after a 2021 mission to GTO launched two communications satellites weighing 10.27t, but it will be just one ton shy.
Jupiter 3 is the 10th mission firmly scheduled to launch on SpaceX’s Falcon Heavy rocket between now and 2025.
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
