Connect with us

News

SpaceX Starship go for nosecone installation after historic static fire

Starship SN8's nosecone was recently stacked and welded atop a barrel section in the last major step before installation on the rocket itself. (NASASpaceflight - bocachicagal)

Published

on

SpaceX CEO Elon Musk has confirmed that Starship and Raptor’s first triple-engine static fire was a success, opening the door for nosecone installation.

Around 3:13 am CDT, October 20th, Starship serial number 8 (SN8) successfully fired up three Raptor engines less than two hours after completing the first successful three-engine preburner test. With zero direct human intervention, SpaceX remotely detanked the rocket’s cryogenic liquid methane and oxygen propellant – the remnants now too warm to be used again in a controlled manner. In an hour or less, SpaceX engineers combed through the data produced and concluded that all three Raptor engines were healthy after their partial ignition test.

Effectively reset to a stable state, SpaceX once again proceeded to load Starship SN8’s propellant tanks with a small amount of supercooled LOx and LCH4, almost exactly mirroring the preburner test. Around 50 minutes after the recycle commenced and 25 minutes after propellant loading kicked off, Starship SN8 ignited three Raptors simultaneously – a major milestone for any rocket engine. Static fire now completed, Starship SN8 has been cleared to become the first operational prototype to reach its full 50m (~165 ft) height.

Shortly before Musk confirmed SN8’s static fire success, SpaceX canceled a preexisting October 20th static fire window and scheduled several new road closures on Wednesday, October 21st. Unlike the company’s recent static fire closures, all but one of which ran from 9pm to 6am, SpaceX’s new Wednesday closures are scheduled from 7am to noon and 3pm to 5pm local (CDT).

While a minor data point, in context with Starship SN8’s static fire success, the closures alone made it clear that SpaceX planned to begin installing Starship SN8’s nosecone on October 21st. Musk confirmed that assumption a few hours after those road closures were published.

Advertisement
-->

It’s not entirely clear but most observers are assuming that Wednesday’s 7am-12pm window is needed to transport a large, new crane the ~2 miles between SpaceX’s Boca Chica factory and launch facilities. Starship SN8’s stacked nose section would then likely be installed on the same self-propelled mobile transporters (SPMT) and rolled to the launch pad from 3pm to 5pm, after which the nose would be lifted and stacked atop Starship SN8.

A visual comparison of Starship Mk1’s (left) and Starship SN8’s nose sections make clear some of the refinements SpaceX has made in ~12 months. (NASASpaceflight – Nomadd)
The aforementioned new crane was loaded onto an SPMT shortly after SN8’s static fire. (NASASpaceflight – bocachicagal)

SpaceX has only fully stacked a Starship prototype once before when Mk1’s nose section was temporarily mated to its tank section to be the centerpiece of CEO Elon Musk’s October 2019 Starship event. It’s unclear why SpaceX wouldn’t simply use one of the mobile cranes its rented for Starship tank section operations (and stacking Mk1) in the past, so it remains to be seen what Wednesday’s road closures will actually be used for.

SpaceX has only stacked a Starship prototype to its full height once before. (Teslarati – Eric Ralph)

SpaceX’s road closure plans end with a wildcard, however. Once installed, the plan is to perform a second triple-Raptor static fire while only drawing propellant from SN8’s header tanks – small internal tanks designed to hold landing propellant, one of which is situated at the tip of Starship’s nosecone. On October 21st and 22nd, SpaceX still has two 9pm-6am closures scheduled for “SN8 static fire” testing. Filed early on October 20th, before SN8’s successful static fire, the most likely explanation is a simple clerical error or miscommunication, with Cameron County or SpaceX failing to properly communicate that those subsequent static fire test windows are no longer needed.

