News
[Update: Scrubbed] SpaceX Starship to attempt same-day static fire and launch
Update: Starship SN11 did manage a timely static fire around 8am CDT but after hours of work, SpaceX appears to have scrubbed a Friday, March 26th launch attempt.
SpaceX’s website has yet to be updated and Friday’s FAA TFR is still active but a road closure meant to last until 7:30 pm CDT to cover the static fire and launch was retracted after the highway was reopened around 2:45 pm. It’s unclear what caused the scrub but weather or technical issues from the static fire are two likely candidates. SpaceX still has TFRs active on Saturday and Sunday, but the company hasn’t tested or flown on a weekend in months.
Lacking only an official confirmation, SpaceX appears to be readying the fourth full-size Starship prototype to attempt a Raptor static fire test and launch on the same day.
That hopeful day in question happens to be today – Friday, March 26th. If all goes according to plan, Starship serial number SN11 will fire up its three Raptors, verifying their health after an engine was apparently swapped out on Wednesday. Possibly just an hour or two later, after detanking and retanking liquid oxygen and methane propellant, the Starship prototype could lift off on SpaceX’s fourth high-altitude test flight.
Late on March 24th, SpaceX rolled Raptor engine SN46 from its Boca Chica factory to the launch pad, where Starship SN11 is installed on one of two suborbital launch mounts. The engine move and subsequent installation came as a surprise, as nobody managed to catch an implied Starship SN11 engine removal in the two or three days prior (extremely thick fog being the likeliest cause).
The implied issue with the Raptor that was removed is likely to blame for a several-day launch delay that followed Starship’s seemingly successful Monday static fire. After that test, SN11’s launch was initially scheduled as early as Tuesday or Wednesday, only to slip day by day as the week proceeded. SN11 first rolled to the launch pad on March 8th, just 18 days ago, so launch delays don’t come as a huge surprise given that the current factory-to-launch record for a three-engine Starship is 33 days, three static fires, and one engine swap.
If SN11 manages a same-day static fire and launch on March 26th, it will still crush that record by almost 50%. To an extent, the feat also isn’t unprecedented. On March 3rd, Starship SN10 aborted its first true launch attempt milliseconds after Raptor ignition when the rocket’s flight computer detected indications that they were producing too much thrust. Amazingly, instead of scrubbing the launch attempt, SpaceX loosened Starship SN10’s thrust limit parameters and tried again, successfully lifting off just three hours after the abort.
Despite the abort and immediate hands-free recycle, Starship SN10 subsequently became the first prototype of its kind to launch to 10 km (6.2 mi), free-fall back to earth, and land in one piece. Minutes later, a fire and harder landing than expected conspired to make SN10 explode, but the test flight was arguably still a massive success. Simultaneously, the flight indicated that Starships are technically capable of successfully flying hours after a post-ignition launch abort, demonstrating an extraordinary level of robustness for clustered high-performance rocket engines.
As such, while it’s probably reasonable to assume that Starship SN11 wont launch today, SN10 proved that there is nonzero chance of a static fire and launch hours apart. Additionally, given just how close SN10 go to unequivocal success (i.e. a soft and survivable landing), Starship SN11 has the best chance yet at at launching, landing, and making it through the ordeal without exploding.
Starship SN11’s third static fire and first launch attempt are both currently scheduled sometime between 7am and 7:30pm CDT (UTC-5). Stay tuned for updates as we wait for SpaceX’s official confirmation and an evacuation notice of Boca Chica Village residents.
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
