Connect with us

News

SpaceX schedules second Starship static fire after first test ends prematurely

On January 6th, SpaceX fired up Starship SN9's three Raptor engines for the first time. (NASASpaceflight - bocachicagal)

Published

on

Update: SpaceX appears to have plans for a second triple-Raptor static fire for Starship SN9 after the rocket’s first test was cut short for unknown reasons.

Identical to previous road closure windows, SpaceX will have an opportunity to test Starship SN9 from 8 am to 5 pm CST (UTC-6) on Friday, January 8th, potentially paving the way for a high-altitude launch attempt early next week if the second static fire goes as planned. Stay tuned for updates!

In what is likely one of the last steps before SpaceX’s next high-altitude Starship launch attempt, the company appeared to successfully put Starship serial number 9 (SN9) through its first triple-Raptor static fire test.

Relatively late into a test window that opened at 8 am CST (UTC-6) but was later pushed to noon, SpaceX’s first Starship SN9 static fire attempt began in earnest around 3:15 pm CST. Signified by venting activity at the propellant farm tasked with preparing and loading liquid oxygen and methane on Starships, slight tweaks in the test flow were observed but the static fire occurred more or less when expected at 4:07 pm.

SN9 ignited all three of its Raptors in quick succession and shut the engines down over the course of 1.5-2 seconds – extremely short relative to all previous nominal Starhopper or Starship-mounted Raptor static fires. Long-time followers immediately noted that small discrepancy, speculating that it could either have been a post-ignition abort or intentionally shortened to avoid damaging the pad’s concrete surface (an incident that’s occurred several times during recent tests).

Not long before the short static fire, SpaceX extended the end of its January 6th test window (in the form of road closure notices) from 5 pm to 8 pm. Oddly, rather than the expected response of detanking Starship and reopening the road after a successful test, SpaceX essentially recycled SN9 and began a separate test around 6 pm. The road was never reopened and a SpaceX team never headed back to the pad between the tests, implying that the company may have run into a minor hardware or software bug earlier in the day.

It’s unclear what the actual goal of the second attempt was and it’s more or less impossible to know for sure with confirmation from CEO Elon Musk. It’s possible – if unlikely – that the first static fire went exactly as planned and the follow-up test was meant to be a simple data-gathering wet dress rehearsal (WDR). Either way, after a surprise downpour briefly engulfed Starship SN9 minutes prior, the second test appeared to abort about 30 minutes into propellant conditioning and loading, precluding both a complete WDR and/or static fire.

Starship SN9 is pictured preparing for its first static fire attempt on January 3rd. (NASASpaceflight – bocachicagal)

According to a test notice received on January 6th by NASASpaceflight contributer and photographer Mary (bocachicagal), SpaceX has another test window available on January 7th in the event that Wednesday’s testing was partially unsuccessful. In a rare case, SpaceX’s hand-distributed warning for residents preceded any additional planned road closures, the last of which lifted on January 6th.

On January 5th, SpaceX received a trio of Temporary Flight Restrictions (TFRs) from the FAA that will allow the company to restrict access to nearby airspace for high-altitude Starship launch attempts on January 8th, 9th, and 10th. Lacking an unequivocally successful static fire, it’s highly unlikely – but not impossible – that Starship will be ready for a launch attempt during any of those three windows. Still, it’s safe to say that SN9 is probably less than a week away from its first flight – expected to be a carbon copy of SN8’s 12.5 km (7.8 mi) launch and landing attempt – if SpaceX can complete a full-duration static fire in the next day or two.

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

Investor's Corner

Tesla Robotaxi gets a massive upgrade in Nevada

Nevada regulators just approved a massive expansion of Tesla’s robotaxi fleet across the entire county.

Published

on

By

Concept art of a Tesla Cybercab in Las Vegas Strip as rendered via Grok

Tesla’s robotaxi footprint in Nevada just grew by roughly 500 times in a single regulatory vote.

The Nevada Transportation Authority approved Tesla’s full Autonomous Vehicle Network Company permit on Thursday, clearing the way for the company to deploy up to 5,000 driverless vehicles across Clark County over the next 12 months. The decision came during a four hour general session meeting that Tesla investor Sawyer Merritt watched live and reported on X, noting the vote replaces the interim order that had limited Tesla to just 10 robotaxis on a narrow stretch of the Las Vegas Strip.

That earlier cap, covered here after it surfaced on August 13, came with restrictions that looked stricter than what Tesla runs in Austin: a 45 mph speed ceiling, no airport pickups, and a geofence confined to the Strip corridor. The new approval extends Tesla’s operating authority to all of Clark County, with room to request an even wider geofence across the state.

Tesla representatives at the meeting said they have no intention of putting 5,000 cars on the road right away. Commercial rides are expected to start within 30 days, pending vehicle inspections, insurance filings, and fare approval, the standard steps every robotaxi operator in Nevada has had to clear.

Tesla’s own Robotaxi account replied to the news with a short line, The golden future is upon us.

The timing lines up with Tesla’s broader robotaxi push this month. The company is preparing to open Cybercab rides to the public in Austin as soon as this month, and it opened a sweepstakes for riders to win a seat at the launch event. Tesla filed its original application for a 5,000 vehicle Nevada fleet back in June, a request regulators trimmed to 10 vehicles when they issued the interim order in July. Thursday’s vote effectively grants the number Tesla asked for from the start.

Zoox, the Amazon owned robotaxi operator, has run in Nevada since 2025 and was capped at 100 vehicles before Thursday’s decision. Tesla’s new ceiling puts it well ahead of that comparison on paper, though the company has said its actual fleet size will depend on how quickly FSD v15 rolls out, the software update executives have called the gateway to scaling unsupervised robotaxi operations nationwide.

