Connect with us

News

SpaceX Starship booster heads to launch pad for the fifth time

Published

on

For the fifth time in five months, SpaceX has transported its most advanced Starship booster prototype from the Starbase factory to the launch pad, setting the stage for another round of testing.

Super Heavy Booster 7 (B7) returned to the factory for the fourth time on August 12th after becoming the first prototype of any kind to perform a static fire engine test while installed on SpaceX’s orbital Starship launch mount. In the days prior, the booster completed two back-to-back static fire tests with one of the 20 Raptor engines installed on the rocket, both of which apparently gave SpaceX enough confidence to prepare for the next phase of testing.

That relatively cautious progress only came after SpaceX attempted to test all 33 of the prototype’s Raptors at once during its first engine test. Whether it was the fault of overzealous managers or executives or a genuine oversight is not clear, but the combined behavior of Super Heavy and the orbital launch pad was not properly characterized before testing began. As a result, the cloud of flammable gas the rocket released during its attempted 33-engine ‘spin-prime’ test found an ignition source and violently exploded on July 11th, causing damage throughout Booster 7’s aft engine section that required several weeks of repairs between July 15th and August 6th.

When the Super Heavy rolled to the pad for the fourth time on August 6th, it was missing all 13 center Raptors, leaving only the outer ring of 20 Raptor Boost engines partially installed for the tests that followed. Thankfully, things went much better on the second try and Booster 7 completed two spin-prime tests with a single Raptor engine, followed by two successful static fire tests on August 9th and 11th. The latter test was the longest Starbase static fire ever (by a factor of ~3) and lasted about 20 seconds, allowing SpaceX to test Booster 7’s autogenous pressurization. That system pressurizes Super Heavy’s tanks by turning small quantities of cryogenic liquid propellant into gas, ensuring that its tanks remain stable as they’re rapidly drained of thousands of tons of propellant.

On August 12th, Booster 7 returned to the factory, where workers installed the rocket’s 13 center engines for the second time. Booster 7 headed back to the orbital launch site (OLS) on August 23rd and the pad’s robotic launch tower used a pair of arms to lift the rocket off its transport stand and place it on the launch mount by the end of the day.

Advertisement

In addition to readying Booster 7 for its next phase of static fire testing, teams of SpaceX workers took advantage of the unplanned lull in testing to modify the orbital launch mount. It’s impossible to know what exactly was done without official confirmation, but it’s likely that SpaceX was attempting to quickly fix the shortcoming(s) that allowed the July 11th explosion to happen. Without a fix, it’s unlikely that SpaceX would want to proceed with plans to ignite large numbers of Raptor engines simultaneously – a series of tests that must be completed before Starship can safely attempt its first orbital launch.

Super Heavy Booster 7 appeared to narrowly avoid catastrophe on July 11th. (NASASpaceflight Starbase Live)
About a month later, Booster 7 and Ship 24 completed their first successful static fire tests on the same day. (NASASpaceflight – bocachicagal)

It’s unclear what exactly that fix entails, but it could involve a system to constantly flood the engine section with fire-stopping nitrogen gas or potentially take the shape of a system of vents that will connect to every Raptor engine and remove methane gas before it can turn into flammable clouds.

It’s possible that Booster 7 has returned to the launch pad solely for fit checks or some other basic proof-of-concept testing. It’s also possible that the returns signifies that SpaceX is confident in its quick launch mount fix and ready to restart static fire testing.

As Booster 7 prepares for that next phase of testing, SpaceX may also be ready to restart static fire testing with Starship S24, which paused shortly before Super Heavy returned to the factory. SpaceX appears to be modifying the suborbital launch mount and test stand Ship 24 is installed on, which could explain the lack of ship testing since August 11th. SpaceX has 12-hour test windows tentatively scheduled on August 24th and 25th, either of which could be used to test either or both prototypes.

If all goes to plan, Ship 24 and Booster 7 will eventually complete all the qualification testing SpaceX can throw at them and be ready to support Starship’s first orbital launch attempt sometime before the end of 2022.

Advertisement

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

Elon Musk

Elon Musk handed Grok something no other AI company can get their hands on

Elon Musk says SpaceX will feed engineering data into Grok’s next model, avoiding restricted material.

Published

on

By

Artistic concept rendering of SpaceX data being incorporated into a Grok AI model

Elon Musk said Tuesday that SpaceX will feed its internal engineering data into the next major training run for Grok, the AI model now folded into SpaceX following February’s merger. In a post on X, Musk wrote that SpaceX’s “massive corpus of world-class engineering data,” excluding anything restricted under U.S. arms export law, will be added during supplemental training of what he called the “2T run,” a reference to a roughly two trillion parameter model that would nearly double the parameters behind the latest Grok 4.5 that’s rolling out.

The excluded material that Musk is referring to would fall under the International Traffic in Arms Regulations (ITAR), which restricts export of technical data tied to defense and space hardware. That likely rules out propulsion specifics for Merlin and Raptor engines along with guidance and control details for SpaceX’s launch vehicles, but leaves manufacturing knowledge, materials science, and Starlink hardware design on the table.

