News
SpaceX sets stage for Starship booster’s first 33-engine static fire
SpaceX has set the stage for a record-breaking Starship booster static fire after the rocket completed a complex fueling test and launch rehearsal earlier this week.
On January 25th, a tower the size of a skyscraper activated a pair of giant mechanical arms to disassemble the largest rocket ever built. The arms carefully grabbed Starship using hard points under its flaps and lifted the 50-meter-tall second stage and spacecraft off of Super Heavy Booster 7. Nicknamed Mechazilla, the robot lowered the hundred-ton (~220,000+ lbs) vehicle hundreds of feet onto a waiting stand and eventually let go. On January 26th, SpaceX transported Ship 24 back to its Starbase, Texas factory for finishing touches.
Booster 7 remained installed on Starbase’s donut-shaped orbital launch mount, which uses clamps and umbilicals to hold Starship in place and power, fuel, and pressurize Super Heavy. In theory, the next time Booster 7 leaves that launch mount, it will do so under its own power. But first, SpaceX must ensure that that unprecedented power can be controlled (and survived).
The update that's rolling out to the fleet makes full use of the front and rear steering travel to minimize turning circle. In this case a reduction of 1.6 feet just over the air— Wes (@wmorrill3) April 16, 2024
This, unfortunately, is far from the first iteration of this story. SpaceX has been seemingly close to the milestone at many points over the last year and a half. In September 2021, for example, CEO Elon Musk reported that Super Heavy Booster 4 would attempt the first static fire on Starbase’s orbital launch mount later that month. Eleven months later, Super Heavy Booster 7 gave the OLM its inaugural static fire test – albeit with just one of its 33 engines.
In the months following that static fire, Booster 7 completed another single-engine test, a two-engine test, a seven-engine test, a fourteen-engine test, and a long-duration eleven-engine test. All of that slow and steady testing has been fairly successful and caused no major damage to the rocket or pad. But five months after it began, SpaceX has never ignited more than 14 – 42% – of Super Heavy’s 33 Raptor engines at once. That must change before SpaceX can gain enough confidence in Starship for (and convince the FAA to license) an orbital launch attempt.
During Super Heavy B7’s 14-engine static fire, the booster could have produced up to 3220 tons (7.1 million pounds) of thrust. When it ignites all 33 available engines for the first time, its maximum thrust could leap to 7590 tons (16.7 million pounds), beating the next most powerful rocket in history – the Soviet N1 – by nearly 60%. In other words, SpaceX will be attempting something unprecedented in rocketry. Success is far from guaranteed and the worst possible failure mode could almost entirely destroy Starship’s only finished orbital launch site, explaining SpaceX’s unusual caution.
On January 23rd, Ship 24 and Booster 7 completed Starship’s first full wet dress rehearsal (a fueling and launch rehearsal test) on the first try – an extremely impressive achievement for any rocket, let alone the largest in history. With that combined test out of the way, the only unprecedented test standing between Starship and its first orbital launch attempt is a 33-engine Super Heavy static fire.
To reduce risk, Ship 24 was removed from Booster 7. Back at the factory, SpaceX needs to close a few gaps left in its heat shield, and will likely also conduct careful inspections to ensure that the Starship is ready for flight. Unburdened of Ship 24, Booster 7 may finally be on the cusp of the most challenging ground test in Starship and SpaceX history. SpaceX has scheduled 12-hour road closures that could be used for that purpose as early as January 30th, 31st, and February 1st.
Those road closures could be used for Ship 25 static fire testing instead of or in addition to Booster 7. The Super Heavy is also missing an important hydraulic power unit (HPU) that was removed before the wet dress rehearsal. It’s unclear if static fire testing can be conducted without that HPU (one of two), why it was removed, or how long replacing it will take, adding more uncertainty. Nonetheless, it still appears that SpaceX is no more than a few weeks away from Starship’s first 33-engine static fire attempt.
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
