Connect with us

News

High winds scrub SpaceX Starship SN9’s Monday launch attempt

Published

on

Update (2:30 pm CST): SpaceX appears to have called off Monday’s Starship SN9 launch attempt due (primarily) to high winds along the flight corridor. Additional opportunities are available from 8 am to 6 pm CST (UTC-6) on Tuesday (Jan 26) and Wednesday (Jan 27).

Technically, lacking any official confirmation, there’s still a chance of a launch attempt or additional ground testing happening today but either possibility is extremely unlikely at this point.

Update: SpaceX has completed what is known as a Flight Readiness Review (FRR) and determined that Starship prototype SN9 is ready to attempt its first high-altitude launch as early as today.

All necessary aviation and maritime notices and restrictions are in place and the company has begun the process of closing a public highway and clearing the launch site of employees. Today’s (Jan 25) launch window lasts from noon to 6 pm CST (UTC-6) and Starship SN9 could likely be made ready to launch anytime after 2pm be ready to fly as early as 4 pm CST according to a loudspeaker announcement at the launch pad. Stay tuned for updates and, hopefully, an official SpaceX webcast.

All signs point to SpaceX’s second high-altitude Starship prototype preparing for a 12.5-kilometer (~40,000 ft) as early as Monday, January 25th in a bid to rectify a last-second bug that caused its predecessor to explode last month.

Known as Starship serial number 8 (SN8), the SpaceX-built prototype was the first to have its basic airframe (tank and nose sections) fully integrated, as well as the first Starship to attempt to break the 150m (~500 ft) ceiling set by Starhopper, SN5, and SN6. Break the ceiling SN8 most certainly did, performing a spectacularly successful 12.5 km launch that aced almost every single goal SpaceX had hoped to complete. Keyword almost.

Advertisement
-

After an impressive 280 seconds of uninterrupted operation of its Raptors, Starship SN8 shut down the last of those three engines, flipped onto its belly, and successful freefell ~12 kilometers back to Earth. The rocket then carried that success even further, reigniting two Raptors, performing a dramatic 120-degree flip, orienting itself vertically, and beginning to slow down for a soft landing.

Only then did Starship SN8’s performance deviate from virtual perfection. At T+6:38, a few seconds after beginning its crucial landing burn, one of Starship’s active Raptors shut down and the other effectively stopped generating thrust. The reason, CEO Elon Musk would later explain, was low head pressure in a smaller tank (‘header tank’) dedicated to supplying fuel during Starship’s wild flip and landing maneuver. It was never confirmed if the Raptor engine shutdown observed milliseconds prior to the other engine losing thrust was intentional.

Cause aside, the end result was unsurprising: without enough thrust to slow down, Starship SN8 accurately impacted the concrete landing zone but did so at high speed – likely around 50-60 m/s (100-150 mph). Given that Starhopper and Starships SN5 and SN6 had already successfully proven Starship’s ability to gently land from 150 meters on a single Raptor engine and that, prior to SN8, Starship’s bizarre belly-flop descent and 90-degree flip had been almost entirely theoretical, SpaceX deemed the launch a spectacular success.

Nothing better exemplifies that than the fact that a little over a month later, SpaceX quite literally began scrapping the most complex, completed section of a future Starship prototype (SN12) before it ever reached the assembly phase. Instead, SpaceX appears to be more focused than ever on a mysterious series of “major” upgrades Musk has said will debut on Starship SN15. Nearly all SN15 subsections have been completed and are simply waiting to be joined together, while parts of SN16 and SN17 are also starting to pile up in staging areas.

Starship SN10 is practically ready to move to the launch pad to prepare for flight as soon as SpaceX chooses to do so and Starship SN11 is likely no more than a week or two of work away from reaching same level of readiness.

Ultimately, despite a long and delay-ridden test campaign, Starship SN9 finally completed what looked like a full-duration static fire of all three of its Raptor engines – the rocket’s sixth static fire overall. On Saturday, January 23rd, SpaceXers installed SN9’s flight termination system (FTS) – a system of explosives designed to destroy Starship if it flies too far off course. For Starship, FTS installation all but guarantees that a launch attempt is a matter of days away. Fresh county roadblocks, Temporary Flight Restrictions (TFRs) granted by the FAA, and Coast Guard a safety notice further imply that SN9 will attempt to launch as early as Monday morning, January 25th, with backup opportunities on Tuesday and Wednesday.

Advertisement
-

With any luck, like SN8’s high-altitude debut, SpaceX hopefully livestream Starship SN9’s own attempt at the same feat. Stay tuned for more details as they come.

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

Lifestyle

Watch Tesla’s “guardian angel” FSD feature take over for collision evasion

Published

on

By

Tesla’s Automatic Collision Evasion feature can be seen in one of the first owner videos of it in action.

Tesla owner Spencer (@scotsrule08) posted on Monday that the feature “worked flawlessly,” saying FSD reengaged itself just as he was about to hit a curb. Ashok Elluswamy, who leads Tesla’s AI team, shared the clip and wrote, “A guardian angel always looking out for you.”

