Connect with us

News

SpaceX Starship wraps up nosecone ‘cryo proof’ and first of several Raptor static fires

While pretty, Starship SN8's firework-like light show is unusual and unlikely to be a good sign. (NASASpaceflight - bocachicagal)

Published

on

SpaceX has successfully ‘cryoproofed’ the first fully-assembled Starship prototype’s nose-based propellant tank and used that same tank to fire up a Raptor engine, crossing off one of the last major tests before the rocket’s 15-kilometer (~9.5 mile) launch debut.

On November 4th, after a few false-starts, Starship Serial Number 8 (SN8) kicked off its first round of testing after becoming the first prototype to have a nose section permanently installed. On that Wednesday evening, SpaceX most likely put the rocket through a partial cryogenic proof test explicitly focused on SN8’s new nosecone and a small secondary propellant tank situated in its tip. Designed to act as a secondary reservoir for the relatively small amount of propellant Starships need to land, SN8’s two header tanks were likely loaded with cryogenic liquid nitrogen – a safe, nonreactive stand-in for liquid oxygen and methane.

Having proven that Starship SN8’s newly-installed liquid oxygen header tank and associated plumbing is capable of loading, managing, and offloading dozens of tons of cryogenic fluid while navigating a 40-meter-tall (~130 ft) vertical pipe, SpaceX was ready to move onto the next step: a wet dress rehearsal (WDR) and Raptor static fire.

While SpaceX has technically completed eight successful Raptor static fires on four separate prototypes, including the first three-Raptor static fire ever attempted with Starship SN8, the company has never attempted a static fire while solely drawing propellant from header (landing) tanks. All but essential for Starships to be able to reliably reignite their Raptor engines in flight and keep cryogenic landing propellant liquid for hours, days, weeks, and even months, much smaller header tanks make it easier to keep propellant highly pressurized and in the right place to supply Raptors.

After several days of test windows come and gone and an aborted attempt on November 9th, Starship SN8 finally ignited one of its three Raptor engines, feeding the engine with liquid methane and oxygen stored in two separate header tanks. Oddly, a second or two after startup and ignition, Raptor’s usual exhaust plume was joined by a burst of shiny firework-like debris. A relatively normal five seconds later, the Raptor cut off, though the engine appeared to remain partially on fire for another ten or so seconds – also somewhat unusual.

Ultimately, the observed anomaly could be as simple as debris accidentally left in the vicinity of Raptor’s plume or, while less likely, concrete erosion. There’s also a chance that it was pieces of Raptor’s complex turbopumps or preburners, although it’s also unlikely that the engine would have continued running (as it did) if it had lost that much internal hardware.

(Update: Thankfully, NASASpaceflight.com reporter Michael Baylor says that the cloud of debris observed on November 10th “is not a [Raptor performance] concern,” making pad debris the likely source.)

SpaceX has canceled another static fire window on November 11th, leaving the next opportunity for a second (of three) expected static fire between 9am and 9pm CST (UTC-5) on Thursday, November 13th.

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

News

Tesla Robotaxi ride-hailing without a Safety Monitor proves to be difficult

Published

on

Credit: Grok Imagine

Tesla Robotaxi ride-hailing without a Safety Monitor is proving to be a difficult task, according to some riders who made the journey to Austin to attempt to ride in one of its vehicles that has zero supervision.

Last week, Tesla officially removed Safety Monitors from some — not all — of its Robotaxi vehicles in Austin, Texas, answering skeptics who said the vehicles still needed supervision to operate safely and efficiently.

BREAKING: Tesla launches public Robotaxi rides in Austin with no Safety Monitor

Tesla aimed to remove Safety Monitors before the end of 2025, and it did, but only to company employees. It made the move last week to open the rides to the public, just a couple of weeks late to its original goal, but the accomplishment was impressive, nonetheless.

However, the small number of Robotaxis that are operating without Safety Monitors has proven difficult to hail for a ride. David Moss, who has gained notoriety recently as the person who has traveled over 10,000 miles in his Tesla on Full Self-Driving v14 without any interventions, made it to Austin last week.