The announcement extends a pattern that has been building since SpaceX’s Nasdaq debut in June, when the company went public with Grok and xAI’s Colossus supercomputer folded into the pitch to investors.

Days after that listing, SpaceX closed its $60 billion all stock acquisition of coding startup Cursor, giving xAI both enterprise software distribution and a stream of real world developer data to train on. Grok 4.5 launched July 8 running partly on that Cursor training data, with Musk describing it as roughly comparable to Anthropic’s Opus 4.7 but faster and cheaper to run.

Feeding SpaceX’s own engineering data into the next AI model follows the same logic Musk has applied across xAI’s sister companies. Tesla supplies real world driving data and manufacturing expertise, X supplies conversational data, and now SpaceX supplies aerospace engineering data built up since 2002.

Musk did not give a release date for the upcoming AI model, referred to elsewhere as Grok 4.6. He has said the two trillion parameter run is in its final training phase and expected to wrap this week.

Continue Reading

News

Tesla expands ridesharing service in California to new hotspot

Published

on

Credit: Tesla

Tesla has extended its Bay Area ride-hailing service to include pickups and drop-offs at San Francisco International Airport (SFO). The update, shared via the company’s official channels on July 21, allows users in the region to request rides directly to and from one of California’s busiest airports.

The expansion builds on Tesla’s secured limousine permit for SFO operations. Public records show the permit became effective March 20, 2026, and remains active through January 31, 2027. Tesla vehicles operating the service now display authorized limousine permits issued by the City and County of San Francisco.

Tesla’s ride-hailing program in California relies on Model Y vehicles equipped with Full Self-Driving (Supervised) technology. Human safety drivers remain present in compliance with state regulations, distinguishing the service from fully driverless operations.

The Bay Area geofence covers a broad area spanning north of San Francisco to south of San Jose, offering extensive connectivity across the region.

UPDATE: Elon Musk reveals why Tesla didn’t say ‘Robotaxi’ upon California launch

This SFO addition follows earlier progress at other Bay Area airports. Tesla previously expanded service to San Jose Mineta International Airport (SJC) in late 2025. The company had engaged with SFO, SJC, and Oakland International Airport officials as early as September 2025 to secure necessary approvals for passenger transport.

The service provides a new option for travelers seeking electric, app-based transportation integrated with Tesla’s ecosystem. Rides are booked through Tesla’s dedicated ride-hailing application, which handles matching, routing, and payments. Pricing follows standard ride-hailing models, with potential adjustments based on distance, time, and demand.

Tesla’s California ride-hailing program launched in July 2025 with an initial invite-only rollout in the Bay Area. It started alongside operations in Austin, Texas, marking the company’s second major U.S. market.

The Bay Area remains a primary focus in California, with service centered on high-demand corridors connecting residential, commercial, and now major transportation hubs. This latest airport integration represents a practical step in Tesla’s broader mobility ambitions within the state.

Continue Reading

News

Tesla reveals 2026 Summer Update with crazy fixes to Nav and more

Published

on

Credit: Tesla

Tesla has officially revealed its 2026 Summer Update, which comes with a variety of crazy new features, including Navigation fixes that owners have been wanting for months.

Tesla routinely releases a larger update with the Spring, Summer, Fall, and Winter updates, where it ships a variety of new features, bug fixes, and other additions to customer cars.

The 2026 Spring Update featured things like “Hey Grok” voice assistance, a redesigned self-driving app, Unreal Engine visual upgrades, and more.

Tesla’s Summer Release has about ten new features; we’ll show you each and detail them below:

New Grok Voice Commands

“Grok can now make phone calls, search and play music, adjust climate, open the glovebox, and answer questions about your Tesla.”

Self-Driving Stats in Mobile App

“View and share self-driving stats from the mobile app.”

Caraoke With Scoring

“Caraoke now scores your singing while in Park. High scores are saved to your Tesla profile.”

Automatic Navigation

“Automatic Navigation now adapts to your routine.

In addition to Home, Work, and upcoming calendar events, your vehicle can now suggest and route to places you visit regularly – like a school drop-off on the way to work, or the gym on the way home.”

Advertisement



Preferred Routes

“For a more personalized experience, navigation now prioritizes routes that you’ve taken before”

Set Arrival Energy from Mobile App

“Set your desired Arrival Energy from your phone.”

Send Custom Wraps from Mobile App

“Skip the USB drive and upload a custom wrap of your car from the mobile app. Instructions for creating a custom wrap here: https://github.com/teslamotors/custom-wraps.”

Rear Display Lock

“Kids can watch content on the rear screen, but only the front row can control it through the rear screen app.”

Other Improvements

  • Find Superchargers by name when searching for a destination
  • Add Apple Music songs to queue from search and artist page
  • Set your preferred zoom level for the Self-Driving visualization
  • Intro animations for new Model 3 and Y
Continue Reading