The video arrives in the middle of a staged rollout. Tesla first shipped Automatic Collision Evasion with FSD (Supervised) v14.3.9 in software update 2026.27.6 earlier this month, which Teslarati covered as it reached cars. Update 2026.27.10, which began going out on September 19, carried the feature improvements with FSD v14.3.10, according to release notes tracked by Not a Tesla App. The newer 2026.27.11 build is now reaching another wave of vehicles.


The feature only runs on HW4 vehicles, and it requires an active FSD purchase or subscription with both FSD (Supervised) and Automatic Emergency Braking enabled. HW3 owners receive FSD v14.2 Lite in the same updates, but that build does not include collision evasion.

Tesla’s release notes describe two triggers. The first is an imminent frontal collision that braking alone may not prevent, in which case the car can activate FSD to steer, brake or accelerate around the hazard. That scenario is limited to highways below 85 mph, with no pedestrians or cyclists detected and no slippery road surface. The second covers a driver who appears inattentive, such as reaching into the back seat, or who seems to have switched off FSD by accident. Spencer’s curb clip appears to fall into that second category.

Tesla plans big safety improvements for Full Self-Driving v15

Once the system takes over, the accelerator is muted and light brake input will not cancel the maneuver. Drivers need to apply firm, deliberate steering force to take back control, and the car chimes to hand control back once the danger has passed.

Elluswamy recently noted that earlier hazard prediction, faster reaction time and better collision avoidance would arrive with FSD v15, the next major version.

Continue Reading

News

Tesla Roadster event gets delayed due to unfavorable weather

Published

on

Credit: Tesla

Tesla is delaying its event for the Roadster, moving it from this Thursday, October 1, to Thursday, October 15, due to unfavorable weather.

The company has said it has been tracking the weather for this Thursday closely with local meteorologists, and because the event can only be held outside, Tesla is making the call to delay it:

“We’ve been tracking the weather closely with local meteorologists, but given the severe conditions predicted & because this event can only be held outdoors, we’ve made the difficult decision to reschedule. New date is October 15. Additional details to follow.”

We are sure that this is bringing back PTSD for some Tesla fans, and we know it is not ideal, but this also reveals some things about the event. Tesla said that this can only be held outdoors, meaning it bodes well for the rumors that the vehicle could potentially hover.

Some believe that this was essentially confirmed by the FAA airspace restriction they were granted, but this could have been for a drone show or to keep drones from spying on the event.

Tesla Roadster is available for order once again following brief hold

The Roadster event has been long-awaited, and it is unfortunate that the weather is going to keep us all waiting a little bit longer.

The Tesla Roadster will be unveiled in Waco, Texas.

Continue Reading

Elon Musk

SpaceX turned a heralding moment for Starship into its greatest

Starship reached orbit despite losing an engine, deployed 26 Starlink V3 satellites on Flight 14.

Published

on

By

SpaceX’s Starship reached orbit for the first time on Monday, and for a few nail-biting minutes it looked like it wouldn’t. During ascent on Flight 14, one of Ship 41’s six Raptor engines shut down early, and SpaceX’s livestream host Dan Huot told viewers the team had decided not to commit to orbit. Minutes later, after what Huot described as a lot of conversation in the control room, the final poll came back in favor, and a roughly 19 second burn of a single Raptor pushed the ship into orbit about 170 miles up.

The reversal matters because SpaceX had written the exit ramp into the mission plan. The company said it would only fire the orbital insertion burn if flight controllers confirmed enough backup hardware remained for the deorbit burn, a condition Teslarati laid out ahead of the flight. Losing an engine was exactly the scenario that rule was built for.

Pressing forward fits Elon Musk’s history. Falcon 1 failed three straight times before its fourth launch reached orbit in 2008, with SpaceX nearly out of money, and Starship was developed by flying prototypes until they broke. What changed this year SpaceX going public, and with $SPCX sliding below its IPO price in July when Flight 13 slipped, the short interest climbed significantly, as Teslarati reported at the time. A Starship potentially lost today with revenue generating next-gen Starlink satellites aboard would have landed directly on shareholders.

That pressure showed up after orbit. SpaceX cut a flight planned to last nearly 10 hours to about three, moving splashdown from west of Chile to the North Pacific near Hawaii. SpaceX gave no reason, though Musk said this month the company was being extremely cautious about debris risk. The single Raptor for deorbit worked, and Ship 41 completed its flip and landing burn before breaking apart in the water, an outcome SpaceX expected. Musk has structured SpaceX’s governance to shield long term bets from market pressure.

The payload is the bigger business story. Musk posted that all 26 Starlink V3 satellites deployed and are “operating nominally.” Each V3 is rated for about 1 Tbps of downlink and 160 Gbps of uplink, so this single launch adds roughly 26 Tbps, about 10 times what a Falcon 9 load of V2 Mini satellites adds. The V3 is too large for Falcon 9, making Starship the only vehicle that can build out the planned 100,000 satellite constellation, at up to 60 per flight once it reaches routine service. Unlike the 20 V3 units on Flight 13, which reentered on a suborbital path, these will raise their orbits and could begin serving customers within weeks and bring in hundreds of millions of additional dollars in projected Starlink revenue.

SpaceX has already begun winding down Falcon 9 Starlink launches from Florida in favor of Starship. Reported targets put Flight 15 as early as October 19, leaving about three weeks to diagnose Monday’s engine shutdown before the next orbital attempt.

Continue Reading