He has tried to get a ride in a Safety Monitor-less Robotaxi for the better part of four days, and after 38 attempts, he still has yet to grab one:

Tesla said last week that it was rolling out a controlled test of the Safety Monitor-less Robotaxis. Ashok Elluswamy, who heads the AI program at Tesla, confirmed that the company was “starting with a few unsupervised vehicles mixed in with the broader Robotaxi fleet with Safety Monitors,” and that “the ratio will increase over time.”

This is a good strategy that prioritizes safety and keeps the company’s controlled rollout at the forefront of the Robotaxi rollout.

However, it will be interesting to see how quickly the company can scale these completely monitor-less rides. It has proven to be extremely difficult to get one, but that is understandable considering only a handful of the cars in the entire Austin fleet are operating with no supervision within the vehicle.

Continue Reading

News

Tesla gives its biggest hint that Full Self-Driving in Europe is imminent

Published

on

Credit: BLKMDL3 | X

Tesla has given its biggest hint that Full Self-Driving in Europe is imminent, as a new feature seems to show that the company is preparing for frequent border crossings.

Tesla owner and influencer BLKMDL3, also known as Zack, recently took his Tesla to the border of California and Mexico at Tijuana, and at the international crossing, Full Self-Driving showed an interesting message: “Upcoming country border — FSD (Supervised) will become unavailable.”

Due to regulatory approvals, once a Tesla operating on Full Self-Driving enters a new country, it is required to comply with the laws and regulations that are applicable to that territory. Even if legal, it seems Tesla will shut off FSD temporarily, confirming it is in a location where operation is approved.

This is something that will be extremely important in Europe, as crossing borders there is like crossing states in the U.S.; it’s pretty frequent compared to life in America, Canada, and Mexico.

Tesla has been working to get FSD approved in Europe for several years, and it has been getting close to being able to offer it to owners on the continent. However, it is still working through a lot of the red tape that is necessary for European regulators to approve use of the system on their continent.

This feature seems to be one that would be extremely useful in Europe, considering the fact that crossing borders into other countries is much more frequent than here in the U.S., and would cater to an area where approvals would differ.

Tesla has been testing FSD in Spain, France, England, and other European countries, and plans to continue expanding this effort. European owners have been fighting for a very long time to utilize the functionality, but the red tape has been the biggest bottleneck in the process.

Tesla Europe builds momentum with expanding FSD demos and regional launches

Tesla operates Full Self-Driving in the United States, China, Canada, Mexico, Puerto Rico, Australia, New Zealand, and South Korea.

Continue Reading

Elon Musk

SpaceX Starship V3 gets launch date update from Elon Musk

The first flight of Starship Version 3 and its new Raptor V3 engines could happen as early as March.

Published

on

Credit: SpaceX/X

Elon Musk has announced that SpaceX’s next Starship launch, Flight 12, is expected in about six weeks. This suggests that the first flight of Starship Version 3 and its new Raptor V3 engines could happen as early as March.

In a post on X, Elon Musk stated that the next Starship launch is in six weeks. He accompanied his announcement with a photo that seemed to have been taken when Starship’s upper stage was just about to separate from the Super Heavy Booster. Musk did not state whether SpaceX will attempt to catch the Super Heavy Booster during the upcoming flight.

The upcoming flight will mark the debut of Starship V3. The upgraded design includes the new Raptor V3 engine, which is expected to have nearly twice the thrust of the original Raptor 1, at a fraction of the cost and with significantly reduced weight. The Starship V3 platform is also expected to be optimized for manufacturability. 

The Starship V3 Flight 12 launch timeline comes as SpaceX pursues an aggressive development cadence for the fully reusable launch system. Previous iterations of Starship have racked up a mixed but notable string of test flights, including multiple integrated flight tests in 2025.

Interestingly enough, SpaceX has teased an aggressive timeframe for Starship V3’s first flight. Way back in late November, SpaceX noted on X that it will be aiming to launch Starship V3’s maiden flight in the first quarter of 2026. This was despite setbacks like a structural anomaly on the first V3 booster during ground testing.

“Starship’s twelfth flight test remains targeted for the first quarter of 2026,” the company wrote in its post on X. 

Continue Reading