Continue Reading

News

Tesla admits to slow Model Y Robotaxi integration, but for a good reason

Published

on

Credit: Tesla

Tesla welcomed JPMorgan analysts to one of its factories earlier this month, with the Wall Street firm highlighting its findings in a new note to investors. One of the more pertinent pieces of information is that Tesla admitted to slowly integrating Model Y vehicles into its Robotaxi fleet, but it has a good reason.

JPMorgan analysts recently toured Tesla’s Fremont Factory and met with the company’s investor relations team, emerging with a clearer picture of the automaker’s Robotaxi strategy. According to the bank’s note, Tesla is intentionally limiting the addition of Model Y vehicles to its existing Robotaxi fleet.

The firm’s analysts said:

“Tesla indicated it is intentionally holding back on adding Model Y units to the robotaxi fleet, expressing confidence in its ability to scale Cybercab in the near-term. On FSD V15, Tesla views this release as a step-change in performance, comparable to the leap from V13 to V14. The V15 upgrade encompasses seven core technologies, with ~40% of those currently being tested in the robotaxi fleet, where initial feedback has been encouraging.”

Far from signaling delays or doubts about autonomy, the move reflects strong management confidence in the near-term scalability of the purpose-built Cybercab.

Tesla has operated its Robotaxi service primarily with modified Model Ys since launching in Austin and expanding to other markets. Yet the company is now deliberately holding back further Model Y conversions. The rationale is straightforward: leadership believes the Cybercab, a two-seat, steering-wheel- and pedal-free vehicle optimized for high utilization, can ramp production and deployment more efficiently in the coming months.

This dedicated form factor promises better unit economics for the majority of rides, which typically involve one or two passengers, while freeing consumer Model Y inventory for retail sales.

Supporting this pivot is Full Self-Driving (FSD) software version 15, which Tesla describes as a genuine step-change in performance, comparable to the leap from V13 to V14. The update incorporates seven core technologies; roughly 40 percent are already undergoing real-world testing in the current Robotaxi fleet, with early feedback described as encouraging.

Tesla is carefully managing software development to minimize regressions in core driving functions as new capabilities are added. Management positions V15 as the primary gateway to scaling unsupervised FSD. Importantly, the existing AI and Hardware 4 stack is already capable of running V15 and supporting unsupervised operation.

Cybercab itself is only the first vehicle on the platform. Tesla reiterated that additional form factors will follow, pointing to concepts such as the earlier “Robovan” demonstration as examples of how the architecture can evolve.

Tesla’s mysterious Robovan makes a sneak peek with Optimus in Terafab video

Parallel progress continues on the Optimus humanoid robot, which remains on track for start of production in the coming months, with commercial sales possible as early as the second half of 2027. Generation 3 details will be revealed closer to production to preserve competitive advantages, while Generation 4 scope will draw on real-world Gen 3 experience.

JPMorgan left the meeting with a deeper appreciation for Tesla’s manufacturing automation and maintained its $475 price target. The decision to slow Model Y Robotaxi integration is therefore not a setback but a calculated prioritization of a more efficient, purpose-built solution that management believes is ready to scale.

Continue Reading

Elon Musk

Elon Musk gives a timeline for SpaceX’s first Starship catch attempt

Published

on

SpaceX Starship V3 from Starbase, Texas on April 14, 2026

SpaceX CEO Elon Musk announced today that the company will likely attempt to catch the Starship upper stage with its launch tower arms “in a few months.”

In a post on X, Musk wrote, “Looks like we will probably catch the ship with the tower in a few months. If there had been a tower out to sea where we practiced landing the ship, it would have been caught.” He added that the first reflight of a Starship vehicle is expected by the end of 2026 or early 2027, describing it as “a fork in the road of history for consciousness reaching the stars.”

Musk’s prediction comes amid ongoing progress toward full reusability of the Starship system, a two-stage rocket designed for rapid turnaround and dramatically lower launch costs. Catching the upper stage, known simply as “ship,” with the Mechazilla tower’s mechanical arms would mark a major milestone. It would allow both stages to return directly to the launch site for quick refurbishment and reuse, eliminating the need for ocean recovery.

Musk has previously signaled plans for a ship catch. In July, shortly after SpaceX’s wildly successful Starship 13 mission, he stated that the company would attempt to catch the ship with the tower on the next flight unless problems emerged in the mission data review. Earlier comments also outline conditions such as successful soft ocean landings before attempting a land recovery to minimize risk.

SpaceX has solved Starship’s biggest challenge, Elon Musk says

The latest update from Musk adjusts this timeline to a few months, reflecting the iterative nature of the test campaign.

SpaceX has already demonstrated the tower catch technique successfully with the Super Heavy booster on a couple of occasions. The first successful booster catch occurred during Flight 5 in October 2024, when the massive first stage returned to the Starbase pad in Texas and was plucked from the air by the tower arms.

Additional catches followed on later flights, including Flight 7, proving the concept for the booster and building confidence in the system as a whole.

Achieving a similar catch for the upper stage would represent a significant step forward. The ship returns from much higher speeds and greater heat loads after orbital or near-orbital flight. Success would advance SpaceX’s goal of full and rapid reusability, potentially reducing the cost of access to orbit by a factor of 100 or more and supporting ambitions for frequent satellite deployments, lunar missions, and eventual Mars flights.

Musk has long emphasized that true reusability, refueling rather than discarding hardware, is essential for making humanity a multi-planetary species.

As SpaceX continues refining Starship through successive test flights, the coming months will test whether the ambitious catch timeline can be met. The combination of prior booster successes and improving ship landing precision suggests the company is steadily closing in on this historic capability.

Continue Reading