News
SpaceX schedules second Starship static fire after first test ends prematurely
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.
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.
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 new Automatic Collision Evasion feature worked flawlessly! FSD reengaged itself just as I was about to hit a curb.
Kudos @Tesla_AI team! 👏 pic.twitter.com/Fbp15HhpL2
— Spencer (@scotsrule08) September 28, 2026
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.
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.”
Roadster event update
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…
— Tesla (@Tesla) September 28, 2026
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.
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.
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.
Splashdown confirmed. Congratulations to the entire SpaceX team on the first orbital flight of Starship! pic.twitter.com/urjmiwnvNl
— SpaceX (@SpaceX) September 28, 2026
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.
Starship’s 14th flight is set to launch on Monday, Sept 28. The 75-minute launch window opens at 7:15 a.m. CT. Live coverage of the mission starts ~35 minutes before launch → https://t.co/uQKQvgaTmJ
— SpaceX (@SpaceX) September 27, 2026
Watch Tesla’s “guardian angel” FSD feature take over for collision evasion
Tesla Roadster event gets delayed due to unfavorable weather