If retaining the static fire closures was intentional, it would mean that SpaceX – likely at Musk’s urging – intends to install Starship SN8’s nosecone in a matter of hours. It’s almost inconceivable that Starship SN8’s nosecone – outfitted with multiple gas thrusters, forward flaps powered by Tesla motors, a liquid oxygen header tank, vents, and plenty of plumbing – can be installed and made ready for testing in less than 12 hours. Barring a surprise method of mating SN8’s nose and tank sections, the nosecone will have to be welded to the rest of SN8 and the weld inspected – typically a multi-day process.

Starship SN8 stands tall after completing the first triple-Raptor static fire test. (NASASpaceflight – Nomadd)

Regardless, given how quickly SpaceX moves and how dead-set CEO Elon Musk is at pushing limits and breaking barriers, it seems reasonable to assume that Starship SN8 may be fully integrated and ready for a second static fire test just a handful of days from now. Once completed, SN8 will be ready to attempt Starship’s first high-altitude flight test, launching to ~15 km (~9.3 mi) to attempt an untested skydiver-style descent and landing.

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

SpaceX Starship Version 3 booster crumples in early testing

Photos of the incident’s aftermath suggest that Booster 18 will likely be retired.

Published

on

Credit: SpaceX/X

SpaceX’s new Starship first-stage booster, Booster 18, suffered major damage early Friday during its first round of testing in Starbase, Texas, just one day after rolling out of the factory. 

Based on videos of the incident, the lower section of the rocket booster appeared to crumple during a pressurization test. Photos of the incident’s aftermath suggest that Booster 18 will likely be retired. 

Booster test failure

SpaceX began structural and propellant-system verification tests on Booster 18 Thursday night at the Massey’s Test Site, only a few miles from Starbase’s production facilities, as noted in an Ars Technica report. At 4:04 a.m. CT on Friday, a livestream from LabPadre Space captured the booster’s lower half experiencing a sudden destructive event around its liquid oxygen tank section. Post-incident images, shared on X by @StarshipGazer, showed notable deformation in the booster’s lower structure.

Neither SpaceX nor Elon Musk had commented as of Friday morning, but the vehicle’s condition suggests it is likely a complete loss. This is quite unfortunate, as Booster 18 is already part of the Starship V3 program, which includes design fixes and upgrades intended to improve reliability. While SpaceX maintains a rather rapid Starship production line in Starbase, Booster 18 was generally expected to validate the improvements implemented in the V3 program.

Tight deadlines

SpaceX needs Starship boosters and upper stages to begin demonstrating rapid reuse, tower catches, and early operational Starlink missions over the next two years. More critically, NASA’s Artemis program depends on an on-orbit refueling test in the second half of 2026, a requirement for the vehicle’s expected crewed lunar landing around 2028.

Advertisement
-->

While SpaceX is known for diagnosing failures quickly and returning to testing at unmatched speed, losing the newest-generation booster at the very start of its campaign highlights the immense challenge involved in scaling Starship into a reliable, high-cadence launch system. SpaceX, however, is known for getting things done quickly, so it would not be a surprise if the company manages to figure out what happened to Booster 18 in the near future.

Continue Reading

News

Tesla FSD (Supervised) is about to go on “widespread” release

In a comment last October, Elon Musk stated that FSD V14.2 is “for widespread use.”

Published

on

Tesla has begun rolling out Full Self-Driving (Supervised) V14.2, and with this, the wide release of the system could very well begin. 

The update introduces a new high-resolution vision encoder, expanded emergency-vehicle handling, smarter routing, new parking options, and more refined driving behavior, among other improvements.

FSD V14.2 improvements

FSD (Supervised) V14.2’s release notes highlight a fully upgraded neural-network vision encoder capable of reading higher-resolution features, giving the system improved awareness of emergency vehicles, road obstacles, and even human gestures. Tesla also expanded its emergency-vehicle protocols, adding controlled pull-overs and yielding behavior for police cars, fire trucks, and ambulances, among others.

A deeper integration of navigation and routing into the vision network now allows the system to respond to blocked roads or detours in real time. The update also enhances decision-making in several complex scenarios, including unprotected turns, lane changes, vehicle cut-ins, and interactions with school buses. All in all, these improvements should help FSD (Supervised) V14.2 perform in a very smooth and comfortable manner.

Elon Musk’s predicted wide release

The significance of V14.2 grows when paired with Elon Musk’s comments from October. While responding to FSD tester AI DRIVR, who praised V14.1.2 for fixing “95% of indecisive lane changes and braking” and who noted that it was time for FSD to go on wide release, Musk stated that “14.2 for widespread use.”

FSD V14 has so far received a substantial amount of positive reviews from Tesla owners, many of whom have stated that the system now drives better than some human drivers as it is confident, cautious, and considerate at the same time. With V14.2 now rolling out, it remains to be seen if the update also makes it to the company’s wide FSD fleet, which is still populated by a large number of HW3 vehicles. 

Advertisement
-->
Continue Reading

News

Tesla FSD V14.2 starts rolling out to initial batch of vehicles

It would likely only be a matter of time before FSD V14.2 videos are posted and shared on social media.

Published

on

Credit: Grok Imagine

Tesla has begun pushing Full Self-Driving (Supervised) v14.2 to its initial batch of vehicles. The update was initially observed by Tesla owners and veteran FSD users on social media platform X on Friday.

So far, reports of the update have been shared by Model Y owners in California whose vehicles are equipped with the company’s AI4 hardware, though it would not be surprising if more Tesla owners across the country receive the update as well. 

Based on the release notes of the update, key improvements in FSD V14.2 include a revamped neural network for better detection of emergency vehicles, obstacles, and human gestures, as well as options to select arrival spots. 

It would likely only be a matter of time before FSD V14.2 videos are posted and shared on social media.

Following are the release notes of FSD (Supervised) V14.2, as shared on X by longtime FSD tester Whole Mars Catalog.

Advertisement
-->

Release Notes

2025.38.9.5

Currently Installed

FSD (Supervised) v14.2

Full Self-Driving (Supervised) v14.2 includes:

  • Upgraded the neural network vision encoder, leveraging higher resolution features to further improve scenarios like handling emergency vehicles, obstacles on the road, and human gestures.
  • Added Arrival Options for you to select where FSD should park: in a Parking Lot, on the Street, in a Driveway, in a Parking Garage, or at the Curbside.
  • Added handling to pull over or yield for emergency vehicles (e.g. police cars, fire trucks, ambulances.
  • Added navigation and routing into the vision-based neural network for real-time handling of blocked roads and detours.
  • Added additional Speed Profile to further customize driving style preference.
  • Improved handling for static and dynamic gates.
  • Improved offsetting for road debris (e.g. tires, tree branches, boxes).
  • Improve handling of several scenarios including: unprotected turns, lane changes, vehicle cut-ins, and school busses.
  • Improved FSD’s ability to manage system faults and improve scenarios like handling emergency vehicles, obstacles on the road, and human gestures.
  • Added Arrival Options for you to select where FSD should park: in a Parking Lot, on the Street, in a Driveway, in a Parking Garage, or at the Curbside.
  • Added handling to pull over or yield for emergency vehicles (e.g. police cars, fire trucks, ambulances).
  • Added navigation and routing into the vision-based neural network for real-time handling of blocked roads and detours.
  • Added additional Speed Profile to further customize driving style preference.
  • Improved handling for static and dynamic gates.
  • Improved offsetting for road debris (e.g. tires, tree branches, boxes).
  • Improve handling of several scenarios, including unprotected turns, lane changes, vehicle cut-ins, and school buses.
  • Improved FSD’s ability to manage system faults and recover smoothly from degraded operation for enhanced reliability.
  • Added alerting for residue build-up on interior windshield that may impact front camera visibility. If affected, visit Service for cleaning!

Upcoming Improvements:

  • Overall smoothness and sentience
  • Parking spot selection and parking quality
Continue Reading